Services
Nine services. One person accountable for all of them.
End-to-end engineering across web, mobile, browser extensions, backends, APIs and platform work. Every engagement is scoped on a call before it is quoted — and if I am not the right person for it, you hear that on the call rather than in an invoice.
At a glance
- Based in
- Lahore, Pakistan — UTC+5
- Working with
- Clients worldwide, async by default
- Experience
- 8+ years, 23 projects delivered
- Engagements
- Fixed price, milestone, retainer or fractional
- Reply time
- Within one business day
9 services9 categoriesTypical reply within one business day
Everything I take on
9 services in 9 categories. Each one links to what it includes, what it is built with, and what it deliberately leaves out.
Money, before you ask
There is no price on these cards, and that is deliberate
A number printed before I know the scope is a guess, and a guess that turns out low is worse for you than no number at all. Each card carries a price slot that fills in the moment a service has a rate I can stand behind; until then it says so plainly.
The one figure that is safe to publish: $800 USD is the floor for a small, well-defined feature. Everything above that comes from a scoping call, in writing, before any work starts.
Four ways to structure it
- Fixed price
- Where the scope is tight enough to hold one. You know the number before I start.
- Milestone
- Split across demos you sign off individually. You can stop after any one of them.
- Retainer
- A set number of days a month for ongoing work. Cancellable, not auto-renewing.
- Fractional
- Part-time inside your team, on your tools, in your standups.
Included whichever service you pick
- The repository, and its full history
- The deployment, and the pipeline that redeploys it
- A README a second developer can start from
- Thirty days of bug fixes at no charge
Why teams hire me
Four things I am explicit about up front
- 01
Starts are fast and dated
Most engagements begin within 48 hours of an agreed scope. You get a timeline, a milestone plan, and a fixed price wherever the scope allows one.
- 02
Scoping that is allowed to say no
I tell you what the work does not include as plainly as what it does. If a request is wrong for your stage or your budget, you hear that instead of a quote — and usually a cheaper alternative with it.
- 03
A hand-over someone else can use
Typed code, a structure a second developer can navigate, and a README covering environment variables, deploy steps, and the two things I would improve next. The repository and the store listings are yours; where it is deployed and what it depends on is named in the handover.
- 04
Thirty days of fixes, then your call
Bug fixes are covered for thirty days at no charge. After that nothing renews on its own: maintenance and new work continue on a retainer only if you ask for one.
Asked before every project
Including the answers that lose work. Those are the ones worth reading first.
What does a project cost?
The number comes from scope, integrations and timeline — and you get it in writing after the scoping call, never before it. I do not quote from a brief alone, because the quotes that come from briefs alone are the ones that get revised upward later.
What is not included, whichever service I pick?
Visual design as a standalone deliverable. Native iOS — I have no Apple Developer account, so I will not claim a platform I cannot ship to. Blockchain work. Copywriting and content. Third-party subscriptions and domain costs are yours, and any architecture that needs a paid service in the critical path gets flagged before it is built, not after.
How long does it take?
Small features 1–2 weeks, an MVP 4–8 weeks, a full production app 8–16 weeks. Those are ranges I have hit on work of that shape before. Something I have genuinely not built before gets a range and a spike, not a confident date.
Do you sign an NDA and transfer IP?
Yes. The NDA is signed before any sensitive detail is shared, and full IP ownership of delivered code transfers to you on final payment. The contract covers confidentiality, deliverables, payment terms and post-launch support.
Can you take over an existing codebase?
Yes, and it starts with an audit rather than a feature. You get a written read on code quality, security and performance, and a prioritised list — which includes the parts I would leave alone. A rewrite is a recommendation I have to earn, not a default.
What happens after launch?
Thirty days of bug fixes at no charge. After that nothing is automatic: maintenance, new features and on-call are a retainer you opt into, and you can end it. I would rather you leave because you no longer need me than stay because cancelling was awkward.
Do you work in my time zone?
I work Pakistan Standard Time, UTC+5, and routinely take meetings across US, UK, EU and Australian hours. Async is the default — written updates and recorded demos — so a call is something we schedule, not something the project depends on.
Need something custom?
If none of the 9 matches what you have, describe the problem in plain English. You get a yes or a no, a rough number, and the next concrete step — usually within a business day. A no comes with a suggestion for who or what would suit the job better.