Run · Custom tools and apps

Software built for how you work.

When no off-the-shelf tool fits, we build one: internal dashboards, booking systems, customer portals, WordPress plugins, Shopify apps, and management systems. Built in-house, documented, and handed over in your name. A small tool takes a few weeks; a full system is scoped and quoted in stages.

01

Is this you?

02

What you get

03

How it works

  1. 01

    Audit

    Free

    What the tool has to do and what it replaces.

    Your part: Show us the spreadsheet or process the tool will replace.

  2. 02

    Scope

    One to two weeks

    Screens, data, integrations, cost.

    Your part: Read the scope, cut anything you don't need, and approve it.

  3. 03

    Build

    In stages

    Each stage usable before the next begins.

    Your part: Use each stage as it's delivered and tell us what's missing.

  4. 04

    Hand over

    At the end

    Training and written notes.

    Your part: Bring whoever will run it day to day to the training.

04

What it costs to run

Hosting and any API fees, written into the quote per project. Usually a small monthly amount.

Third-party costs are paid straight to the provider. Our fee is separate and quoted after the audit.

05

Proof

E-commerce, our own brand

A candle and humidifier brand, built from nothing, where bundles became the best sellers.

Candellic sells scented candles and humidifiers. We built it from zero and run everything: the store, the theme, the ads and the video ads.

OutcomeThe bundles sold through our own bundle builder are now the store's best sellers, and the ads are measured against real purchases, not clicks.

Read the case study

06

The tools we use

  • Node.js
  • React
  • WordPress development
  • Shopify development
  • PostgreSQL
  • Cloudflare

Named, not sold. The tool is the detail; the judgement and the setup are the work.

07

Questions

Isn't custom software expensive?

Compared with a subscription that does half the job for years, often not. The scope tells you the number before you decide. Building in stages also limits the risk. If the first stage doesn't earn its keep, you stop there.

Who owns the code?

You do, from the first commit. It lives in a repository in your name, and the hosting account is yours too, so nothing depends on us staying involved.

What if you're not available later?

The code and notes are yours. Another developer can continue from them.

Can you add AI to it?

Where it helps: summarising, drafting, classifying, answering. We say where it doesn't. AI usage is a running cost, so the scope states what each AI feature should cost per month before it is built.

What does a custom tool usually replace?

A spreadsheet several people edit at once, a stack of subscriptions that each do part of the job, or a manual step between two systems. If an existing product does the job well for a fair price, we tell you to buy it instead.

How long does a small tool take?

A few weeks for something like an internal dashboard or a booking page. Larger systems are split into stages, and each stage has its own date in the scope. You see a working version early in each stage, not only at the end, so changes are easy to make.

Can it connect to the software we already use?

Usually. Anything with an API or an export can feed the tool or receive data from it. The scope lists every connection before we start.

Who looks after it once it's live?

You can, with the notes we hand over, or another developer can. If you want us to keep it updated, that is agreed separately and is never a condition of the build.

Related

Often bought together

Free audit

Find out whether the tool you need already exists, or should be built.