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: grow from adoption, not forced upgrades

Recommendation: Build enterprise sales around companies whose teams already choose Flowboard. Preserve self-serve as our distribution engine; sell enterprise when adoption creates a governance or expansion need. Treat $5M as a conditional operating target—not a forecast justified by hiring alone.

1. What the evidence says

The 65 supplied opportunities show materially different businesses by source:

Product-qualified opportunities produced $1.38M—74% of won ARR—from 38% of opportunities. Outbound produced smaller contracts, much more slowly; 17 of its 21 losses were to Miro as the company standard.

The interviews reinforce the mechanism: all seven interviewed winners already had users, while four of five losses faced entrenched Miro deployments. These are small, selected samples, not guaranteed future conversion rates, but they strongly favor adoption-led selling over broad Fortune 2000 prospecting.

2. Who we sell to

Primary ICP: Companies with multiple active Flowboard teams, meaningful or growing usage, an internal champion, and an enterprise trigger: SSO, user provisioning, security review, fragmented purchasing, or broader deployment.

Company size is a filter, not qualification. A 15,000-person company with 18 active users is not automatically better than a 2,400-person company with 54.

Our first outreach cohort:

• Brightfield Bank: six teams, 54 active users, 36 paid seats, SSO request.
• Fennick Holdings: eight teams, 48 active users, 30 paid seats, SSO request.
• Corvel Logistics: five teams, 45 active users, SSO request.
• Eastlake Health: three teams, 30 active users, SSO request.

Contact Aldergate and Dunmore too, but establish deployment potential before forecasting enterprise contracts. Their explicit SSO requests matter; their current adoption is relatively shallow. Nurture Galloway, Hartwell, and Oakhurst through champions and usage growth rather than treating a security-page visit as buying intent.

The economic buyer is typically an IT or business leader; the entry point is the team champion. Qualification requires a concrete workflow, sponsor, governance need, plausible deployment scope, and decision process.

Deprioritize cold replacement of company-wide Miro. Pursue such accounts only when a differentiated workflow and motivated sponsor justify migration costs. Do not infer a banking or healthcare vertical strategy from this small account list.

3. How product and sales work together

Keep unlimited-user free collaboration and self-serve checkout above ten seats. Free supplies 70% of new paying teams. Neither attachment provides evidence that restricting it would improve total revenue.

Create a company-level product-qualified account system across free and paid teams:

• Combine team count, sustained activity, growth, paid adoption, security interest, and explicit requests.
• Prompt admins to discuss governance or rollout when relevant; keep ordinary purchases self-serve.
• Have sales contact champions with a specific value proposition—not “you crossed our seat limit.”
• Let sales assemble a cross-team rollout and procurement case. Let customer success drive adoption after purchase.

A seat threshold can trigger optional assistance, not a checkout blockade. Sales should earn the enterprise upgrade through centralized administration, deployment support, and an agreed expansion plan.

Measure free-to-paid conversion, self-serve ARR, activation, product-qualified pipeline, and enterprise conversion together. Compensate sales on incremental enterprise ARR, with account-level attribution, so existing self-serve revenue is not mistaken for growth.

4. Product and competitive positioning

Replace generic category messaging with:

> Turn complex team thinking into clear, live diagrams—then scale the tool your teams already choose, with enterprise control.

The buyer-reported distinction is real-time diagramming that stays tidy. Demonstrate it in a customer’s actual workflow rather than claiming universal superiority.

• Against Miro: Win the diagramming workflow and existing user preference, not a feature-checklist war. Where permitted, begin with a bounded departmental deployment rather than demanding wholesale replacement. Migration support should follow demonstrated demand.
• Against photos and slides: Show the value of a shared, editable diagram through a short workflow pilot.
• Against doing nothing: Quantify the customer’s actual administrative burden, duplicated purchasing, or blocked rollout; agree on success criteria and a decision date.

Enterprise controls are purchase enablers, not our differentiation. Validate current capabilities and prioritize SSO, SCIM, auditability, and organization-level administration against live opportunities. Do not commit to data residency without evidence of incremental deals sufficient to justify its infrastructure and operating costs.

Use paid, time-boxed pilots only where needed, with a champion, measurable workflow outcome, security workstream, and commercial decision date.

5. Revenue, pipeline, and capacity

Finance should define the $5M target as annualized incremental contracted ARR, subtracting displaced self-serve ARR on conversions and excluding services. Report churn separately; if the board means company-wide net-new ARR, losses must also be covered.

At historical product-qualified ACV, $5M requires approximately 69 wins before subtracting existing self-serve revenue. That is a lower bound.

For operating planning, assume $65,000 incremental ARR per win—a hypothesis to validate against actual account spend:

• Required wins: 77; operating target: 80, yielding $5.2M.
• At a conservative 60% qualified-opportunity win rate, approximately 134 qualified opportunities.
• At today’s ten wins per AE annually, approximately eight productive AE-years.

One capacity model retains three AEs and adds four in January and four in April. Assuming three months of zero-output ramp followed by current productivity:

3 existing AE-years + 4 × 0.75 + 4 × 0.5 = 8 productive AE-years.

This supports 80 wins, but assumes timely recruiting, adequate pipeline, and successful ramp. At eight wins per productive AE-year, revenue falls to $4.16M.

Therefore, authorize up to eight hires, but release the second cohort only when qualified pipeline supports its capacity. Start with two account-development reps, focused on adoption-led accounts, rather than six broad-outbound SDRs. Budget a shared solutions/security specialist and an enterprise customer-success owner; verify workload before further hiring. Product must separately scope administration, qualification instrumentation, and security delivery before committing dates or staffing.

6. Changes to Jordan’s plan and board gates

I would reject the free-user cap and checkout removal, replace broad outbound with product-qualified account development, make hiring conditional, sequence enterprise features by purchase blockers, and replace generic messaging with workflow differentiation.

The largest unresolved issue is demand. We observed only 25 product-qualified opportunities last year. The 24 named companies are a starting list, not proof of the roughly 134 opportunities required; even if all bought at our planning value, they would contribute only $1.56M.

Within 30 days, deduplicate the installed base into companies, validate the first cohort, measure displaced self-serve ARR, and establish a credible quarterly pipeline build. Review conversion, incremental ACV, hiring ramp, and self-serve health monthly. If demand does not support the model, revise the forecast early—not restrict the product or hire ahead of evidence.

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.