Service Bespoke software

Tools built for your operations, not adapted templates.

Almost every SME works with software that only half fits: a huge CRM used at a tenth of its capacity, spreadsheets standing in for an ERP, features paid for every month that nobody opens. The business ends up adapting to the tool, when it should be the other way round.

Why it is now within reach

Until recently, bespoke software only made financial sense for a large business.

When all code was written by hand, building your own software meant months of work and a budget beyond an SME’s reach. So the usual approach became buying a generic product and adapting the way you worked to it.

AI-assisted development has changed that calculation. Building is now considerably faster, putting something within an SME’s reach that was not possible before: a tool made exactly for how it works, without paying every month for features it will never open.

What we build

Four examples of common outcomes. They are not a closed catalogue: what gets built is decided by your operations, not a list.

A small CRM
With the fields you need and nothing else: who each customer is, where things stand and what needs doing tomorrow.
An order management tool
One that follows your actual process, with the statuses you really use and notifications where you need them.
A dashboard with your numbers
Your business metrics, calculated the way you calculate them, not the way someone else’s template defines them.
An internal portal
Where your team finds what it needs first time: documents, procedures and each customer’s history.

And the software is yours: no per-user licences, no fee that rises every time someone new joins the team.

What you get

Your team adopts it because the screens speak its language: the same names, the same steps and no unnecessary features. It reflects how you really work, not how an average user works.

And when the process changes — because you open a new business line, a rule changes or you find a better way to do it — the tool changes with it. You do not have to wait for a supplier to add that feature to its roadmap.

A tool your team uses from day one and that evolves at the pace of your business.

How commissioning works: in two stages

Nobody should commission development blindly. First we define the scope; the budget follows from that.

  1. Fixed-price scoping

    A short, bounded phase in which we define what to build, in what order and with what priority. The price is agreed before it starts, so you know exactly what you are committing to.

  2. The actual budget

    The scoping phase produces the development budget, based on a defined scope rather than a guess. With that figure, you decide whether to go ahead and how much to build.

  3. Development

    Work is delivered as a project or in sprints, depending on the scope. At every point you know what is being built and how it is progressing.

  4. Monthly maintenance

    Once delivered, the tool moves into maintenance: we remain available to fix, adjust and support it as your process changes.

The first step is small and has a fixed price: its purpose is to find out what your bespoke software costs before you commit to it.

Still unsure what to build first? That diagnosis is the job of the Comprehensive AI audit: it examines your entire operation and prioritises where to start.

Automate or develop?

It is the most common question when requesting a quote, and the answer is simple.

Automate

Connecting tools you already use so they stop requiring manual work: an invoice reaching your accountant automatically, an order updating stock.

Develop

Building a tool that does not exist yet because no product on the market fits how you work. That is what this page is about.

If yours is the first case, start there.

Frequently asked questions

  • What does the initial scoping include?

    A short, fixed-price phase in which we define the actual project scope: what we build, in what order and with what priority. It produces the actual development budget.

  • How much does development cost?

    It depends on the scope established in the initial phase; there is no fixed figure beforehand because every operation is different. Scoping exists precisely to give you that number on a sound basis.

  • What happens after the software is delivered?

    It moves to monthly maintenance: we remain available to fix, adjust and support the tool as your process changes.

  • How is this different from buying an off-the-shelf CRM or ERP?

    The tool is built around how you work, with only the fields and screens you need — not the other way round, adapting your operations to a generic product.

  • Can it have AI built in?

    Yes. When it adds real value to the tool — for example, to classify, summarise or answer — we include it as standard, not as a separate add-on.

  • Is this the same as Process automation?

    No. Automation connects tools you already use; this builds a tool that does not exist yet. If yours is the first case, Process automation is the better service to talk to.

If you pay every month for software that does not quite fit your business, let’s talk.

Book an initial meeting