Websites that earn the click.
Marketing sites that load fast, rank, and convert. Hand-coded, owned by you. The first revenue line.
- Next.js · Vercel
- Edge-deployed
- Performance-budgeted
- Owned outright
Skip to main contentThe method Six builds, one P&L Row · revenue Row · ops Row · revenue Row · margin Row · efficiency Row · ops Sample engagement
Method · Read · Find · Write
Every leak is a row. Every fix is a build.
A direction for owners who already trust the numbers. We start at the row that's bleeding. The code follows the cell that doesn't reconcile.
Item
Last 12mo
After fix
Diff
1
Bookings revenue
£182,000
£208,400
+£26,400
2
Deposits secured
£11,200
£14,800
+£3,600
3
Repeat-customer revenue
£42,800
£51,200
+£8,400
4
Missed bookings — no-shows, slow replies
−£18,400
−£2,200
+£16,200
5
Late invoices written off
−£6,200
−£800
+£5,400
6
Manual admin (hrs × £45)
−£8,000
−£1,000
+£7,000
7
Margin recovered
—
+£66,600
+36%
Found · row 4The leak.
14% of enquiries went unanswered after 4pm. A two-week build closed the gap.
P&L · liveBookingsCommsRota+
UK only Owner-operator service businesses2-week Build window£10–40k Typical margin / yr 13-6 mo Typical payback
Read. Find. Write.
Three weeks reading the sheet before we write a build. The build follows the leaking row, not the brief.
- 01
Read
Two weeks reviewing the P&L row by row. Every leak gets a number with a reason next to it. We share the sheet — you see what we see.
- 02
Find
One row gets prioritised — the one bleeding the most. We propose the smallest build that closes the gap. Fixed price, fixed timeline.
- 03
Write
Two-to-six weeks. Owned outright. Documented. The diff lands on next quarter's sheet — visible, owned, repeatable.
The rows we close.
Each thing we build shows up as a row on someone's P&L. Not a deliverable on a brief. A line item that moves.
Apps the staff actually use.
Mobile and web apps for staff and customers, designed for the work as it happens.
- React Native · Expo
- Offline-capable
- Per-role views
- Tablet & phone
End-to-end booking systems.
Enquiry, deposit, reminder, no-show recovery, rebook. The full loop, not a calendar widget.
- Hold-on-message
- Stripe deposits
- Reminder cadence
- No-show recovery
Live dashboards.
Your numbers on one screen. P&L in real time, not in PDF. Decisions on facts, not gut.
- Live P&L & cash
- Per-channel attribution
- Forecast & anomaly
- Owned data
AI tools, custom.
Trained on your voice, your docs, your customers. Custom, not generic.
- Claude · GPT · local
- Routing & triage
- Auto-drafted replies
- Domain-tuned
BrainBase knowledge stack.
SOPs, contracts, training — one searchable, owned, exportable place. The opposite of a Drive folder.
- Search & semantic
- Versioned content
- Per-role permissions
- Exportable, ours-not-theirs
The clinic where one row recovered £18,000.
Six rooms. One owner. Row four bleeding £18,400 a year.
A six-room dental practice was losing fourteen percent of enquiries to slow replies and no-shows. The leak showed up clearly on row four of their P&L. Two-week build: routed booking flow, automated deposits, written-by-us reminder sequence. Year one: row four down to −£2,200, margin recovered.
+£16.2krow 4 recovery
+36%margin lift, year one
9 hrsowner admin returned per week
Open the sheet.
One call. No deck. We come prepared.
Send the brief