Andrew Dorokhov

SaaS & MVP development

From zero to a paying-customer-ready product: the boring, critical parts done right the first time.

Most MVPs don't fail because of the core idea. They stall on everything around it: sign-up and login, team invitations, roles, subscriptions, invoices, emails, admin tools and a deployment that doesn't fall over on launch day. That work is not glamorous, but customers notice immediately when it's missing or broken.

I build the whole product with you, from the first database table to the first paying customer. You work directly with one senior engineer who has shipped production software for over 15 years, so decisions get made quickly and the codebase stays small enough for your future team to understand.

The goal is a product you can sell, not a prototype you'll have to throw away. That means a deliberately small scope, a boring and proven stack, and code with tests and documentation from day one.

What you get

What's included

01

Scope and architecture

We cut the feature list down to what's needed to sell. You get a written plan, data model and a fixed price or budget range before development starts.

02

Accounts, teams and permissions

Sign-up, social login, email verification, organizations, invitations and role-based access, the foundation every B2B SaaS needs.

03

Billing that just works

Stripe subscriptions, trials, plan changes, invoices and webhooks handled correctly, so revenue isn't lost to edge cases.

04

Admin and internal tools

Dashboards to manage users, plans and data without asking a developer to run SQL queries.

05

Production from week one

Docker, CI/CD, staging and production environments, error tracking and backups. You can demo and deploy at any point.

06

Handoff or long-term partnership

Documentation and a clean repository you fully own. When you hire a team, I help onboard them, or I stay on as your technical partner.

Typical stack

  • Next.js
  • React
  • TypeScript
  • Laravel
  • Node.js
  • PostgreSQL
  • Stripe
  • Docker

Case studies

Related work

Cover: the Backlinks System 'Place links' screen with the 'Choose anchor text' dialog for summitlog.net, next to the title 'Backlinks System'.

SEO / link building · Own product

From anchor to published link in one click

Link-building workspace that keeps every anchor and donor site in check

An internal tool for running link building across many sites: anchor lists per promoted URL, a shared base of donor sites, placement in one click with memory of what is already there, and a module on my own network of sites that publishes each link as soon as it is placed.

  • PHP
  • MySQL
  • jQuery
  • Bootstrap
Cover: the blog's home page with the 'Engineering Excellence' hero and a phone showing the mobile menu, next to the title 'Developer blog'.

Developer blog · Own project

400 articles in 30 sections on one set of templates

A Hugo theme with glow, motion and a knowledge graph built from front matter

A dark custom theme for my development blog: Hugo templates, Tailwind 4 in Hugo's own pipeline and about 400 lines of plain JavaScript for the typing hero, the filterable knowledge graph and the scroll reveals.

  • Hugo
  • Go templates
  • Tailwind CSS
  • JavaScript
  • esbuild
  • Netlify
  • Netlify Forms

FAQ

Common questions

How long does it take to build an MVP?

It depends on scope, but a focused B2B MVP with accounts, billing and one core workflow usually takes 6 to 12 weeks. You get an estimate after reviewing your brief, before any work starts.

Will I have to rewrite the MVP later?

No, if it's built right. I use mainstream frameworks and conventional architecture so the same codebase can grow with your product and your team.

Can you work from my designs or Figma files?

Yes. If you don't have designs yet, I can build a clean interface on a proven component library and you can bring in a designer later.