How to validate a UK SaaS idea in 7 days (without writing code)

Most UK builders spend six weeks building the wrong thing. The fix isn't a cleverer MVP — it's a week of deliberate validation before you touch Claude Code.

This is a seven-day plan, UK-first, that answers one question: will ten real UK customers pay for this? Not "is this interesting?" Not "would you use it?" Would they hand over a card.

You can run the whole thing for under £50 and finish the week either building with conviction or killing the idea with zero code written.

Why UK-specific validation matters

Most validation guides are generic. They tell you to interview customers and build a landing page. Fine. But UK SaaS has four quirks that change the playbook:

• VAT threshold at £90,000 (2026). You don't need to register on day one, but it changes price architecture if you plan to cross it.
• ICO registration — most UK SaaS processing personal data needs to pay the £40-60 annual data protection fee.
• MTD (Making Tax Digital) compliance for your own accounting from day one if you trade as a limited company.
• Cookie + GDPR consent on any landing page that uses analytics or a form.

These aren't blockers. They're just the frame your validation has to fit inside. You can ignore them for the first seven days, but the price you charge and the pitch you write should account for them.

Day 1 (Monday): Sharpen the idea

One hour. No more.

Answer these questions in writing. If you can't, the idea isn't ready.

• Who exactly is the customer? Not "UK small businesses". "UK independent bookshops with 1-3 staff using Shopify."
• What's the specific pain? "Manually counting stock every Monday morning takes the owner two hours."
• What's the current workaround? Spreadsheet? Pen and paper? A £200/yr tool that half-works?
• What would they pay per month to make this go away? Write a number. £15? £29? £49?
• What tool will you use to build if this validates? Claude Code for the backend, Lovable for a marketing site, Supabase for data, Stripe UK for payments. Write it down now so you don't deliberate later.

If any question is fuzzy, sharpen it. If two of them are fuzzy, pick a different idea.

Day 2 (Tuesday): Desk research the competition

Three hours. Cheap tooling.

Search for your problem on Google, Reddit (r/SideHustleUK, r/startups, r/UKPersonalFinance, relevant niche subs), Indie Hackers, LinkedIn and YouTube. Note:

• Direct competitors — tools that solve the same problem for the same audience. List five. Their pricing, their positioning, their review scores.
• Adjacent competitors — tools that solve a nearby problem. What do customers say in the reviews about gaps?
• UK-specific voices — is anyone covering this problem with UK context? GBP pricing, UK regulatory references, UK case studies?

If three of your five direct competitors are US-based and charge in dollars, that's a signal. UK buyers often pay a 15-25% "dollar tax" and prefer GBP-native tools.

If there are zero competitors, that's usually a red flag, not an opportunity. Someone's probably already tried and failed. Find out who and why.

By the end of today you should have a one-page competitor teardown and a clear answer to "why does my version exist?". If the answer is "I think I can do it slightly better", go back to day one.

Day 3 (Wednesday): The 10-conversation sprint

Four hours, probably spread over the evening. This is the hardest day and the one most people skip.

Your job: talk to ten real UK people who fit your target customer. Not interested, not signed up. Ten conversations where someone describes the problem in their own words before you pitch anything.

How to find them:

• LinkedIn search — UK filter, job title, industry. Send 30-50 connection requests with a short, genuine note.
• Reddit DMs — find people asking about the problem in relevant subs over the last 30 days. Message them.
• Your own network — two warm intros are worth ten cold LinkedIn messages.
• Communities — UK Business Network, Tech London, local Slack/Discord groups for your vertical.

The format: 15 minutes, Zoom or phone. Questions you're not allowed to ask:

• "Would you use this?" (useless)
• "Would you pay for this?" (useless)
• "What do you think?" (useless)

Questions you should ask:

• "Walk me through the last time you did X."
• "How long did it take?"
• "What did you use?"
• "What was the worst part?"
• "Have you looked for a tool to fix this? What did you find?"

If 7 of 10 describe the problem in similar language without you prompting them, you have something. If fewer than 5 do, the problem isn't as sharp as you thought. That's useful — you can re-scope tomorrow.

Day 4 (Thursday): Build the fake door

One afternoon. No code.

Create a landing page that describes the product, the price, and has a "Start 7-day free trial" or "Join the waitlist" CTA. Use Lovable, Carrd or a Notion-to-site tool. Domain is optional — a lovable.app or notion.site URL is fine for a test.

Required elements for a UK audience:

• GBP pricing displayed prominently. Not "$29" — "£29".
• One-sentence positioning in the hero. "Stock counting on autopilot for UK independent bookshops."
• Three features max, with outcomes not features. "Close Monday stock-take in 15 minutes, not 2 hours."
• Social proof placeholder — "beta testers" block if you have quotes from day 3.
• A single CTA — email address capture. Tell people you'll email when early access opens.
• Cookie banner — yes, even on a test. Two lines of JavaScript or a free Cookiebot plan.
• Privacy policy — one page, written by you in plain English, linked from the footer. A proper one goes in on launch day.

Cost so far: £0-10 depending on the domain.

Day 5 (Friday): Drive traffic

One day. Your goal: 200 visits, measure conversion.

Where UK traffic actually comes from at this stage:

• A Reddit comment in a relevant UK-focused sub answering a real question with your tool mentioned at the end as "I'm building this, would love input". Do not post. Comment.
• A LinkedIn post from your personal profile — one-paragraph story of the problem, link to the landing page, tag 3 people who might find it useful.
• A post in a relevant UK Slack/Discord community — same story format. Ask moderators first.
• Targeted Meta ads, optional, £20-30 budget, UK only, interest-based targeting. Only if your audience is on Facebook/Instagram. Don't bother for B2B tech.

A 5-10% email conversion rate on a warm audience (Reddit, LinkedIn personal) signals real interest. 1-3% is normal for cold ads. Below 1% and your messaging is off, not necessarily the idea.

Day 6 (Saturday): Sell before you build

Half a day. The most important half-day of the week.

Email the people who signed up from day 5 and the 10 people you interviewed on day 3. Offer a "founding member" deal: the first month free, lifetime 50% discount, or a pay-what-you-want price for the first 30 days. You're going to deliver the service manually for the first ten customers.

This is the single hardest bit of validation, and the most predictive. If five people put a card down (via Stripe Checkout, which takes 20 minutes to set up), you have paid validation. If nobody does, the pain isn't sharp enough yet — but now you know before writing a line of code.

For your first Stripe Checkout page you don't need a full product. A £9.99 "early access" one-time payment that lets them email you the job to do manually is enough. You'll spend two hours on each request for the first week. You are not scaling yet. You are validating.

Day 7 (Sunday): Decide

Half a day of writing, no activity.

Write a one-page decision doc covering:

• Demand signal — interviews that described the problem unprompted, email signups, paid conversions.
• Pricing signal — what price did people actually pay? Did objections cluster around price or around the product?
• Competitor signal — is there whitespace, or is the market genuinely saturated?
• Your energy signal — do you still want to build this? Be honest. A year is a long time to spend on something you've lost interest in by day seven.

Four outcomes:

Signal	Decision
5+ paid early-access customers, clear pain, excited	Build. Start day 8 with Claude Code, ship MVP in two weeks.
20+ email signups, 0-2 paid customers, interested	Narrow. The problem is real but your pitch or price is off. Re-scope and re-test in 7 days.
< 20 signups, weak interview signals	Kill. Write a short retro. Pick the next idea tomorrow.
Lots of interest but you're bored of it	Kill anyway. You won't ship something you don't care about.

The UK regulatory layer (once you decide to build)

Assuming you choose "build", add these in your first week of building:

• ICO registration — £40-60/yr for most solo builders. Takes 15 minutes online.
• Company registration (optional but usually wise) — Companies House, £12. Get a separate business bank account from day one (Starling, Monzo Business, Tide).
• MTD-compatible accounting — FreeAgent, Xero, or QuickBooks. Most are free for new limited companies.
• Terms and conditions + privacy policy — use a UK-specific template (Juro, Simply Docs, or a £150 hour with a UK SaaS lawyer).
• Cookie consent — Cookiebot or a free alternative that supports UK GDPR.

None of this is hard. All of it is faster to do upfront than to retro-fit.

What to avoid in this 7-day sprint

• Don't write code. If you catch yourself in Claude Code or Cursor before day 8, stop.
• Don't build a community before you have a product. Newsletters and Discords are multipliers, not validators. You validate with money.
• Don't optimise the landing page. Ship the ugliest version that answers "what is it, how much, what now?". Polish after validation.
• Don't expand the audience. Stick to your specific UK segment. "Freelance accountants in the North West" validates faster than "UK finance professionals".
• Don't skip the sell step. Interviews and email signups are cheap. Cards being charged is the only real signal.

What happens after day 7

If you validated, your next week looks like this: day 8 is planning in Claude Code, days 9-14 build the MVP (Lovable landing + Claude Code backend + Supabase + Stripe). Day 15 you ship to your paid early-access cohort. Day 22 you collect feedback. Day 30 you review pricing.

If you killed it, you've spent seven days and maybe £50 to learn something that would have cost six weeks and a fresh burnout if you'd gone straight to building. That's a good trade.

The goal of this week isn't to be right. It's to find out quickly.

Key takeaways

• Seven days of validation before code beats six weeks of building the wrong thing, every time.
• Ten real conversations where the customer describes the problem without prompting is the minimum bar; under five and the pain isn't sharp.
• Paid early access (even a GBP 9.99 Stripe Checkout) is the only validation signal that matters; email signups are a lagging indicator.
• UK specifics - VAT threshold at GBP 90,000, ICO registration, MTD compliance - shape price and copy but don't block validation.
• A decision doc on day 7 forces a clean build / narrow / kill choice, and a clean kill is a win.

FAQs

How much should I spend on validation? Under £50 for the 7-day sprint. Optional Meta ads can take it to £100. If you spend more, you're building, not validating.

What if I can't get 10 interviews in a week? You can. LinkedIn connection requests to 40-60 targeted people usually yield 10 calls. If you can't get 10, your audience isn't reachable and that's a signal on its own.

Do I need an LLC or Ltd before validating? No. Validate as a sole trader. Register a limited company on day 8 if you decide to build.

Is £9.99 a fair "founding member" price? It's a starter. The number matters less than the fact that someone actively paid. You'll set real pricing after 10-20 paying customers tell you what's worth what.

What if the data says "kill" but I'm still excited? Write down specifically what the data showed. Sit on it for 48 hours. If you still want to build, narrow the audience and re-test. Don't over-ride a clean kill signal.

[!info] Next step Ready to dig deeper on the "what to build" question? Read this week's free report for a fully researched UK business opportunity with keyword data, competitor analysis, and builder prompts.