FAQ
Common questions
Pre-empts the questions that come up in nearly every inbound. If anything's missing, ask on the contact page.
Engagement
What kind of work are you taking on?
Multi-tenant SaaS builds, AI platforms, fintech and payments, and APIs at scale. I take on greenfield builds, scoped feature additions, rescue work, and architecture reviews. I do not take on pure design work or pure WordPress theming.
Hourly, fixed price, or retainer?
All three. Hourly for ambiguous scope or research work. Fixed price for milestones with a clear deliverable. Retainer for ongoing partnerships of 3+ months. I can also work fixed-price for a discovery phase, then move to hourly or retainer for the build.
What is your typical engagement size?
Most engagements run 4 to 12 weeks. Smaller scopes are fine if the deliverable is clear. Multi-month retainers are open for the right product fit.
Solo or as part of a team?
Both. I work solo end to end on small to medium projects. I also pair into existing teams as a senior architect, a tech lead, or a code reviewer.
Working style
Where are you based and what is your time zone?
Pakistan (PKT, UTC+5). I overlap several hours daily with UK, Europe, and the East Coast US. West Coast US overlap is morning-only on my side.
How do you communicate during a project?
Async by default with daily updates in writing. Live calls for kickoff, milestone demos, and unblocking. Slack, Linear, GitHub, and email all work for me.
How often do I see progress?
Demos at the end of every shipped milestone. For longer projects, weekly Loom or written updates between demos. Code is pushed to GitHub continuously, never batched into one big drop at the end.
Do you work on weekends?
Sometimes, by choice. I do not commit to weekend availability and I do not bill weekends as overtime. If a launch needs weekend coverage, we plan it.
Process
What does a typical kickoff look like?
60 to 90 minutes. We walk through the problem you are solving, who the user is, success criteria, and the constraints (timeline, budget, integrations, team). I leave with enough to write a tight scope doc within 48 hours.
How do you handle scope creep?
New scope is welcome but it lands in a parking lot, not the current sprint. We review the parking lot at each milestone and decide together what is in scope, what is a phase 2, and what is out.
What does delivery look like?
Code in your repo, deployed to your infrastructure (or to a target you control), with a written handoff doc covering architecture, deploy, and operations. No vendor lock-in to my tooling.
Legal and IP
Who owns the code?
You do, on payment. I assign rights on the contract. I do reserve the right to discuss generic patterns publicly (blog posts about Stripe Cashier integration, for example), but never client specifics.
Will you sign an NDA?
Yes. I will sign a mutual NDA before any non-public scoping discussion. I prefer mutual NDAs and I will push back on overly broad confidentiality clauses that try to restrict my generic skills or future work.
Can I keep my project private?
Yes. Anything we agree is private stays private — no case study, no GitHub showcase, no LinkedIn mention. The default for non-named work is private; I ask before featuring anything publicly.
Pricing
What does this cost?
Depends on scope, depth, and whether the engagement is hourly, fixed price, or retainer. After a 60-minute scoping call I can quote with a 1 to 2 day turnaround.
Do you offer discounts or trial periods?
No discounts. For new engagements I am open to scoping a small first milestone (a week or two) to de-risk the working relationship before committing to the full project.
Still have a question?
Drop me a message on the contact page and I'll get back within 24 hours.