Tell us what you need

Describe the problem,
and we will tell you what it takes.

This is the fastest way to a useful answer. The more precisely you can describe what is going wrong today, the more precisely we can tell you what fixing it involves, and whether it is worth doing at all.

Every system is scoped and built around the business it runs in. What follows is the shape of the work, not a specification.

What happens after you send this
  1. 01Every request is read in full. It does not go into a queue.
  2. 02If it is a fit, a scoping call: what is actually wrong, what it would take, and whether the return justifies the build.
  3. 03An indicative range comes after that call, not from this form. A firm number comes after scoping, when there is something real to price.

The primary question. What is going wrong, who it affects, and what it is costing in time or missed work. At least twenty characters.

The manual process, who does it, and roughly how long it takes them.

In your own words. Whatever you actually use.

Optional, and only if you have one. It helps rule out a build that was never going to fit.

If what you need is smaller than what we build, or a tool you can buy already does it, we will say so and point you at it. That is a cheaper outcome for both of us than a badly fitted engagement.

Would rather just talk? Book a scoping call

Questions. Asked before every engagement.

Your data is yours. You can export it at any time, and it is exported to you in a documented format before any engagement closes. The software itself is licensed: we build it around your business, host it, and run it, and you pay monthly for that. If you'd rather own it outright, that's possible. It's a different kind of engagement and it's priced accordingly. Licensing keeps maintenance our problem rather than yours, which is why it is the default.

Two weeks' notice, either side. Your data is yours. You can export it at any time, and it is exported to you in a documented format before any engagement closes. The system stops running. If you'd rather keep it running, the ownership option is available at that point as well. Ending the retainer doesn't force you to lose what was built.

Typically four to eight weeks from signing to a working system, depending on how many tools it connects to and what state the data is in. A scoping conversation and a written plan come first, so the timeline is agreed before anything is committed to.

Access to the tools and data the system will work with, one person who can make decisions, and a few hours in the first two weeks while we map how work actually moves through your business. After that, very little. The point of the engagement is that it runs without your attention.

Usually. Most business software exposes an interface we can build against, and where one doesn't there's normally a way around it. Which connections are viable is settled in the scoping conversation, so you find out before committing rather than after.

Hosting region for a system we build for you is decided at the start of the engagement, not inherited from a default. If data residency is a hard requirement, raise it in the first conversation and we will tell you plainly whether we can meet it. This website is separate and its processing is already fixed: enquiries, quote requests, bookings and chat are handled by Supabase in Tokyo, Resend in Tokyo, Cloudflare, cal.com and Moonshot AI, which the privacy policy names individually along with where each one processes. Nothing from a client system is ever sent to the chat assistant.

That's the normal starting point, and mapping them is part of the work. Automating a process nobody has examined just makes the confusion faster, so we don't start there. The first phase establishes how things actually happen, as opposed to how they're supposed to.