Stillwater Weddings
A fictional wedding photographer with no systems at all — showing what an honest build looks like when there is nothing to integrate with: the payment layer becomes the system of record for money.
Where the Time Was Going
A fictional business, drawn from a real and common shape — and the payment admin it was carrying.
Stillwater Weddings is a fictional photographer whose entire business ran on an inbox, an enquiry spreadsheet and e-signed contracts — which is to say, like most creative sole traders. Every booking meant two payments to shepherd by hand: a deposit to confirm the date, then a balance chased by email about a month before the wedding, landing in the couple’s most stressful fortnight. Fifty hand-written payment conversations a season, each one a small withdrawal from the client relationship.
- Two payments per wedding × 25 weddings = ~50 hand-typed payment threads a season, each needing follow-up, checking and a thank-you
- Balance chasing lands four weeks before the wedding — precisely when couples are most stretched and goodwill matters most
- A late balance means shooting a wedding not yet paid for, or an ultimatum to people whose day she is about to share
- Like all UK small businesses: roughly half of invoices are paid late (Xero), and affected businesses average 86 hours a year chasing (DBT, 2025)
What We Could Realistically Touch
An honest map of the existing setup — because what a third-party developer can and cannot access decides what should be promised.
Already in Place
- An inbox, an enquiry spreadsheet and e-signed contracts
- A portfolio site and Instagram
- No CRM, no booking system, no API — nothing to integrate with
What We Worked With
- Honestly: nothing to plug into — and the build says so rather than pretending otherwise
- Her own processor account — settlement straight to her business account
- Booking details typed once into a simple season sheet that generates everything else
What Stayed Untouched
- Her contracts, her inbox and her way of working — the payment layer is the only new thing
- No software to buy, migrate to or maintain
The smallest businesses often have no system at all — and the honest offer there is not a fantasy integration, it is a payment layer self-contained enough to BE the money system: every wedding, deposit and balance in one view, with a CSV her accountant can take at year end. When there is nothing to connect to, we say so, and build for that.
From Payment Page to Payment System
The page is the visible part. The build is everything that stops payments needing to be chased, matched and remembered.
- The booking-confirmation page with the open payment schedule (the demo below)
- Deposit charged at booking; the balance request sends itself four weeks before the date
- Gentle automatic reminders if a balance sits unpaid — written once, in her voice
- A season view: every wedding, every deposit, every balance, at a glance
- Automatic receipts and thank-yous to every couple
- CSV export for the accountant at year end
A couple has just confirmed their wedding date. Press play to follow both payments — without a single chase email.
A simulated, user-controlled walkthrough — fictional data and simulated system connections. No real systems are involved and nothing plays until you press play.
Try the Interactive Demo
A working page in the Stillwater Weddings branding — a fictional brand, running in test mode only.
Stillwater
Wedding Photography
Booking Confirmation — SW-1106
The Full Day Collection
Eleanor & James · Saturday 19 September 2026
The Walled Garden, Pelham Green · preparations to first dance
Payment Schedule
Your Date Is Booked
Thank you, Eleanor & James — Saturday 19 September 2026 is now held for you.
A receipt has been emailed to you.
Funds settle directly to Stillwater Weddings’ own bank account. Nothing more is charged today — we will write to you before the balance is due.
Your Card Was Declined
No payment has been taken and your date is still available. Please check the card details or try a different card.
Stillwater Weddings is a fictional brand created for this demonstration — it is not a SettlePay client and no real payments are taken.
The Part the Customer Never Sees
Every payment page comes with the management layer behind it — statuses, reminders and reconciliation that run themselves.
An illustrative view of the payment-management layer — fictional names and statuses, shown to demonstrate the workflow.
What That Adds Up To, Honestly
Quantified from published UK industry figures — and labelled as the model it is, not passed off as a client result.
Requests, reminders and receipts compose themselves — the conversations that strained client goodwill simply stop happening.
The four-weeks-out request sends itself even in peak season — late asks were the single biggest cause of late balances.
Roughly 45 minutes of chasing, checking and matching removed per wedding — time that was coming out of editing evenings.
How These Figures Are Modelled
- No reliable published figures exist for wedding suppliers specifically, so this scenario leans only on cross-sector data: roughly half of UK small-business invoices are paid late (Xero), and businesses affected by late payment average 86 hours a year chasing it (DBT / Small Business Commissioner, 2025).
- 25 weddings a year, two payments each, ~45 minutes of combined chasing and reconciling per booking — our assumptions, stated so you can swap in your own numbers.
Like the business itself, these figures are illustrative: a scenario modelled on published UK industry averages, not measured results from a real client. Your own numbers will depend on your volumes and on how you get paid today.
Now Try It on Your Own Numbers
Drag the sliders to your business. The figures recompute live, costed against the same UK data.
And the balance request sends itself four weeks out — even in peak season — so the awkward money chase at the worst possible moment simply stops.
A model, not a measured result: what your hour is worth and time-per-item are yours to set, costed against published UK figures. Your own savings depend on your volumes and how you get paid today.
How It Connects
Behind the page, every payment carries its reference — an invoice number, tenancy, lot or mandate — so it is matched back to the business's records automatically, reminders go out on schedule instead of from someone's evening to-do list, and the books update themselves. Funds settle directly from the processor to the business's own bank account; SettlePay never holds funds. Payments are processed by FCA-regulated partners.
What Would This Look Like on Your Numbers?
Tell us how you get paid today — bank transfers, cheques, card numbers over the phone — and what systems you already run. We'll map what we could realistically automate for you, and what it would save.