Write a GTM plan

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.

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.

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.