Turn repeat work into software that runs without you.

We design and build software for businesses, then keep it running so the work keeps moving.

Start a project

The same work, handled by hand, again and again.

Each of these is a person doing a repeatable job. Each one is a candidate for software that does the first pass, then hands the rest to a person.

9:41

Tuesday 14 October

  1. PhonenowOpenHandled Missed call after hours Voicemail, and nobody called back
  2. Leads2m agoOpenHandled New lead waiting since Tuesday Form submitted, no reply yet
  3. Inbox14m agoOpenHandled Quote request never answered Sitting in the contact inbox
  4. Billing1h agoOpenHandled Invoice 14 days overdue Reminder still typed by hand
  5. Reports3h agoOpenHandled Spreadsheet export needed again Same report, rebuilt from scratch
  6. SupportYesterdayOpenHandled Same question answered again Typed out by hand, every time
  7. Dime DataLiveRunning Missed calls become booked appointments Routed to a record, followed up on time

What we build

Six kinds of system we design, build and keep running for businesses. Each one below is a real design, with the outcome first and how it works after.

Inbound callSample call
  1. CallerHi, I wanted to ask about getting a quote.
  2. ReceptionistHappy to help. Which day suits you for a visit?
  3. CallerTuesday morning, if you have it.
  4. ReceptionistTuesday morning is open. Booking it now.

Booked for Tuesday morning, logged to the CRM

Illustrative transcript. Anything the receptionist cannot answer clearly goes to a person.

AI voice receptionist

Answers the calls that used to go to voicemail, after hours included.

  • It answers at any hour and logs every call.
  • Anything unclear is handed to a person straight away.
CRM call room screen showing a live call beside the lead it belongs to

CRM built around the call

Every call and lead lands on one record, with the next step visible.

  • We shape the pipeline around how your calls actually come in, not a generic template.
  • Follow-ups are scheduled from the same record, so nothing waits in someone's head.

Lead engine with evidence

Finds the businesses most likely to need you and shows, in plain words, why each one made the list.

  • The engine watches newly registered domains every day for businesses that fit your customer profile.
  • Each lead lists the reasons it scored well or poorly, so a person can check the thinking before anyone is contacted.
The phone view of an outreach system we built: a While you were away summary showing new leads found, drafts waiting for approval, replies and a meeting booked Approval queue where outreach waits for a person to approve it before sending

Approval-gated outreach

Outreach is drafted, reviewed and approved by a person before it can be sent.

  • Send guards are enforced in the database, so nothing goes out unapproved.
  • Agents draft the message. Nothing goes out until a person says yes.
The phone view of an agent system we built: a Today screen with agents, a needs-you item and the next suggested routine Daily view of the agent system showing today's queue of work and what needs a person

Agent automations and MCP systems

Agents that work through the day's queue and hand back what needs judgment.

  • We design a team of agents, so work is routed the way a team would route it.
  • MCP servers give agents access to the tools a business already uses, with a person in the loop where it matters.
This site's contact form filled in with a sample message, next to an alert card saying the message was saved and sent to the team

Custom web apps and sites

A site or app shaped to how the business takes work, wired to the calendar and CRM behind it.

  • This site is an example: the form you reach from the button below saves each message and alerts us within minutes.
  • Every change is checked by automated tests before it goes live.
See what we could build for you

How we work

One engineer builds and operates every system, so the person you talk to is the person who builds it.

You talk to Christian Dixon, the engineer who builds and runs your system.

  1. We scope it with you

    We map the work as it actually moves, then agree what gets built before any build starts.

    You know what you are getting before anything is built.

  2. We build it in the open

    You see each part working on the tools you already use, and you approve it before anything goes live.

    Nothing switches over until you have seen it work.

  3. We run it and keep it running

    We operate what we build and tune it as the business changes.

    The system keeps working after it is handed over.

Built with Docker Postgres Cloudflare Twilio MCP Google Calendar

Why it holds up

Answers that cite their source

Every answer our assistants give is traced back to the document it came from.

Checked before it ships

Changes to your system run through automated tests before they reach you.

A person stays in the loop

Anything uncertain goes to your team instead of being guessed.

Bring us the work that keeps coming back.

Tell us what your business does by hand each week. We will tell you what can be built, and how it would run.

Tell us what you need