Ditin Agrawal
AI Product Engineer
Taking two projects for Q3
Selected work
Four projects, four different problems. Each one shipped and still running.
Northbeam Logistics — 2026
A shipment-tracking dashboard their ops team actually opens. The old one took eleven clicks to answer “where is my container”; this one answers it on load.
Eleven clicks to one screen
Rye & Salt — 2025
A bakery in Lisbon wanted a menu that changes daily without calling a developer. Now the head baker edits it from her phone at 5 a.m.
Menu updates without a developer
Independent, self-funded — 2025
A rehearsal scheduler for chamber groups. Built it because my sister's quartet was running on a group chat and a shared spreadsheet.
Replaced a spreadsheet and a group chat
Meridian Type — 2024
Documentation for a type foundry's variable-font API. Specimen pages that render the actual font, not a screenshot of it.
Live specimens instead of screenshots
Services
Four shapes of work. Prices are starting points — I quote the actual number after a 30-minute call, and it does not move after that.
A site that loads fast, ranks, and that your team can edit without me.
From an idea to a live product people can sign up for and pay for.
The repetitive part of your week, handed to something that does not get bored.
Something is slow, broken, or the last developer disappeared. I triage first, quote second.
Retainers are available for product teams that want a steady design and build partner. I still avoid vague discovery-phase work and only quote what I can reasonably commit to.
Results
Measured, not estimated. Every figure below comes from the client's own analytics or from Lighthouse on the shipped build.
Process
Four stages, in this order, every time. You always know which one we are in.
Thirty minutes. You describe the problem, I ask the annoying questions. Within two days you get a fixed price and a date — or an honest “I'm not the right person, talk to X”.
Free · 30 minutes
No forty-page Figma file you have to imagine in motion. I build the real thing on a staging URL from week one, and you click it on your own phone.
Week 1
You get the staging link, the repo, and a Friday note that says what moved and what did not. Nothing is a surprise on launch day.
Weeks 2 to n
A written hand-off, a recorded walkthrough, and thirty days where I fix anything that breaks for free. Then the code is yours and you owe me nothing.
Launch + 30 days
About
I have been building for the web since 2022 — two of those years inside product teams, the rest on my own. The in-house years taught me what happens to a codebase eighteen months after the agency leaves. That is most of why I work the way I do.
I take one, sometimes two projects at a time. You get the person who scoped the work, not a strategist who hands you to a junior in week three. When you email me, I answer.
Outside of this: bad chess, long walks, and a slowly growing collection of mechanical keyboards I do not need.
Stack
Boring on purpose. I pick tools I can still support in three years, not the ones that trended last month.
References
“He shipped in four weeks what our agency had been finalising for seven months.”
The difference was that we could see the real site from week one, on our own phones, instead of reviewing screenshots in a deck.
“I am not technical and I never once felt talked down to. I edit our menu from my phone now.”
“The hand-off document was better than the documentation for tools we pay for.”
Questions
Marketing sites start at $1,500. An MVP or platform starts at $5,000, AI automations at $2,000, and a rescue audit at $600. You get one fixed number after our call, and it does not change unless you change the scope in writing.
Usually two to four weeks out. If you need something sooner, say so in the first email — sometimes a slot opens up, and I would rather tell you no quickly than string you along.
Both. If you have a designer, I build to their file and give them a component library back. If you do not, I design it — in the browser, not in a deck.
You do, from the first commit. It lives in your GitHub organisation, not mine. There is no license, no lock-in, and nothing you have to keep paying me for.
Thirty days of free fixes for anything I built. After that I am available hourly, but most clients do not need me — that is rather the point of the hand-off.
Yes. Ask on the call and I will walk you through a real repo, including the parts I would write differently today. Anyone who claims they would not change anything is selling you something.
Yes. I work with a small number of clients on an ongoing basis when there is a clear product cadence, a working roadmap, and a need for steady iteration. I do not take indefinite fire-fighting retainers.
Yes. For short-term support, bug-fix work, or one-off product help, I am available hourly. My usual rate is $10 per hour, with a clear scope and a realistic estimate before the work starts.
Next step
Thirty minutes, no deck, no pitch. Bring the half-finished thing, the vague idea, or the site that has been “nearly ready” since March. You leave with a real number and a real date, whether or not you hire me.