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.

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.

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.