Services — Ahsan Mahmood. Nine ways to hire one developer.
Nine engineering services across web apps, Android, browser extensions, backends, APIs, security, AI, e-commerce and architecture. Scoped on a call first. Typical reply within one business day.
The deployment, and the pipeline that redeploys it
- Thirty days of bug fixes at no charge
Included whichever service you pick
- A README a second developer can start from
- The repository, and its full history
Where the scope is tight enough to hold one. You know the number before I start.
Part-time inside your team, on your tools, in your standups.
Four ways to structure it
Split across demos you sign off individually. You can stop after any one of them.
A set number of days a month for ongoing work. Cancellable, not auto-renewing.
- Retainer
- Featured
- Price
- Quoted after a scoping call
- View details
Everything I take on
- Loading services
- Backend
- Cloud
- Commerce
- Advisory
- Data
- DevOps
- Extension
- Mobile
- Other
- Security
- Design
- Web
- Describe your project
Need something custom?
About this service
Scope is agreed on a call before anything is quoted, and what the work does not include is written down at the same time as what it does. If this is the wrong service for your problem, that is a sentence you get on the call rather than a discovery in week three.
- Or something adjacent
- All services
- Built with
- Compare the nine
Tell me what you are building and roughly when you need it. The first call is thirty minutes, costs nothing, and ends with either a scope or an honest reason not to proceed.
Ready to start?
How long it takes
- Get a quote
- What’s included
Every engagement of this shape covers
Five deliverables, every time this service is bought. Anything outside this list is quoted separately rather than assumed.
What is included
Visual design as a standalone deliverable, native iOS — there is no Apple Developer account, so that platform is not offered — and the third-party subscriptions the finished product needs to run.
- The full list is on the services FAQ
Not included, here or in any of the nine
Frequently bought alongside this one, or a better fit if this is not quite it.
Related services
- — services — Ahsan Mahmood
- After launch
- Thirty days of fixes included
- Category
- Engagement
Fixed price, milestone, retainer or fractional
- How this one runs
- Reply time
- Within one business day
- Starts with
- A free 30-minute scoping call
- How this one goes
What the work actually looks like
The default set for this service. A project with a good reason to differ gets that reason written down before we start.
Technologies and tools
Four commitments that hold for this service the same way they hold for the other eight.
Empty, loading, offline and error states are built with the feature rather than after it, because those are what a real user meets on a first run or a bad connection.
The failure paths are designed, not discovered
Repository, store listings and documentation are yours. Nothing needed to run or rebuild the product stays on my machine, and nothing is licensed back to you.
Handed over completely
Why choose this
Typed end to end, structured so a second developer can find things, and commented where the reasoning is not obvious from the code. You are not buying a codebase only I can read.
Built the way it will be maintained
A working demo against the milestone, not a status update. If something slipped you hear it that week, while there is still time to change what we do about it.
You see it running every week
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.
- What happens after launch?
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 does a project cost?
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.
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.
What is not included, whichever service I pick?
Asked before every project
Including the answers that lose work. Those are the ones worth reading first.
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.
- Do you sign an NDA and transfer IP?
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.
- Can you take over an existing codebase?
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.
- Do you work in my time zone?
- Based in
- Lahore, Pakistan — UTC+5
- Engagements
- Experience
- 8+ years
At a glance
- Working with
- Clients worldwide, async by default
- 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.
- Start a conversation
- Money, before you ask
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.
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.
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.
Starts are fast and dated
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.
Thirty days of fixes, then your call
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.
A hand-over someone else can use
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.
Scoping that is allowed to say no
- Service catalogue summary
- Typical reply within one business day
- Why teams hire me
Four things I am explicit about up front
Services
https://aoneahsan.com/services