A short call to work out whether there is anything worth building. Tell us what you are trying to solve and pick a time. You will get a calendar invitation immediately.
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.