Write a GTM plan

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 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.

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.