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.

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.

MEMORANDUM

TO: Chief Executive Officer FROM: VP Product DATE: October 24, 2023 SUBJECT: Counter-Proposal to CRO Enterprise GTM Plan: Path to $5M New Enterprise ARR

*

Executive Summary

Reaching $5M in new enterprise ARR next year is achievable, but Jordan’s draft will choke the very engine that powers our business.

Jordan’s proposal relies on a legacy top-down playbook: restricting free/self-serve adoption and deploying cold outbound reps against Fortune 2000 accounts. The data from our last 12 months shows this approach is commercially unviable: * Cold outbound fails: Outbound win rates are 16%, sales cycles take 190 days, ACV is low ($36.8k), and 68% of losses go to Miro because they already hold the enterprise standard. * Product-Qualified Leads (PQLs) dominate: Enterprise deals originating from existing Flowboard usage boast a 76% win rate, a 64-day cycle, and an average ACV of $72.6k.

Flowboard does not win by out-shouting Miro in cold enterprise RFPs. We win via Product-Led Sales (PLS): landing virally with teams via our free and self-serve plans, and expanding into six-figure IT-sponsored enterprise contracts once organic adoption takes root.

---

What to Change in Jordan’s Plan & Why

---

1. Who We Sell To (Target ICP)

We do not target cold accounts. Our Enterprise ICP consists of: * Target Accounts: Mid-market and Enterprise companies (1,000–15,000+ employees), heavily indexing on engineering, architecture, product, and design organizations. * Entry Footprint: Organizations with $\ge$2 active Flowboard teams or $\ge$20 active users across free/self-serve tiers. * Economic Buyers: VP of IT / CISO (concerned with governance, security, consolidation) paired with internal VP/Director Champions in Product/Engineering. * Immediate Target List: The 24 large enterprises already using Flowboard (e.g., Corvel Logistics, Brightfield Bank). Six of these companies already have multiple teams, paying seats, and active requests for SSO—representing an immediate pipeline of ~$450k ARR.

---

2. The Product-Led Sales Engine: Product & Sales Alignment

Instead of sales acting as a barrier to product adoption, the product serves as the primary pipeline generation channel for sales.

``` [ Free Plan: Unlimited Users ] ──> [ Self-Serve Expansion (up to 50 seats) ] │ │ └───> [ Domain Consolidation Trigger ] <───┘ │ ▼ [ Enterprise Sales (SSO, Governance, Security) ] ```

1. Top of Funnel (Free): Maintain the unlimited-user tier to let individual squads adopt Flowboard without procurement hurdles. 2. Expansion Triggers (PQL Engine): Instrument automated alerts to the BDR/AE team when: * A single company domain crosses 20 active monthly users across workspaces. * A workspace admin visits `/security`, `/compliance`, or searches for "SSO". * Multiple corporate credit cards from the same domain are paying for disjointed self-serve accounts. 3. In-Product Enterprise Gates: * Domain Control & SSO: When IT attempts to enforce SSO, the domain is claimed, prompting an enterprise consolidation conversation. * Centralized Admin & Audit Logs: Free and self-serve plans lack cross-workspace audit logs, data retention policies, and SCIM provisioning.

---

3. Positioning Against Alternatives (Winning Against Miro)

In head-to-head enterprise RFPs against Miro, we lose (17 outbound losses last year were to Miro standards). Switching thousands of legacy boards is an impossible sell. We win by changing the battleground:

Key Narrative: "Miro is where teams brainstorm; Flowboard is where technical teams design, architect, and build. Keep Miro for casual sticky-notes, or standardize on Flowboard for clean, mission-critical systems architecture."

---

4. Capacity Model & Math to $5M New Enterprise ARR

Jordan’s proposal to hire 8 AEs and 6 cold SDRs adds excessive headcount burn with terrible pipeline efficiency. By focusing on PQLs and high-intent inbound, our reps will achieve substantially higher conversion and velocity.

#### Operating Assumptions (Derived from Historical Data) * Average Enterprise ACV: $70,000 (historical PQL average is $72.6k; outbound was $36.8k). * Target ARR: $5,000,000 $\rightarrow$ Requires 72 closed enterprise deals. * Win Rate: 60% (blended between 76% historical PQL win rate and 40% inbound demo rate). * Deals Needed in Late-Stage Pipeline: $72 / 0.60 = \mathbf{120\text{ qualified opportunities}}$. * Sales Cycle: 65–75 days (allowing fast pipeline velocity and intra-year closes).

#### Staffing Requirements * Account Executives (AEs): * Experienced enterprise AE capacity on warm PQLs = 12 deals/year ($840k ARR quota). * 72 deals $\div$ 12 deals/rep = 6 fully productive AEs. * Plan: Retain our 3 current AEs; hire 4 new AEs (staggered: 2 in Q1, 2 in Q2 to account for ramp). Total = 7 AEs. * Business Development Reps (Product BDRs): * Hire 2 Product BDRs (not 6 cold outbound SDRs). * BDRs do not dial cold Fortune 2000 lists. They mine our 31,000 paying teams, identifying multi-license domains, mapping org charts, and securing meetings with IT directors and engineering leads. * Capacity: 2 BDRs generating 5 qualified enterprise pipeline meetings/month each = 120 qualified opportunities/year. * Total Headcount Investment: 6 new hires (4 AEs, 2 BDRs) vs. Jordan’s 14 new hires (8 AEs, 6 SDRs).

This delivers more than 50% savings in customer acquisition cost (CAC) while cutting execution risk.

---

5. Summary of Recommended Product & GTM Deliverables

1. Q1 Product Roadmap Enablers: * Ship SAML 2.0 SSO, SCIM user provisioning, and Centralized Domain Capture. * Build internal PLG scoring dashboard connecting Segment/Mixpanel product events to Salesforce/HubSpot (flagging $\ge$2 teams or SSO searches). 2. Q1 Pricing & Packaging: * Keep Free (unlimited users, 3 active boards). * Keep Self-Serve Pro/Team up to 50 seats. * Package SSO, SCIM, custom data retention, and audit logs exclusively in Enterprise. 3. Sales Enablement: * Arm sales with the "Architecture vs. Whiteboarding" competitive battlecards against Miro. * Launch warm outreach sequences immediately into the 24 identified large accounts already using Flowboard.