Sales Battlecard

Acme · Sales Intelligence

01 / 08

Sales Battlecard · Q1 2026

Sales
Battlecard

Competitive Intelligence for the Field

Corpus & Coverage

9 competitive calls Jan – Mar 2026 2 Closed Won 4 Active / Strong 2 At Risk

Top competitors: Vercel (5 deals) · AWS Amplify (5 deals) · Cloudflare Pages (3 deals). Analysis synthesized from per-call intelligence briefs — no raw transcripts in this summary.

Acme Sales Intelligence · Q1 2026 · Internal use only

Sales Battlecard · Top 5 Actions

02 / 08

⚡ Top 5 Actions

What sales does differently — starting this week

01

Lead with TCO model, not features

Vercel's per-invocation pricing spike ($6K→$22K at ZephyrMedia on an 8x traffic bump) is the #1 conversion lever. Build the cost model in call 2, before trial. Every AE needs a 2-slide pricing comparison ready for any deal >5M req/month or 3x growth projection.

vs. VercelAll AEs

02

Run competitive trials — not solo Acme demos

Brightwave is at risk because Priya's Vercel preference was never tested against us. Structure every trial as "Acme vs. [incumbent] on build time and deploy cycle." Solo demos default to the incumbent. TechFlow's POC setup is the right model.

vs. VercelAEs + SEs

03

Book the economic buyer before trial results

In 4 of 10 Q1 deals (TechFlow, PolarAnalytics, GlobalRetail, DataStack) the EB was absent during the trial. Book the "business case preview" call with VP Eng or CTO before results exist. A champion presenting solo is a 50% close rate.

Top Loss RiskAll AEs

04

Lead Cloudflare deals with architecture clarity on day one

"Acme sits behind your Cloudflare CDN as origin — you keep your network investment." Don't wait for Wei Zhang to raise it. Say it in discovery: "You don't have to choose between us and Cloudflare."

vs. CloudflareAEs

05

Design a discretionary-budget pilot for stalled champions

DataStack stalled 6+ weeks because Owen wouldn't advocate without executive air cover. Fix: $5K/mo pilot under EM authority, no CTO approval needed. Champion becomes a data-advocate, not a vendor pusher.

Champion RiskAll AEs

Q2 Must-Win Matchups

ZephyrMedia — Vercel displacement; TCO model must land
TechFlow — Vercel finalist; POC + CTO engagement before Mar 26
CascadeHealth — Amplify displacement; urgency reset needed
Ironbridge — Amplify + Cloudflare; fintech reference is final gate

Sales Battlecard · Competitor Profile

03 / 08

Competitor · Primary Threat

Vercel

"We created Next.js — you get the best Next.js experience on our platform."

Genuine Advantages (Be Honest)

Next.js native — Vercel created it, ships features first. Every Next.js shop feels this. Don't dismiss it.
DX brand equity — "Polished DX" without trialing us (Priya, Brightwave). We win on DX evidence in side-by-side trials, not reputation.
Simpler at small scale — Individual dev or small team: fast, well-documented. We need a team-scale problem to win.

Win Pattern

The trigger: prospect had a bill surprise, is modeling growth, or is running infrastructure cost forecasts. Lead with TCO. Get VP Eng + Staff Eng in the same conversation. Don't pitch features — pitch predictability.

Vercel — Traffic Spike$22Kfrom $6K on 8x traffic (ZephyrMedia)

Acme — Same TrafficFlatBandwidth model — predictable at any scale

Our Strengths in This Matchup

Pricing model is the lever. At 5M+ req/month, per-invocation math breaks. Acme's bandwidth model doesn't. Build the cost model in call 2.
Framework-agnostic = enterprise risk story. Vercel owns Next.js and can deprecate, change pricing, or lock behavior. Acme doesn't own any framework. Lands with VPs and CTOs.
More mature enterprise motion. RBAC, audit logs, contractual SLA, named CSMs. Multiple Q1 deals surfaced compliance/SLA as requirements — areas where Acme has documented answers.
Build caching for monorepos. "80-85% of commits skip rebuild" — Marcus at TechFlow. For large, multi-repo codebases, Acme's build system is measurably faster.

Objections & Responses

Objection	Response Framework
"All-in on Next.js — Vercel feels natural"	Acme fully supports Next.js (SSR, ISR, Edge Middleware). "The question isn't which platform knows Next.js best — it's which one you want locked into as your stack evolves."
"Vercel offered us a discount"	"A discount on a broken pricing model is still a broken pricing model. Let me show you what the math looks like at 3x your current volume."
"Vercel has better DX"	Don't debate it. Propose the competitive trial: "Let's test head-to-head on your actual codebase — build time, preview cycle, rollback."
"Vercel is the market leader"	"They lead in Next.js mindshare. We lead in enterprise deployment velocity, pricing predictability, compliance. Which matters more in 12 months?"

"The math breaks at scale; can't explain to CFO why costs spike with traffic."— Cassandra Bell, VP Engineering, ZephyrMedia — on Vercel's per-invocation model

Sales Battlecard · Competitor Profile

04 / 08

Competitor · Incumbent Displacement

AWS Amplify

"You're already in AWS — we're the native frontend layer. No new vendor, no migration."

Genuine Advantages (Be Honest)

AWS procurement already approved. No legal review, no net-new vendor InfoSec questionnaire. Real friction we add.
AWS ecosystem integration. Cognito, AppSync, DynamoDB, IAM — all native. Heavy AWS backend teams feel this.
Default safety for AWS-committed orgs. Enterprise CIOs with AWS contracts don't want more vendors. Organizational inertia, not product quality.

Win Pattern

Sequence: (1) Build time benchmark in first technical call. (2) Atomic rollback demo — especially to ops/platform personas. (3) In compliance verticals, own the documentation lane: fast, specific, contractual. (4) TCO model with champion before CFO conversation.

Our Strengths — Evidence-Based

Build times: 5-8 min vs. 28-35 min. CascadeHealth, Ironbridge, Meridian — all acutely painful. Lead with the benchmark.
Atomic rollbacks: 30 sec vs. 25 min. "25-minute rollback window erodes your error budget" — Dmitri Volkov, Ironbridge. Moved a skeptic to conviction. In fintech/healthcare, this is an operational risk.
Compliance responsiveness. Leo at CascadeHealth got a generic AWS BAA from Amplify. Marcus sent Amplify-specific BAA + SOC 2 + pen test policy in under 24 hours. Speed and specificity are the differentiator.
Native Datadog integration. Ironbridge built fragile custom webhooks. Samantha Cho: "Cleaner than what we've built; I'd be deleting it."
TCO flips the cost story. Meridian: 0.5 FTE maintenance overhead on Amplify. CFO approved after TCO model. Build from the prospect's own numbers.

Objections & Responses

Objection	Response Framework
"We're an AWS shop — more vendors = friction"	"Acme runs on AWS under the hood. It's not a competing cloud — it's the best interface for deploying your frontend on your existing AWS investment. Your backend stays in AWS."
"Amplify is cheaper"	"Let's build the TCO together: maintenance overhead + build time in eng hours + staging overhead. Meridian found 0.5 FTE + 30 min/cycle. What's your number?"
"Our CISO needs to review any new vendor"	Send: pre-templated BAA, SOC 2 Type II, pen test policy in writing within 24 hours. Speed and specificity are the differentiator — not the documents themselves.

"The comparison to how Amplify handles enterprise questions is… not favorable to them."— Rachel Kim, VP Engineering, Meridian — on Marcus's 24-hour compliance documentation

Sales Battlecard · Competitor Profile

05 / 08

Competitor · Price & Consolidation

Cloudflare Pages

"One throat to choke — DNS, DDoS, CDN, and hosting in one vendor. And our free tier is generous."

Genuine Advantages (Be Honest)

Consolidation narrative is powerful. Ironbridge infrastructure team: "one throat to choke." Platform engineers managing sprawl feel this. We don't have a single-vendor pitch.
Generous free tier. For small/startup workloads, Cloudflare is genuinely cheaper. Don't fight this — we don't win at that scale.
Network + edge compute in one vendor. Teams already using Cloudflare Workers have natural pull toward Pages.

Win Pattern

Cloudflare displacement requires a concrete product limitation, not a feature comparison. StrataCommerce model: identify edge use case hitting Workers CPU/memory limits → 2-week trial measuring real revenue impact → resolve ecosystem concern on day 1.

Our Strengths — Evidence-Based

Edge function CPU/memory limits are a concrete product gap. StrataCommerce: 10ms/50ms CPU limits blocked checkout personalization. Alicia had to move logic server-side. Acme had no such constraint. This cost Cloudflare the deal.
Ecosystem objection has a clean reframe. Wei Zhang raised ecosystem separation concern. Priya: "Acme as origin behind Cloudflare's CDN — you keep your DNS, DDoS, CDN." Wei: "That changes the conversation." Say this in discovery, proactively.
Enterprise DX maturity. Marcus at Ironbridge: "Network company adding hosting vs. hosting company with network." Deploy Previews maturity, contractual SLAs, dedicated support — none at equivalent Cloudflare Pages depth.
Trial-validated revenue impact. StrataCommerce: 12% checkout conversion lift in 2-week trial on 20% production traffic. Real revenue beats benchmarks with economic buyers.

Objections & Responses

Objection	Response Framework
"Switching Pages means losing Cloudflare investment"	"You don't have to choose. Acme as origin behind Cloudflare's CDN — you keep DNS, DDoS, network. Layer, don't replace." Say this in discovery.
"Cloudflare Pages is free for us"	"Free is right for side projects. At team scale — preview environments, enterprise auth, compliance SLAs — the economics shift. What's the cost of one deploy outage?"
"One throat to choke / fewer vendors"	"Consolidation is right for infrastructure. For dev tooling, you want best-of-breed. Cloudflare's network is excellent; their hosting DX and enterprise support aren't their core product. Ours is."
"Cloudflare Workers handles our edge compute"	"It handles most cases. The question is whether CPU/memory limits on complex logic (personalization, checkout, A/B) become a ceiling. Let's trial one of those flows."

"That changes the conversation; we can layer this instead of replace."— Wei Zhang, CTO, StrataCommerce — on architecture clarity that Acme sits behind Cloudflare's CDN

Sales Battlecard · Training Scenarios

06 / 08

Training Scenarios

Based on actual language from Q1 calls

Scenario 1 · vs. Vercel · Brightwave / TechFlow archetype

"Our team is all-in on Next.js. Vercel created it — they're the obvious choice."

Don't say"Acme supports Next.js too." True but doesn't move the conversation.

"I hear you — Vercel's Next.js story is genuinely strong. What we're hearing from teams your size is that the platform choice looks different when you factor in pricing at scale, compliance, and a stack that might evolve. Would it be worth running a side-by-side build time comparison on your actual codebase — not a demo, your repo — before you decide?"

Leave-BehindBuild time benchmark proposal. "If Vercel is faster on your stack, you should know that. If we are, so should you."

Scenario 2 · vs. Amplify · CascadeHealth / Meridian archetype

"We're deep in AWS. Swapping Amplify means another vendor, contract, security review."

Don't say"We're really easy to migrate." Minimizes the concern.

"That friction is real — I won't pretend otherwise. Acme runs on AWS under the hood; not a new cloud. I can send our BAA, SOC 2, and pen test policy today. Most security reviews close in two weeks. We start with one low-risk site in one sprint before any larger migration."

Leave-BehindCompliance documentation packet + phased migration plan.

Scenario 3 · Champion Hesitation · DataStack / PolarAnalytics archetype

"I'd love to move this forward, but my CTO is risk-averse and I don't want to be the person pushing something new."

Don't say"Let's get your CTO on a call." Creates the political risk they're avoiding.

"That makes sense — I wouldn't want you in that position. Here's a path with no executive approval needed: we run a 2-week pilot under your existing engineering budget. Pick your highest-pain use case, we instrument it, you gather the data. You're not pushing a new tool — you're running an experiment. If the data doesn't support it, we close it down."

Leave-BehindPilot scope doc. Budget ~$5K/mo under EM discretionary authority. No CTO approval path.

"I feel better… I'd been avoiding it because I didn't see a path, but this is actually a path."— Owen Fletcher, EM, DataStack

Scenario 4 · vs. Cloudflare · Ironbridge archetype

"We want fewer vendors. We use Cloudflare for DNS and DDoS — adding Acme goes the wrong direction."

Don't say"But we're better at hosting." Completely misses the consolidation concern.

"The consolidation instinct is right — and it doesn't require choosing. Acme works cleanly as your origin server behind Cloudflare's CDN. You keep your DNS, DDoS, and network investment intact. You're not replacing Cloudflare — you're using a better tool for the hosting layer."

Leave-BehindArchitecture diagram — Acme-as-origin behind Cloudflare CDN. Reference the StrataCommerce pattern.

Scenario 5 · CFO Blocker · Meridian / GlobalRetail archetype

"The VP Eng is on board, but our CFO isn't convinced the economics justify migration."

Don't say"We're competitively priced." Not what CFOs care about.

"Let's build the ROI model using your numbers: staging cycle time per PR, engineers in review loop, burdened eng cost. At Meridian the math showed 0.5 FTE in Amplify overhead alone — that flipped the CFO from 'expensive alternative' to 'net negative cost.' Can we put 20 minutes on with you and your VP Eng?"

Leave-BehindTCO model template with engineer-hour inputs. Pre-fill with benchmarks; let prospect validate.

Sales Battlecard · Win / Loss Summary

07 / 08

Win / Loss Summary

Q1 2026 · 9 competitive calls · 2 Closed Won

Q1 Record by Competitor

Competitor	Q1 Wins	Active	At Risk	Key Differentiator
AWS Amplify	2 (Meridian, Ironbridge*)	2 (CascadeHealth, TechFlow)	1 (PolarAnalytics)	Atomic rollback 30s vs 25 min · Build caching 5-8 min vs 28-35 min · Compliance documentation speed
Vercel	0	3 (ZephyrMedia, Brightwave, TechFlow)	0	Pricing predictability at scale · Framework-agnostic risk story · Enterprise support maturity
Cloudflare Pages	1 (StrataCommerce)	1 (Ironbridge)	1 (PolarAnalytics)	Edge function runtime limits · Enterprise DX maturity · "Complementary not competitive" architecture reframe

*Ironbridge not closed won yet — 75/100 deal health, moving to proposal

Proof Points That Worked — Repeatable Patterns

1

Atomic Rollback Operational ROI

Ironbridge, Meridian

30-second rollback vs. 25 minutes moved Dmitri Volkov from skeptic to conviction. Rachel Kim shifted from "expensive alternative" to "risk-reduction investment."

Repeatable when

Ops/platform persona or fintech/healthcare with production risk sensitivity.

2

TCO Model Flips CFO Conversation

Meridian, StrataCommerce

Meridian: 0.5 FTE Amplify overhead + 30+ min staging cycles = Acme is net negative cost. CFO approved. StrataCommerce: 12% checkout lift over 2 weeks validated by trial revenue data.

Repeatable when

CFO or CTO in the conversation. Build from prospect's own numbers, not benchmarks.

3

Compliance Documentation Speed

CascadeHealth, Meridian

Marcus sent Amplify-specific BAA + SOC 2 + pen test policy in under 24 hours. Leo: "That's better than Amplify." Rachel's CISO approved after written answers, not verbal assurances.

Repeatable when

Healthcare, fintech, or any compliance-heavy vertical. Speed and specificity beat thoroughness and bureaucracy.

4

Ecosystem Reframe for Cloudflare

StrataCommerce

"Acme as origin behind Cloudflare's CDN — you keep your network investment." Wei: "That changes the conversation." This nearly cost the deal when raised late. Saying it proactively in discovery = zero cost.

Repeatable when

Any prospect using Cloudflare DNS, DDoS, or CDN who might raise consolidation concern. Say it in discovery.

Top 3 Deal Risk Patterns — Q2 Watch

#	Risk Pattern	Affected Deals	Mitigation
1	Economic buyer absent in late-stage deals	TechFlow, PolarAnalytics, DataStack	Book EB conversation before trial results exist. Minimum: one "business case preview" call with VP Eng/CTO.
2	Champion political hesitation	PolarAnalytics, DataStack (pre-pilot)	Discretionary-budget pilot model. Champion becomes data-advocate, not vendor pusher. No CTO approval required.
3	Solo Acme trial without competitive comparison	Brightwave	Structure trial as head-to-head build time + deploy cycle vs. Vercel. "Try Acme" defaults to incumbent.

Sales Battlecard · Sources

08 / 08

Sources & Methodology

Call Corpus — Q1 2026

Company	Date	Stage	Outcome	Competitors
ZephyrMedia	2026-01-08	Discovery	Active	Vercel (incumbent)
CascadeHealth	2026-01-16	Technical Eval	Active	AWS Amplify
Ironbridge Financial	2026-01-27	Champion Building	Active (75/100)	Cloudflare Pages, Vercel, AWS Amplify
PolarAnalytics	2026-02-11	Technical Eval	At Risk	AWS Amplify, Cloudflare Pages
StrataCommerce	2026-02-20	Closed Won	Won	Cloudflare Pages (displaced)
Brightwave	2026-03-10	Discovery	Active	Vercel (implicit preference)
TechFlow	2026-03-15	Technical Eval	Active	Vercel (finalist), AWS Amplify
GlobalRetail	2026-03-18	Champion Building	Active	None (custom CloudFront)
DataStack	2026-03-22	Late Stage	Stalled → Pilot	Vercel (ruled out)
Meridian Health Tech	2026-03-28	Closed Won	Won	AWS Amplify (displaced)

Methodology

Intelligence synthesized from per-call Intelligence Briefs (YAML frontmatter + markdown analysis) for 10 calls in Q1 2026. Analysis uses MEDDPICC, SPICED, and Behavioral Dynamics frameworks applied at the per-call level. Cross-call patterns identified via raw competitive aggregation artifact.

All quotes are sourced from call transcript analysis. Competitor characterizations reflect what was stated in calls — not independent research.

Internal Use Only — This document contains deal-specific competitive intelligence and prospect quotes. Do not share externally or include in prospect-facing materials without verification.

To update this document: Drop new call transcripts into transcripts/ and re-run the CI pipeline. This document is generated from analyzed per-call reports.