1,036 wordsby CONNOR J. LAUGHLIN
Messaging that survives scrutiny.
Why messaging falls apart when the proof behind it isn't governed.
Repositioning the company from collections vendor to strategic cash flow partner
- Role
- VP of Marketing & GTM (acting CMO)
- Timeline
- 2024-2025
- Team size
- Four direct reports, agency partners, and stakeholder groups across the business
- Challenge
- Fragmented messaging across the business units, feature-centric positioning, inconsistent sales narratives
The challenge
The company had grown through acquisition. Every business unit carried its own messaging, value propositions, and sales narratives: collections, healthcare revenue cycle, business process outsourcing, the acquired SaaS platform, and loan servicing. The result showed up everywhere.
- Sales teams used inconsistent talk tracks, creating confusion in multi-product deals
- Marketing campaigns competed with each other for attention and budget
- RFP responses were copy-paste nightmares with conflicting claims
- Website messaging was feature-heavy ("we have AI") where it should have been outcome-focused ("you recover more, faster")
- Executive stakeholders could not articulate a single company-wide value proposition
The stakes: an enterprise at real scale was still speaking like a commodity vendor.
The solution
Phase 1: cross-functional discovery (weeks 1-4)
I led a messaging audit across every stakeholder group that touched the story:
- Sales leadership (directors, VPs, top performers)
- Product owners across the proprietary collections, AI, and platform products
- Compliance and legal, to validate claims
- The executive team (CEO, CFO, COO)
- Client success, to capture proof points
- Client references, to validate that the messaging landed
Key discovery: sales reps were leading with "we're a collections company with AI" when they should have led with "we help regulated enterprises turn receivables into reliable cash flow."
Phase 2: architecture development (weeks 5-10)
I built the messaging framework with a stakeholder validation gate at every level of the business.
1. Messaging pillars
The pillars were "recover more, faster," carried by digital and AI prioritization that improves liquidation rates. "Protect brand and experience," carried by a complaint rate low enough to be a proof point in regulated deals. "Reduce risk and compliance exposure," carried by a heavy annual audit load passed clean. "See and steer the whole recovery lifecycle," carried by platform transparency. And "start fast, scale on proof," carried by a 4 to 8 week implementation.
2. Business-unit specific guides
I tailored messaging for collections, healthcare revenue cycle, business process outsourcing, the SaaS platform, and loan servicing. Each guide carried vertical-specific pain points and outcomes, competitor differentiation with the field mapped, objection handling for the objections that came up in that vertical, and a proof-point library of client outcomes and compliance stats.
3. Voice and style guardrails
Writers were told to lead with client outcomes, use specific figures, and cite compliance credentials. They were told to avoid superlatives without proof, feature-first openings, and unsubstantiated AI claims.
4. RFP-ready snippets
Pre-vetted copy blocks for security questionnaires, compliance attestations, and operations descriptions.
Phase 3: stakeholder alignment (weeks 11-12)
I presented the architecture to every stakeholder group and put the open questions on the table rather than around them:
- Are the compliance claims (SOC 2, PCI, ISO, HITRUST) accurate and current?
- Can we publicly name the proprietary AI engines?
- Which superlatives need legal review?
- Are the forward financial projections approved for external use?
- Do sales teams have competing narratives we need to retire?
- Are product owners aligned on the feature-to-outcome translations?
- Is the executive team aligned on the single-company positioning?
- What is the rollout timeline for each business unit?
Outcome: sign-off from every group, with minor adjustments.
Phase 4: deployment (weeks 13-16)
- Sales enablement: talk tracks, one-pagers, competitive battlecards
- Website: a full corporate site rewrite with outcome-first copy
- RFP team: a pre-approved response library
- Marketing: campaign briefs aligned to the messaging pillars
- Executive team: a single elevator pitch for investor and analyst conversations
The outcome
Messaging consistency
A multi-hundred-line messaging architecture went live across every business unit. Every group signed off on the core value propositions, and conflicting claims stopped appearing in multi-product RFPs.
Sales impact
We were aiming at a lift in client payment rates and a reduction in their cost to collect, on the theory that a clearer digital and AI value proposition sells the outcome rather than the tooling. Cross-sell conversations ran off one narrative instead of a different one per business unit.
Operational efficiency
RFP responses got materially faster once the pre-approved snippets existed. Website messaging was consistent across the whole site, and there was a single source of truth for go-to-market copy.
A complaint rate low enough to be a proof point in regulated deals, which only works as a headline when the messaging leads with outcomes rather than features.
Leadership angle: cross-functional orchestration
This was filed as a marketing project, and the real work was alignment. It required getting the following groups to the same place.
| Stakeholder group | What they needed | How I delivered |
|---|---|---|
| Sales leadership | Talk tracks that win deals | Vertical-specific scripts with proof points |
| Product owners | Feature credit without feature dumping | A feature-to-outcome translation matrix |
| Compliance and legal | Zero risk of false claims | A pre-vetted claim library with citations |
| Executive team | Investor-grade positioning | A single company-wide narrative |
| Client success | Recognition of their proof points | Proof-point attribution in all materials |
| RFP team | Faster, compliant responses | Pre-approved copy blocks by category |
The team was four direct reports covering content, design, ops, and analytics, an external agency for copywriting, and internal stakeholders across six departments.
Attribution clarity
My work:
- Messaging strategy and architecture
- The cross-functional stakeholder alignment process
- Voice and style guardrails
- Proof-point library structure
- Competitive differentiation framework
- Objection handling scripts
- RFP snippet library
- Deployment planning and enablement
The company's assets:
- The underlying product capabilities
- Compliance certifications (SOC 2, PCI, ISO, HITRUST)
- Client outcomes data and CSAT scores
- Financial projections and operational metrics
What made this work
I did not write the messaging in a vacuum. I interviewed stakeholders across the whole business, validated every claim with compliance, and got executive sign-off before anything deployed.
The architecture was a working document sales teams could open in a live deal, which is the only test that matters for a messaging framework.
Every feature claim was translated into a client outcome. "We have AI" became "you recover more, faster."
Artifacts
- The messaging architecture document
- Business-unit messaging guides
- Headline bank of tested headlines
- Objection handling framework
- Before and after rewrite examples
- Voice and style guardrails
- RFP snippet library
- Competitive context mapping
Keywords MessagingArchitecture CrossFunctionalLeadership Positioning StakeholderManagement GTMSystems