← Reece Douglas

By Reece Douglas · 9 November 2026 · Guides

Building an MVP without wasting money: a founder's guide

A man at a grey desk holds a small circuit board beside a smartphone showing an app screen, with an open notebook of sketches nearby.
Photo: ThisIsEngineering on Pexels

An MVP is the smallest working version of your idea that a real person can use to solve one real problem. Build that one thing well, put it in front of real users quickly, and let what they do decide what you build next.

You run a business and you’ve had an idea for years. Maybe it’s an app, maybe a platform, maybe a tool your customers keep asking for. You have the budget. What worries you is spending it on the wrong thing, ending up with something that looks finished but nobody uses. That worry is healthy. Here’s how I’d approach a first version, and how I did it with my own app.

What actually is an MVP?

An MVP is the first version of your product that does one job properly for one kind of person. It isn’t a mock-up and it isn’t a half-built version of the full dream. It works. Someone can pick it up and get something useful from it.

The word “minimum” scares people into thinking it means cheap or rough. It doesn’t. It means narrow. The one thing it does should feel finished and trustworthy. Everything else waits.

A good test: can you describe what it does in one sentence, for one type of person? If you need a paragraph, it’s not minimum yet.

What should I leave out of the first version?

Leave out anything that doesn’t help someone complete the core job. That usually means most of your list.

Write every feature you’ve imagined on a page. Then ask of each one: would a first user walk away without it? If not, cross it out.

Usually keep Usually leave for later
The one core task, done well Admin dashboards and reports
A simple way to sign up or start Multiple user types and permissions
A way to hear from users Social features, sharing, badges
Clear, honest wording Integrations with every other system

The things on the right aren’t bad ideas. They’re second-version ideas. You’ll build better versions of them once real people have shown you what they actually need.

How do I prove people want it before building everything?

Put something useful in front of people early, then watch whether they come back. Asking friends if they like the idea tells you very little. Watching strangers use it tells you a lot.

With FreshPlate, my own iPhone app, the idea was recipes written around a person’s medicines, conditions and allergies. The website has a free food and medication checker and guides cited to NHS and NICE. In the 30 days to 4 October 2026, 2,057 people visited the website, most of them from search engines.

Whatever you’re building, here’s an approach worth trying:

How do I test it with real users?

Get a working build into real hands as early as you can stand, and keep shipping small updates. The first version you show will be wrong in places. That’s the point of showing it.

For FreshPlate I’ve put out over fifty TestFlight builds, Apple’s way of sharing an app with testers before it goes on the App Store. It’s about to launch on the App Store.

Some practical habits that help:

If your idea touches health, money or legal matters, check the rules that apply with the right body before you test with the public. With FreshPlate the guides are cited to NHS and NICE so people can see where the information comes from.

How do I avoid wasting money with whoever builds it?

Insist on seeing it working early and often, and keep the scope written down. Money gets wasted when months pass with nothing to touch, then the result doesn’t match what was in your head.

Whoever you hire, ask for:

When I build, every layer is mine to build, so there’s no handing off between people. Once a build starts, you see it working within two working days. If you’re a founder in Liverpool or Wirral, I work with businesses there and across the UK.

If you want it done for you

The easiest way to see how I work is the free preview: I’ll design your new homepage and send a short video walking you through it within two working days. Tell me what your idea is and what you need, and we’ll work out the smallest version worth building.

Questions

Should my MVP be an app or a website?

Often a website first. It's quicker to change, search engines can find it, and it lets you prove demand before you commit to an app. FreshPlate has a website with a free tool alongside the iPhone app.

How many features should an MVP have?

As few as it takes to do one job properly for one type of person. If a first user wouldn't walk away without a feature, leave it for the next version.

Do I need investors before building an MVP?

Not necessarily. If you do want investment, a working product with real users is a far stronger case than an idea.

What if my idea involves health information?

Check the rules that apply with the right regulator before you put it in front of the public, and cite trusted sources for anything you say. Never let the product give medical advice; send clinical questions to a qualified person.

Free, and no obligation

Want this sorted? See your new homepage first, free

Tell me about your business. Within two working days I’ll send you a preview of your new homepage, designed for your business, and a short video of me walking you through it.

  1. You tell me about your business. Two minutes.
  2. I design your preview and record a short walkthrough.
  3. You decide. Keep the ideas either way. No sales call unless you ask for one.
What would help most?

I’m Reece. I’ll design it myself and reply from contact@reecedouglas.com. What you send is used for your preview and nothing else. Privacy