The whole engagement, written down.

You write to us through the form on the home page, with your name and how to reach you. What you send is recorded, and a person reads it. We do not answer scope questions by email, and that is not a policy for its own sake: the first conversation is where the read happens, and a read done by email is a guess with a signature on it. If you want to come prepared, bring the tools you actually log into in a week and the name of the person the work between them lands on.

If a conversation follows, here is the whole of what happens in it, so none of it is a surprise. Edwin asks what you run and where the work piles up, there is nothing presented and there are no slides, and you leave with three things whether you hire us or not. Three numbers are worth having to hand: roughly how many hours a week go on moving things between two systems by hand, whose hours those are, and what an hour of that person's time is worth to the business. A close guess is fine, and if you have none of them we still get there.

No deck, no capabilities document, no sample of the work and no NDA is sent before the conversation, and each absence is deliberate. An NDA sent before anything has been said asks you to sign something to hear a sales pitch. The findings are not sent in advance either. A finding read alone the night before arrives with its counterargument already written, so they are delivered in the room, one at a time, with a person in front of you.

Edwin runs it and nobody else does. Most of it is questions, and the questions are about your business, not ours: which tools you log into, where something gets copied out of one and typed into another, who does the copying, what never quite gets done, who reads a thing before it reaches a customer, and who would be the name on the approvals if we did this. Then we tell you what the system cannot do before we tell you what it can. Then the arithmetic, done in front of you out of numbers you said in the room: what carrying the work by hand costs you today, in your figures, never ours. That is your current cost. It is not a saving we promise.

You leave with three things, out loud, whether you hire us or not. A straight read on whether this fits. Where the work is leaking between your tools, two or three seams, in your own nouns. And a fixed build quote, which stage 03 then puts in writing. If the honest answer is that this is not for you, you hear it on the call.

What was said on the call is repeated in writing after it, so it exists as a document you can forward to a partner or to counsel. It is written to be forwarded: short sentences, real nouns, no adjective doing a fact's job. If the answer was no, the written read still goes out. That is what "whether you hire us or not" means.

The quote is one document, the Order Form, issued unsigned. It names the build fee as one figure, the license fee as one figure a month, each milestone amount and what triggers it, how many lanes, connected systems and named approvers, the monthly generation envelope, and the term. It contains no timeline and no guarantee. And it does not move after you sign. The detailed scoping happens after signature, inside the build fee, and it cannot change the figure.

Yes means two documents signed together: the Build and Operate Agreement and the Order Form. The first milestone falls due at signature. Before you sign, any connected system that could not be handed back to you on exit is named on the Order Form. Nobody signs without knowing which of their systems that applies to.

Two columns, and a buyer's counsel will ask about both.

This is where the build gets found out. It produces one document, the Statement of Work, signed by both sides. It settles everything in the second column above. Your named approvers are named in it. The systems we connect are listed, each with how it is held: in your own account, or through a relationship we hold. If the second, it is one you already saw on the Order Form. The acceptance criteria for go live are written here, before a line of the lane is built, so acceptance is never an argument at the end. Timing is set here too, in the plan, after we have seen your systems and not before.

The build runs in nine phases. They are the same nine the pricing page estimates hours against.

Go live means one thing on this site and it is the sharpest line in the engagement: the system is proven working on your live surface, against the accounts you actually run, against the acceptance criteria written into the Statement of Work at scoping. Not a demo. Not a staging copy.

Those criteria are written to be watched happening rather than argued about, and four of them are the same in every engagement. Every lane prepares work end to end and the prepared work reaches your approval chain. Every connected system is proven reading or writing as its row says it does. A named approver of yours releases at least one real item, and that release is visible in the audit trail. And the audit trail is live, exportable by you, and verified against a real record. Criteria specific to your business are written in beside those four, at scoping, by you.

After the demonstration you have a written window, set in your Statement of Work, to accept in writing or to state in writing what was not demonstrated. The last milestone falls due here and nowhere else, which is the reason it sits here. The license fee starts here. The twelve months start here.

The instance, with a perpetual license to operate it for your own internal business use. Your configuration. Everything the engine generated for you. Your analytics. Your accounts and credentials, with one exception named in the same breath: the stored copy of a connected login is encrypted with a key we hold, so on the day you leave that one thing needs us to hand it over. Your audit records, readable by you. Your approvers trained on the queue, the gate and the record, and written operating notes for the people who run it.

That arrives as one pack, and here is what is in it. The signed acceptance record. A map of what exists, what talks to what, and what is deliberately absent, in your vocabulary rather than ours. An operating runbook, one page per role: day one, and then the running of it. A register of who holds every account, where the data lives, and who can grant and revoke. A plain language account of how we proved the data is yours, and how that was tested. And an honest gaps register: what is not built, why, and what it would take, each item dated and countersigned by you, because a gap you have signed is a scope decision and the same gap unsigned is a future complaint.

Social posting is the second exception, and it belongs here as much as on the pricing page: it runs through a posting vendor we hold the relationship with, under a profile that is yours inside our account. We say it here because you would find it later and be right to ask why we had not.

From go live, the engagement is the license fee and the running. Each time it runs, it prepares, drafts and queues across your connected systems. Your named person reads the queue and says yes. Each release lands in the record. Nothing on it reaches a customer, moves money, or changes a price until your person says so. The monthly generation envelope is fixed on the Order Form before you sign, and the infrastructure and model cost sits inside it. There are no overage invoices. Every generalized improvement to the engine lands in your instance while you license it.

There is no rebuild fee, ever. If you leave, the pricing page's exit section is the list of what you keep. It is the same list as stage 08.