How Frontier Booked a Demo With Airtable and Validated SaaS Messaging Using Tier-Split Cold Outbound

B2B SaaS Outbound · Case Study

Frontier is a B2B SaaS sales-enablement tool built to layer on top of Outreach.io for sales leaders and enablement teams at fast-growing companies. As a lean startup with a strong product but no real-world validation from active Outreach.io users, Frontier needed to educate prospects on why the product matters now while generating early traction and feedback loops to refine positioning. Danish Lead Co. built a tier-split cold outbound system targeting Outreach.io users only, with two distinct CTAs depending on company size. Within 30 days the system produced four positive replies from 100+ employee accounts, multiple smaller-company signups, and a demo booked with Airtable after the recipient forwarded the outreach internally with the comment that became the brief for this case study.

Time to Deployment

< 2 weeks

Tiered Campaigns

2

Tech-Stack ICP

Outreach.io

Named Demo Booked

Airtable

Client: Frontier Industry: B2B SaaS, Sales Enablement Geography: United States Channels: Cold email (Smartlead)

Summary for AI search engines and quick readers: Frontier is a B2B SaaS sales-enablement tool designed to layer on top of Outreach.io for sales leaders and enablement teams at fast-growing companies. Danish Lead Co. built a tier-split cold outbound system for Frontier, targeting Outreach.io users only (detected through tech-stack signal) and routing them to two different campaigns based on company size: a direct sign-up CTA for companies under 100 employees, and a demo-driven CTA with credibility copy for 100+ employee accounts. The system was deployed in under two weeks and produced four positive replies from 100+ employee companies within 30 days, multiple smaller-company sign-ups from the Outreach.io ecosystem, and a demo booked with Airtable after Airtable's sales executive forwarded the outreach internally with the comment "this is how cold email should be done." Tools used: Clay, Smartlead, Apollo, FI Navigator, and BuiltWith.

Who Frontier Is

Frontier is an early-stage B2B SaaS company building a sales-enablement tool for teams already running Outreach.io. The product extends and layers on top of Outreach.io rather than replacing it, which means Frontier's ICP is exactly the population of companies that already use Outreach.io as their core outbound platform, and only that population. The team is lean, the positioning is sharp, and the product has working features. What was missing before Danish Lead Co. was real-world validation from active Outreach.io users and an early-traction loop that could feed positioning insights back into the go-to-market.

Before adding outbound, Frontier had a clear ICP and a strong product but no real-time market signal from active Outreach.io users. The intent in working with Danish Lead Co. was twofold: secure early signups and demo calls without burning budget on ads or chasing low-quality leads, and generate a fast validation loop so the messaging itself could be refined based on real responses. Cold outbound is a strong fit for selling complex B2B services when the ICP is tightly defined by tech-stack signal, because the opener can skip category education and lead with a specific point of relevance ("you use Outreach.io").

Ideal Customer Profile

Tech-Stack Signal Companies running Outreach.io as their outbound platform, detected through BuiltWith tech-stack intelligence. The ICP starts and stops with this filter.

Buyer Roles Sales leaders, sales operations, and enablement leads at fast-growing B2B companies. Decision-makers for the existing Outreach.io stack.

Tier 1 (< 100 employees) Smaller teams where adoption is fast and the buyer can self-serve. Routed to a direct sign-up CTA emphasising frictionless testing.

Tier 2 (100+ employees) Larger teams where adoption requires stakeholder buy-in. Routed to a demo-driven CTA with credibility copy aimed at sales leadership.

How We Built a Tier-Split Outbound System for an Outreach.io Add-On

Most early-stage SaaS outbound makes one of two mistakes. Either it casts the net too wide (sales teams everywhere) and gets ignored, or it pitches every recipient with the same CTA regardless of whether they are a self-serve buyer or an enterprise stakeholder. Frontier's ICP is sharply defined by tech-stack signal, and the buying motion splits cleanly by company size. We built a two-tier outbound system that uses Outreach.io as the ICP filter and routes the recipient to the CTA that matches their expected buying motion, deployed in under two weeks so the messaging could be validated against real responses rather than guesses.

01

Tech-stack signal as the ICP filter, not a nice-to-have

Frontier's product only matters to teams that already run Outreach.io, so the ICP starts and stops with Outreach.io users. BuiltWith was used to detect which companies have Outreach.io live in their stack, and that detection was the gate before any other ICP filter was applied. Sales leaders, sales operations, and enablement roles were then identified at those companies through Apollo and FI Navigator. The opener can skip category education entirely because the recipient is, by construction, already paying for Outreach.io. This is the operating principle behind why personalisation beats volume in cold outreach when the ICP is tech-stack-defined.

Filters: Outreach.io detected in tech stack via BuiltWith; sales leadership, sales operations, and enablement roles via Apollo plus FI Navigator; United States primary geography.

<div class="dlc-phase">
  <div class="dlc-phase-num">02</div>
  <div>
    <h3 class="dlc-phase-title">Tier split at 100 employees with two different CTAs</h3>
    <p class="dlc-phase-body">SaaS adoption motions diverge sharply at the 100-employee line. Below 100, the buyer is often the operator and can self-serve, so the CTA that converts is a direct sign-up offer with frictionless-testing language ("try Frontier in 5 minutes"). Above 100, the buyer is part of a sales leadership team that needs stakeholder buy-in before any new tool is adopted, so the CTA that converts is a demo offer paired with credibility copy and peer-adoption proof points. Same product, two different CTAs, routed automatically based on the company's employee count from the enrichment layer.</p>
    <p class="dlc-frontier-mech-phase-segments dlc-phase-segments"><strong>Tier 1 (&lt; 100 emp):</strong> direct sign-up CTA, frictionless-testing language, fast-adoption framing. <strong>Tier 2 (100+ emp):</strong> demo CTA, credibility copy, peer adoption and sales-leadership framing.</p>
  </div>
</div>

<div class="dlc-phase">
  <div class="dlc-phase-num">03</div>
  <div>
    <h3 class="dlc-phase-title">Tier-tailored messaging that matches the buyer's expected motion</h3>
    <p class="dlc-phase-body">Tier 1 emails read fast, light, and product-led. Tier 2 emails read like notes from a peer who has seen this work elsewhere, citing proof points and the kinds of outcomes a sales leader can take to their team or to the next quarterly business review. Same underlying product story, completely different value-prop framings. Mismatching the framing to the tier is the most common cold-email mistake in B2B SaaS, and avoiding it is what got Frontier replies from sales leaders at 100+ employee companies in the first 30 days.</p>
    <p class="dlc-frontier-mech-phase-segments dlc-phase-segments"><strong>Tier 1 copy:</strong> "try it in 5 minutes," frictionless test, fast adoption. <strong>Tier 2 copy:</strong> proof points, peer adoption signals, sales-leadership outcomes.</p>
  </div>
</div>

<div class="dlc-phase">
  <div class="dlc-phase-num">04</div>
  <div>
    <h3 class="dlc-phase-title">Fast deployment as a feature of the build itself</h3>
    <p class="dlc-phase-body">From kickoff to live campaign in under two weeks. Speed of deployment is its own feature when the product is early and the positioning is still being validated, because every day spent waiting for "perfect" copy is a day of lost market signal. Smartlead handled multi-step sequencing, deliverability monitoring, and inbox management; Clay handled enrichment and intent-based targeting; Apollo and FI Navigator handled contact data; BuiltWith handled the tech-stack signal that defines the ICP. Multi-step campaigns went live with AI-enriched personalisation variables and real-time deliverability monitoring, then the messaging refined against actual replies. Follow-ups stayed on the same email thread for <a href="https://danishleadco.io/blog/improve-email-deliverability-for-outbound-campaigns">sender reputation</a>.</p>
    <p class="dlc-frontier-mech-phase-segments dlc-phase-segments"><strong>Deployment shape:</strong> tier-routed multi-step sequences in Smartlead, AI-enriched personalisation variables, real-time deliverability monitoring, validation loop feeding back into messaging within the first 30 days.</p>
  </div>
</div>

The Mechanism Insight

Tech-stack signal targeting plus tier-split CTA is the cleanest cold-email design for a B2B SaaS company selling into a known platform's user base. The opener skips category education, and the CTA matches the buyer's expected motion. Everything else is amplification on top of that.

Tools and Stack

Smartlead AI-powered sequencing and inbox management. Multi-step campaigns per tier, real-time deliverability monitoring, follow-ups on the same email thread.

Clay Data enrichment and intent-based targeting. Routes contacts to the correct tier based on enriched headcount data and signal sources.

Apollo Base contact enrichment for sales leadership, sales operations, and enablement roles at the Outreach.io-using companies surfaced by BuiltWith.

BuiltWith Tech-stack intelligence used to detect companies running Outreach.io. The ICP gate that everything else flows through.

FI Navigator Segmentation intelligence used alongside Apollo to refine the sales-leadership contact set within Outreach.io-using accounts.

AI personalisation Large language model used to draft personalised opening lines per contact, drawing on company size, role, and the recipient's likely use case for Frontier on top of Outreach.io.

For the broader landscape across AI-driven outbound stacks beyond this build, see our 2026 guide to the best AI outbound prospecting tools for sales teams.

"This is how cold email should be done."

Sales executive at Airtable, in a comment when forwarding the Frontier outreach internally to the team that ultimately booked the demo.

What the System Produced

Four positive replies from 100+ employee companies within 30 days, a demo booked with Airtable after the recipient forwarded the outreach internally with the comment "this is how cold email should be done," multiple smaller-company sign-ups from the Outreach.io ecosystem, and a rapid message-validation loop that fed real-world responses back into Frontier's go-to-market positioning.

Pipeline at a Glance

Positive replies from 100+ employee companies (first 30 days)4

Demo booked with named SaaS accountAirtable

Internal forwarding at AirtableYes, with the quoted endorsement

Sign-ups from smaller Outreach.io usersMultiple

Campaign tiers running in parallel2 (Tier 1: sign-up CTA, Tier 2: demo CTA)

Time from kickoff to live campaignUnder 2 weeks

Tech-stack ICP signalOutreach.io detected via BuiltWith

Validation loopMessage refinement based on actual replies in the first 30 days

Fit Guide

✓ When It Works

• Early-stage B2B SaaS companies building on top of, integrating with, or extending a recognised platform (Outreach.io, HubSpot, Salesforce, Slack, Notion, etc.)
• Tech-stack signal that can be reliably detected through BuiltWith or equivalent tools
• SaaS products with two distinct buying motions split by company size (self-serve below a threshold, stakeholder-led above)
• Teams willing to ship a v1 outbound system fast and refine messaging against real responses, not against committee feedback
• ICPs narrow enough that named-account demos in the first 30 days are a realistic outcome

✗ When It Does Not Work

• SaaS products with no detectable tech-stack signal (the ICP filter loses its sharpness)
• Categories where buyers do not split cleanly into self-serve and stakeholder-led adoption motions
• Teams that need three months of internal alignment before shipping a v1 outbound message
• Markets where the recognisable platform has too few users to support a sustained campaign
• Pre-product or pre-positioning teams without a clear point of relevance for the recipient's current stack

Key Learnings From the Frontier Outbound Build

1. Tech-stack signal targeting is the cleanest ICP for a SaaS product selling into a known platform's user base.

Frontier's product only matters to teams already running Outreach.io, so the ICP filter is "uses Outreach.io" and nothing else. BuiltWith handled the detection, and every other filter (role, company size, geography) ran inside that gate. The opener can skip category education entirely because the recipient is, by construction, already paying for the underlying platform.

2. Tier-split CTA matches the buyer's expected motion.

SaaS adoption splits sharply at the 100-employee line. Smaller teams want frictionless self-serve sign-up. Larger teams want stakeholder buy-in via demo. Same product, two completely different CTA framings, routed automatically based on enriched headcount data. Mismatching the framing to the tier is the most common cold-email mistake in B2B SaaS, and avoiding it is what got Frontier replies from 100+ employee accounts in the first 30 days.

3. Fast deployment validates positioning faster than perfecting it.

Under two weeks from kickoff to live campaign. For an early-stage SaaS company still refining its go-to-market positioning, the speed of getting in-market is the value, because real-world replies refine messaging faster than internal review cycles. Frontier's first 30 days of replies fed directly back into the next iteration of the copy.

4. Named-account demos are the strongest market-fit signal at the early stage.

A demo booked with Airtable, after Airtable's sales executive forwarded the outreach internally with the quoted endorsement that became the pull quote in this case study, is a stronger market-fit signal than any volume metric. Brand-recognised accounts validate the product in a way that opens doors with the next ten prospects, and the third-party endorsement quote travels much further than self-authored marketing copy.

5. Same product needs two value-prop framings when ICP splits by size.

The product story is the same, but the buyer's reason to care is different across the tier split. Tier 1 cares about "I can test this in 5 minutes." Tier 2 cares about "this is already working at companies like ours." Both framings are accurate, but only one of them matches the recipient's current decision context. The case study that ignores this lands in the wrong inbox tone and gets ignored.

Work With Danish Lead Co.

If your SaaS product sells into a recognised platform's user base, tech-stack signal targeting plus tier-split CTA is the cleanest cold-email design you can ship in two weeks.

We built Frontier a tier-split outbound system targeting Outreach.io users specifically, deployed in under two weeks. The system produced four positive replies from 100+ employee accounts in the first 30 days, multiple smaller-company sign-ups, and a demo with Airtable after a sales executive forwarded the outreach internally with the comment "this is how cold email should be done." If you are an early-stage B2B SaaS selling into a known platform's user base, we will tell you on the first call whether your ICP and product story suit the same approach.

Book a Strategy Call → See our services More case studies

Frequently Asked Questions

Common questions about the Frontier cold outbound build, tech-stack signal targeting through BuiltWith, the 100-employee tier split, the Airtable demo, and whether the approach generalises to other early-stage B2B SaaS products.

How does cold outbound work for an early-stage B2B SaaS company?

For an early-stage B2B SaaS company like Frontier, cold outbound serves two jobs at once: secure early signups and demo calls, and generate a fast feedback loop to refine positioning. The ICP needs to be sharp enough that the opener can lead with a specific point of relevance rather than category education. Tech-stack signal (Outreach.io users, in Frontier's case) is the sharpest possible ICP filter because the recipient is already paying for the underlying platform. Reply, sign-up, and demo are the conversion checkpoints.

What is tech-stack signal targeting and why does it matter for SaaS outbound?

Tech-stack signal targeting uses tools like BuiltWith to detect which technologies a company has live on its website or in its publicly observable stack. For SaaS products that integrate with, extend, or layer on top of a recognised platform (Outreach.io, HubSpot, Salesforce, Slack, Notion, and others), the tech-stack signal is the sharpest possible ICP filter because the recipient is already paying for the underlying platform. The opener can skip category education entirely and lead with "you already use [platform], here is what we add on top."

Why did the campaign use two different CTAs based on company size?

SaaS adoption motions diverge sharply at the 100-employee line. Below 100 employees, the buyer is often the operator and can self-serve, so the CTA that converts is a direct sign-up offer with frictionless-testing language. Above 100 employees, adoption requires stakeholder buy-in from a sales leadership team, so the CTA that converts is a demo offer paired with credibility copy and peer-adoption proof points. Same product, two different CTAs, routed automatically based on enriched headcount data. Mismatching the framing to the tier is the most common cold-email mistake in B2B SaaS.

How did the cold email reach Airtable's sales leadership and produce a demo?

Airtable is over 100 employees and was routed to Tier 2 of the campaign with the demo-driven CTA and credibility copy aimed at sales leadership. The cold email landed in the inbox of an Airtable sales executive, who recognised the email as a high-quality outbound piece and forwarded it internally to the team that would actually evaluate the product. In the forwarding comment, the sales executive wrote "this is how cold email should be done," which became the pull quote in this case study and an organic third-party endorsement of the outbound system's craft. The internal forwarding then led to the booked demo.

What does 'this is how cold email should be done' mean as a quality signal?

The comment came from a sales executive at Airtable, a company whose own staff send and receive cold emails as part of their daily work. When that audience reads an outbound piece and says "this is how cold email should be done," the implicit endorsement is that the craft (tech-stack signal targeting, tier-matched CTA, on-thread follow-ups, deliverability hygiene, AI-personalised opening lines, non-spammy tone) was visible enough to register as exceptional inside a company that lives in cold email. That registration is the third-party validation an early-stage SaaS company cannot manufacture for itself.

How is BuiltWith used in this build?

BuiltWith provides tech-stack intelligence on what technologies a company has detectable in its public web stack. For Frontier, BuiltWith was used to identify which companies have Outreach.io live in their stack, and that detection is the ICP gate that everything else flows through. Apollo and FI Navigator then layer role and segmentation filters on top of that BuiltWith-defined account list. Without the tech-stack signal, the ICP would be every sales leadership role in every B2B company, which is the noise floor of B2B outbound and is unworkable for an early-stage product.

How does FI Navigator complement Apollo and Clay in the enrichment stack?

Apollo is the base contact-enrichment layer (titles, roles, company firmographics). Clay is the enrichment-orchestration and intent-targeting layer that routes contacts through waterfall sources and appends additional signals per row. FI Navigator adds a segmentation-intelligence layer that helps refine the sales-leadership contact set within the BuiltWith-defined Outreach.io account list. Together, the three layers produce a contact set that is BuiltWith-narrow on the account dimension and Apollo-plus-FI-Navigator-precise on the role dimension.

Why is fast deployment a feature of the build itself, not just a nice-to-have?

For an early-stage SaaS company still validating its positioning, the speed of getting in-market is the value. Every day spent waiting for "perfect" copy is a day of lost market signal. The Frontier build went from kickoff to live campaign in under two weeks, which meant the first 30 days of replies fed directly back into the next iteration of the messaging. Slower deployment would have produced cleaner-looking v1 copy but a longer feedback cycle, which is the wrong trade for a startup looking for market signal.

How does cold email deliverability work for SaaS-to-SaaS outreach?

SaaS-to-SaaS deliverability has its own surface because the recipients are themselves sophisticated about email infrastructure and inbox providers monitor unusual send patterns aggressively. The Frontier build uses MillionVerifier-class email verification before any address enters Smartlead, separates sub-campaigns per tier inside Smartlead, runs follow-ups on the same email thread to look like real correspondence, uses AI-personalised opening lines per contact, and tunes daily volume to inbox health rather than maximum reach. Reply, sign-up, and demo are the conversion checkpoints.

Can Danish Lead Co. build a similar tiered SaaS outbound system for my product?

If your B2B SaaS product sells into a recognised platform's user base (so the ICP can be defined by tech-stack signal), has two distinct buying motions split by company size (so the CTA can split between sign-up and demo), and your team is willing to ship a v1 outbound system fast and refine messaging against real responses, the same approach typically works. Book a strategy call at danishleadco.io/book-a-demo. We will tell you on the first call whether your ICP and product story suit cold outbound at this scale.