A Four-Property Gate That Grew MQLs, Not SQLs
A case-study download was the only signal marking a contact ready for sales. Against a target list of roughly 150 manufacturers and retailers, that wasn't enough to tell a real opportunity from a casual read. We built a four-property qualification gate inside HubSpot that marks a contact sales-qualified only once every check clears, and it then creates a deal automatically instead of relying on a manual handoff. Persona and lifecycle segmentation feeds contacts into separate nurtures ahead of that gate.
Executive Summary
Context
A Sydney market research and FMCG product innovation consultancy needed its inbound nurtures to route about 150 target accounts towards a genuine sales conversation, not a growing subscriber list. Its lifecycle stage moved on marketing activity alone, with no signal for fit.
What We Built
We built a four-property qualification gate that lets HubSpot mark a contact sales-qualified only once every check clears, and then opens a deal for the rep automatically instead of leaving qualification to memory. Persona and lifecycle segmentation routes the same contacts into a top-of-funnel or middle-of-funnel nurture before they reach the gate.
Tech Stack
- HubSpot Marketing Hub
- HubSpot Sales Hub
- HubSpot contact properties
- HubSpot deal pipeline
- HubSpot sequences
Not a fit if your addressable market is too narrow to convert lead volume into matching sales-qualified opportunities. A list near 150 target accounts kept nurture volume healthy but left too few contacts able to clear all four checks each quarter, which capped how many could reach Good Fit.
The Challenge
Contacts moved through persona and lifecycle-segmented nurture lists, but the only signal marking a contact ready for sales was a case-study download. That download alone triggered a review task with no further check behind it. A rep could spend time on a contact who matched none of the target list's industry, title or size criteria, while HubSpot's lifecycle stage kept advancing on activity regardless of fit.
Against a list of roughly 150 accounts, every wasted review took a larger share of the addressable market's attention.
Our Approach
A contact who downloaded a case-study report at the end of a nurture series used to be marked towards SQL on that action alone, with only a review task as a check before outreach. We built four Yes/No properties under 'SQL Qualification': Right Industry?, Right Job Title?, Right Size and SQL Qualified. A download now starts the review rather than finishing it.
A single No reverts the contact to Subscriber, which keeps an unqualified download out of a rep's queue. When a contact passes all four, 'Good Fit' is set to Yes, and HubSpot creates a deal in the Pre-Brief stage and a notification task automatically.
If a deal stays in Pre-Brief for 14 days without reaching Proposal, a reminder task points the rep at 'S2 | CIMs Sequence' or 'S2 | IMs Sequence', and a reply un-enrols the contact automatically. The trade-off is that the gate filters hard on fit, so a single No sends the contact back to Subscriber.
Impact
Nurture-influenced pipeline that closed real revenue
Segmented lists split by persona, lifecycle stage and interest tracked 4,058 contacts as nurture-influenced, and those contacts closed 40 deals worth roughly 1.3 million dollars, with the MQL nurture converting at 26 percent.
New-business lead volume that beat its quarterly goal
In Q3 2022 the segmented nurtures and the SQL review together produced 78 new-business marketing-qualified leads against a goal of 63, so lead volume was never the shortfall the sales team faced that quarter.
A qualification bottleneck the volume increase did not fix
The same quarter closed at 4 sales-qualified leads against a goal of 21. The four-property gate reverted a contact to Subscriber as fast as the nurtures fed contacts in, so more top-of-funnel volume never became more contacts clearing Right Industry, Right Job Title and Right Size at once.
A stale deal that could not age out of view
A deal sitting in Pre-Brief for 14 days without moving to Proposal triggered a reminder task pointing the rep at a named follow-up sequence. A contact that cleared the qualification gate could therefore still stall in the pipeline, but the stall wouldn't go unnoticed.
Four Yes/No fields sit under 'SQL Qualification': Right Industry?, Right Job Title?, Right Size and SQL Qualified, next to 'Good Fit.' A No on any of the four reverts the contact to Subscriber, so a rep reviews once, not on every touch.
Persona type, lifecycle stage and interest segment contacts into lists at the point of form submission, routing a TOFU offer into a Lead nurture and a MOFU offer into a separate MQL nurture. The MQL-to-SQL transition sends the assigned salesperson a token-filled notification instead of a shared report.
Good Fit set to Yes creates a deal directly in the Pre-Brief pipeline stage and fires a notification task, replacing a manual handoff with a system-created record the moment a contact clears every qualification property.
A deal that has not reached the Proposal stage 14 days after opening triggers a reminder task suggesting enrolment in the 'S2 | CIMs Sequence' or the 'S2 | IMs Sequence.' A reply from the contact un-enrols them automatically, so the sequence never talks past a contact who has already responded.
A form submission places a contact in persona and lifecycle lists, and a nurture email series follows; a case-study download at the end of it opens an SQL review in HubSpot. Four Yes/No properties check fit, and any single No sends the contact back to Subscriber in Marketing Hub. When all four pass, Good Fit is set and a deal is created in the Pre-Brief stage in Sales Hub. A 14-day reminder task fires there if the deal hasn't reached Proposal.
FAQ
Any single No on Right Industry, Right Job Title, Right Size or SQL Qualified reverts the contact straight back to Subscriber. Nothing is lost by that reset: the properties simply clear, so the contact can be reviewed again after more nurture activity rather than being blocked outright.
Not on its own. In the quarter this gate ran, MQLs beat goal by 15 while SQLs missed theirs by 17, because the four-property check filters on fit, not activity. A wider or better-matched list raises qualified pipeline, not a heavier nurture cadence.
