How delivery works: from signed scope to weekly report

From signature to weekly report

Scope signed. The scope is the list of deliverables on the system's page, with its fixed price. You sign it, the deposit arrives, and the clock for the days below starts. Before you sign, a proposal for your chosen system is written in everyday words.
Audit of your current flow. A person maps what happens today to the task: who does it, in which tools, how long it takes, and where the data lives. You get the gaps in writing. This is where we say what is not built yet for your tools. The system pages already list that, row by row.
Build. We write and configure the system in accounts you control. The workflow, the account and the data belong to you from the first day. Every connection to your tools goes through the provider's own sign-in, which you can revoke at any time.
Pre-launch testing. Every system starts in a dry run: the agents do the work and nothing leaves. Every draft waits in an outbox for you to read. Before anything reaches a customer, you check the wording, the limits and the handoffs.
Go-live. Turning a system on is one recorded step by a named person. From the first message, consent records, the AI disclosure, the daily send cap, STOP handling and the kill switch apply. Finance stays inside the limits you set, and anything above them comes to you.
Weekly report. Each system files the report named on its page, daily, weekly or monthly as listed: the response-time report, the win-back report or the weekly coverage report, for example. A report counts what happened. It promises no result.

Days to live

Every figure below is in business days from a signed scope and the deposit, and the delivery clock starts when the deposit arrives. The written proposal states the same figures.

Days from a signed scope and the deposit to live, per system, from the price list.
System	Live in
Dormant List Revival	7 business days
Managed Automation & Infrastructure Retainer	7 business days
Lead Response Engine	10 business days
Quote-to-Invoice Automation	10 business days
Client Onboarding Pipeline	12 business days
E-commerce Order, Returns & Product Support Assistant	12 business days
AI Outreach & Lead Qualification Engine	14 business days
AI Receptionist	14 business days
Connected Operations Layer (MCP)	21 business days

What we need from you

A named person who can say yes: who approves the limits, the wording and the go-live step.
Access through each tool's own sign-in, never a password handed over in plaintext. Which accounts depend on the system: a WhatsApp Business account, your mailbox or domain, your calendar, your CRM or your accounting package, for example.
Your content. That means the answers the system may give, your opening hours, your return or booking policy, and, where the system writes to a customer list, a consent record for each person on it.
Your limits, if the system touches money: what it may quote, which discounts it may offer, and what must come to you.
A little time in week one for the audit of your current flow, and again before go-live to read the outbox.

Handover and exit plan

The written proposal states this plan, and our own delivery process enforces it.

Ownership. The workflow, the account and the data are yours from the first day, not ours.
Credentials and documentation reach you in writing before we mark the system live, not after.
No live without a handover. Our delivery process refuses the step until three things are written down: what you now own, where the credentials are kept, and what happens if Gonzo cannot be reached.
If we disappear, you already hold the workflow, the accounts and the written documentation, so you or someone you choose can run it.
Timeline. The days above are the figures in the proposal. What happens if a system is not live within them is not settled in writing, so this page does not state it. A person confirms it in writing before you sign.

Credentials never travel in plaintext. A few terms are not on file yet, and a person confirms them in writing before you sign: the cancellation and minimum-term terms, the deposit and any balance, and where your data is stored and for how long. The doubts page and the trust page list what is still open.

What has and has not run yet

Each of the nine systems has been built and tested in a sandbox, on simulated customers, messages and money. See a replay.
None has run against a live mailbox, WhatsApp number, payment account or calendar. A first live start is at the dry-run rung, and nothing leaves until you have read the outbox.
No client result, logo or testimonial appears on this site, because none has been earned and agreed.

Before you sign anything

Send one web address for the free audit, or watch a sandbox run first. The fixed prices are on the pricing page.

How delivery works, step by step.