Work order NZV-001 · open
You brief me Monday.Your product is livethe Monday after.
MVPs, internal tools, CRMs and AI features, built end to end by one senior developer. A sprint is one week. A full build is two to five. Either way you talk to the person writing the code, and there is nobody standing between you and it.
- Next available slot
- NEXT SLOT · BRIEF MON 10 AUG → HANDOVER MON 17 AUG
- Starting price
- PROJECTS START AT $4,000
No deck, no discovery phase. On the call I tell you whether this is a week or a month. You get a fixed quote and a fixed date the next morning.
August is open. One project at a time.
One project at a time · Bangkok
- FASTEST CRM HANDOVER: 6 DAYS
- ONE PROJECT AT A TIME
- 20+ PROJECTS SHIPPED SOLO
- REPLIES IN UNDER 3 WORKING HOURS
No account manager, no discovery phase, no circling back. The person who answers your email is the person who writes the code.
03 / scoped
What fits in a work order.
- 1 WEEK
The sprint
One fixed scope, one fixed price, one fixed date. An internal tool, a working MVP, an integration, a migration — something a real person can log into on Friday.
- SPEC ON DAY 1
- DEMO LINK EVERY EVENING
- DEPLOYED TO YOUR DOMAIN
Not this: a design system, a brand, or a native mobile app.
- 2–5 WEEKS
The build
A full product with users, auth, payments and the boring parts done properly. You get a demo link every week and a written scope you approved before I opened an editor.
- AUTH, BILLING, ADMIN
- WEEKLY DEMO
- TESTS AND LOGS THAT MEAN SOMETHING
Not this: something that needs six people and a Jira board.
- 1–2 WEEKS
AI features that are not a demo
Retrieval that answers from your actual data. Agents that touch your real systems. Evals, so you find out it broke before your customers do.
- EVALS BEFORE LAUNCH
- COST CAPS
- A FALLBACK FOR WHEN THE MODEL IS WRONG
Not this: a chatbot glued onto your marketing site.
- 2 DAYS
Rescue and takeover
Someone vibe-coded you into a corner, or your last developer went quiet. I read the repo, tell you the truth in writing, and you keep the document either way.
- WRITTEN FINDINGS YOU KEEP
- RISK LIST, RANKED
- A REAL ESTIMATE, NOT A GUESS
Not this: a rewrite I talk you into on day one.
Projects start at $4,000.
Below that line there is one thing. One working day, $2,000, bought on a date. Something small wired into a system you already run, deployed to your accounts that evening. There is no call. It is not a cheaper version of the week.
One working day →04 / schema
Your competitor shipped. You are still in discovery.
Same ruler, both lanes. Monday you brief me. Tuesday you are clicking a real schema with your own data in it. The following Monday it is on your domain.
The gap is not talent. It is the four people who have to agree before anything gets written.
| Stage | Weeks |
|---|---|
| A normal agency: Discovery | Week 1 to 3 |
| A normal agency: Proposal | Week 4 to 4 |
| A normal agency: Kickoff | Week 5 to 5 |
| A normal agency: A build you never see | Week 6 to 13 |
| A normal agency: Handover | Week 14 to 14 |
| A normal agency: First change order | Week 15 to 16 |
| Me: brief to handover | Week 1, seven days: Brief, Schema, Build, Build, Integrations, QA, Handover |
05 / building
What a week actually looks like.
- MON1/7
Spec
Forty-minute call, then I write the spec myself and send it back the same evening. If we are going to disagree, we disagree on Monday instead of week six.
- TUE2/7
Schema
Schema, auth, deploy pipeline. Production infrastructure on day two, not day twenty. You get a link. It is ugly and it works.
- WED3/7
Build
The build. A working URL you can open every evening, so you are never guessing what I am doing.
- THU4/7
Build
The build continues. This is the day the thing starts looking like the thing.
- FRI5/7
Integrations
Integrations and real data. Stripe, your email, your calendar, whatever your business actually runs on.
- SAT6/7
QA
QA and hardening. Real error handling, real logs, real backups. This is the day that separates software from a demo.
- MON7/7
Handover
Deploy to your domain, your accounts, your repo. You get the keys, a ten-minute video, and a written page on how to change things.
WHAT I NEED FROM YOU: 40 MINUTES ON MONDAY. ONE ROUND OF FEEDBACK ON THURSDAY. SIGN-OFF ON MONDAY. NO STANDUPS. NO SLACK TAX.
06 / building
The log.
I cannot show you everything. Most of it is behind an NDA and the rest is somebody's internal tool. So here is the ledger, labelled honestly. The redacted lines are redacted, not missing.
The ledger goes live with the first entries. Ask me on a call and I will walk you through the work I cannot publish.
Three you can open right now.
None of these is client work and none of them is a case study. They are the things I have built that are mine to show, so they are here instead of a testimonial I would have to ask someone for.
- ZephyroA work management platform where the vocabulary is yours: an insurance workspace calls the work a claim, not a task. Four languages, with Hebrew and Arabic mirroring the whole layout, and Claude drives it through an MCP connector. The team I work with runs on it.EARLY ACCESS (opens in a new tab)
- TumbloA puzzle game on the App Store. Rotate the whole board, the tiles fall and merge. Built alone, in my own time, and the seller name on the listing is my own.APP STORE (opens in a new tab)
- AxentiusData analytics and AI automation, with the team I have worked alongside for years. Bigger machinery and longer timelines than anything on this page, and the reason I can tell you honestly when a project belongs there instead of here.THE TEAM (opens in a new tab)
07 / qa
How this works. No hourly meter, no mystery.
- FIXED SCOPE. FIXED PRICE. FIXED DATE.
- Agreed in writing before I open an editor. Hourly billing means you pay for slow, and this is not slow.
- HALF TO START, HALF ON HANDOVER.
- No retainer to get on the calendar.
- YOU OWN EVERYTHING FROM DAY ONE.
- Repo in your GitHub org, infrastructure in your accounts, domain in your name. Day one, not day ninety.
- ONE CHANGE OF DIRECTION PER PHASE, ON ME.
- What is fixed is the scope and the price. What is not fixed is your mind.
- IF I MISS THE DATE, YOU DO NOT PAY FOR THE OVERRUN.
- The date is agreed in writing before I start. If I run past it, the extra days are mine, not yours. That is the whole point of a fixed date.
- ONE PROJECT AT A TIME.
- That is why the slot matters, and why I will sometimes tell you to wait two weeks.
08 / qa
Yes, I use AI. Here is the part that matters.
AI writes a large share of the code on every project I take. I am not going to be coy about it, and you should be suspicious of anyone in 2026 who is.
That is not the interesting part. Unreviewed AI output is exactly the mess people are now paying two hundred dollars an hour to unpick. The reason a senior human still costs money is that somebody has to own the schema, make the security calls, write the tests, and be awake at 2am when it breaks. I read every line. I am on the hook in six months.
If you have already been burned by something vibe-coded, that is literally a service I sell. I have seen the bill.
And the speed is mostly not about AI anyway. There is no sales call that is not with the builder. There is no project manager translating between us. There is no junior learning on your budget, and there is no office to pay for.
- Brief·
- Schema·
- GenerateASSISTED
- ReviewMANUAL, ALWAYS
- TestMANUAL, ALWAYS
- Ship·
09 / qa
Who you are actually hiring.
Bangkok · UTC+7 · Europe overlaps my afternoon, the US East coast my evening
I am Vladimir. For ten years I have built software that has to survive real traffic: data platforms doing 200,000 requests a second, systems that lose money if they blink. I still co-run a development studio that does that work for enterprises.
This page is not that studio. The studio needed six weeks and four people to start a CRM. I built a comparable one alone and it was live in six days. Nothing about me got better in between. The way I work did. So I started taking a small number of projects directly, at the speed I actually work at.
I work from Bangkok. If you are in the US that is an advantage rather than a tax: my working day is your night, so the demo link goes up while you sleep and is waiting when you start. If you are in Europe, we simply share an afternoon.
I am probably wrong for you if:
- you want the cheapest quote in the thread
- you need six people and a Jira board
- you want someone to also do your brand and your go-to-market
- nobody on your side can make a decision in under a week
- the scope genuinely cannot be frozen, in which case hire an agency and I mean that
Vladimir Nizovtsev · Senior full-stack developer
10 / qa
The things you are already thinking.
One week is not a real timeline.
For a sprint with a frozen scope, it is. For a product with billing, roles, an admin panel and three integrations, it is not, and I will tell you that on the call rather than after you have paid a deposit. One week is what a sprint is, not what everything is.
What happens if you get hit by a bus?
The repo is in your GitHub organisation from the first commit and the infrastructure is in your accounts. The handover video and the written change guide exist from day one, not day ninety. Worst case you hand it to any competent developer, which is the situation the README exists for.
Is this going to be AI slop?
Slop is unreviewed. Most AI code is bad and the research agrees with you. Everything here is reviewed, tested and monitored by the person who is still on the hook in six months. I do not hide that I use it — there is a whole section about it above.
Why are you not as expensive as an agency?
You are not paying for a salesperson, a project manager translating between us, an office, or a junior learning on your project. Same output, one third of the org chart. I am also not the cheapest quote in your inbox: projects start at $4,000 and I do not negotiate that down.
What if my thing is smaller than $4,000?
Then buy a day instead of a week. One working day, $2,000, on a date you pick, and no call at any stage. You write the brief first and it costs nothing. I read it and tell you inside one business day whether it fits in a day, and if it does not I tell you what it actually is before you have paid me anything. The $2,000 comes off any project you book in the next thirty days, down to $4,000 and not below, so on a floor-priced sprint it is worth nothing and I would rather you read that here. If your thing is smaller than a day, I am the wrong person, and saying so takes me one email.
What if I need changes after handover?
Two options. Hire me monthly for changes and ops, or hand it to anyone else. You own it, so both actually work.
Can you take over an existing codebase?
Yes. Always the audit first, and you keep the findings document whether or not you hire me for the fix.
Will you sign an NDA?
Yes. Mutual is fine. Send yours.
What if we are four days in and it is clearly not working?
Then we stop on day four and you pay for the four days. I would rather lose half a sprint than deliver something you are going to resent.
Can I talk to someone you have built for?
Not yet. I am building this practice in the open and I am not going to invent a reference. Ask me on the call and I will walk you through the work I cannot publish, in detail, including the parts that went badly.
11 / shipped
Ship NZV-001.
Book this week. The next brief is MON 10 AUG, and you are live by MON 17 AUG.
Door one
Book 40 minutes
I will tell you on the call whether this is a week or a month, and you get a fixed quote and a fixed date the next morning.
Book 40 minutesDoor two
Not ready to talk
Send me what you are building and I will send back a written plan and a fixed price within 24 hours.