How to build a SaaS with AI tools: a UK builder's walkthrough for 2026

If you're a UK solo builder waiting for the right moment to ship a SaaS, it was six months ago. The second-best moment is this weekend.

State of play in April 2026: Claude Code writes production-grade TypeScript end-to-end. Lovable puts a working UI in front of you in 15 minutes. Supabase handles auth, Postgres and storage free until real money arrives. Stripe UK does VAT calculation for you. Vercel deploys to the London edge in under 90 seconds. Shower-thought to "someone paid me £12" in under a fortnight — no co-founder, no YC batch, no £50k.

What you need is a UK-native playbook, because almost nobody's writing one. Search "build SaaS with AI UK" and you get ten pages of vendor marketing from California. This is the walkthrough I wish I'd had.

Why UK solo builders should care, right now

The maths has changed. In 2022, a B2B SaaS MVP cost six to eight weeks of evenings, ~£400 in tooling, and a grasp of React. In 2026, the same MVP costs a weekend, ~£35 in month-one tooling, and a credit card.

Three builders I know shipped paying products Jan-March 2026: an invoicing tool for plumbers (£180 MRR, six weeks), a CRM for driving instructors (£240 MRR, eight weeks), a Stripe reconciliation dashboard for UK accountants (£420 MRR, ten weeks). None had formal coding backgrounds. All used Claude Code or Lovable.

The UK market has a gap the Americans can't fill: HMRC workflows, Companies House integrations, MTD compliance, CIS deductions, GBP pricing with 20% VAT baked in. These aren't niches, they're moats. A US horizontal SaaS won't beat you on "handles the quarterly VAT return the way a UK accountant actually wants."

The stack: what you actually need

Ignore anyone saying you need eight tools. You need four.

Layer	Tool	Cost month one
AI builder	Claude Code or Lovable	£0-£17
Database + auth	Supabase	£0 (free tier)
Payments	Stripe UK	1.5% + 20p per card
Hosting	Vercel	£0 (hobby) or £15 (Pro)

Month-one spend: £0 to £32. Once taking money, expect £25-£80 until you cross ~500 users. No Kubernetes, no Redis, no separate auth service, no analytics SaaS. Add those later when paying customers justify them.

The walkthrough: weekend one

Step 1 — spec the thing with Claude (Friday evening, 90 minutes)

Don't start with code. Start with a spec. Paste this into Claude:

"I want to build a [one-sentence description]. My target user is [specific UK persona]. The core job-to-be-done is [concrete outcome]. I want to charge £X/month. Write me a minimal spec: data model, core user flows (max 5), pricing tiers, and the one feature I should ship first. Cut anything non-essential for a paying MVP."

Claude will push back and suggest cuts. Let it. You want the argument on Friday night, not Sunday afternoon with 2,000 lines of code around a bad premise.

When the spec is tight — one page, five flows, one killer feature — ask Claude to produce a README.md and schema.sql. That's your Saturday brief.

Step 2 — build the UI with Lovable or Bolt (Saturday morning, 3-4 hours)

Lovable (£17/mo starter) and Bolt (free tier is enough for MVP) both turn an English description into a working Next.js app in minutes. Lovable is better for CRUD-heavy dashboards, Bolt is better for landing pages — either gets you an 80% UI in a morning.

Paste your README into Lovable and ask for a landing page with email capture, an authenticated dashboard showing the core flow, and settings plus billing stubs. You'll get a passable first draft in 15 minutes. Spend three hours refining: copy, spacing, colour palette, logo.

Don't over-polish. A Linear-clone dashboard isn't the point. Shipping is.

Step 3 — wire the backend with Supabase (Saturday afternoon, 2-3 hours)

Create a Supabase project. Free tier: 500MB Postgres, 50,000 monthly active users on auth, 1GB storage. Plenty for MVP.

Point Claude Code at your Lovable repo and your schema.sql, then say:

"Wire this Next.js app to Supabase. Use @supabase/ssr. Set up row-level security on every table. Add middleware for protected routes. Use server components for data fetching where possible."

Claude Code will edit files, run migrations, and tell you which env vars to drop into .env.local. You'll spend most of the session fixing RLS policies — that's normal, RLS is fiddly, and getting it right on day one saves you a breach on day sixty.

Test auth end-to-end: signup, login, logout, password reset, protected route. Fix any breaks before moving on.

Step 4 — wire Stripe for GBP and VAT (Saturday evening, 2 hours)

This is the step US tutorials botch.

Create a Stripe UK account. Enable Stripe Tax — non-negotiable for UK and EU customers. It calculates VAT by country, handles UK digital services rules, and produces the reports you need for VAT returns.

Price products in GBP with tax behaviour exclusive (you charge £20, Stripe adds £4 VAT, customer pays £24). Pick a tax behaviour and be consistent.

In Claude Code:

"Add Stripe subscriptions. Use Checkout for first payment, customer portal for management, webhooks to sync status to Supabase. GBP prices. Stripe Tax enabled. Webhook handler updates a subscriptions table on checkout.session.completed, customer.subscription.updated and customer.subscription.deleted."

Test with 4000 0082 6000 0000 — a UK card that simulates 3D Secure, which your customers will hit.

Step 5 — deploy to Vercel (Sunday morning, 45 minutes)

Connect GitHub to Vercel. Set env vars. Set function region to lhr1 (London Heathrow). This matters: Vercel's default is Washington DC, and UK users feel every millisecond of that 80ms round-trip.

Add a custom domain. 123-reg or Namecheap sell .co.uk for ~£8/year; Vercel DNS is two records.

Turn on Vercel Analytics and Speed Insights — Core Web Vitals aren't optional in 2026 and Google punishes a slow LCP.

Step 6 — test and ship (Sunday afternoon)

Full end-to-end smoke test, in order:

1. Land on homepage (incognito)
2. Sign up with a real email
3. Receive confirmation email and log in
4. Go through the core flow to Stripe Checkout
5. Pay with a real £1 test product using your own card
6. Receive Stripe receipt; check Supabase — subscription row created?
7. Cancel via customer portal; check Supabase — status updated?

Don't ship until all seven pass. An MVP with broken signup is worse than no MVP.

Then tweet it. Post to r/ukentrepreneur or r/ukpersonalfinance. LinkedIn if brave. Tag three people who might care. That's your launch.

UK specifics you absolutely cannot skip

Four boring legal things that will bite you if ignored.

1. ICO data protection fee (£40-£60/year). If you process personal data — any signup form qualifies — register with the Information Commissioner's Office. £40 for sole traders, 15 minutes online, up to £4,350 fine for non-registration. Do it day one.

2. UK GDPR and a privacy policy. Similar to EU GDPR but not identical. You need a privacy policy covering what data you collect, why, retention, and deletion requests. Termly or iubenda (~£5/month) generate compliant ones. Don't copy from a US site — they have no equivalent of right to erasure.

3. VAT registration threshold (£90,000). From April 2024, the threshold is £90k taxable turnover over any rolling 12 months. Below: don't register. Above: must. Many UK SaaS founders voluntarily register from day one to reclaim VAT on costs and look established — judgement call.

4. Making Tax Digital. If you register for VAT, you need MTD-compatible software. FreeAgent (£19/mo, free if you bank with NatWest or Mettle) is the default for UK solo founders.

The realistic timeline

Nobody ships a paying product in a weekend. They ship a working product in a weekend, then fight for customers for three weeks.

• Weekend 1: MVP live, end-to-end flow working, custom domain
• Week 2: Five friendly testers, two bugs, copy rewritten four times
• Week 3: First cold outreach — 20 DMs, 4 replies, 1 "I'll try it"
• Week 4: First paying customer (£12-£49)
• Weeks 5-8: 5-15 paying customers with active founder-led sales; 0-2 if just tweeting
• Weeks 9-12: £300-£800 MRR is green light. Under £100 MRR is pivot or kill.

Budget twelve weeks. Most people quit at week six. Don't be most people.

Five honest pitfalls

1. The AI will confidently build the wrong thing. Claude Code will happily spend three hours on a feature you didn't need because your spec was vague. Get the spec tight first. Re-read it Sunday morning and kill anything that isn't on the critical path to first payment.

2. RLS policies will leak your data. Row-level security in Supabase is easy to get wrong. Before launch, create two test users, log in as one, and try to fetch the other's data from the browser console. If it works, your RLS is broken.

3. Stripe webhooks will silently fail. In dev, webhooks work because Stripe CLI forwards them. In production, if you haven't set up the webhook endpoint and verified the signing secret, you'll take payments and never update your database. Test it on launch day.

4. You'll optimise for the wrong metric. Lighthouse scores, bundle size — none of it matters for the first ten customers. Customer conversations matter. Refactoring with zero users is time stolen from sales.

5. You'll burn out in week four. Week four, when the dopamine has worn off and nobody's replying to cold emails, is where 80% of solo builders quit. Plan for it. Book a day off. The grind phase is the work; shipping was the warm-up.

Year-one cost breakdown

Line item	Cost (year 1)
Claude Code or Claude Pro	£200 (£17/mo)
Lovable (optional, 3 months)	£51
Supabase free tier	£0
Supabase Pro (from month 4)	£180 (£20/mo × 9)
Vercel Pro (from month 6)	£105 (£15/mo × 7)
Stripe fees (on ~£3,000 revenue)	£65
Domain (.co.uk)	£8
ICO fee	£40
FreeAgent (if VAT registered)	£171 (£19/mo × 9)
Privacy policy generator	£36 (£3/mo × 12)
Total	£856

Strip the optional bits (Lovable, FreeAgent, paid Vercel) and you can run a UK SaaS for under £300 in year one. Month one, pre-revenue, can be under £50.

Lower cost than a decent bicycle. Unlike the bicycle, this one can generate recurring revenue while you sleep.

CTA

Free report — The UK Solo SaaS Report 2026

We tracked 47 UK indie hackers who shipped an AI-built SaaS in 2025-26: what they built, how much they charged, what worked, and what killed the ones that failed. Free on IdeaStack.

Read the report →

FAQs

Q: Can I build a SaaS without knowing how to code? A: In 2026, yes — for a simple product. Claude Code and Lovable write the code. But you need to understand what you're building well enough to spec it, test it, and spot when the AI is wrong. Non-technical founders who ship spend their first weekend learning enough React to read the output, not write it.

Q: Claude Code vs Lovable vs Bolt — which? A: Claude Code for end-to-end control on your own stack. Lovable for CRUD dashboards where speed matters. Bolt for landing pages. Most UK builders use Claude Code as primary and Lovable for the initial UI scaffold.

Q: Do I need to register for VAT on day one? A: No. UK threshold is £90,000 taxable turnover over any rolling 12 months. Most solo founders stay under for the first year or two. Voluntary registration earlier lets you reclaim VAT on costs but adds quarterly returns.

Q: How much can I realistically earn in year one? A: Median for UK solo builders who ship and stick with it: £0-£500 MRR by month six, £500-£2,000 MRR by month twelve. Top decile: £3,000-£8,000 MRR by month twelve. Persistence is the main variable.

Q: Biggest mistake UK builders make? A: Copying US playbooks. US advice assumes no VAT, no ICO, and a market 5x larger. You need UK-native positioning, GBP pricing, and UK channels (r/ukentrepreneur, LinkedIn, UK newsletters) over Product Hunt and Twitter. Build for UK first, expand after.

Key takeaways

• You can ship a UK SaaS MVP in a weekend for under GBP 50, and go from idea to first paying customer in 2-4 weeks with Claude Code, Lovable, Supabase, Stripe UK and Vercel.
• The four-tool stack (AI builder + Supabase + Stripe UK + Vercel) is all you need; skip everything else until paying customers justify it.
• UK specifics matter: ICO fee (~GBP 40/year), UK GDPR privacy policy, VAT threshold (GBP 90,000), and Making Tax Digital will bite you if ignored.
• Set your Vercel function region to lhr1 (London) and use Stripe Tax with GBP-priced products, tax behaviour exclusive -- US defaults will cost you speed and compliance.
• Year one total cost is realistically GBP 100-300 lean or GBP 850 with all the trimmings; the main risk isn't money, it's quitting in week four before you've had enough customer conversations to know if it works.