Questions, answered plainly.

We look at one problem with you for 30 minutes and tell you honestly whether it's worth fixing. If it isn't, we say so, and there's no pitch.

It depends on the job, so we don't quote a number before we've seen it. For businesses, the Ops Map ends in a fixed price for the build. For startups, the scoping session does. Either way you know the price before any build starts.

US hours. We're a senior-led team, and the people who build your system are the people you talk to.

The 21 days start on the day we have the access we agreed we need: logins, API keys, repositories and so on. If what we agreed isn't working 21 days after we get access, you get the build fee back. The full conditions are on our guarantee page.

The build fee is split in two. The second half is only paid once the build does what we agreed it would do.

Then you get your money back and keep the plan. The same applies if, within 7 days, you feel it wasn't worth it. The full conditions are on our guarantee page.

The ones you already pay for: your CRM, project tool, accounting software, forms and email, plus Zapier or Make if you use them. We use what they can already do before we build anything new.

No. It's about the hours your team spends copying data between tools, chasing updates and retyping. That time goes back to the work you hired them for.

No. The new system runs next to the old way of working until it works. Your team only switches over once it's doing the job.

We keep it running. With Ops Care we watch it, fix it, make small changes, re-check it when your tools or the AI change, and report the hours saved. You get a reply within 4 business hours and a fix within 1 business day, or that month is half price.

Once your first build is working, the monthly plan adds one new automation every month on top of Ops Care. We agree each one with you, build it the same way, and it joins everything else we look after.

An AI feature added to your product, a first version of a new product, a prototype made solid enough for real users, or a senior engineer to own the build. All of it in production code, front end to back end.

Yes. A demo that breaks with real users is one of the most common things we're asked to fix. The scoping session looks at what's there and fixes a price for making it solid.

Yes. We build in your repository, in production code your own engineers can read and take over. If you don't have a codebase yet, we set one up that you own.

Yes. A dedicated senior engineer is available on request, to own the backend and the AI inside your team, on US hours. We agree exactly what they own in a scoping session first.

You do, from day one. We build in accounts you own, the code lives in your repository, and the keys are yours. If we stop working together, nothing has to be moved or bought back.

We sign an NDA before we see anything. We work in your accounts with access you give us, and that access is removed when the work ends. Our security page has the details.

Anything the AI does for your customers or your money is checked by a person until it's accurate. You see what it gets right and wrong before anyone relies on it.