Write a GTM plan

To: CEO From: VP Product Subject: Enterprise GTM Plan: Hitting $5M New ARR via Product-Led Sales

Here is my assessment of Jordan’s enterprise draft and an alternative go-to-market plan to hit the board's $5M new enterprise ARR target next year.

If we execute Jordan’s traditional top-down outbound playbook, we will starve our self-serve engine and miss the $5M target. Our data shows we already have a repeatable, high-margin enterprise motion—it is Product-Led Sales (PLS), not cold outbound.

---

1. The Data: What’s Working vs. What’s Failing

An analysis of all 65 enterprise opportunities over the last 12 months ($1.86M total new ARR across 28 wins) reveals three starkly different motions:

\Note: 4 outbound wins totaling $147.2k (16% win rate).*

Why Cold Outbound Fails: 18 of our 21 outbound losses were to "Miro (company standard)." Win/loss interviews confirm that when Miro is entrenched, ripping and replacing thousands of boards top-down is a non-starter. Outbound AEs spend 6+ months chasing $37k deals with an 84% failure rate.

Why PQLs Win: Every single buyer in our win interviews already had teams using Flowboard ("Our designers refused to give it up"; "IT approved it because 300 people were already on it"). PQLs close 3x faster, at nearly 2x the ACV, and win 76% of the time. Notably, 4 of our 6 PQL losses were to "No decision" (not Miro)—meaning with better IT/security packaging and multi-threading, our PQL win rate could exceed 80%.

---

2. Who We Sell To (ICP & Target Accounts)

We do not sell to cold Fortune 2000 IT buyers. We sell to mid-market and enterprise companies (1,000+ employees) where Flowboard already has grassroots adoption across multiple teams.

We have two immediate buyer personas within these accounts: 1. The Champions (Design, Product, & Engineering Leads): They adopt Flowboard bottoms-up because our real-time diagramming stays tidy (unlike Miro’s freeform sprawl). 2. The Economic/Economic-Gatekeeper Buyer (IT, InfoSec, Procurement): Triggered when usage hits critical mass, shadows IT thresholds, or requires SSO/security reviews.

Immediate Pipeline: Looking at our user base today, we have 24 enterprises (>1,000 employees) with active self-serve/free footprints: * Tier 1 (Immediate Sales Ready - 6 Accounts): Aldergate Bank, Brightfield Bank, Corvel Logistics, Dunmore, Eastlake Health, and Fennick Holdings. All 6 have multiple teams (up to 54 active users), visited our security page in the last 30 days, and explicitly asked for SSO. At our $71k PQL ACV, these 6 accounts alone represent ~$425k in near-term ARR. * Tier 2 (High-Intent Expansion - 10 Accounts): Companies like Galloway Retail (9 teams, 36 active users) and Hartwell Group (4 teams, 48 active users) that viewed our security page in the last 30 days. * Tier 3 (Nurture/Expand - 8 Accounts): Large enterprises (e.g., Redfern, Thornbury Bank) with 2–3 isolated teams where we need to bridge internal silos before pitching IT.

---

3. How Self-Serve and Sales Work Together

Self-serve is not competing with enterprise sales; self-serve is our enterprise customer acquisition cost (CAC) engine. Today, 70% of our 31,000 paying teams come from the free plan.

Instead of erecting paywalls that block adoption, Product and Sales will run a 4-step Land-Consolidate-Close loop:

1. Frictionless Land (Product): Keep the free plan unlimited in users (3 boards/user) and keep self-serve checkout completely open. Let teams inside 5,000-person companies spread Flowboard virally across departments without needing IT or procurement approval. 2. Domain Aggregation & PQL Scoring (Product + Data): Build internal tooling that groups accounts by corporate email domain (`@aldergate.com`). Trigger an automatic PQL alert to Sales when a domain hits any of these thresholds: * $\ge 3$ separate teams or $\ge 25$ active users across an enterprise domain. * Admin/user views the Security page or clicks "Request SSO / Enterprise." * Self-serve spend crosses $5,000/year across corporate credit cards. 3. In-Product "Trojan Horse" Prompts (Product): Show non-intrusive prompts to workspace admins at large domains: "8 other teams at Corvel Logistics use Flowboard. Want to consolidate billing and unlock SSO?" 4. Consultative Consolidation (Sales): Sales reaches out to Champions and IT not with a cold pitch, but with an audit: "You have 54 users across 6 teams paying on separate credit cards. Let’s consolidate your billing, put them under SSO/SCIM, and give you a volume tier."

---

4. Positioning & What We Say Against Alternatives

Jordan’s proposed messaging ("The visual collaboration platform for the enterprise") puts us head-to-head against Miro on their home turf. We will lose that fight.

Our Positioning: "Real-time diagramming and whiteboarding that actually stays tidy—built for product, design, and engineering teams, and ready for enterprise IT."

How We Win Against the Alternatives: * Against "Miro is our company standard" (Our #1 Loss Reason): Don't ask IT to rip and replace Miro company-wide. Position Flowboard as the specialized diagramming standard for technical/design teams where Miro is too messy, OR build a 1-click Miro Board Importer so entrenched teams can migrate without losing thousands of boards (directly solving the objection from 4 of our 5 loss interviews). * Against Status Quo / "No Decision" (Our #1 PQL Loss Reason): Arm champions with an ROI & Security Kit showing IT the risk of unmanaged "shadow IT" diagrams living on personal/fragmented accounts, making enterprise consolidation the safest choice.

---

5. What I Would Change in Jordan’s Plan (and Why)

---

6. Capacity & Math to Hit $5M New ARR

To hit $5M in new enterprise ARR next year, here is the capacity math:

• Deal Volume Needed: At our PQL average ACV of $71,000, $5M requires ~70 closed-won deals (vs. 28 this year).
• Pipeline Needed: Assuming a conservative 65% blended win rate on PQL/warm inbound deals, Sales needs to work ~108 qualified enterprise opportunities next year.
• AE Capacity: Today, 3 AEs close ~10 deals/year each (30 total) while wasting half their time on 200-day outbound losses. Focused purely on 63-day PQLs and warm inbound, a ramped AE can comfortably close 12–14 deals/year (~$850k–$1M ARR/AE).
• Hiring Plan:
• Keep our 3 current AEs (expected yield: ~36–40 deals / $2.7M ARR).
• Hire 5 new AEs in Q1 (ramping to ~6–7 deals each in Year 1 = ~32 deals / $2.3M ARR).
• Hire 2 Product-Led SDRs (to map org charts inside our 31,000 paying teams and connect AEs with IT/Procurement) and 1 Sales Engineer (to handle security reviews and accelerate the 63-day cycle).

Bottom Line: We don't need to break our product to build an enterprise business. By turning our 31,000 self-serve teams into our enterprise hunting ground, shipping SSO/SCIM + Domain Claiming in Q1, and scaling to 8 PQL-focused AEs, we will hit the $5M target while accelerating—not cannibalizing—self-serve growth.

Flowboard enterprise plan: win through product-led adoption

Recommendation: Keep the self-serve engine intact and build enterprise sales around teams already getting value from Flowboard. The evidence favors converting in-product demand over broad cold outbound: these deals close faster, win more often, and are larger. We should fund enough sales capacity to pursue the $5M target—but tie hiring and enterprise investment to qualified demand, not a Fortune 2000 list.

Who we sell to

Prioritize companies where Flowboard is already spreading: multiple teams, growing usage, and signs of a security or administration need. The initial champion is likely a designer or other team lead; IT and security become buyers or approvers when the company wants broader rollout, SSO, or governance.

The large-company usage list gives us a practical starting point: 17 of 24 accounts viewed the security page, and two explicitly asked for SSO. Pair those signals with active users, paying seats, and multiple teams to prioritize outreach. Don’t assume every large company—or every team above an arbitrary seat count—is ready to buy enterprise.

How self-serve and sales work together

Protect the free plan. Today it has unlimited users, and it feeds 70% of new paying teams. Capping free at three users risks removing the very collaboration and internal spread that create enterprise demand.

Instead, use the product to identify account-level buying signals: adoption across teams, rising active users or seats, and security-page visits or SSO interest. Let teams continue to start, collaborate, and buy self-serve. Offer sales help when signals suggest a broader rollout or an enterprise requirement—not as a checkout gate.

Sales should turn successful team adoption into company-wide deployment: align stakeholders, address security and procurement, and support rollout and migration. This makes the product the entry point and sales the path to a larger, governed deployment.

What we say—and don’t say—against alternatives

“The visual collaboration platform for the enterprise” is too generic. Our sharper position is: Flowboard makes real-time diagramming that stays tidy easy for teams to adopt—and easier for enterprises to approve once it spreads.

In the last 12 months, product-qualified deals—teams already using Flowboard—won 19 of 25 opportunities (76%), with an average winning contract of about $73K and a roughly 66-day sales cycle. Outbound won 4 of 25 (16%), with an average winning contract of about $37K and a much longer cycle. Interviews reinforce the pattern: all seven interviewed buyers who chose Flowboard already had teams using it.

Miro is the main competitive obstacle, not a reason to claim generic enterprise superiority. Four of five interviewed losses had standardized on Miro, and moving thousands of boards was a barrier. Don’t lead with a rip-and-replace pitch. Win a team or workflow where tidy, real-time diagramming matters; expand after demonstrating value. Make migration and coexistence easier where we can.

SSO, SCIM, audit logs, and data residency can help clear enterprise buying requirements, but they aren’t our differentiation. Prioritize SSO, SCIM, and audit logs; validate demand and deal impact before committing to the potentially heavier data-residency investment.

Capacity and the $5M target

The 65 logged opportunities produced 29 wins worth about $1.86M—roughly in line with today’s $64K average contract. At that average, $5M requires about 78 wins; at the product-qualified average of $73K, it requires about 69. That is roughly 2.4–2.7 times the observed win output.

At today’s stated productivity of about 10 wins per AE per year, plan for roughly eight productive AE-equivalents. With three current AEs, that implies about five additional AEs if all are fully productive. Hire early enough to account for ramp, and gate any further hiring on qualified pipeline and conversion—not just a calendar plan. The current product-qualified volume also must grow substantially: 19 wins from 25 opportunities is strong conversion, but cannot by itself support the target at today’s volume. Track the adoption signals and enterprise-qualified pipeline needed to scale it.

What I’d change in Jordan’s plan

• Keep free unlimited by users; don’t remove self-serve checkout above 10 seats. Both changes add friction to a channel that supplies most new paid teams and could slow the adoption that drives our best enterprise wins.
• Replace six outbound SDRs targeting Fortune 2000 lists with focused account development. Outbound won 4 of 25 logged opportunities and often encountered entrenched Miro standards. Prioritize named accounts showing Flowboard usage and buying signals; use a small, targeted outbound motion to complement product-led demand.
• Hire to the evidence-based capacity need, not 11 AEs by default. Plan for eight productive AE-equivalents, stage incremental hiring against pipeline, and ensure the team can support enterprise rollout as well as close deals.
• Make enterprise features a buying enabler, not the headline. Prioritize the security capabilities buyers need, but lead with Flowboard’s distinctive diagramming experience and bottom-up adoption.

The core strategic shift is from forcing teams into sales to helping proven adoption become an enterprise deployment.

Enterprise GTM: VP Product recommendation

Bottom line: Jordan's plan sends our new hires at the channel that works worst and puts friction on the channel that works best. I'd back the enterprise features and some added sales capacity, but build the motion around the teams already using Flowboard. The board should see $5M as a stretch and about $3.4M as the likely case.

What last year's deals show

Last year we worked 65 deals, won 29, and booked about $1.86M of new ARR.

Outbound is two-thirds of the effort and 8% of the revenue. Of its 21 losses, 17 went to Miro as the company standard.

Across all sources, Miro took 26 of our 36 losses. "No decision" took 10, including 4 of the 6 product-qualified losses. The interviews agree: every win had teams already on Flowboard, and four of the five losses were Miro-standardised companies where switching meant migrating thousands of boards.

Who we sell to

Primary customer: a company with Flowboard already in several teams, where Miro is not yet the standard and IT is starting to engage.

The usage data lets us tier the 24 large companies already on Flowboard: - Tier A (6 accounts): asked for SSO. All six also viewed the security page. Aldergate, Brightfield, Corvel, Dunmore, Eastlake and Fennick together have 27 teams and 116 paying seats. Sales owns these now. - Tier B (10 accounts): viewed the security page but haven't asked for SSO. A product-led nudge and a light sales touch. - Tier C (8 accounts): no IT signal yet. Keep nurturing in-product.

Seat count is the wrong trigger. Aldergate (10 seats) and Dunmore (4 seats) asked for SSO and would be missed by a ">10 seats" rule. Six of the ten accounts above 10 seats have shown no IT interest.

Two gaps in this data: - The file covers only companies over 1,000 employees, so it understates our real product-qualified pool. - We don't record which incumbent tool a prospect uses. We should add that field now, because "Miro is the standard" predicts the loss.

How self-serve and sales work together

Self-serve generates demand and sales converts it.

1. Free plan stays open. It feeds 70% of new paying teams, and buyers cite "a free plan teams can start on without IT" as something Miro doesn't offer.
2. Checkout stays open at every size. Sales is triggered by signals: an SSO request, security page views, three or more teams in one domain, or a domain crossing an active-user threshold. A rep reaches out while the team keeps buying normally.
3. Sales sells the consolidation: security review, one contract, and an admin console, backed by the customer's own usage data ("300 people already use it"). That also answers the "no decision" losses, which need a champion kit and a usage-based business case.
4. Inbound demos are routed to the same team. A 40% win rate is worth keeping, but half the losses are to Miro standards, so qualify for the incumbent tool early.

What we say against the alternatives

• Miro: don't contest "the enterprise whiteboard." Position as the best tool for real-time diagramming that stays tidy, and one that teams adopt without waiting for IT. Don't ask anyone to migrate. Win the team first and let usage make the case. Only 2 of 25 product-qualified deals went to Miro, versus 17 of 25 outbound deals.
• Status quo (photos and slides): show the cost of the current process using their own team's usage.
• Other tools: the data doesn't show us losing to any, so I'm making no claims about them.

Jordan's line, "The visual collaboration platform for the enterprise," is Miro's category claim, and it leaves out our actual advantages. I'd use something like: "Diagramming your teams already love, ready for IT to approve."

Capacity

Today each AE works about 22 opportunities a year (65 across 3 AEs) and closes about 10.

To reach $5M: - 60 product-qualified wins at 76% means about 79 opportunities, or $4.4M. - 12 inbound wins at 40% means 30 demos, or $0.66M. - That's about 109 opportunities, or roughly 5 AEs at today's load. - Product-qualified cycles are 63 days against 190 for outbound, so new AEs ramp faster on this mix. - Hire 3 AEs for 6 total. That gives a buffer, a faster ramp, and no outbound headcount.

Other hires (not part of Jordan's plan): - 2 reps who work product-qualified accounts, in place of 6 outbound SDRs. - 1 solutions engineer for security reviews. - 1 RevOps/growth analyst to build account-level usage scoring.

That's 7 sales-side heads against Jordan's 14, plus the engineering squad below.

The real risk is volume, not headcount. $5M needs product-qualified opportunities to roughly triple, from 25 to about 79. At double (50 opportunities), we land near $3.4M. The 24-company list can't deliver that alone, so RevOps needs to size the full pool, including sub-1,000-employee companies, before we commit to the board.

Engineering sequence: 1. SSO and SCIM first. Six accounts have already asked, and IT approval is the gate in our win stories. 2. Audit logs next. 3. Data residency only when a named deal requires it. Nothing in the loss data points to features. We lose to incumbency and indecision, so features are a gate, not a growth driver.

What I'd change in Jordan's plan

Why Jordan's plan lands short in-year (my estimate): an outbound AE produces about $368K a year (10 deals × $36.8K). New hires starting in Q1 won't see a first outbound close until around Q3, so 8 AEs yield well under $1M this year. Adding that to last year's $1.86M gives roughly $2.6M, before counting damage from the free cap and checkout changes to our best channel.

What I'd ask the board for

• Commit to about $3.4M, with $5M as the stretch if product-qualified volume triples by mid-year.
• Approve the smaller hiring plan and the SSO/SCIM squad.
• Review progress quarterly on product-qualified opportunity count, win rate, and the share of losses to Miro.

I'd like to walk Jordan through this before the board meeting. We agree on the target and on the need for enterprise features. We disagree on where the next dollar of sales effort should go.