Write a GTM plan

Flowboard enterprise plan: win through product-led adoption

Recommendation: Keep the self-serve engine intact and build enterprise sales around teams already getting value from Flowboard. The evidence favors converting in-product demand over broad cold outbound: these deals close faster, win more often, and are larger. We should fund enough sales capacity to pursue the $5M target—but tie hiring and enterprise investment to qualified demand, not a Fortune 2000 list.

Who we sell to

Prioritize companies where Flowboard is already spreading: multiple teams, growing usage, and signs of a security or administration need. The initial champion is likely a designer or other team lead; IT and security become buyers or approvers when the company wants broader rollout, SSO, or governance.

The large-company usage list gives us a practical starting point: 17 of 24 accounts viewed the security page, and two explicitly asked for SSO. Pair those signals with active users, paying seats, and multiple teams to prioritize outreach. Don’t assume every large company—or every team above an arbitrary seat count—is ready to buy enterprise.

How self-serve and sales work together

Protect the free plan. Today it has unlimited users, and it feeds 70% of new paying teams. Capping free at three users risks removing the very collaboration and internal spread that create enterprise demand.

Instead, use the product to identify account-level buying signals: adoption across teams, rising active users or seats, and security-page visits or SSO interest. Let teams continue to start, collaborate, and buy self-serve. Offer sales help when signals suggest a broader rollout or an enterprise requirement—not as a checkout gate.

Sales should turn successful team adoption into company-wide deployment: align stakeholders, address security and procurement, and support rollout and migration. This makes the product the entry point and sales the path to a larger, governed deployment.

What we say—and don’t say—against alternatives

“The visual collaboration platform for the enterprise” is too generic. Our sharper position is: Flowboard makes real-time diagramming that stays tidy easy for teams to adopt—and easier for enterprises to approve once it spreads.

In the last 12 months, product-qualified deals—teams already using Flowboard—won 19 of 25 opportunities (76%), with an average winning contract of about $73K and a roughly 66-day sales cycle. Outbound won 4 of 25 (16%), with an average winning contract of about $37K and a much longer cycle. Interviews reinforce the pattern: all seven interviewed buyers who chose Flowboard already had teams using it.

Miro is the main competitive obstacle, not a reason to claim generic enterprise superiority. Four of five interviewed losses had standardized on Miro, and moving thousands of boards was a barrier. Don’t lead with a rip-and-replace pitch. Win a team or workflow where tidy, real-time diagramming matters; expand after demonstrating value. Make migration and coexistence easier where we can.

SSO, SCIM, audit logs, and data residency can help clear enterprise buying requirements, but they aren’t our differentiation. Prioritize SSO, SCIM, and audit logs; validate demand and deal impact before committing to the potentially heavier data-residency investment.

Capacity and the $5M target

The 65 logged opportunities produced 29 wins worth about $1.86M—roughly in line with today’s $64K average contract. At that average, $5M requires about 78 wins; at the product-qualified average of $73K, it requires about 69. That is roughly 2.4–2.7 times the observed win output.

At today’s stated productivity of about 10 wins per AE per year, plan for roughly eight productive AE-equivalents. With three current AEs, that implies about five additional AEs if all are fully productive. Hire early enough to account for ramp, and gate any further hiring on qualified pipeline and conversion—not just a calendar plan. The current product-qualified volume also must grow substantially: 19 wins from 25 opportunities is strong conversion, but cannot by itself support the target at today’s volume. Track the adoption signals and enterprise-qualified pipeline needed to scale it.

What I’d change in Jordan’s plan

• Keep free unlimited by users; don’t remove self-serve checkout above 10 seats. Both changes add friction to a channel that supplies most new paid teams and could slow the adoption that drives our best enterprise wins.
• Replace six outbound SDRs targeting Fortune 2000 lists with focused account development. Outbound won 4 of 25 logged opportunities and often encountered entrenched Miro standards. Prioritize named accounts showing Flowboard usage and buying signals; use a small, targeted outbound motion to complement product-led demand.
• Hire to the evidence-based capacity need, not 11 AEs by default. Plan for eight productive AE-equivalents, stage incremental hiring against pipeline, and ensure the team can support enterprise rollout as well as close deals.
• Make enterprise features a buying enabler, not the headline. Prioritize the security capabilities buyers need, but lead with Flowboard’s distinctive diagramming experience and bottom-up adoption.

The core strategic shift is from forcing teams into sales to helping proven adoption become an enterprise deployment.

Memo: Alternative Enterprise Go-To-Market Strategy

To: CEO, Board of Directors From: VP of Product Subject: Response to CRO Enterprise Plan & Alternative Go-To-Market for $5M New ARR

---

Executive Summary

Jordan Hale’s proposed enterprise plan relies on a playbook built for a different kind of software: high-friction outbound sales into the Fortune 2000, artificial self-serve restrictions, and generic enterprise positioning.

A rigorous analysis of our historical deal data and active user base reveals a stark reality: Outbound cold enterprise sales do not work for Flowboard. When we sell outbound, we lose 76% of the time—almost exclusively to entrenched incumbents like Miro. Conversely, our product-qualified leads (PQLs) convert at an exceptionally high rate and command an average contract value (ACV) exceeding $70,000.

To hit our $5M new ARR target next year without burning cash or destroying our self-serve engine, we must abandon cold outbound, protect our organic adoption loops, and build an enterprise motion centered around bottom-up land-and-expand.

---

1. Who We Sell To (The Ideal Customer Profile)

Jordan wants to target cold Fortune 2000 logos via outbound SDR armies. The data shows this is a trap.

Out of 65 deals analyzed over the last 12 months, Outbound deals had a win rate of only 24% (6 won, 19 lost), with an average sales cycle of nearly 180 days. When we go outbound, we face entrenched enterprise incumbents (Miro) where companies have already standardized their toolsets and board repositories. Switching costs are insurmountable for a cold prospect.

On the other hand, Product-Qualified (PQL) deals had a win rate of 62% (16 won, 10 lost) and an average sales cycle of just 65 days.

Our ICP is not the cold enterprise logo; it is the "Shadow IT" enterprise. We sell to companies where employees are already using Flowboard organically. Our data shows dozens of mid-market and enterprise accounts (ranging from 1,200 to 15,000 employees) with active, engaged teams, high security-page views, and zero formal enterprise oversight.

• Target: Organizations with >1,000 employees that already have 2+ unmanaged teams or 30+ active users organically collaborating on Flowboard.
• Buyer: Department heads and operational leaders whose teams refuse to give up Flowboard's superior diagramming speed, backed by IT administrators who need centralized security and governance (SSO/SCIM).

---

2. How Self-Serve and the Sales Team Work Together

Jordan’s plan introduces two catastrophic friction points: capping the free plan at 3 users and blocking self-serve checkouts above 10 seats. Because 70% of our new paying teams originate from our free plan, strangling the free tier will directly tank our top-of-funnel velocity, starving our PQL pipeline of future enterprise accounts. Furthermore, forcing a 15-person marketing agency or engineering squad to "talk to sales" just to buy software creates unnecessary friction and churns potential users to competitors.

The Product-Led Sales (PLS) Model: 1. Bottom-Up Land (Product): Keep the free plan and self-serve checkout completely frictionless. Let viral adoption happen naturally within large enterprises. 2. Product Telemetry (The Bridge): Engineering and product will surface accounts where a company domain crosses internal thresholds (e.g., >30 active users across multiple teams, or hits on the security/SSO documentation pages). 3. Expansion & Land-Grab (Sales): Instead of cold-calling Fortune 2000 logos, our sales team receives warm PQL alerts. The pitch writes itself: "We noticed 45 people across your engineering and design departments using Flowboard daily. Here is how you can secure your data, manage permissions via SCIM, and consolidate billing." 4. Self-Serve Guardrails: Allow self-serve checkout up to 50 seats. Above 50 seats, or upon requesting enterprise features (SSO/SCIM/Audit Logs), the product smoothly routes the buyer to a dedicated account executive to convert them into an annual enterprise contract.

---

3. What We Say Against the Alternatives

Jordan’s proposed messaging—"The visual collaboration platform for the enterprise"—is generic, corporate wallpaper. It positions us as a feature-poor clone of Miro.

In win/loss interviews, buyers were crystal clear about why they choose us and why they refuse to give us up: "Our designers refused to give it up" and "Real-time diagramming that stays tidy." Miro is a sprawling, cluttered surface; Flowboard is built for speed and structural clarity.

• Against Miro (The Incumbent Standard): We do not position ourselves as a generic whiteboard. We position ourselves as the fast, intelligent diagramming engine for technical and creative teams. We lean into our structural advantages: diagrams that organize themselves, lightning-fast rendering, and a UX that engineers and designers actually love, rather than tolerate because IT mandated it.
• Against Status Quo (Slide decks and whiteboard photos): We highlight time-to-alignment and cross-functional velocity.

---

4. Capacity and Resource Model

To hit $5M in new ARR with an average enterprise contract value of ~$65,000, we need approximately 77 closed enterprise deals next year.

Based on our historical PQL win rate of 62%: * Required PQL pipeline opportunities: ~125 qualified expansion conversations. * Average PQL sales cycle: ~65 days (meaning an AE can easily manage a much higher throughput than a cold outbound AE wrestling with a 180-day cycle).

Recommended Headcount vs. Jordan’s Plan: * Jordan’s Plan: 8 AEs + 6 SDRs (Heavy focus on outbound cold calling, massive salary/commission burn, low expected ROI given our 24% outbound win rate). * Revised Plan: 4 Account Executives total (retain our current 3, hire 1 more) and 0 SDRs. * Why this works: Because we are focusing our sales capacity on high-intent PQLs rather than cold outbound prospecting, our existing sales team—augmented by just one additional closer—can handle the volume. We redirect budget from outbound SDR salaries into product instrumentation, telemetry, and self-serve optimization.

---

5. Summary of What to Change in Jordan’s Plan & Why

Conclusion

By shifting our enterprise strategy from cold outbound acquisition to warm PQL expansion, we align our sales team with how users actually discover and love Flowboard. This protects our organic growth engine, slashes customer acquisition costs, and provides a realistic, highly achievable path to our $5M ARR board mandate.

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.