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.