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.

To: CEO From: VP Product Re: Enterprise plan for the board

Bottom line: Jordan is right that enterprise revenue should run through sales. But the draft caps the motion that produces most of our enterprise deals, and it spends hiring budget on the motion that loses most often. I'd keep the free plan open, route accounts on buying signals, hire against proven pipeline, and present $3.0M committed with $5M as a stretch tied to specific gates.

What the last 12 months show (65 enterprise opportunities, 29 won, $1.86M ACV)

Across all 36 losses, 26 went to Miro as company standard and 10 to no decision. All seven enterprise wins in the interviews had teams already using Flowboard.

Who we sell to

Our best enterprise buyers are large companies where we already have several teams. Of the 24 companies over 1,000 employees using us, 16 have looked at our security page in the last 30 days. Six have also asked for SSO: Aldergate, Brightfield, Corvel, Dunmore, Eastlake and Fennick. Together they hold 116 paying seats. That's the first account list, and it's warm.

I would not start with Fortune 2000 cold outbound. That motion wins 16% of the time, and the companies on those lists are the ones most likely to have standardised on Miro.

How self-serve and sales work together

• The free plan stays open. A 3-user cap breaks the motion that generated 19 of our 29 wins. The enterprise deals came from teams that grew to hundreds of people on free, with designers who "refused to give it up." A cap doesn't make those teams call us. It sends them to Miro, or it keeps them on the free plan without ever reaching the buyer.
• Routing should follow signals, not one seat number. Route an account to sales when it has three or more teams in one company, asks for SSO or SCIM, views the security page, or passes about 25 paying seats. Self-serve checkout stays available below that line. Removing checkout at 10 seats would push paying mid-size teams into a sales cycle they don't need, and we'd lose that ARR.
• Division of labour. Sales owns the contract, the security review and the SSO rollout. Product owns in-app signals, admin controls and the usage data that tells sales where to go. AEs work the warm account list, not cold lists.

What we say against the alternatives

• Against Miro: Don't compete on feature parity. Buyers chose us for real-time diagrams that stay tidy and a free start that doesn't need IT. "The visual collaboration platform for the enterprise" puts us in Miro's category and invites a feature comparison we lose. I'd use: "The whiteboard your teams already chose, now with the controls IT needs."
• Where Miro is already company standard, we lose most of the time. Don't spend outbound effort there. Instead, scope a Miro board import. Buyers cited migrating thousands of boards as the reason they stayed. If we can make the migration a file import, we can contest some of those standardisation decisions. Engineering needs to size this.
• Against no decision (10 losses): My hypothesis is that these stall in IT or security review. SSO, SCIM and audit logs address exactly that. Sales should check lost-deal notes to confirm.

Capacity

• Three AEs closed 29 deals, about ten each, or roughly $620K per AE. New AEs take around six months to ramp.
• The binding constraint is pipeline, not AE headcount. At the product-qualified average of $72.6K, $5M is about 69 wins. At a 76% win rate, that needs roughly 90 product-qualified opportunities a year. We have 25.
• Hiring eight AEs before that pipeline exists leaves most of them waiting. Six SDRs working outbound would be pointed at our lowest-converting motion.
• My estimate: three current AEs plus four hires in Q1 (about half a year of productivity each) gives roughly five effective AEs, or about $3.1M. The large-account program could add $0.5–1M. That supports a $3.0–3.5M base. The $5M case requires roughly tripling product-qualified pipeline and having the new hires productive by Q3. Nothing in the data shows that yet.

What I'd change in Jordan's plan, and why

1. Keep the free plan unlimited. It produces the enterprise pipeline, and a cap would reduce that pipeline.
2. Replace the 10-seat rule with signal-based routing (see above) and keep checkout below about 25 seats. This sends sales the accounts most likely to buy without cutting paying self-serve revenue.
3. Hire four AEs now and two more on a gate: 40 or more qualified product-qualified opportunities in a quarter, and a trailing win rate above 60%. If the gate isn't met, we don't carry the cost.
4. Cancel the six outbound SDR roles. Put two SDRs on inbound demo follow-up (40% win rate, and most inbound losses were to Miro or no decision, so speed-to-follow-up matters). Put two on expansion of the 24 large accounts. Hold two until the gate is met.
5. Build SSO, SCIM and audit logs first. Six accounts have asked for SSO, and 16 of 24 large accounts have looked at the security page. Defer data residency. No deal in the last 12 months cited it, so build it only when a named deal requires it.
6. Change the messaging as above and drop "for the enterprise."
7. Scope the Miro board import as a product workstream, with a decision in 30 days.

What I'd ask the board for

• A committed number of $3.0M enterprise ARR, with $5M as a stretch.
• Gates the board can track quarterly: qualified product-qualified opportunities, win rate, the six SSO accounts closed, and no-decision losses as a share of the total.
• Approval to hire four AEs now and two on the gate.

I'd rather present a number we can defend than one that depends on hiring eight people before we have the pipeline to keep them busy.