Custom software studio· Karachi, Pakistan
Software your business actually runs on.
Client portals, booking systems, internal tools and dashboards. Built for teams that have outgrown spreadsheets and off-the-shelf software. Fixed scope, fixed price, fixed date.
No pitch deck. On the call we’ll tell you whether the thing is worth building, including when it isn’t.
| 1 | Client | Date | Status | Paid |
| 2 | Nadeem Traders | 14/10 | confirmed | y |
| 3 | A. Khan | 14-10-26 | CONFIRMED | yes |
| 4 | Bilal & Co | 14/10 | ?? | |
| 5 | Nadeem Traders | 14/10 | confirmed | y |
| 6 | S. Rehman | 15/10 | pending | #REF! |
Bookings
Tue 14 October
- Nadeem Traders09:00Confirmed
- A. Khan11:00Confirmed
- Bilal & Co13:00Pending
- 14:00 unavailable, held by booking #204
Last change · Ayesha · 2 min ago
- Scope
- In writing, before anything starts
- Quote
- Within three working days
- First build
- A working URL in week one
Figure 01 · Where the truth lives now
Whether this is worth your twenty minutes.
We build one kind of thing, for one kind of problem. Here’s how to tell quickly if that’s yours.
This is probably you if
- A core part of your business runs in a spreadsheet that three people are afraid to touch.
- You pay for software that does 20% of what you need, and none of it the way you actually work.
- You asked for a quote for a “website” when what you need is a system: logins, records, approvals, reports.
- A developer took your deposit and went quiet.
And we’re the wrong call if
- You need a brochure site. We’d be an expensive way to get one, and we’ll tell you where to go instead.
- You want a developer to join your team by the hour.
- You’re collecting quotes to find the cheapest one.
Systems, not pages.
- 01
Client & customer portals
Logins, role-based permissions, documents, statuses, and the record of who changed what and when.
- 02
Booking, scheduling & inventory
Availability that can’t double-book, pricing calculated on the server, approvals routed to the right people, confirmations sent automatically.
- 03
Internal tools & admin dashboards
The thing your team currently does across four spreadsheets and a WhatsApp group, in one place with one source of truth.
- 04
Integrations & automation
Payments, email and SMS, accounting, and the systems you already have, wired together so nobody re-types anything.
Where AI genuinely helps inside one of these, we’ll build it in. We don’t sell “AI” as a thing by itself.
Figure 02 · Who is allowed to do what
“Role-based permissions” is the phrase everyone uses. This is the grid it turns into, and the one you sign off before we build it.
| Can they… | Customer | Staff | Manager | Accounts |
|---|---|---|---|---|
| See today’s bookings | Own only | Allowed | Allowed | Not allowed |
| Create a booking | Allowed | Allowed | Allowed | Not allowed |
| Cancel after payment | Not allowed | Not allowed | Allowed | Not allowed |
| Issue a refund | Not allowed | Not allowed | Allowed | Allowed |
| Change prices | Not allowed | Not allowed | Allowed | Not allowed |
| Export the ledger | Not allowed | Not allowed | Allowed | Allowed |
How we work
Four steps, and you can leave after the first two.
The real question isn’t whether we’re any good. It’s what happens if we disappear. So the answer is structural: a written scope and a fixed quote before any money changes hands, then half to start and half on delivery.
20 minutes
A call, 20 minutes
We work out what you actually need. If it isn’t worth building, we’ll say so and you’ve lost twenty minutes.
Three working days
A written scope and a fixed quote
Every screen, every rule, what’s included and what’s explicitly not. One price. One date.
Up to here, you have paid nothing
The bulk of it
Weekly builds
A working URL in the first week and an updated one every week after. Nothing is a surprise at the end, because there is no end you haven’t already seen.
30 days
Launch, then 30 days of fixes
Anything broken in the first 30 days after launch, we fix free. After that, a support plan if you want one, and no obligation if you don’t.
Fixed fee, agreed before anything starts.
We don’t bill by the hour. You shouldn’t pay more because something took us longer than we thought.
A single system
fromPKR90,000
3 to 5 weeks
One workflow, one or two kinds of user, launched in weeks rather than months.
- Written scope before anything starts
- One or two user roles
- Email notifications
- Hosted on our infrastructure while we build
A full application
fromPKR250,000
8 to 14 weeks
Several roles, integrations with systems you already run, and your existing data moved in.
- Everything in a single system
- Three or more user roles with real permissions
- Payment, accounting, email or SMS integrations
- Migration of your existing data
Ongoing
PKR40,000per month
Rolling, cancel any time
Changes, support and small additions after launch. Month to month, no lock-in.
- An agreed number of change hours each month
- Bug fixes at no charge
- Dependency and security updates
- Uptime monitoring
Half the fee when you agree the scope, half when the system is delivered. The call and the written scope cost nothing.
Prices are for clients billing in Pakistan. Work for clients elsewhere is quoted separately.
Figure 03 · What moves the number
Four things, mostly.
If you can answer these before the call, the quote gets sharper and faster.
Dots mark where a typical project lands
Kinds of user
Systems to talk to
Existing data to move
Still undecided at kickoff
Small and new. Here’s both sides of that.
DawoodFounder, and the person writing the code
You deal directly with the person writing the code. There’s no account manager, no handover to a junior after you sign, and few enough projects at a time that yours isn’t queued behind ten others.
What we can’t show you is a decade of logos. What we can give you is a fixed price, a working build every week, and a written scope you can read in full before you pay anything.
The things people ask before they say yes.
How long does a project take?
A single system is usually three to five weeks from the day scope is signed. A full application with several roles and integrations runs eight to fourteen.
You'll have a working URL in the first week either way, so you're never waiting until the end to find out what you bought.
What if I don't know exactly what I need yet?
That's the normal case, and it's what the first call is for. Most people arrive with a problem, not a specification.
You don't need a document. Bring how the work happens now: the spreadsheet, the WhatsApp group, the thing that keeps going wrong. We'll turn it into a scope you can read and check.
Who owns the code when it's done?
You do, once the final invoice is paid. The code is then transferred to you along with everything needed to run it.
During the build it lives in our repositories and runs on our servers, which is what lets you have a working URL in week one without setting up any infrastructure of your own.
What happens if I need changes after launch?
Anything broken in the first 30 days is fixed free. That's a bug, not a change.
New work after that is either a monthly plan with an agreed number of change hours, or a fixed quote per change if you'd rather not commit to anything. Plenty of clients need neither for months, and there's no obligation to take one.
Do you work with clients outside Pakistan?
Yes. Most of the work is remote either way, and calls are scheduled around your hours rather than ours.
The prices published on this site are for clients billing in Pakistan. Work for clients elsewhere is quoted separately, and you'll have that number in writing before anything starts.
Why fixed price instead of hourly?
Because hourly bills you for our learning curve. If something takes longer than expected, that's our estimate that was wrong, and you shouldn't pay for it.
Fixed price also forces a real scope up front, which is where most software projects actually go wrong. The number can only change if you change what you asked for, and then it changes in writing, before the work starts.
What do you not do?
Brochure sites, logos and brand work, ad campaigns, SEO retainers, and staffing. We don't put a developer on your team by the hour.
We also won't take a project we don't think is worth building. If a tool you can buy for a few dollars a month does the job, we'll name it on the call.
Next step
Tell us what you’re trying to build.
Twenty minutes, no obligation, no deck. Bring the messy version of the problem. That’s the useful one.
We reply within one business day.
Loading calendar…