All writing

ArchitectureBy 2 min read

Shipping an enterprise MVP without painting yourself into a corner

How to build the smallest thing that proves value to an enterprise client, with the seams in the right places so success doesn’t force a rewrite.

On this page · 6 sections
  1. What viable means for an enterprise
  2. Choose boring, proven technology
  3. Should an MVP start with microservices?
  4. Put the seams where change is likely
  5. Tight scope and weekly demos
  6. The lesson I carried forward

As a senior developer, I led the build of a complete MVP for an enterprise client on Angular, Spring Boot, PostgreSQL and Docker. Enterprise MVPs sit in an awkward spot. The client wants speed and a demo that wins budget, and if it works, they expect it to become the real system. Build too little and it collapses under its own success. Build too much and it never ships.

What viable means for an enterprise

“Viable” for an enterprise includes things a consumer MVP can skip: authentication that fits their identity setup, basic audit trails, role-based access, and data handling their security team will sign off on. Leave those out and your MVP never gets past procurement, however good the demo is. Everything else is negotiable.

Choose boring, proven technology

I picked the stack for delivery speed and a long working life. Novelty didn’t come into it:

  • Angular for a structured, opinionated frontend that a larger team could later extend consistently.
  • Spring Boot for a mature backend ecosystem the client’s own engineers could support.
  • PostgreSQL because a relational model with real constraints catches mistakes early, and it scales further than most MVPs will ever need.
  • Docker so every environment (laptop, CI, staging, production) ran the same thing.

An MVP is the wrong place to learn a new framework on the client’s budget.

Should an MVP start with microservices?

I don’t start MVPs with microservices. A well-structured monolith with clear internal module boundaries ships faster, is easier to debug, and can be split later along those same boundaries if scale or team structure demands it. Most never need to be split, and the ones that do are glad the seams were already there.

Put the seams where change is likely

You can’t make everything flexible, so choose where the flexibility goes:

  • Put integrations behind interfaces. Enterprise clients always change the systems you integrate with, and adapters make that a local change.
  • Use configuration over code for anything the business will want to tweak, such as thresholds, workflows and feature flags.
  • Use schema migrations from day one. Versioned migrations let the database evolve without becoming fragile.

Tight scope and weekly demos

Weekly demos of working software did more for client confidence than any status report. They also made scope conversations concrete. Saying “not yet” to a feature is much easier when the client can see what they already have.

The lesson I carried forward

Build the MVP architecture you won’t have to apologise for six months later.

Build small, but put the seams where the future will need them. That idea has shaped every system I’ve led since, and it’s how we approach FinMoon AI today.