
Overshoot
A motion lab for designers — tune the spring by feel, race it against any curve, leave with the CSS.

Working from Stamford
375+
apps built on Base44
12
built from one prompt
72
AI agents in production
20+
years shipping software
Base44 Ambassador · Stamford, Lincolnshire
I build on Base44 most days and run my own businesses on what I build. The Ambassador role puts that in a room in Stamford, Lincolnshire: free, hands-on sessions where you bring a real problem and leave with a working app.
Everything I have learned getting there is on this page, published in full.
30 live builds on this page, each written up with the prompt behind it, plus the free prompt library. Read them, copy them, use them.
Browse the free promptsFree, hands-on sessions for people who run things and want to build with AI. No session is confirmed yet. Join the list and you hear as soon as one is.
See the sessionsA fixed-scope Base44 build: entities, access rules, payments and email wired and tested, in a number of working days agreed before the start.
See the build offerEvery one started as a question asked in the Base44 Discord. Each page gives you the sixty-second checks to run first, then the prompt to paste into the builder chat — because most of the time you do not need the prompt.
The offer
You bring the idea and the data. I build the app. Entities, access rules, payments and email, wired and tested, in a fixed number of working days agreed in writing before the start.
Not a mockup. Not a prototype you then pay someone else to finish. Not a quote that grows once the work begins.
A running app
On its own URL, with you as the admin from day one.
The data model
Every entity and every field, written down, not left in my head.
The access rules, read back
Who can see what and who can change what, in plain English.
Payments and email, wired
Checkout and transactional email working end to end, with the test log.
The tests
What was checked, how, and what it does when a check fails.
The handover
The keys, and the walk through of how to drive it.
Built on it myself. 375+ Base44 apps and 72 agents in production. The builds below are from that list.
Price
Given on the enquiry.
One fixed price for the agreed scope. You get it on the first reply.
Five minutes. It goes to the same form as the Sprint, and I read it myself.
Or build it yourself on Base44, opens in a new tabBase44 links on this page are affiliate links. If you sign up through one, Dean may earn a commission at no extra cost to you.The builds
Each card links to the build and the prompt behind it. The full list is one click away.

Start here
A regulated, multi-tenant fundraising platform used by 1,000+ clubs, charities and foundations.

A motion lab for designers — tune the spring by feel, race it against any curve, leave with the CSS.

A business-in-a-box for independent travel advisors — quotes, client portal, commissions and billing.

A cozy idle tycoon built as a road trip — and a reusable, dependency-free game engine underneath it.

The calm baby tracker — two taps, one-handed, in the dark, shared properly between both parents.

A style-led wedding venue directory — couples shortlist and enquire, venues and suppliers quote back.

Every non-league table, fixture and result. 22 seasons. Free forever.

A family meal planner that plans round the people, not the recipes.

A specialist sports-travel group running on a 42-entity CRM with its own in-house AI copywriter.

A 0–100 Work-From-Here score built only from filed field reports — never scraped, never estimated.
The method
The apps below aren't the result of a clever sentence. They're the result of a structure. Same nine sections whether it's a game, a ledger or a suite of 24 tools — and skipping any one of them shows up in the output within seconds.
01
What it is, in a sentence a stranger understands. If you cannot write it, the app has no shape yet.
02
The ten seconds that make someone say "wait, what?". Name it explicitly or the build will hide it.
03
Every entity, every field, every type. This is the single biggest quality lever, and almost nobody does it.
04
Screen by screen, in nav order, with the one interaction that matters on each.
05
Named calls with the response schema written out. Never let the interface parse free text.
06
Palette in hex, typeface, motion, density. Vague design instructions produce generic output. Every time.
07
Populate on first run. An empty app reads as a broken app, and you only get one first impression.
08
What not to do. Most one-prompt builds fail the same four ways: auth wall, no loading states, broken on mobile, blank first screen.
09
Acceptance criteria the build can check itself against. Without this you get something plausible instead of something finished.
None of this is secret, and publishing it costs me nothing. The method isn't the hard part — knowing which nine things to specify, and having built enough to have opinions about them, is.
The nine-part structure behind every prompt on this page. Data model first, guardrails, seed data, acceptance criteria. Plus one worked example, in full.
For anything tagged "One prompt", yes. One message, no follow-ups, no patching. The data model, the integrations, the guardrails and the seed data all came out of that single message. Everything else was built normally, over several passes.
No. Base44 builds the application and the prompt is plain English. What you do need is to know what to specify, which is the point of the method above and the reason the prompts are long.
Sometimes it does. A build that lands at 80% is a different attempt, not a patch job. Re-run the same prompt with the weak section expanded. That is cheaper and cleaner than trying to talk the model into fixing itself.
Because the method is not the moat. Anyone can read a prompt. Far fewer will build hundreds of apps and develop a view on what matters. Publishing the how is what makes the claim credible.
The Vault
Anyone can describe an app to an AI and get something back. The difference is in the structure — and the structure is what's written down in here.
Every build prompt on this page
Full text, not summaries. Copy and run.
313 production Claude skills
Installed, organised, documented.
The scaffold and the method
How the prompts are structured, so you can write your own.
Cancel any time. Or read the free prompts first — they're the same standard as the paid ones, which is rather the point.
The site keeps essential storage so it works, and the site and its hosting platform count visits anonymously, with no cookie. Accept and Google Analytics, which sets cookies, counts visits too. Decline and neither the site’s own count nor Google Analytics runs. Nothing creepy. You choose.