Visual Identity Group logoField Report / 004Mixed / Guardrails
"I appreciate you allowing me to sit in the driver's seat here. I went through all the documentation, all the workflows, and this has been a very helpful thing."
Jason WeamerFounder, Visual Identity Group

From Outlook to a founder-led outbound operating system

Visual Identity Group grew for two and a half decades on relationships and referrals. Jason Weamer was the founder and the only person selling, running GTM out of Outlook tasks with outbound paused since April. The work was not to sell for him. It was to build the infrastructure, the operating rhythm and the documentation so he could run outbound himself — and hand it to a rep later without rebuilding it.

  • ~7 weeks from discovery to founder-operated handoff

    Proof point 01

    Engagement term · client publishing record

  • HubSpot + ZoomInfo + Smartlead + Expandi installed as one system

    Proof point 02

    Phase 1 close-out summary

  • Founder independently running the end-to-end weekly workflow

    Proof point 03

    Handoff review · engagement transcript

Report thesisCapability transfer, not outsourcing: the goal was for the founder to run a documented outbound workflow himself after the engagement ended.

  • Founder-Led Sales
  • Outbound System
  • Messaging
Industry
Creative Marketing & Software Agency
Engagement
Revenue Rebuild — Founder-Led Outbound System Build
Dates
Dec 2025 – Feb 2026

Two-phase $7,500 engagement. Contracted term Dec 15, 2025 – Jan 31, 2026, with discovery beginning mid-December and final documentation handoff closing out in early February. This report publishes system, infrastructure and capability outcomes only. No pipeline value, closed revenue, meeting count or ROI figure is claimed, because the engagement evidence does not support one — performance guarantees were explicitly out of scope in the agreement.

Evidence index

Artifacts from the work

A compact view of the engagement record. Open any item to inspect it.

Fig. 01 · Engagement scope · Dec 15, 2025
Outbound System Build — engagement scope
Fig. 02 · ICP definition · Dec 2025
Ideal Customer Profile — healthcare-first
Fig. 03 · Operating playbook · handoff asset
Operating Playbook — how the system runs
Fig. 04 · Operating documentation · handoff asset
Daily Outbound Workflow — founder-led
Fig. 05 · Close-out summary · Jan 2026
Phase 1 close-out — delivered and out of scope
01
The Situation

What was actually happening

Visual Identity Group had built a real business — millions in managed media spend, deep healthcare delivery experience, end-to-end creative, web, SEO and advertising — almost entirely through relationships and referrals. That works until it is the only thing that works. Jason was the founder and the only person doing sales. There was no CRM. Targeting was, in his words, boiling the ocean. GTM lived in Outlook tasks, and outbound had been paused since April because there was nothing underneath it to make restarting worth the effort. He did not want a campaign. He wanted the foundation built properly before he turned outbound back on.

02
Diagnosis

What we found

The problem was not effort or intent — it was that nothing was connected. ZoomInfo, Sales Navigator and Expandi were all present in some form, but none of them fed anything. There was no system of record, so no signal survived past the week it arrived. And because targeting was undefined, every list was a judgment call made from scratch. Restarting outbound on that base would have produced activity and no compounding. The order of operations mattered more than the volume: install the spine, define the buyer, then turn it on.

Finding 01

No CRM. GTM activity was tracked in Outlook tasks and the founder's memory.

What it meant

Nothing could be measured, delegated or handed to a future rep. Every restart began from zero.

Finding 02

ICP was undefined — targeting spanned industries, company sizes and seniority levels.

What it meant

List building was a weekly judgment call, which made messaging generic and made outbound feel like guesswork.

Finding 03

ZoomInfo intent and Sales Navigator were licensed but not used intentionally.

What it meant

The company was paying for the highest-value signal in the stack and sourcing leads manually anyway.

Finding 04

Outbound had been paused since April, with Expandi configured but not operating as a complete engine.

What it meant

Restarting without infrastructure would have repeated the same stall — activity without a system to catch it.

Finding 05

One seller, and he was the founder, splitting attention across delivery, client work and the business.

What it meant

Anything requiring more than ~30 focused minutes a week would not survive contact with a real founder calendar.

03
The Rebuild

What we built

  • HubSpot as the CRM spine — company and contact architecture, lifecycle stages, lead statuses, pipeline structure, activity logging, Outlook sync and follow-up task automation.
  • A defined healthcare-first ICP: senior marketing leaders at US healthcare organizations above a set revenue and headcount floor, with construction, electronics and food & beverage as secondary expansion segments.
  • Layered targeting logic that turns the ICP into a repeatable filter — firmographics, then seniority and experience, then a recent job-change trigger, then an agency-intent overlay.
  • Intent-tiered ZoomInfo workflows on an automated weekly lead-delivery cadence — a high-intent workflow and a broader mid-intent workflow, both pushing straight into HubSpot.
  • Auto-updating HubSpot lists and views — High Intent Contacts, Mid Intent Contacts, High Intent Companies — so the weekly export requires no manual sorting.
  • Expandi configured for LinkedIn on High Intent only, with safety limits, warm-up, daily rotation and a HubSpot connector, running Jason's own messaging cadence rather than an agency voice.
  • Smartlead and Maildoso email infrastructure — segmented email infrastructure by intent tier, with domain and inbox warm-up, sending limits and rotation.
  • Founder-led messaging structure: LinkedIn first-touch scripts, email templates, objection handling and three entry angles built from what the ICP actually feels — AI and SEO volatility, paid media efficiency, and creative and brand gaps.
  • The operating documentation that makes it survivable without us: daily outbound workflow, weekly review rhythm, CRM usage rules, an operating playbook and activation checklists, all stored in a shared Drive Jason owns.
04
Operating Rhythm

How the work ran

Two phases, deliberately sequenced. December was infrastructure only — no volume sending, no vanity activity. January was activation: sequences live, messaging in market, weekly calls to review what came back. Throughout, the test we applied to every build decision was whether Jason could operate it alone in about thirty minutes on a Monday morning. Anything that failed that test got simplified or automated, not documented harder.

  1. 01DiscoveryStrategy call surfaced the real constraint: no CRM, no ICP, outbound paused since April, and a founder managing GTM from an Outlook task list.
  2. 02Phase 1 — FoundationDec 15–31. HubSpot spine, ICP definition, targeting logic, ZoomInfo intent workflows, Expandi safety configuration, Smartlead and Maildoso provisioning, baseline messaging. Infrastructure first, no high-volume sending.
  3. 03Phase 1 reviewDec 29 alignment check before Phase 2 was invoiced — a deliberate gate so activation only started on a foundation both sides agreed was actually built.
  4. 04Phase 2 — ActivationJanuary. Multichannel sequences across LinkedIn, email and call, campaign and case-study assets, founder-led thought leadership material, live sequence reviews and weekly optimization.
  5. 05CalibrationTuning against real-world friction: blank ZoomInfo company fields, irrelevant intent topics, deliverability guardrails, and cost-conscious decisions about how far to upgrade the stack.
  6. 06HandoffDocumentation finalized, walkthroughs recorded, ownership transferred. Jason driving the live workflow himself with no ongoing obligation.
05
From the Field

Receipts from the engagement

Fig. 01 · Engagement scope · Dec 15, 2025
Outbound System Build — engagement scope

The original build document. It names the starting state plainly — no CRM, undefined ICP, outbound paused, Outlook workflows — and sequences infrastructure before activation.

Fig. 02 · ICP definition · Dec 2025
Ideal Customer Profile — healthcare-first

Where 'boiling the ocean' became a filter: a defined healthcare firmographic and senior marketing ICP, narrowed further by a recent job-change trigger and an intent overlay.

Fig. 03 · Operating playbook · handoff asset
Operating Playbook — how the system runs

The weekly lead-import cadence, written for the person who has to run it. It also states what the system does not do: it does not guarantee meetings or close deals.

Fig. 04 · Operating documentation · handoff asset
Daily Outbound Workflow — founder-led

Thirty to forty-five minutes, five steps, one rule: if it isn't in HubSpot, it doesn't exist. Built to fit a founder's day rather than a rep's.

Fig. 05 · Close-out summary · Jan 2026
Phase 1 close-out — delivered and out of scope

The close-out is explicit in both directions: what was built and live, and what was deliberately excluded — campaign management, SDR hiring, and performance guarantees.

06
What Changed

How the team operates now

The change is not that outbound got louder. It is that outbound now exists as a system with an owner. Signal arrives on a schedule instead of when someone remembers to look. Contacts land in a source of truth instead of a task list. And the founder's weekly job shrank to something a founder can actually sustain: about thirty minutes on Monday morning, with outbound running by nine.

System of record
Before

Outlook tasks and founder memory

After

HubSpot as single source of truth, with automated logging and follow-up tasks

Targeting
Before

Undefined ICP — 'boiling the ocean'

After

Healthcare-first ICP with layered firmographic, seniority, trigger and intent filters

Lead sourcing
Before

Manual, ad hoc, restarted from scratch each time

After

Intent-tiered ZoomInfo workflows on an automated weekly lead-delivery cadence into HubSpot lists

Channels
Before

Expandi stalled; outbound paused since April

After

LinkedIn on High Intent only, email across High and Mid Intent, both with safety guardrails

Founder's weekly job
Before

Undefined and open-ended, so it kept losing to client work

After

~30 minutes Monday to load campaigns; daily reply management in 10–20 minutes

Ownership
Before

Whatever existed lived with whoever set it up

After

Documented, walked through and fully owned in-house by Visual Identity Group

07
Results

What we can verify

Infrastructure
  • HubSpot CRM configured, structured and operational as the source of truth
  • ZoomInfo intent workflows live, scheduled and pushing into HubSpot automatically
  • Expandi and Smartlead campaigns active with deliverability and safety guardrails in place
  • Domains, mailboxes and warm-up healthy at handoff
System & Documentation
  • Healthcare-first ICP and repeatable targeting logic documented
  • Multichannel sequence structure operational across LinkedIn and email
  • Daily workflow, weekly rhythm, CRM usage rules and operating playbook written and stored in a shared Drive the client owns
  • Structure built to scale to a future rep without rebuilding it first
Founder Capability
  • Jason independently completed the end-to-end weekly workflow at handoff
  • Weekly operating cadence established — ~30 minutes Monday, outbound running by ~9 a.m.
  • Thought-leadership material identified from ~25 years of company-building experience
  • In-house operating ownership established at handoff; Jason could run the workflow independently

Deliberately absent from this report: pipeline value, closed revenue, meeting counts, reply rates and ROI. The agreement excluded performance guarantees and the engagement closed at handoff, so no audited outcome metric exists. What is claimed here is what the evidence supports — infrastructure installed, system documented, and the founder operating it himself. The operating playbook itself states that results compound after 30–60 days of consistent operation.

08
In Their Words

I really feel like we're gaining steam here. I'm starting to see it all come together.

Jason Weamer
09
Operating Assets

What stayed behind

  • HubSpot CRM — configured pipeline, lifecycle stages, lead statuses, auto-updating intent lists and views
  • Ideal Customer Profile document with tiers, personas, triggers and entry angles
  • ZoomInfo High Intent and Mid Intent workflows, scheduled and mapped into HubSpot
  • Expandi LinkedIn campaigns with safety limits, warm-up and rotation configured
  • Smartlead and Maildoso email infrastructure segmented by intent tier, with warm-up and rotation logic
  • Founder-Led Outbound Messaging Playbook
  • Outbound Revenue Engine Operating Playbook
  • Daily Outbound Workflow, Weekly Review Rhythm and CRM Usage Rules
  • Phase 1 close-out summary and activation checklists in a shared Drive owned by the client
10
Open Questions

What remained unproven

Every engagement leaves something unresolved. These are the limits of what this report can claim.

  • No audited pipeline, revenue or meeting outcome exists for this engagement, and none is claimed
  • Whether the founder-run cadence holds through busy delivery periods was not measured after handoff
11
Takeaway

The strongest outcome here is not a number. It is that the founder can run the thing without us — and that a rep hired next year inherits a system instead of a story.

12
Related Reading

The thinking behind this work

Build the foundation before you turn outbound back on.

If you want this kind of operating-partnership work in your own org, see how the Revenue Rebuild works today. Read the evidence first, then we can talk about your system.

Sources: the signed engagement scope, the Phase 1 close-out summary, the ICP document, the operating playbook and the workflow documentation produced during the engagement, plus call transcripts from the engagement period. The two Jason Weamer quotes are verbatim from recorded engagement transcripts. Real-world friction encountered during the build — blank ZoomInfo company fields, irrelevant intent topics surfacing under agency-adjacent searches, manual inbox checking in Smartlead, and cost concerns around further HubSpot upgrades — is described because it happened, not as a claim about the outcome. No performance metric is published because none was contracted, measured or audited.