GTM:METRICS/Modules

Turning leads into customers, in a CRM people actually trust

Lifecycle stages that mean something, routing and ownership, a handover both sides trust, and a way to bring back the deals that went quiet. The other module people come for.

First result First workflow live inside 4 weeksRuns Weeks 3 to 8Built in HubSpot

What this actually is

A CRM nobody trusts is worse than no CRM, because the team keeps a private spreadsheet and the reporting quietly describes a company that does not exist. This module rebuilds the parts that decide whether a lead becomes a customer, and it does it in a way that survives the next reorganisation.

What gets built

  • Lifecycle stages that mean something. Each stage has an entry condition anyone can check, an owner, and an exit. If two people can disagree about which stage a record is in, the stage is not defined yet.
  • Properties with a purpose. Every field either drives a workflow, appears in a report, or gets deleted. Most CRMs carry hundreds of fields nobody has read in two years.
  • Routing and ownership. By language, territory and segment expertise, so people receive work they can actually do. With a rule for what happens when the owner is away, which is where most routing quietly breaks.
  • A handover both sides trust. An explicit definition of what marketing hands over, what sales accepts, and what happens to the ones sales rejects. Rejection with a reason, feeding back into scoring.
  • Reactivation. The deals that went quiet are the cheapest pipeline in the building. A sequence that reopens them on a trigger rather than on a calendar reminder.
  • Reporting that survives a reorg. Built on stages and properties rather than on individual people, so it still works when the team changes.

The test for a lifecycle stage. Show the definition to one person in sales and one in marketing, separately, with ten real records. If they sort them the same way, the stage is defined. If not, you have a label rather than a stage, and every report built on it is fiction.

How it runs

WhenWhat happens
Week 3Audit of what exists, which fields are actually used, and where records currently get stuck.
Week 4Lifecycle stages and properties agreed and built. First workflow live.
Weeks 5 to 6Routing, ownership, handover and rejection paths.
Weeks 7 to 8Reactivation, plus the migration of historical records onto the new stages.

When this is not the right module

If you have no pipeline yet because you have no leads, build lead sources first. A perfect lifecycle model with nothing flowing through it is an expensive diagram.

Where this connects

WHERE THIS STARTS

You get the map first.

The first two weeks produce a status map of your own stack. Every piece named, colour coded by how proven it is, gaps included. You keep it whether or not we work together.