A 250-person enterprise HR tech firm in Singapore had two business units: a consulting arm - the number one SAP SuccessFactors implementation partner in Singapore and Malaysia, holding 50 of Singapore's top 100 enterprise logos and a product arm, building add-ons for the same platform with 45 active customers and a global target of 6,000.
For 15 years, pipeline came through SAP and Workday. The firm never needed to prospect.
Then they expanded. Adding a competing platform meant the referral model broke. Both SAP and Workday stopped sending deals.
Overnight, a business that had never hunted needed to become a hunter.
The challenge wasn't just building outbound. Their total addressable market was finite - roughly 200 accounts in Singapore and Malaysia for the consulting arm, 5,800 globally for the product arm.
Volume outbound against a finite market doesn't just underperform. It permanently damages every account you haven't reached yet.
The 3 Approaches That Failed Before the Architecture Was Built
Email outbound agencies
Four to five leads per month at $200 per lead. Zero conversions.
Not an execution failure - a model mismatch. Spray-and-pray in a 200-account market burns the list. Every uncontextualized email to a Singapore CHRO made the next one harder.
Internal BDR hire
Hired before the motion existed. No ICP clarity, no routing logic, no qualification criteria. The BDR had a dialer and a list and nothing to plug into.
The role was eliminated. The conclusion drawn was "the channel doesn't work." The right conclusion: you can't hire a driver before you build the car.
Post-event email blasts
Events consistently drew 15-20 senior enterprise attendees. Post-event follow-up: one email to all attendees, then nothing.
Zero conversion from their warmest asset. The asset existed. The infrastructure to convert it didn't.
What the Audit Revealed
38 business-level discovery questions per business unit. 4 stakeholder interviews across commercial, product, and operations.
What we found:
- HubSpot used only for landing page hosting and manually updated deal records
- Sales team had reverted to Excel
- No pipeline stage definitions, no entry criteria, no lead source attribution
- No secondary email infrastructure - no warmed domains, no sending accounts
Any system built on top of what existed would have been ignored. The audit was not optional. It was the only way to know what to actually build.
Also Read: The Economics of Manual GTM: Why Founders Can't Scale Themselves
The 4 Foundation Decisions That Everything Else Runs On
1. One CRM instance, two separate pipelines
Consulting arm and product arm in the same HubSpot instance. Separate pipelines, separate ownership rules, separate lifecycle stages. No bleed between business units.
2. Three-tier account segmentation
Suspect → marketing nurture only. Prospect → full cadence. High Priority → direct sales motion.
Every account lives in exactly one tier. Tier determines what happens next. No ambiguity, no rep discretion.
3. Signal scoring per business unit
Consulting arm: 10 signals, 25-point maximum. Product arm: 6 signals, 22-point maximum with a hard qualification gate.
Accounts only enter active outbound when they cross the threshold. Below it, they stay in nurture until something changes.
4. Routing before sequences
Consulting arm routes to 13 service-line sequences. Product arm routes to 11 product sequences. Routing is automatic — a Claygent reads signal scores and assigns the right sequence without human intervention.
What Exists Now That Didn't Before
CRM
- HubSpot rebuilt from near-scratch for both business units.
- Chatbot flows on both domains with route-to-property mapping. Email capture before any qualification questions.
- 37 intent values mapped to contact properties triggering automatic sequence enrollment.
- Real-time lead alerts routed to the correct business unit owner.
Email infrastructure
6 secondary domains. 5 accounts per domain. 30 total sending accounts. Full warm-up protocol before any outbound sent.
Clay ABM
Signal scoring Claygents per signal category.
- Routing Claygent per business unit - reads signal pattern, assigns sequence automatically.
- Reply classification Claygent - positive, neutral, negative using business-specific sentiment rules.
- Scoring explanation Claygent - plain English explanation of why each account scored as it did, visible inside HubSpot for the sales team.
Sequences
36 inbound sequences for the product arm across 9 intent paths. 56 inbound sequences for the consulting arm across 21 service-line paths. Signal-To-Motion™ SOPs for both business units.
Reporting
Full outbound activity dashboard. LinkedIn activity, email activity, reply segmentation breakdown. Zero manual data entry. Every metric derived from task parsing.
What Part 2 Covers
The architecture is the foundation. Part 2 covers what runs on top — the outbound strategy, the signal-to-message logic, the cold outbound angles for High Priority accounts, and how post-event follow-up became a structured pipeline motion instead of a single email blast.
If Part 1 is the car, Part 2 is how we learned to drive it.
[Read Part 2: The Outbound Strategy →]
If your team is coming out of a partnership-dependent model, or sitting on a HubSpot instance the sales team doesn't trust, start with an audit, not a campaign.
Get your GTM architecture reviewed →
