What we have built, and how we build it
Most bespoke software sits behind a login, so a portfolio page can only ever show part of it. What we can do — and what we offer every prospect — is a screen share through a real system with the engineers who built it, answering questions as they occur to you.
Our delivery record is currently international rather than UK based, and we would rather say that plainly than imply a local portfolio we do not yet have. There are no invented figures on this page: where a result is stated, it describes what was delivered, not a percentage nobody can check.
Delta Hospital
Aama Jewellers
Himalayan Clean Energy
Fit and Fine
RM AgrotechDelta HospitalAama JewellersHimalayan Clean EnergyFit and FineRM AgrotechWhat kinds of problem do we actually take on?
Almost nobody rings an agency asking for bespoke software. They ring because the same order gets typed in twice, or because the director wants a number that takes an afternoon in Excel to produce. These six cover most of what comes through the door.
The process lives in one spreadsheet three people edit
A system with one record and real permissions, so two people cannot quietly hold different versions of the truth.
The CRM has no field for the way you actually sell
A CRM shaped around your pipeline instead of a licence your team works around and updates afterwards.
The same order is typed into two systems every week
An integration between them, so the re-keying — and the errors it creates — stop.
Customers ring to ask where their job is
A client portal where they can see it themselves, which removes the calls rather than staffing them.
The reports the director wants mean an export into Excel
Reporting built on the data you already hold, rather than a monthly afternoon of reconciling.
The site looks fine and produces almost no enquiries
Usually not a rebuild. Usually the enquiry path, or what the site is found for.
If none of those is quite it, the shape is usually still the same — everything we build is listed here, and what drives the cost of a bespoke system is written up in full using UK market figures rather than ours.
What should you ask about any of this?
Put these to us, and put them to whoever else you are speaking to. The answers separate an agency that built the thing from one that configured it, and that difference is invisible in a screenshot.
- 01Can we see it working, not just a screenshot? A picture proves a design existed, not that a system runs.
- 02Who on your team actually built this one, and are they still here?
- 03What was the hardest decision on this project, and what did you get wrong first?
- 04What did this client have before, and what specifically changed?
- 05Can we speak to them? A reference who will take a call is worth more than a logo.
- 06What have you built that did not work out, and why?
- 07Is this a template you configured, or something you wrote?
Four gates, and you sign off at each one
- 01
Discovery
We sit with the people who do the work and follow the process as it actually runs, including the parts nobody has written down and the workarounds everyone has stopped noticing. You get a written scope: what the system will do, what it will not do in the first release, and where the risks are.
- 02
Design
Screens and data model before any code. You see wireframes of every screen your team will use and sign them off, because changing a drawing costs an afternoon and changing a built system costs a fortnight.
- 03
Build
Delivered in stages, each onto a staging environment your team can log into and use with real-looking data. You are never waiting until the end to discover whether we understood you, which is the failure mode that sinks most bespoke projects.
- 04
Handover & support
Your existing data migrated with a reconciliation you can check before go-live, training for the people who will use it, and the source code, database schema and documentation handed over. Support afterwards on a retainer or as you need it — and if you leave, you take everything.
What people ask about the work
Why is most of your work not shown on this page?
Because bespoke software sits behind a login. A CRM, an operations system or a client portal cannot be linked to publicly, and the screens usually contain the client's own customer data. What can be shown publicly is the websites and shops; the systems are shown on a call.
Can we see a system you have built?
Yes. We offer every prospect a screen share through a real system with the engineers who built it, answering questions as they occur to you. It is a better test than a portfolio image, because you can ask it to do something and watch what happens.
Will you show our project to future clients?
Only if you agree to it in writing, and only at the level you agree to. Plenty of clients are happy for the problem to be described without being named, and that is the default rather than the exception.
Do you have UK clients?
Our delivery record so far is international rather than UK-based. We would rather say that plainly than imply a local portfolio we do not yet have, and it changes nothing about how a project is scoped, reviewed or handed over.
What happens to the work if we stop using you?
It stays yours. The source code, the database schema and the designs are handed over with the repository history, the deployment documentation and every account in your own company name, because a supplier who is hard to leave is a supplier you cannot negotiate with.
More on how we work is on the about page, and if you would rather start with the arithmetic than the portfolio, what a custom CRM costs against a per-seat licence is the comparison most buyers are actually running.
Have an idea worth building?
Tell us what you're building, improving or transforming. We'll propose a plan, timeline and a realistic cost estimate.