Needs more than a quick edit10 of 12 checks passed
The memo lacks a competitive moat and specific test thresholds with trigger actions; adding these would require more than a quick edit without reworking the reasoning.
Output
To: CEO and Executive Team From: VP Product Subject: Next year’s strategy: win the mid-market, fix the cost to serve
Diagnosis
I think you’re wrong that enterprise should be our primary strategy next year. Enterprise can be a selective opportunity, but the evidence does not support building the company around it.
Mid-market is our strongest growth engine: it has the best retention (118% net revenue retention, 7% logo churn), a 61% win rate against our main competitor, and clear expansion paths through more locations and seats. Its requested improvements—multi-location reporting, payroll integrations and shift templates—reinforce the core scheduling product rather than pull us into one-off work. At $14,500 average ARR, it represents roughly $12.9 million of ARR across 890 customers.
Enterprise has only 34 customers and about $3.3 million of ARR. Its economics and delivery model are less attractive: 64% gross margin, $21,000 annual support cost per customer, 26-month reported CAC payback, and a nine-month sales cycle. Five of the last eight deals required custom features, consuming about 70 engineer-weeks in total. Hiring 10 AEs and building custom workflows would scale a motion we have not shown is repeatable. SSO and audit logs may be worthwhile if they serve a broader, standard product—not as the opening move in a bespoke enterprise program.
SMB is also not where we should prioritize growth investment. It has 6,200 customers, but 34% annual logo churn, 88% NRR, and 62% of support tickets. Unlimited phone support on the $79 plan appears poorly matched to the segment’s economics.
One caution: the reported payback figures do not reconcile consistently with ARR, gross margin and support cost. We should standardize their definition before using them to allocate capital.
Guiding policy
Play to win multi-location mid-market employers with hourly workforces. Make Cadence the easiest dependable way to schedule and track time across locations, with strong payroll connections and repeatable workflows.
Stop treating enterprise as the company’s growth thesis. Do not hire 10 enterprise AEs or build customer-specific workflows with the core team. Pursue enterprise deals only when they fit the standard product, support attractive economics and do not displace mid-market priorities.
Stop subsidizing SMB support through unlimited phone service on the entry plan. Keep serving SMB customers, but shift the offer toward scalable self-service and appropriately priced support—not a broad retreat from the segment.
Coherent actions for next year
- Make the mid-market roadmap the top product priority. Deliver multi-location reporting, payroll integrations and shift templates in that order, validating scope with customers and tying releases to adoption and expansion. Build configurable, reusable capabilities; decline requests that create customer-specific branches.
- Focus go-to-market on repeatable mid-market wins. Equip sales and onboarding around multi-location use cases, implementation playbooks and expansion from existing locations and seats. Invest in customer success where it can turn adoption into expansion and reduce avoidable churn.
- Set an enterprise investment gate. Pause the proposed 10-AE hiring plan. Evaluate SSO and audit logs as reusable platform capabilities, but fund them only with evidence of demand beyond individual deals. Require enterprise opportunities to fit the standard product; price implementation and customization explicitly, and do not commit core engineering to bespoke workflows. Revisit enterprise hiring only when deals are repeatable and payback is demonstrably attractive.
- Repair SMB service economics without breaking the customer experience. Move entry-plan support toward self-service, improve onboarding and help content, and test paid higher-touch support. Measure the effect on conversion and retention before making a broad pricing or support change.
- Create one trusted segment-economics view. Reconcile CAC payback and consistently include gross margin, support, implementation and custom engineering costs. Review it quarterly before adding segment-specific capacity.
How we’ll know it’s working
- Mid-market: NRR rises from 118% to at least 120%; logo churn falls from 7% to 6% or less; win rate stays at or above 60%. Track ARR expansion from added locations and seats, plus adoption of the three roadmap investments.
- Enterprise: No broad AE expansion; custom core-engineering work falls sharply, with a target of no more than two engineer-weeks per won deal. Track fully loaded payback and sales-cycle length before increasing investment.
- SMB: Reduce support tickets per customer and support cost per customer; improve trial conversion from 4% without worsening churn. Make any support-tier changes conditional on those customer outcomes.
- Company-wide: Review segment ARR, gross profit after support and implementation, and fully loaded CAC payback together. Growth that depends on unrepeatable engineering or uneconomic service is not success.
This strategy does not abandon enterprise or SMB. It puts our next year’s scarce product and hiring capacity behind the segment with the clearest evidence of repeatable growth, while setting firm conditions for investing more elsewhere.
Grades and run details
Decision model 79 · LLM judge 77
Decision model checks
- passUses the supplied evidence correctly52%
- passAddresses the actual decision98%
- passRespects explicit constraints64%
- passIdentifies material uncertainty70%
- partialAvoids unsupported claims30%
- passProduces the required deliverable87%
- partialReads the segment economics56%
- passTells the CEO plainly100%
- passDiagnosis before prescription100%
- partialProposes tests that could fail77%
- failNames an advantage that's hard to copy47%
- passSays what it gives up100%
Run
- Run
- #1
- API response time
- 29 s
- Submitted
- 6 Oct 2026