Rolling Positioning Out Across Site, Sales, and CRM
The workshop is the cheap part. Most positioning work fails after the decision is made, when the document goes in a shared drive and the company keeps running on the old story. Rollout is the deliverable. If the position only reached the homepage, nothing changed.
Key takeaways
- ·Six surfaces have to move together: homepage, service pages, sales deck, CRM fields, MQL definition, and onboarding.
- ·Updating only the website means the position decays back within a quarter.
- ·Positioning that never reaches the CRM can never be checked against evidence.
- ·Onboarding is the surface everyone forgets and the one that decides whether the position survives your next three hires.
The six surfaces
Each row has an owner and a done-when test. The done-when matters more than the change description, because it is the only way to tell the difference between work that was completed and work that was discussed.
| Surface | What changes | Owner | Done when |
|---|---|---|---|
| Homepage hero | New value proposition, one sentence, naming the buyer. The old headline usually described the service; the new one describes who it is for and what changes for them. | Marketing | A stranger reading only the hero can say who the company serves and what they get. |
| Service and product pages | Each page leads with the outcome, carries one proof point per claim, and answers the objections that page raises rather than the generic ones. | Marketing | No claim on the page lacks a proof point within one scroll of it. |
| Sales deck and one-pagers | Same words as the site. Not a paraphrase, not a longer version, the same sentences in the same order. | Sales | Someone can read the homepage and the deck back to back without noticing a change in voice or claim. |
| CRM fields and pipeline stages | Add or fix the fields that let you count what the new position predicts: competitive alternative considered, segment, and a picklist loss reason. | Sales ops or whoever owns HubSpot | You can run a report that counts loss reasons without reading free-text notes. |
| The MQL definition document | Rewrite the shared definition of a qualified lead so it matches the buyer the new position targets, and get both sales and marketing to sign it. | Both, jointly | Sales and marketing give the same answer to whether a specific recent lead was qualified. |
| Onboarding and internal docs | The position goes into the first-week onboarding pack so new hires learn it before they learn the service list. | Whoever runs onboarding | A new hire can explain the position after one week without a slide. |
The MQL definition document
This is the surface teams skip, and skipping it is why the lead quality argument never ends. An MQL definition document is one page that both sales and marketing sign, stating exactly what makes a lead qualified. HubSpot documents this as part of a sales and marketing service level agreement.
Put four things in it. The firmographic fit criteria that match the buyer your new position targets. The behavioural threshold that suggests intent. The explicit disqualifiers, which do more work than most teams expect. And the handoff rule: who contacts a qualified lead, and how fast.
Keep it to one page. A definition nobody can recall is a definition nobody applies. Test it by picking three recent leads and asking sales and marketing separately whether each was qualified. Different answers mean the document is not done. For a copy-ready template plus the 12-question audit that finds where the handoff leaks between the two teams, see the sales-marketing handoff audit.
A realistic sequence
Six to ten weeks for a company of 10 to 50 people. Start with the CRM fields and the MQL definition in week one, because they are fast and they start collecting evidence immediately. Homepage and service page copy runs weeks two through six, since copy has to be written and usually designed. The sales deck follows the site, never the reverse, so the two cannot drift apart.
Finish with onboarding. Once the position is in the first-week pack, it survives turnover. After that, the 12-question audit becomes a quarterly check rather than a one-time exercise.
FAQ
What is an MQL definition document?
An MQL definition document is a short written agreement between sales and marketing that states exactly what makes a lead marketing-qualified: which firmographic traits, which behaviours, and which disqualifiers. Both teams sign it. Its purpose is to end the recurring argument about lead quality by replacing opinions with a shared rule. HubSpot documents this as part of setting up a sales and marketing service level agreement. Without one, marketing counts leads sales does not want, and neither side can prove the other is wrong.
What should an MQL definition actually contain?
Four things. The firmographic fit criteria, meaning the company traits that make someone a real prospect for the position you chose. The behavioural threshold, meaning what the person did that suggests intent. The explicit disqualifiers, which matter more than most teams expect. And the handoff rule stating what happens when a lead qualifies, who contacts them, and how fast. Keep it to one page. A definition nobody can recall is a definition nobody applies.
Why does positioning have to reach the CRM?
Because positioning is a bet about which buyers you win, and the CRM is the only place you can check whether the bet is paying off. If competitive alternative and loss reason are free-text notes, nobody can count them, so the position never gets corrected by evidence. Add a picklist loss reason and a field for what else the buyer considered. Within two quarters you will know whether the position is holding up or whether you guessed wrong about the alternative.
How long does a positioning rollout take?
For a 10 to 50 person company, plan six to ten weeks from signed-off position to everything moved. The homepage and service pages take the longest because copy has to be written and often designed. The CRM fields take an afternoon. The MQL definition takes one meeting and a week of arguing. The onboarding pack is usually forgotten, and it is the one that determines whether the position survives your next three hires.
What happens if we only update the website?
The position decays back to whatever it was within about a quarter. Sales keeps using the old deck because it is familiar, the CRM keeps collecting data shaped by the old assumptions, and new hires learn the old story from colleagues rather than the new one from onboarding. The website ends up describing a company the rest of the organization is not running. This is the single most common way a positioning project produces nothing.
Which of the six rollout surfaces matters most if the budget only covers one or two?
The homepage and the sales deck, because they are the two places a buyer and a rep both encounter the position in the same week a deal is active. The CRM fields and MQL definition matter for measuring whether the position works over time, but a company can survive without them for a quarter. Skipping the homepage or the deck means the new position is not actually live where deals happen.
How do you know the rollout actually worked, not just that it shipped?
Check the CRM loss-reason field two quarters after rollout. If the recorded competitive alternative matches the one named in the positioning framework, the sales team has internalized the position enough to log it accurately. If loss reasons still read like the old, vague version, the rollout reached the website but not the people having the conversations.
Does the onboarding pack need to be updated every time a new hire joins?
The document itself stays stable between positioning reviews, but each new hire needs a real walkthrough of it, not just a link in a welcome email. New hires who learn the company story secondhand from colleagues, rather than from the actual onboarding pack, are the most common way a rolled-out position quietly reverts within a year of the original project.