One year of implementation that leaves you with working systems and the capability to run them.
Most "AI transformation" work ends with a deck, a pilot and a vendor. This ends with workflows in daily use, built in your repositories and accounts, owned by named people on your side, with the documentation and practice to change, monitor and recover them without us. The consultant is inside your team for the year — with your email address, your tools, your weekly rhythm — and works themselves out of the job on purpose.
Operating architecture first
Processes, responsibilities, handoffs, decisions and success measures mapped before anything is automated. A prioritised backlog, not a wish list.
Complete workflows, not demos
Triggers, context, permitted actions, outputs, human review and exception handling — connected to the tools you already run.
Handed over, not hosted
Source, configuration, documentation, operating instructions and maintenance sessions throughout the year. Your people run it by month twelve.
Every workflow shipped has a named owner on your side, a baseline it is measured against and acceptance criteria written before it is built. The bookshelves say what has to exist for that to be true; the engagement is the year spent making it exist.
One offering, three starting points
Choose one primary starting point and expand through an agreed roadmap. Each maps to one of the three Agentic Organisation playbooks — the shelves guide what needs to exist for each workflow, and the books become the first artifacts.
| Starting point | Implementation focus | Example workflow |
|---|---|---|
| GTM Agentic Organisation | Sales, marketing, RevOps and customer success: CRM, account intelligence, campaigns, pipeline and reporting. | Account research → qualification → CRM updates → seller tasks → performance review |
| Agentic Organisation | Shared organisational foundations: knowledge, ownership, decision rights, approvals and workflows across departments. | Internal request → relevant context → approval → execution → recorded outcome |
| Product Agentic Organisation | Product discovery, delivery, growth and product operations, with selected agents inside the team or the product. | Customer feedback → evidence synthesis → opportunity brief → prioritisation → delivery follow-up |
Not sure which? The first month's assessment decides it with you. Most commercial teams start on the GTM track; most companies that have already automated GTM start on the shared foundations.
What gets built
Six areas, in roughly this order. Not all of them at full depth for every client — the backlog from month one decides the weighting.
- Operating architecture. Map the selected processes, responsibilities, handoffs, decisions and success measures. Turn these into a prioritised implementation backlog.
- CRM and data foundations. Configure objects, properties, lifecycle stages, ownership, data-quality rules and reporting definitions. Connect relevant customer, product and operational records.
- Brains and shared knowledge. Build maintained knowledge collections containing approved strategy, ICP, positioning, product information, policies, metric definitions and decision history. Assign owners and update rules.
- Automations, agents and integrations. Build complete workflows with triggers, context, permitted actions, outputs, human review and exception handling. Connect them to your existing tools.
- Production operation and improvement. Deploy, test on representative cases, monitor quality and running costs, resolve failures and improve the delivered workflows.
- Adoption and handover. Train the people who use and maintain the systems. Provide source code, configurations, documentation, operating instructions and practical maintenance sessions throughout the year.
The instruments on this site are part of the kit: the GTM Control Room for governed reporting, the Sales Leaders Calendar for the operating rhythm, and the CRM Revenue Growth playbook for the CRM architecture.
The year, quarter by quarter
Each quarter ends with something you can review — not a status report, a working thing with a named owner.
| Period | Focus | Reviewable milestone |
|---|---|---|
| Months 1–3 | Assess the current setup, agree priorities, establish essential foundations and deliver the first workflow. | First workflow in use, with a baseline, an owner and acceptance criteria. |
| Months 4–6 | Deliver further priority workflows and connect shared knowledge and systems. | An initial portfolio of working implementations with measured results. |
| Months 7–9 | Improve reliability, adoption and coverage across agreed teams. | Internal owners operate the systems with decreasing consultant involvement. |
| Months 10–12 | Complete agreed releases, resolve remaining issues and finish the transfer. | Your team demonstrates it can operate, change, monitor and recover the systems. |
What "inside your organisation" means in practice
Forward deployed is a set of concrete arrangements, not a mood. These are the five.
| Arrangement | What it means |
|---|---|
| Client identity | A client-domain email address, company-managed access and seats in the relevant tools. |
| Client environment | All implementation assets live in your repositories, workspaces, cloud infrastructure and SaaS accounts from day one. New interfaces use your domain where applicable. |
| Client control | Credentials, billing, data, deployments and administrative ownership remain with you. Approved external AI services run on client-controlled accounts. |
| Embedded delivery | One named consultant, agreed monthly capacity, a weekly working session, regular demonstrations and quarterly roadmap reviews. |
| Client participation | An executive sponsor, available system owners and a named future operator. Customer-facing product agents also need an agreed engineering and release owner. |
Systems built in a vendor's account are rented. Systems built in yours, by someone with your email address, alongside the person who will run them next year, are owned. The difference shows up the first time something breaks after month twelve.
Commercial terms
How it is priced
- Fixed 12-month term.
- An agreed monthly fee and defined delivery capacity.
- Software and infrastructure costs paid directly by you, on your accounts.
How scope is protected
- Start with one primary track; concurrent build workstreams are limited.
- Significant additions require reprioritisation or additional capacity — never silent absorption.
- Support after month twelve is a separate engagement, so the handover is real.
Is it the right shape for you?
- Not for a two-week proof of concept — the GTM Audit or a scoped project is the right entry there.
- Not for organisations that want the systems hosted and operated by us — the whole design is transfer.
- Not without a sponsor and a named future operator; without them the year ends with orphaned systems.
Forward Deployed Implementation is one of the five ways to work with Revenue Puzzles: Entry (GTM Audit), Project, Fractional leadership, Build (this page) and Run (ongoing support).
Bring the revenue problem and the team that owns it. Tell me what is going on — I read every message myself, and I will say whether a year embedded is the right shape or whether something smaller fits better.