00 Custom software
When the spreadsheet, the shared inbox and the off-the-shelf tool stop fitting the way you work, we build the app: CRMs, client portals, booking and internal tools, with AI only where it does a real job.
01 What we build
One place for every lead and customer: who owns it, where it stands, what happens next. Built around your own stages, not a template's.
A login where clients see their documents, their status and your messages, instead of chasing you by email.
The figures you put together by hand every Monday, live from your own data, with each person seeing only what they should.
Bookings, reminders and capacity across people, rooms or sites, in one diary everyone trusts.
The spreadsheet that quietly became a system, rebuilt as a proper tool with permissions and a history of who changed what.
Suggesting a reply, sorting an enquiry, summarising a thread, with a person approving anything that matters. Never as decoration.
02 How we build
01 · Listen
A thirty-minute call, then time with the people who use the spreadsheet or the shared inbox today. We want the real process, workarounds included, before we draw a single screen.
02 · Map
We draw the work as it runs now and as the app would run it, then agree the smallest useful first release. Roles, permissions and an approval step go in wherever a person has to sign off.
03 · Build
You see real software on your own data from the first release, not a reveal at the end. An audit log records who did what and when, so nothing depends on anyone's memory.
04 · Run
We host, monitor and look after the app, or we hand it over with the documentation to run it yourselves. Either way you get a person, not a ticket queue.
03 When not to build
If what you need is one of these, it is the lighter answer, and we would rather point you there than sell you an app.
The work is the same few steps between tools you already own: triage, filing, chasing. A workflow behind those tools does it, with no new app for your team to learn.
Read moreYou are happy with your tools and want something working inside them: reading enquiries, updating the CRM and handing anything unusual to a person.
Read moreStaff or clients keep asking questions your own policies already answer. An assistant that answers from those documents and shows the source it used.
Read moreYou know something is wrong but not what to build. We map how the work runs first, then tell you what is worth doing and what is not.
Read moreRun a lettings agency? Start with AI for letting agents and property managers, which covers the front desk and the back office.
04 How we quote
Two to four weeks
Eight to twelve weeks
Rolling monthly
A number on a website is priced to the website, not to your process. We quote each build as a fixed figure after a discovery call, once we know how many people use it and how many other systems it talks to. Hosting and third-party fees are listed separately and agreed before anything goes live.
05 Hosting and handover
Built in the UK. Hosted on managed servers in the EU, under UK GDPR, with backups, monitoring and updates handled. Or we hand it over with the documentation to run it yourselves. Either way, the code and the accounts are yours, so nothing sits behind our login.
Hosting with us is a service you choose, not a lock-in. If you want to move it later, or bring it in-house, the handover is written so another competent team can pick it up without us.
06 Software we run ourselves
Smiles Tracker and Evergreen both came out of recurring client work. We built them, we host them and we answer when something needs fixing, so we know what keeping software alive takes.
A CRM built for dental clinics. Clinic teams see every enquiry on a board, answer from message templates drafted with AI help, and keep each patient's history on one record.
Read moreSearch content from research to publish in about twenty minutes per article. Four UK businesses publish with it.
Read more07 Case
A multi-location services group wanted head office to see across every site without making every site work the same way. We built it rather than bend an off-the-shelf tool.
CaseMulti-location services groupUK · anonymised
Head office sees across the group. Local teams keep the way they already work.
Multi-site CRM case study6
Locations live
Each site has its own inbox, pipeline and permissions.
0
Leads lost to email
Measured across fourteen months in production.
14 mo
In production
Stable daily use across the group.
Names redacted out of respect for our clients.
08 Questions
Cost, timing, ownership and what happens when someone else built it first, answered the way we would on a call.
It depends on how many people use it, how many other systems it talks to and how much of your process it has to carry, so we do not publish a rate card. After a discovery call we give you a fixed quote for the first release, with hosting and any third-party fees listed separately. We would rather build the smallest useful version first than quote a big number for a big plan.
A focused first release is usually live in two to four weeks, so you are using real software on your own data early. A bigger build, with several modules, integrations and staff handover, tends to take eight to twelve. We build in stages on purpose: you use the first part before you commit to the rest.
You do. The code, the accounts, the credentials and the documentation are yours. We can host and look after the app for you on managed servers in the EU, but that is a service you choose, not a lock-in. If you ever want to move it or bring it in-house, the handover is written so another competent team can pick it up.
Yes. Most software earns its keep by sitting between the tools you already use: your email, WhatsApp, accounting package, calendar or database. Before any budget is committed, we check what each tool lets us read and write, and we say so plainly if one is too closed to rely on.
No. Plenty of good software has none. We add AI only where it does a real job, such as suggesting a reply, sorting an enquiry or pulling fields out of a document, and always with a person approving anything that matters. If what you want is AI working inside the tools you already have, rather than a new app, that is AI agents.
Usually, yes, once we have looked at it. We start with a short review of the code, the hosting and the documentation, and tell you plainly what is sound, what is fragile and what we would change first. Then you choose: we look after it as it is, fix the weak parts, or rebuild the pieces that are not worth keeping.
09 Enquiry
Tell us what the tool would do and who would use it. We will tell you what we would build first, and if software is the right answer at all.