ABOUT MAZHAR SIDDIQI
I'm the developer other people's clients never meet.
And that's the point.
WHAT I ACTUALLY DO
A developer inside your business, for as long as you need one.
I am a software developer who works inside other people's businesses. Agencies bring me in when a project exceeds their capacity. Founders bring me in when they need a product built before they can justify a hire. Consultants bring me in when a client asks for something technical.
I work in their repo, follow their process, and deliver under their brand. When the project ships, I step away.
It is an unusual way to run a development business, and it is deliberate. Most clients do not need a developer permanently. They need one occasionally, with enough experience to work independently.
“Most teams do not need a developer permanently. They need one occasionally, with enough experience to work independently.”
The operating principle
HOW I WORK
The standards I bring into your team.
The quality of an engagement is not only what ships. It is how easily your team can follow the work, question a decision, and continue building when I step away.
I adopt your process
Your branching strategy, ticket format, and review standards. Consistency in a codebase matters more than my preferences.
I raise problems early
If a scope has a flaw in it, you hear about it in week one rather than the week before launch.
I write for whoever comes next
No clever solutions that require me to explain them. If your team cannot pick up my work without a phone call, I have done it badly.
I tell you when the answer isn't me
If your project needs a technology I do not work in, or does not need custom development at all, I will say so.
THE STACK
What I build with.
Platform work and the technical side of SEO sit alongside the core development stack when a project needs them.
React
Next.js
TypeScriptReact Native
Node.js
NestJS
Express
PostgreSQL
MongoDB
WordPress
Shopify
Webflow
FramerI have kept this list narrow on purpose. Depth in one ecosystem is more useful to you than a list of twenty technologies I have touched once.
WHY THIS MODEL
Why I work this way.
I have watched agencies hire developers they could not keep busy, and watched them turn down good projects because their one developer was already committed. Both are expensive, and both come from the same mismatch: development demand is intermittent, and salaries are not.
Working per project fixes the mismatch. You get senior capacity in the weeks you need it and pay nothing in the weeks you do not. I get to work on a wider range of projects than any single employer could offer.
The reason it keeps working is repeat business. Agencies come back because the second project is faster than the first once I know their codebase and conventions.
“I would rather turn down a project than deliver one badly.”
WORKING TOGETHER
What to expect.
A price agreed before work starts
Fixed-scope, hourly, or retainer, settled up front. No invoice you did not expect.
An honest scope assessment
Including what to cut or validate another way.
Visible progress in your repo
Work you can see rather than status reports you have to interpret.
Documentation written for your team
The handover is part of the build, not an extra.
Full IP transfer on completion
The product and code are entirely yours.
No claim on your client relationship
Ever.
Have something that needs building?
Tell me the scope and the deadline.