Write a GTM plan

Flowboard enterprise plan: turn team adoption into governed company adoption

Recommendation: Keep the $5M target, but build a product-led enterprise motion—not a cold-outbound motion powered by restrictions on self-serve. Sell first to companies where teams already depend on Flowboard, then help an internal champion bring IT and procurement along.

The target is achievable only if we generate substantially more qualified opportunities and ramp sales capacity early. Neither is proven today; the board should approve a milestone-based investment, not treat $5M as an assured forecast.

1. What the evidence says

The last 12 months of deals show markedly different economics:

These are small, non-random samples—not guarantees—but the direction is compelling. Product-qualified wins are nearly twice the size of outbound wins and close in one-third the time. The interviews reinforce the pattern: all seven interviewed winners already had teams using Flowboard; four of five losses had standardized on Miro.

Our advantage is existing user commitment plus differentiated diagramming, not a generic enterprise feature list.

2. Who we sell to

Primary ICP: Large companies with multiple active Flowboard teams, recurring diagramming or visual collaboration work, and a reason to consolidate purchasing or introduce governance.

Employee count helps establish potential, but adoption and buying intent should determine priority. We should not infer a winning industry segment from this small dataset.

Prioritize accounts using three signals:

• Adoption: active users, multiple teams, usage growth and repeat collaboration.
• Intent: SSO requests, security-page visits and explicit procurement questions.
• Commercial potential: a credible departmental rollout, sponsor and budget—not simply total employees.

Start with Brightfield Bank, Fennick Holdings, Corvel Logistics and Eastlake Health: each has multiple teams, meaningful activity, security interest and an SSO request. Aldergate Bank and Dunmore Holdings also merit immediate discovery, but their smaller active footprints make rollout potential less certain. Security-interested accounts such as Hartwell, Galloway and Upton form a second wave.

Map the buying group: a user champion, a departmental budget owner, and IT/security/procurement. Sell an initial governed deployment around demonstrated demand, with an expansion path.

The 24 listed companies are a starting queue, not sufficient pipeline. Even if all became qualified opportunities, applying the historical 76% win rate and $70K incremental ARR assumption yields only about $1.3M. We must discover many more qualified accounts across the installed base.

3. How self-serve and sales work together

Keep free adoption and self-serve checkout open. Free supplies 70% of new paying teams, and buyers explicitly value starting without IT. Capping free at three users would damage the mechanism that creates our strongest enterprise opportunities.

Likewise, crossing ten seats should trigger an optional sales-assist offer, not a purchasing barrier. Seat count alone does not establish enterprise need.

Build an account-level product-qualified motion:

1. Aggregate teams by company domain, with appropriate access and privacy controls.
2. Score sustained usage, multi-team adoption, growth and governance intent.
3. Offer relevant help in-product: “Bring your teams together with centralized administration and security.”
4. Route high-intent accounts to sales promptly; nurture lower-intent accounts while preserving checkout.
5. Equip AEs with an account adoption summary and a champion toolkit: rollout proposal, security documentation and an economic justification.

Sales should close the governance and purchasing gap, not force users through one. Customer success then drives onboarding, broader adoption and expansion.

Keep Jordan’s SSO, SCIM, audit logs and data-residency direction, but sequence delivery against buyer requirements. Establish a minimum enterprise-readiness package first; validate residency demand and delivery cost before committing to regions. These capabilities enable procurement; they are not our differentiation.

4. What we say against alternatives

Replace “The visual collaboration platform for the enterprise” with:

> Real-time diagramming that stays tidy—now governed for the teams already relying on it.

• Against Miro: Lead with diagramming and demonstrated user preference. Where Miro is entrenched, propose an approved specialist deployment rather than company-wide replacement. Do not assume customers will migrate thousands of boards.
• Against slides and whiteboard photos: Demonstrate a live, editable shared diagram for one recurring workflow. Prove improved collaboration through a bounded pilot rather than unsupported productivity claims.
• Against no decision: Establish the sponsor, purchase trigger and rollout outcome early. Enterprise governance must solve a current problem, not merely add features to a pitch.

5. Revenue, pipeline and capacity

Define the board target as incremental enterprise ARR added next year, excluding self-serve ARR already paid by teams that convert. Report new logos, conversion uplift and existing-enterprise expansion separately; do not count the same revenue twice.

Historical product-qualified ACV is $72.6K, but we do not know the existing self-serve revenue attached to those wins. For planning, use $70K incremental ARR per win as an assumption to validate.

• $5M requires 72 wins at $70K.
• At the historical 76% product-qualified win rate, that requires approximately 95 qualified opportunities.
• Target 105–110 qualified opportunities, allowing some execution cushion.
• At today’s ten annual wins per fully productive AE, 72 wins require 7.2 fully productive AE-years.

Three current AEs provide approximately 30 wins. Eight new AEs averaging six wins each during their first year would add 48: 78 wins and $5.46M at the assumed incremental deal size.

Thus, Jordan’s eight AE hires can be justified—but only with early hiring, sufficient pipeline and a credible ramp. At five wins per new AE, we reach only 70 wins, or $4.9M. Smaller incremental contracts or slower qualification would widen the shortfall.

Hire in Q1 against explicit pipeline and ramp gates. Start with two SDRs focused on installed-base account development, not six running broad Fortune 2000 lists. Provide named solutions/security support and customer-success capacity for enterprise onboarding. Product, engineering and data capacity must also fund account identification, routing and enterprise readiness.

6. What changes in Jordan’s plan—and how we govern it

I would:

• Reject the free-user cap: it weakens our strongest acquisition advantage.
• Reject mandatory sales above ten seats: it introduces friction without proving enterprise demand.
• Redirect outbound toward adopted accounts: historical cold outbound is slower, smaller and less successful.
• Retain AE investment conditionally: capacity is necessary, but cannot substitute for qualified demand.
• Keep governance features; sharpen positioning: security gets us approved; tidy real-time diagramming gets us chosen.

In the first 90 days, instrument account-level adoption, validate incremental contract economics, engage the six SSO-requesting accounts and establish the qualified-pipeline trajectory. Track incremental ARR, source-level conversion, sales cycle, AE ramp, rollout adoption and self-serve conversion/retention.

If those indicators do not support the hiring and revenue assumptions, reforecast openly. We should not manufacture enterprise “leads” by breaking the product-led engine.

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.

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.