Five shapes of bespoke software.
Software is the product. The shape it takes depends on what your operation actually needs.
Custom platforms.
Full applications for customer-facing workflows or revenue-generating operations — the system the business actually runs on. Built around how the work moves, not around what a vendor was willing to sell. Booking platforms, marketplaces, member portals, ops consoles, and the public-facing products you don't yet have.
Example. A residency-booking platform with integrated payments, customer accounts, and the admin tooling the studio runs from — built and shipped in four weeks for Potter Sanctuary.
Internal tools.
Admin systems, operations dashboards, purpose-built CRMs for how your team actually works. Keyboard shortcuts, bulk actions, and the screens that vendor software refuses to give you. Designed by an operator who has used the spreadsheet you're trying to replace.
Example. A renewal-quoting console that batches 3,200 quotes into one tabular view, with keyboard nudges that cut the controller's Monday from four hours to thirty minutes.
AI-visible web presence.
For businesses with no site, or whose current site is invisible to ChatGPT, Claude, Perplexity, and Google AI Overviews. Engineered to be cited by AI search engines, not just indexed by traditional ones. Schema.org graphs, llms.txt directive layers, direct-answer markup, and the editorial register that AI engines surface verbatim. Indexed by Google is a side effect, not the goal.
Integrations & automation.
Connecting the systems you already run so they behave like one. Webhook plumbing, state reconciliation, and the operator UI to fix things when they drift. ERP ↔ Stripe, CRM ↔ inbox, payment provider ↔ ledger — and the dashboard that tells you when something didn't line up.
Example. A nightly job that reconciles three subscription providers against a single customer ledger and surfaces the diffs in a Slack channel before the morning standup.
Legacy replacement.
Retiring a fragmented SaaS stack or an aging custom system, in pieces, without a sixteen-month replatform. Cut over one workflow at a time. The old system stays live until the new one is honestly better. The first engagement targets the workflow with the worst fit and works outward from there.
Example. Replacing a $4k-a-month subscription with a custom internal tool, then absorbing the next two adjacent workflows in subsequent four-week engagements.
Common questions.
How long does a build take?
A fixed four-week cycle. The brief is written and signed off on the Monday of week one, the build runs through the weeks with a staging URL by day three, and you go live on the Friday of week four.
Who owns the code?
You do, from day one. The source repository is transferred to your organisation at launch, with a runbook and a walkthrough. No lock-in, no per-seat licence on your own software.
What does it cost?
A fixed fee agreed before the build starts, scoped to the four-week cycle. You know the number up front, with no hourly surprises.
What kinds of software do you build?
Five shapes: custom platforms, internal tools, AI-visible web presence, integrations and automation, and phased legacy replacement. If your problem doesn't match a shape, that's the conversation worth having.
Can you replace our existing SaaS without a long migration?
Yes, in pieces. We cut over one workflow at a time, starting with the worst fit, and the old system stays live until the new one is honestly better. No sixteen-month replatform.
What makes a site AI-visible?
It is engineered to be cited by AI search engines like ChatGPT, Claude, Perplexity, and Google AI Overviews, not just indexed by traditional search. Schema graphs, an llms.txt directive layer, direct-answer markup, and an editorial register these engines surface verbatim.
Don't see your shape?
If you have an operational problem and you're not sure what shape the answer takes, that's exactly the conversation worth having.
Start a conversation