This story condenses a source-backed brief. Some historical details and internal metrics are not established. [Inference] marks analysis. Source numbers keep the numbering of the full case, and the evidence is from the 10 Nov 2026 research edition. Read the research method.
Building an engine did not identify every buyer
The 2017 company-hosted case study describes Gould as a computer scientist who spent years developing the underlying calculation architecture. It places the first customer in 2010, but the supplied research does not identify that customer or reconstruct the first founder-led sale. Exact early contract terms are also unknown. [1]
[Inference] A broad calculation capability can support many possible tasks, which makes positioning difficult. Prospects do not buy an abstract engine merely because it is technically impressive. They need to understand which decision process it improves, what information it requires and how their working routine would change. The first credible use case therefore matters as a way to make technical breadth evaluable.
Quota planning supplied a concrete application
The case study describes HP signing in February 2013 to improve sales-quota planning, followed by rollout five months later. HP executive Sue Barsamian reported better planning and insight. These are reported customer outcomes within a company-hosted study, not an independent causal evaluation or a disclosure of the complete contract economics. [1]
[Inference] Quota planning gives a broad platform a bounded initial test. A team can compare the old process with the proposed model and identify who owns the inputs and decisions. The rollout interval also reminds readers that purchase and useful deployment are separate events. A signed agreement is not enough to show that users trust or routinely apply the resulting plans.
The model has organizational dependencies
[Inference] Spreadsheet-heavy planning often involves assumptions held by different people. Replacing the surface without agreeing those assumptions can leave disagreement intact. A useful evaluation would examine data ownership, model transparency and the authority to resolve conflicting inputs. It should distinguish faster calculation from better planning decisions rather than treating them as equivalent outcomes.
[Inference] This creates a buying unit broader than a single enthusiastic analyst. A sponsor may value improved insight while operational users judge whether they can maintain the model. The supplied record does not name every stakeholder in HP’s purchase, so these are questions for interpreting a planning deployment rather than a reconstructed account map.
The founder and partners supplied different expertise
Gould later concentrated on customer solution design after hiring specialists to lead other functions. The case study says Anaplan partnered for integration and consulting instead of building every capability internally. It establishes those choices but does not identify a complete early hiring sequence or named account-management team. [1]
[Inference] A partner can help translate platform capability into a working model within the customer’s environment. That may increase delivery capacity while introducing coordination obligations. The vendor and partner should agree who owns configuration, training and unresolved adoption problems. Otherwise, a customer can receive a technically completed implementation without knowing how to operate it confidently.
More planning scope needs demonstrated usefulness
The supplied research does not verify current prices, CAC, gross margin, payback or retention cohorts. Nor does one HP example establish a general expansion rate. The first customer’s identity and detailed founder closing sequence remain gaps, even though the later deployment provides a concrete commercial reference. [1]
[Inference] Anaplan’s useful lesson is to enter a broad problem through one consequential decision process. Expansion should follow a trusted model and a maintainable operating practice, with expert modeling and integration counted as real costs. A stronger evaluation would track whether successive use cases reuse capability or require another bespoke project, because those paths imply very different economics behind the same platform story.
Anaplan: the full GTM case
The complete case holds the named people, the economics, the available historical evidence, the critique and the open research questions.
Read Anaplan’s full GTM caseTerms in this story
Questions behind the story
How do I choose between product-led and sales-led growth?Why does the site leave CAC and retention blank for some companies?All 104 GTM questions answered
Sources
Numbers match the source list of the full Anaplan case. A source’s publication date and the date of the event it reports can differ.
- The Change Catalyst anaplan.com