What the two-week GTM Engine Assessment produces

Most automation projects start in the tool and work backwards to the process. The assessment exists to do it the other way round, in two weeks, before any configuration is paid for.

What I look at

The commercial process as it actually runs: where inquiries come from, who touches them, how long they wait, where they die. The tools you own and the licences you are paying for, including the ones nobody logs into. The data: how many records, how clean, who owns which field, which system is lying to which. The operational gaps: the handoffs that depend on a person remembering, the opt-outs that only reach one system, the reports that describe activity rather than outcomes. And the commercial priorities, because the first release has to move a number someone cares about.

What you receive

The blueprint. Target accounts, buyers, qualification criteria, messaging, handoffs and the buyer evidence each stage requires, with a named owner and a response expectation for every step. The architecture. Which system is authoritative for which record, how the tools connect, which connections are native, which need custom work, and who maintains each one. The scope. The first production release, the milestones behind it, and the external approvals, access and data readiness that have to be in place before a launch date is committed. The acceptance criteria. The live tests that will say each component launched: a submission reached the right owner, an opt-out blocked outreach everywhere, a booking produced the right activity, a failed integration raised a visible exception.

You also receive a straight answer to a question nobody asks early enough: whether the engine is the right next investment at all. If the ICP is unsettled or the motion has not closed deals by hand, the assessment says so and points at the stage that needs the work first.

What you bring

Access to the CRM and the tools, read-only is enough. A week of someone’s partial attention who knows how deals really move. The last ninety days of inquiries, replies and bookings. The number the business needs this quarter.

What happens next

The build, if the assessment justifies it: ninety days organised around the milestones in the scope, with the first release aimed at the highest-priority workflow. The fixed fee for the build is quoted from the assessment, so there is no second discovery. If you take the blueprint and build it with your own team, it is written to be followed without me. The full engagement is described on GTM Engine Build & Launch.

Questions this page answers

What does the GTM Engine Assessment produce?

Four things in two weeks: a prioritised blueprint of the commercial process with owners and response expectations, the architecture that says which system is authoritative for which record and how the tools connect, the scope of the first production release with its milestones and dependencies, and the acceptance criteria that will decide whether each component launched.

How long does the GTM Engine Assessment take?

Two weeks, with a kickoff call, access to the CRM and tools, a review of the last ninety days of inquiries, replies and bookings, and a written readout: blueprint, architecture, scope and acceptance criteria.

Do I have to buy the build after the assessment?

No. The blueprint is written to be followed by your own team, and the assessment is priced on its own. If the build goes ahead, its fixed fee is quoted from the assessment and there is no second discovery.