Support

Custom software for the way your business runs, AI voice agents that answer your phone, AI automation for the repetitive work, mobile apps for staff or customers, integrations between the tools you already pay for, and SaaS products you sell to your own customers. If the sentence "the same information gets typed into three different places every day" sounds like your week, that is our work.

No. The people we build for run hotels, schools, clinics, engineering firms, shops and restaurants. You are the expert on how your business actually works; our job is to understand it well enough to build it. If you ever need a progress update translated, we have written it badly.

Usually not, and usually you should not. Most of this work sits alongside what you already run and talks to it. Replacing a system that works is a big, slow, risky project, and we only recommend it when the old one is genuinely the thing holding you back.

A focused internal tool or a voice agent is usually a matter of weeks. A full platform, or a system several teams depend on, takes longer. You get a scope and a timeline in writing before any code, and something you can click within the first few weeks rather than a reveal at the end.

We work with teams in other time zones as a matter of course. We agree a window that overlaps your working day for calls, and keep everything else written down so nobody is stuck waiting for a conversation before they can make progress. In practice the gap works in your favour more often than against it, because work happens while you are asleep.

The people writing the code. There is no account manager relaying your messages to a delivery team you never meet. You get a short written update on what moved, what is next and anything we need from you, plus a call when there is something to look at rather than one booked out of habit. If you find yourself chasing us for a status, we are doing it wrong.

We scope the work first, then put a price for that scope in writing before anything is built, with payments tied to milestones rather than an hourly meter running quietly in the background. If the scope changes -- and on most projects something does -- we price the change and you approve it before we start on it.

Because a number without a scope is a guess dressed up as a quote. Two booking systems that sound identical on a phone call can be a month of work apart. Tell us what you need and you get a real figure for your actual project, in writing, before you commit to anything.

Two separate things. First, hosting and any paid services the system uses -- these are billed to your own accounts by those providers, at their price, not marked up through us. Second, our time, if you want us on hand for changes and fixes. We show you both before you commit, and the first one keeps working whether or not you keep the second.

You do. The source code, the data, and every account it runs on -- hosting, domain, app stores, payment provider, AI providers. All in your company name. We work inside your accounts rather than ours, because an agency that owns your App Store listing owns your app.

You can, and we build so that stays possible: standard tools, ordinary patterns, no proprietary framework of ours in the middle, and written documentation an incoming developer can read without ringing us. Being difficult to leave is not a business we want to be in.

Real use finds things that testing does not, so we stay on through the weeks after launch to fix them. After that it is your call: keep us on a small monthly arrangement for changes and fixes, or hand it to your own developer. We set it up so either one works, and we say which we think fits you.

Email us, say what has stopped and say that it is urgent. We are a small team rather than a round-the-clock desk, and we would rather be straight about that than sell you a guarantee we could not keep. What we do build in is monitoring and alerting, so a failure raises an alarm instead of waiting to be discovered by an annoyed customer on Monday.

In your own accounts, hosted in the region you need it to be in -- which matters if you are subject to rules about where records may be kept. Inside the system, access is by role, so people see what their job needs and nothing more, and sensitive actions are logged. On our side, we hold access while we are working for you and hand it back when we are not.

No. Where we use AI providers we use the business tiers that exclude your data from training, and for genuinely sensitive work the processing can stay inside your own infrastructure. If a specific regulator or contract sets a rule on this, tell us at the start and we will design to it rather than around it.

It will, sometimes. Anything that reads a document or answers a phone gets things wrong occasionally, and a supplier who tells you otherwise is selling. So the review step is built in: a confidence score on what it extracted, a person checking anything involving money, health or a contract, and a hand-off to a human the moment it is out of its depth. Before you rely on it, we run it quietly alongside your team and show you exactly where the two disagreed.