Write a GTM plan

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.

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.

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.