Enterprise Systems for Decision Makers

The thirty days

What the month actually costs you

Not what it costs us — you can see the price on the pricing section. This is the part nobody publishes: how many hours of your week it takes, what we need from you and when, and what exists at the end of each one.

1. Day 00.5–1h of your time

   The call, and the answer to whether this is worth doing

   Thirty minutes. You bring the bottleneck that costs you the most; we map it and tell you what removing it would take, including what it would cost. If the answer is that you do not need us yet, we say so — that has happened and it will happen again.

   What exists at the end

   • A written scope with a price range, not a proposal deck
   • An honest read on whether automation is your actual constraint

   What we need from you

   • Thirty minutes
   • Rough monthly lead volume and where leads come from
2. 1
   Week 13–5h of your time

   Audit and blueprint

   We get read access to what you already run — CRM, inbox, calendar, forms, whatever the stack is — and trace a real enquiry end to end. Most of what we find is not what anyone expected, which is why this comes before any building.

   What exists at the end

   • A map of every place a lead currently stalls, waits or gets re-typed
   • The system architecture, written down and agreed before a line of it is built
   • A fixed scope: what is in, what is explicitly out

   What we need from you

   • Read access to your current tools
   • One session walking us through how the work is done today
   • Whoever actually answers enquiries, for thirty minutes
3. 2
   Week 22–4h of your time

   Build, against your data

   The capture, qualification and routing layer gets built and connected to your real accounts — not a sandbox. You get a link to a working environment at the end of the week and can break it on purpose, which we encourage.

   What exists at the end

   • Capture live across every channel you use
   • Qualification running against your rules, in your words
   • Routing and notifications wired to the right people
   • A staging link you can test yourself

   What we need from you

   • Write access to the tools we agreed in week 1
   • Your qualification rules — who is a good lead, who is not
   • An hour reviewing the staging build
4. 3
   Week 32–3h of your time

   Automation and follow-up

   Booking, CRM writes, reminders, follow-up sequences and the reporting layer. This is the week the system stops being a form and starts being an operator.

   What exists at the end

   • Calendar and booking automated against real availability
   • CRM records created and updated with no re-typing
   • Follow-up and reminder sequences, in your tone
   • A dashboard showing what the system did, in plain numbers

   What we need from you

   • Sign-off on the message wording — it goes out under your name
   • Availability rules and who covers what
5. 4
   Week 41–2h of your time

   Launch, handover, and the part most agencies skip

   We run live traffic through it with a human watching, fix what surfaces, then hand it over properly. You get the credentials, the documentation and a recorded walkthrough — the system is yours whether or not you keep us on support.

   What exists at the end

   • Live, with the first week monitored
   • Every credential and account in your name, not ours
   • A recorded walkthrough of how to change things yourself
   • A written runbook: what to do when something breaks at 2am

   What we need from you

   • An hour for handover
   • A decision on ongoing support — optional, either way