Add-ons attach to an existing engagement or run standalone — either way, one fixed price before anything starts.
How an engagement runs
01Scope
A 30-minute call, then a written brief covering the problem, constraints, and what has to be true when it ships.
02Proposal
A fixed price against that brief, with milestones, dates, and what is explicitly out of scope.
03Build
Weekly demo of working software on a staging URL. A shared board you can read at any time.
04Launch
Deployment, monitoring, and a handover pack: architecture, environment, and how to run it without me.
05Support
Thirty days of warranty on delivered work, then an optional retainer if the system keeps growing.
What you are protected by
The terms, before you have to ask.
01
Fixed price, written first
You approve a brief and a number before any work starts. No hourly meter, no invoice that arrives larger than the conversation.
02
Paid by milestone
Work is split into stages you can see. You never pay for the next one until the last one is in your hands.
03
Revisions are built in
Two rounds per milestone are part of the price, not an upsell. Changing your mind about a detail is normal.
04
Thirty-day warranty
If something I delivered breaks in the month after launch, I fix it. Not a support ticket, not a new quote.
05
You own everything
Source code, repositories, domains, and every third-party account are in your name from day one. Nothing is held hostage.
06
Replies within a business day
Silence is the most common complaint about freelancers. You will always know where your project stands.
Questions worth answering up front
How is pricing worked out?+
Every engagement gets one fixed price against a written brief before any work starts — never an hourly meter. The offers above are starting points; the real number comes from a short scoping conversation about what the system actually needs to do.
How long does a project take?+
It depends on the engagement — an MVP typically runs 3–5 weeks, a full SaaS platform 6–12 weeks. You get exact dates in the proposal, before you commit to anything.
How many revisions are included?+
Two rounds per milestone are built into the price, not billed as an upsell. Changing your mind about a detail partway through is normal, not a change order.
Who owns the code and the accounts when it's done?+
You do — source code, repositories, domains, and every third-party account are registered in your name from day one. Nothing is held back or licensed out to you.
What happens after launch?+
Thirty days of warranty on everything delivered — if something I built breaks, I fix it, no new quote. After that, an optional monthly retainer covers performance work, monitoring, and ongoing changes for a system that keeps growing.
How do we communicate during the build?+
A weekly demo of working software on a staging URL, plus a shared board you can check any time. Messages get a reply within one business day — usually sooner.
What do you need from me to get started?+
A clear description of the problem, access to any existing systems or accounts involved, and one person who can approve the brief and sign off each milestone. Everything else gets figured out on the scoping call.
Do you work with clients outside Pakistan?+
Based in Islamabad, Pakistan — working across US, UK, and EU hours. All prices are in USD. Calls are scheduled to overlap your working hours, and most of the day-to-day happens async over the shared board and email so the time difference is rarely a bottleneck.