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.

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.