You’re hiring one person. Here’s who.
No account manager, no handover to a junior after you sign. The person on the call is the person writing the code.
Dawood
Founder, and the person writing the code
- Based
- Karachi, Pakistan
- Works with
- Clients anywhere
- Projects at once
- Two, at most
I started Notations because the same conversation kept happening: a business with a process that works, running on a spreadsheet that doesn’t, and quotes in front of them for a “website” that would not have fixed it.
I build the whole thing myself: the database, the screens, the rules underneath, the deployment. That’s a limit on how much work I can take at once, and it’s also the reason you never explain your business twice.
The studio is deliberately small. Few enough projects at a time that yours isn’t queued behind ten others, and no layer between the person you meet and the person writing the code.
Both sides of small
What I can’t show you is a decade of logos. What I can give you is a fixed price, a working build every week, and a written scope you can read in full before you pay anything. That’s a better guarantee than a testimonial, and it’s one you can hold me to.
Four rules I don’t break.
I’ll tell you not to build it
If something off the shelf does the job, that’s the advice you get on the first call, before either of us has spent anything. A studio that has never talked a client out of a project is telling you something.
Everything in writing, before the work
Scope, price, date, payment terms, and what’s explicitly excluded. Not because of lawyers, but because most software arguments are really two people remembering a conversation differently.
You see it every week
A working URL from week one. It’s harder for me. There’s nowhere to hide a slow month, which is exactly why it’s worth promising.
You own it when it’s paid for
The build runs on my infrastructure so you don’t have to set anything up to watch it come together. On final payment the code is yours, transferred with everything needed to run it. Locking clients in is a business model I’m not interested in.
Why “Notations”.
A notation is a way of writing something down precisely enough that someone else can act on it: a score, a formula, a schema. That’s most of this job: taking a process that lives in people’s heads and writing it down exactly enough that a machine can run it.
Directly, not through a form if you’d rather not.
Or read how a project runs first. It’s the honest version of what you’d be signing up for.