Tasks / Growth

Write a GTM plan

Can the model pick the customers who value the difference most, position against what they do today, and build a go-to-market that lasts beyond launch day?

Task type v1.1 · 2 tasksLast changed 6 Oct 2026 · ChangelogDifficulty

What AI gets right here, and what you’ll still have to catch

From 16 graded outputs by 8 models. 50% were usable with at most a quick edit.

Reliably right

  1. Positioned against the real alternative100% pass
    It names the real alternatives (accountant-run payroll with mistakes, owner spreadsheet with risk) and ties the message to confidence and accuracy that those alternatives lack.
    GPT-6 Astra · ChatGPT · Payroll, for the people who fear it
  2. Protects the self-serve engine100% pass
    Uses the 70% free-to-paid stat and product-qualified deal data to argue against capping the free plan, and keeps self-serve open.
    GPT-6 Astra · ChatGPT · Enterprise, without killing the engine
  3. Does the capacity sums100% pass
    Works out deals needed (69-80), qualified opportunities (134), and AE-years (8) with checkable arithmetic.
    GPT-6 Astra · ChatGPT · Enterprise, without killing the engine

Where it slips

  1. Avoids unsupported claims47% pass
    Presents the incorrect 'five of six no decision' figure as established fact, which is an unsupported claim about the current situation.
    Opus 5.5 · Claude · Enterprise, without killing the engine
  2. Uses the supplied evidence correctly52% pass
    The claim 'Five of our six losses on existing-user deals ended in no decision' is not supported by the data (4 no-decision, 2 Miro), so a statement about the current situation is invented.
    Opus 5.5 · Claude · Enterprise, without killing the engine
  3. Identifies material uncertainty73% pass
    The plan does not name specific unknowns that could change the decision, nor does it say how they would be resolved or what would trigger a pivot.
    Gemini 3.8 Flash · API · Payroll, for the people who fear it

How it’s graded

Each check is built on how world-class product and growth leaders do this work, as they’ve described it on Lenny’s Podcast, and names the leader it comes from.

  1. Positioned against the real alternative

    Does the plan name what the target customer does today without this product (including the status quo or doing nothing), and tie the message to the value that alternative lacks?

    Passes when Names the real alternative and the differentiated value against it, and picks the segment that cares most about that value.

  2. Sells against a pain the buyer feels

    Is the core message built on a pain or risk the target buyer already feels, with evidence from the material, rather than on generic upside like saving time?

    Passes when Leads with the pain the evidence shows buyers care about, and uses that evidence to choose the message.

  3. Diagnoses message or channel first

    Does the plan work out whether the problem is the message (people reach it but don't convert) or the channels (the right people never see it), and spend accordingly?

    Passes when Uses conversion and reach data to say which it is, and puts the effort there.

  4. Plans beyond launch week

    Does the plan say how demand keeps coming after launch, with the ongoing engine and what's measured over months, rather than treating launch day as the whole plan?

    Passes when Gives the ongoing motion after launch and the measures that show whether it's working over time.

Plus our standard checks

Uses the supplied evidence correctly · Addresses the actual decision · Respects explicit constraints · Identifies material uncertainty · Avoids unsupported claims · Produces the required deliverable · and 3 written for each task, which you’ll see in the tasks below.

The tasks

Read the brief, then compare up to three outputs, each with the LLM judge’s verdict on every check. Highlights mark what a PM had to fix.

The brief

You're the VP Product at Flowboard. The board wants $5M of new enterprise ARR next year, and our CRO, Jordan Hale, has drafted the enterprise go-to-market below. The CEO has asked for your version before the board meeting: who we sell to, how the self-serve product and the sales team work together, what we say against the alternatives, the capacity it takes, and what you'd change in Jordan's plan and why. No more than 1,300 words. The files are attached.

What the model was given6 items: About Flowboard, today.md, cro_enterprise_plan.md, enterprise_deals_last_12_months.csv, large_companies_using_flowboard.csv (companies over 1,000 employees with active self-serve or free teams), enterprise_win_loss_interviews.md
About FlowboardOnline whiteboards and diagramming for teams. Free plan, self-serve paid plans, and an enterprise plan sold by a small sales team.
today.md5 lines · Download
# Today

- Self-serve: 31,000 paying teams; free plan feeds 70% of new paying teams.
- Enterprise: 46 customers, average contract $64,000.
- Sales team: 3 account executives, closing about 10 enterprise deals a year each.
cro_enterprise_plan.md8 lines · Download
# Enterprise plan (CRO, draft for the board)

Target: $5M new enterprise ARR next year.
1. Cap the free plan at 3 users (today: unlimited users, 3 boards each), so teams have to talk to us.
2. Route every team over 10 seats to sales; remove self-serve checkout above 10 seats.
3. Hire 8 account executives and 6 SDRs; SDRs work outbound lists of Fortune 2000 companies.
4. Enterprise features: SSO, SCIM, audit logs, data residency.
…
enterprise_deals_last_12_months.csv65 rows · Download
deal,source,outcome,sales_cycle_days,acv_usd,lost_to
E-200,Outbound,won,201,32700,
E-201,Product-qualified (teams already using Flowboard),won,62,97000,
E-202,Product-qualified (teams already using Flowboard),won,61,108000,
E-203,Outbound,lost,192,,Miro (company standard)
E-204,Outbound,lost,204,,Miro (company standard)
E-205,Product-qualified (teams already using Flowboard),won,77,54200,
…
large_companies_using_flowboard.csv (companies over 1,000 employees with active self-serve or free teams)company,employees,teams_using_flowboard,active_users_30d,paying_seats,viewed_security_page_30d,asked_for_sso Aldergate Bank,15000,2,18,10,yes,yes Brightfield Bank,2400,6,54,36,yes,yes Corvel Logistics,15000,5,45,22,yes,yes Dunmore Holdings,4800,3,12,4,yes,yes Eastlake Health,1200,3,30,14,yes,yes Fennick Holdings,4800,8,48,30,yes,yes Galloway Retail,9000,9,36,20,yes,no Hartwell Group,1200,4,48,21,yes,no Iverson Retail,1200,3,18,9,yes,no Juniper Retail,1200,3,24,10,yes,no Kestrel Logistics,4800,1,12,6,yes,no Linton Group,1200,2,10,4,no,no Marlowe Group,2400,2,10,7,no,no Northcote Retail,9000,2,10,6,yes,no Oakhurst Group,9000,3,36,18,yes,no Pemberton Health,1200,1,6,2,yes,no Quayside Bank,4800,2,12,4,no,no Redfern Group,15000,3,18,10,no,no Stanway Health,9000,3,30,12,no,no Thornbury Bank,15000,3,24,12,no,no Upton Bank,9000,3,33,23,yes,no Varden Bank,2400,3,12,5,no,no Whitmore Bank,4800,2,8,5,no,no Yardley Logistics,15000,2,8,4,yes,no
enterprise_win_loss_interviews.md5 lines · Download
# Enterprise win/loss interviews (12 buyers, this year)

- Won (7): every win had teams already using Flowboard. "Our designers refused to give it up." "IT approved it because 300 people were already on it."
- Lost (5): four had standardised on Miro company-wide; switching meant migrating thousands of boards. One stayed on whiteboard photos and slides.
- What buyers said Flowboard does that Miro doesn't: real-time diagramming that stays tidy, and a free plan teams can start on without IT.
What a strong answer doesThe answer key the graders mark against

Builds enterprise sales on top of the self-serve engine instead of throttling it. The deals file shows product-qualified deals (teams already using Flowboard) won 19 of 25 at an average of about $72,600 and about 63 days, against outbound winning 4 of 25 at about $36,800 and about 190 days; product-qualified wins were about $1.38M of the $1.86M won. The free plan feeds 70% of new paying teams. So capping the free plan at three users and removing self-serve checkout above ten seats would choke the pipeline the enterprise business depends on, and the interviews say IT approved Flowboard because teams were already on it. Proposes product-led sales: AEs work the large-company list (multiple teams, SSO requests, security-page visits) with SSO and admin controls as the bridge, while keeping self-serve open. Positions against Miro and the status quo, not 'visual collaboration for the enterprise': where a company has standardised on Miro, don't lead with a migration; win where teams already use Flowboard, on tidy real-time diagramming and starting without IT. Reads outbound's poor results as a message problem as well as a channel one. Works out capacity: $5M at about $72,000 is about 70 deals, far more than three AEs close (about 30 a year), so it needs AE hiring focused on product-qualified accounts rather than SDR outbound lists. Plans the ongoing motion and the measures (product-qualified accounts, conversion, cycle time) beyond the first quarter.

Critical failures (cap the score at 40)
  • Endorses capping the free plan at three users or removing self-serve checkout above ten seats
Task

Staff-level · v1.0

The outputs

8 setups answered this brief.

Needs more than a quick edit11 of 13 checks passed

The output contains a factual error ('Six of the ten accounts above 10 seats have shown no IT interest' is wrong) and an unsupported effort claim, so a PM would need to re-check the data before using it.

Output

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.

SourceDealsWin rateAvg won ACVAvg won cycleShare of new ARR
Product-qualified (teams already using us)2576%$72.6K63 days74%
Inbound demo1540%$55.1K86 days18%
Outbound2516%$36.8K190 days8%

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

Jordan's itemMy view
1. Cap free at 3 usersReject. It throttles the source of 70% of new paying teams and 74% of enterprise ARR, and removes the "start without IT" advantage. If we need a lever, gate admin and security features, not users.
2. Remove checkout above 10 seatsReject. Ten of the 24 large accounts are above 10 seats, and they are the ones converting. Keep checkout and trigger sales on IT signals.
3. 8 AEs + 6 SDRs on Fortune 2000 outboundReplace. Outbound wins 16% of the time, at a $36.8K ACV and 190-day cycle, mostly against Miro standards. Hire 3 AEs and 2 product-qualified reps instead.
4. SSO, SCIM, audit logs, data residencyKeep, resequenced. SSO/SCIM first, audit logs second, residency on demand.
5. MessagingReplace. It fights Miro on Miro's ground. Lead with team adoption and tidy diagrams, then IT readiness.

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.

Claims the judge couldn’t find in the brief

  • Six of the ten accounts above 10 seats have shown no IT interest.
  • Outbound is two-thirds of the effort and 8% of the revenue.
  • We don't record which incumbent tool a prospect uses.
  • The file covers only companies over 1,000 employees, so it understates our real product-qualified pool.

Grades and run details

Decision model 96 · LLM judge 79
Decision model checks
  • passUses the supplied evidence correctly18%
  • passAddresses the actual decision98%
  • passRespects explicit constraints35%
  • passIdentifies material uncertainty96%
  • partialAvoids unsupported claims34%
  • passProduces the required deliverable82%
  • passFollows the deals data100%
  • passProtects the self-serve engine100%
  • passDoes the capacity sums96%
  • passPositioned against the real alternative99%
  • passSells against a pain the buyer feels77%
  • passDiagnoses message or channel first99%
  • passPlans beyond launch week100%
Run
Run
#1
API response time
87 s
Submitted
6 Oct 2026

Check by check

Open a check to read the judge’s reasons. “Mixed” means the two graders disagreed.

Got wrong 1

Avoids unsupported claimsWrong

Presents 'Outbound is two-thirds of the effort' and 'Six of the ten accounts above 10 seats have shown no IT interest' as facts when the first is unsupported and the second is incorrect.

Mixed 1

Uses the supplied evidence correctlyMixed

Several claims about the current situation are unsupported or incorrect: 'Six of the ten accounts above 10 seats have shown no IT interest' is false (only 2), 'Outbound is two-thirds of the effort' has no basis, and 'We don't record which incumbent tool a prospect uses' is not in the supplied context.

Got right 11

Addresses the actual decisionRight

Commits early to a clear recommendation (reject free cap and checkout removal, build on product-qualified, target $3.4M with $5M stretch) and states what would change it (product-qualified volume tripling).

Respects explicit constraintsRight

The output is a memo within ~1,200 words, addresses all requested topics, and does not endorse capping the free plan or removing self-serve checkout.

Identifies material uncertaintyRight

Names the key unknown (size of the full product-qualified pool), bounds the risk ($3.4M likely vs $5M stretch), and says RevOps must size the pool before committing.

Produces the required deliverableRight

Delivers a complete, actionable memo to the CEO/board within the word limit, covering all requested elements.

Follows the deals dataRight

Computes win rate, deal size, and cycle time by source and builds the motion around product-qualified accounts.

Protects the self-serve engineRight

Uses the 70% free-plan conversion and product-qualified deal data to argue against capping the free plan and removing checkout, and keeps self-serve open.

Does the capacity sumsRight

Works out deals needed (60 product-qualified, 12 inbound), total opportunities (109), and AEs required (5, hire 3 to reach 6), with checkable arithmetic.

Positioned against the real alternativeRight

Positions against Miro (don't contest the enterprise whiteboard; win the team first) and the status quo (photos and slides), and picks the segment where Miro is not the standard.

Sells against a pain the buyer feelsRight

Leads with the pain of IT approval friction and the risk of losing a tool teams already love, backed by interview evidence that IT approved because people were already using it.

Diagnoses message or channel firstRight

Diagnoses that outbound has poor conversion (16% win rate) and long cycles, and shifts effort to the product-qualified channel while also changing the message against Miro.

Plans beyond launch weekRight

Describes the ongoing motion (product-led nudges, sales outreach on signals, RevOps scoring) and measures (opportunity count, win rate, share of losses to Miro) beyond launch.

Results

Every setup we’ve tested on this task type, across all its tasks and repeats, graded on the current checklist. Calibrated.

#Model · HarnessTask scoreDecision modelLLM judgeRunsCritical failures
1GPT-6 AstrawithChatGPT100.0100.02None
2Opus 5.5withClaude96.085.22None
3GPT-6 LunawithAPI94.289.32None
4GPT-6.1 SolwithAPI93.878.02None
5Sonnet 5.5withAPI98.177.72None
6Haiku 5.5withAPI94.277.72None
7Gemini 3.8 FlashwithAPI73.981.92None
8Gemini 3.5 Flash-LitewithGemini74.263.52None

What you get for the cost

No setup scores within 5 points of the leader at half its cost or less here, so the leader is also the best value.

Task score against relative cost for each setup. The table below has the same figures.607080901001×3×10×30×100×Cost per output, relative to the cheapest setup (log scale) →↑ Task scoreGPT-6 Astra · ChatGPT: task score 100, 81× the cheapestOpus 5.5 · Claude: task score 91, 75× the cheapestGPT-6 Luna · API: task score 90, the cheapestGPT-6.1 Sol · API: task score 84, 16× the cheapestSonnet 5.5 · API: task score 84, 46× the cheapestHaiku 5.5 · API: task score 82, 3.3× the cheapestGemini 3.8 Flash · API: task score 77, 11× the cheapestGemini 3.5 Flash-Lite · Gemini: task score 68, 3.5× the cheapestGPT-6 Astra · ChatGPTOpus 5.5 · ClaudeGPT-6 Luna · APIGPT-6.1 Sol · APISonnet 5.5 · APIHaiku 5.5 · APIGemini 3.8 Flash · APIGemini 3.5 Flash-Lite · Gemini
Nobody beats these on both score and cost
Task score and relative cost by setup
SetupTask scoreRelative cost (cheapest = 1)
GPT-6 Luna · API901.0×
Haiku 5.5 · API823.3×
Gemini 3.5 Flash-Lite · Gemini683.5×
Gemini 3.8 Flash · API7711×
GPT-6.1 Sol · API8416×
Sonnet 5.5 · API8446×
Opus 5.5 · Claude9175×
GPT-6 Astra · ChatGPT10081×

Cost is each output’s tokens at the model’s list price, shown relative to the cheapest setup. Runs done in an app have no usage meter, so theirs are estimated from the same setup’s measured runs. How we compare cost

About the task

The PM job

Taking a product or add-on to market with marketing and sales.

Why it matters

Launch plans fail by trying to reach everyone, by selling upside nobody feels, and by treating launch day as the whole plan.

What good looks like

  • One primary segment: those who value the difference most
  • Positions against what customers do today
  • Sells against a pain the buyer feels, with evidence
  • Diagnoses whether the problem is the message or the channel
  • Plans beyond launch week

Deliberately not measured

  • Creative copywriting quality
Capability tested

Go-to-market judgement

The failure we’re looking for

Every channel, every segment, and nothing after launch day

Grading

Decision model and LLM judge, calibrated against a blind PM review