Write a GTM plan

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.

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.