Fair questions.

You do. The system runs in your Microsoft (or Google) tenancy, the code lives in a repository your business owns, and every subscription is billed to you. If SKEP disappeared tomorrow, nothing you rely on goes with it.

Your data stays in your own accounts — your tenancy, your database, your logins. Where AI services are used, they are configured on business terms that do not use your data for training. The governance section on the home page describes how access is restricted and recorded.

$350 per block, per month, plus $19 per user, per month. There is no build fee, no deposit and no minimum term, so the cost of starting is one month. The full model is on the process page.

Weeks, not quarters, for a first working system — because nothing starts until the specification is agreed, the build itself moves quickly. A live pilot with real users typically follows within two to three weeks of the Design stage closing.

No. Often the right answer is to keep the tools that work and connect them so information stops being retyped between them. Replacement is a choice you make per tool, over time — not a precondition.

You receive documentation, admin access and the source code, and your team is shown how to run the system day to day. Support, monitoring and continued development inside a block's scope are part of the monthly charge, not a separate retainer. The measure of a good handover is that you don't need SKEP to keep the lights on.

Two ways. These systems are specified by someone who spent ten years working inside a real business, across several parts of it and across every system it ran — the spreadsheet being replaced has usually been lived in, not just looked at. And AI-assisted delivery means the economics are different: work that priced at enterprise scale a few years ago is now within reach of a fifty-person firm.

If one person spends part of every week retyping information from one place into another, the business is big enough for the maths to work. The Design stage exists partly to answer this question honestly — if the numbers don't stack up, that's the finding, and it's yours to keep.

Messy processes are the normal starting point — growth causes mess; that isn't a failing. The Design stage maps how the work actually runs, including the workarounds, before anything is committed to software. Systems built on an idealised process fail; systems built on the real one stick.

Yes — references are available on request once we're in conversation. Client work is described on the work page in as much detail as each client has approved.