Skip to content
Onboarding

What happens
after you say yes.

Many owners have been burned by a supplier who went quiet after the deposit. So here it is up front: what we do, when, what we need from you, and how you get every key back.

The shape of it

Nothing starts until the boring parts are done.

Nothing gets built before the paperwork is signed and the access works. A job that opens with two weeks of “still waiting on the DNS login” spends its goodwill early. How long the build takes is set in the scope you approve.

  1. Within 5 days of signing

    Kickoff

    An hour with everyone from the consultation, plus whoever holds the keys to your systems. We walk the scope one last time: the last free moment to say “that is not quite how it works”. Access requests start live on the call, not as a list emailed afterward. A written summary lands the same day.

    What we needThree names: who decides, who does the work, and who holds the logins.

  2. First week

    Something to look at

    By the end of week one there is a URL you can open. It will look unfinished, on purpose: it surfaces misunderstandings while they still cost nothing to fix.

    What we needAccess, per the checklist we start on the kickoff call.

  3. Through the build

    A rhythm you can set your watch by

    A written update the same day every week, even when nothing moved. A half-hour call you can skip. Staging you can open whenever you like, without asking. If a date is going to slip, you hear it in the next update.

    What we needAnswers within a couple of days, and your content by the date we agreed.

  4. Whenever it comes up

    Changes, priced before they happen

    Changing your mind halfway through is normal and we plan for it. Anything outside the scope gets written down and priced, and you approve it before a line of it is built.

  5. Before it goes live

    You use it first

    Not a demo. Whoever will live in the thing does a normal piece of their work in it while we take notes. Most of what is worth changing surfaces in that hour, and nothing goes live before it.

    What we needAn hour of the person who will use it most, and sign-off in writing.

  6. One morning

    Go-live

    A Tuesday or Wednesday morning. Never a Friday, never before a holiday, never while the person who depends on it is away. Someone watches the first hour. The rollback is written down before we begin, and every path is walked by hand on the live system within a day.

  7. Handover week

    It becomes yours

    Training with the people who will use it, in your systems, on your work. Short recorded clips, one per task. Documentation you can edit yourself. Every account in your name on your billing. Every piece of access we were given, handed back and switched off.

    What we needRotate the passwords we were given. We will remind you.

  8. 30 days after go-live

    The thirty-day review

    A month is how long it takes for the awkward cases to turn up. We look at what gets used, what broke, and whether the hours we predicted were real, including where we were wrong. If nothing more is needed, that is a good place to stop.

Your side

Four things we will need.

None of them is hard, and each one decides whether the dates hold. A late project is usually late here, not in the building.

  • One person who can decide

    Reachable within a couple of working days. Builds stall far more often waiting for a choice than on hard problems.

  • Your content, by its date

    Copy, photographs, documents, team details. It is the most common reason a project runs late, so we say it on day one.

  • An hour of the person who does the work

    For demos, and for the session before go-live. Their time is the most valuable input, and the easiest to under-book.

  • A heads-up on anything in flight

    An office move, a software migration, a partner retiring, a busy season. None of that is a problem. Learning about it in week three is.

Access and your data

How we ask for the keys, and how you get them back.

At some point we need access to the systems your business runs on. If you hold client files, patient records or payroll, how a supplier asks for that access matters more than anything else on this site. Here is our answer before you ask.

  • We will never ask you to email us a password

    Not a password, not an API key, not a recovery code. Mailboxes get backed up, forwarded and, in a lawsuit, read by the other side. If a secret has to move, it travels through a one-time link that expires, and you change it at handover regardless.

  • We ask to be invited, not to be given your login

    You add us as users on systems you already control, with the narrowest permissions that do the job. Never a shared account. Never yours.

  • You can switch us off at any time

    Without asking, without notice, and without breaking anything you have paid for. We keep a written register of every access we hold, and hand you that same list at the end with every line struck through.

  • Your data does not go into a chatbot

    Not into a consumer AI tool, and not as an example in somebody’s prompt. If any part of a build would send your data to a third-party AI service, you are told which service and asked in writing first. You can say no and still have the build.

Before any of this

It still starts with a conversation, and the conversation is free.

None of it applies until you have had the call, read the written summary, and decided there is something worth building. Stopping at the summary is a good outcome.