Write a GTM plan

Flowboard Enterprise Go-to-Market: VP Product Version

To: CEO | cc: Jordan Hale, CRO

Summary

Our enterprise deals come from teams already using Flowboard. Last year, deals with existing teams closed 3x faster, at 2x the contract size, and at nearly 5x the win rate of outbound deals. Jordan's plan invests most heavily in outbound, our weakest motion, and caps the free plan that creates our strongest one. I recommend we build the enterprise motion on product usage instead.

On the evidence we have, that motion supports about $3.4M of new enterprise ARR, with a funded path to $5M if product-qualified pipeline grows as expected. We should give the board that range rather than commit to $5M.

What the data shows (65 enterprise deals, last 12 months)

• Where the revenue came from: existing-user deals produced $1.38M of the $1.86M won.
• Where we lose: 26 of 36 losses were to companies already standardised on Miro, and outbound found most of them.
• What buyers told us: all 7 interviewed winners already had teams on Flowboard. All 4 Miro losses came down to the cost of migrating thousands of boards. When buyers described what we do better, they named the free plan teams can start on without IT.

Who we sell to

Primary target: companies with 1,000+ employees where two or more teams already use Flowboard. - Champion: the team lead whose people "refused to give it up." - Approver: IT or security, who signs off once enough people are already using the product.

The current list of large companies using Flowboard (24 accounts) splits into three tiers:

Who we don't target: companies standardised on Miro with no Flowboard usage. That describes most of the outbound pipeline, and we lost 17 of those 21 outbound deals.

Data gap to close before the board meeting: 24 accounts can't produce the roughly 50 product-qualified opportunities this plan needs. We need the full pool of qualifying accounts, including companies under 1,000 employees that look like past enterprise buyers. The capacity numbers below depend on that pool existing.

How self-serve and sales work together

1. Self-serve stays open. - No seat cap on checkout. - The free plan keeps unlimited users. - It feeds 70% of new paying teams and is the source of nearly every enterprise win.

2. Product defines a "product-qualified account" (PQA) and routes it to sales. - Trigger: a 1,000+ employee domain with any of these: - 2+ teams, - 25+ active users, - a security-page view, - an SSO request. - Product owns the scoring. Sales owns the response time. - Routing is by account signal, not by team size. A 15-seat team at a 60-person agency stays self-serve.

3. Enterprise features are the upgrade path. - Admin controls (SSO, SCIM, audit logs) appear in-product with a "talk to us / start a trial" path. - This gives IT a reason to engage without blocking the teams that are already working.

4. Fix the "no decision" problem. Five of our six losses on existing-user deals ended in no decision. The champion needs help getting IT to approve, not more prospecting. We will provide: - a security review pack, - an admin console demo, - a business case built from the account's own usage data.

5. No channel conflict. - AEs get credit for self-serve revenue that consolidates into their enterprise contract. - Self-serve keeps its own targets below the enterprise threshold.

What we say against the alternatives

Headline: "The diagramming tool your teams already chose — now ready for IT."

• Against Miro: don't pitch a company-wide replacement. Buyers have told us migration cost decides those deals, and we lose.
• Lead on what buyers said we do better: real-time diagramming that stays tidy.
• Lead on proof of adoption: "300 people are already on it."
• Where Miro is the standard, test positioning Flowboard as the diagramming tool alongside it. Treat this as a hypothesis and measure it on 5–10 deals before scaling.
• Against whiteboard photos and slides (no decision): the free plan lets a team start this week without an IT project. IT controls come later, when the usage justifies them.
• Against "the enterprise platform": that phrase is Miro's ground, and claiming it invites the head-to-head comparison we lose.

Capacity

Pipeline and revenue. These assume historical win rates and contract sizes hold.

People: - AEs: about 50 deals at roughly 10 per ramped AE needs 5–6 AE-years. - We have 3 AEs. Hire 4 more in Q1. - I'm assuming about a one-quarter ramp, which is plausible with 63-day cycles but needs validating with Jordan. - Sales engineer (1): owns security reviews and the no-decision problem. - Account manager (1): owns expansion across our 46 enterprise customers. - Product: a PQA scoring and routing squad, plus the enterprise feature roadmap. - Total: about 7 hires, versus 14 in Jordan's draft.

Path to $5M (the remaining ~$1.6M) has two options: 1. Stretch pipeline. At 76% win rate and $72.6K average, $5M needs about 90 existing-user opportunities. We should only fund this against evidence: - Checkpoint: if Q1 produces 15+ product-qualified opportunities, hire 3 more AEs in Q2. 2. Expansion. If the board counts expansion of existing enterprise customers as new ARR, those 46 accounts (~$2.9M base) are a real source. The board needs to settle that definition.

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

1. Cap the free plan at 3 users. → Drop it. - The free plan feeds 70% of new paying teams and seeds almost every enterprise win. - Buyers named it as a reason they chose us over Miro. - A cap forces conversations with teams that haven't adopted yet, and that kind of deal is where we lose most often.

2. Route every team over 10 seats to sales and remove checkout. → Route by account signal; keep checkout. - With 31,000 paying teams, a seat-count rule would bury AEs in small-company teams that will never be $64K deals. - It would also add friction to the self-serve revenue we already have.

3. Hire 8 AEs and 6 SDRs on Fortune 2000 outbound. → Hire 4 AEs, 1 sales engineer, and 1 account manager; no outbound SDR team. - Outbound wins 16% of the time at $36.8K over 190 days. - Reaching $5M through outbound would take about 850 opportunities. - An AE hired in Q1 on a 190-day cycle closes little or nothing in-year, so most of that headcount pays off in the following year. - If we want SDRs at all, use 1–2 to work product-qualified accounts, not cold lists.

4. Enterprise features (SSO, SCIM, audit logs, data residency). → Agree, with sequencing. - Ship SSO, SCIM, and audit logs first. Six Tier 1 accounts are asking for SSO now. - Build data residency against named deals. The bank and health accounts on our list are the likely candidates.

5. Messaging: "The visual collaboration platform for the enterprise." → Change it. - It positions us head-on against Miro on Miro's strongest ground. - Lead with the diagramming quality and bottom-up adoption that buyers say actually win the deal.

Where Jordan and I agree: we need more sales capacity and real enterprise features. We differ on where the pipeline comes from.

I'd like to walk Jordan through these numbers before the board meeting so we present one plan. That plan would be built on how our customers actually buy.

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.

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.