Loading page…
An enterprise planning platform built to replace spreadsheet-heavy budgeting, forecasting, and scenario work for large teams.
customers grew 10x in 12 months · 170 people
Enterprise SaaS starts before the MVP when the product must earn trust from the finance team, the security team, and the executive who owns the spreadsheet everyone depends on.
Fewer bars = easier, cheaper, or faster for an AI-assisted solo builder. Editorial judgments based on the case details.
Pigment was founded in 2019 by Eleonore Crespo and Roman Nicoli as an enterprise planning and performance-management SaaS. The product helps companies handle budgeting, forecasting, scenario analysis, workforce planning, and sales planning in a business database designed to be more agile than spreadsheets. Crespo came from Google and Index Ventures; Nicoli was formerly a cofounder and CTO at Criteo. They chose enterprise from day one because replacing Excel for large companies requires a powerful modeling engine, deep connectors, security, governance, and an intuitive interface. The founders spent six months interviewing people before deciding what to build, then another nine months designing with customers, advisors, partners, and investors. The interview reports a 170-person company, offices in France, London, and New York, ARR growth of 5x in six months, and customer growth of 10x in 12 months. Pigment had raised a €3.5M seed and a later €20M-plus round; Crespo also discussed a $65M round that was preempted through investor relationships. The growth and funding figures are founder-reported, while no absolute ARR or customer count is supplied.
For Pigment, the first customers came from a long design phase and a network capable of opening enterprise doors. Spend the first months interviewing finance, legal, security, operations, and planning leaders to understand why their current spreadsheet or incumbent system fails.
The quick-reference card — acquisition channels, replication playbook, risks & traps, and our verdict — is members-only.
Join the Unicorn Club — $5/moCancel anytime, in one clickPaste into Claude Code / Codex and get a working version of this product end-to-end.
Two production-grade prompts per idea — a full build spec and an SEO growth plan — plus 10 tailored build specs a week. Members only.
Join the Unicorn Club — $5/moCancel anytime, in one clickEvery claim traces back to a listed source — open any of them and check the number yourself.
Data credibility: Founder interview; the 5x ARR growth, 10x customer growth, 170-person team, offices, and funding figures are self-reported and unaudited. No absolute ARR or customer count is given in the transcript.
Pigment's first dollar arrives through a high-touch enterprise commitment, not a self-serve checkout. The buyer needs confidence that the planning model will handle sensitive financial data, fit existing processes, and be supported when a forecast or budget is due.
Pigment's flywheel combines usage, trust, reference customers, and investor or partner networks. A planning platform becomes more valuable when several teams use the same business model, because finance can connect workforce, sales, and budget scenarios instead of reconciling separate files.
Enterprise founders can spend a long period with little visible traction because the product takes time to build and buyers take time to trust it. Pigment's founders used six months of interviews and nine months of design before launch, then raised enough capital to pursue a multi-year enterprise build.
Pigment is an enterprise planning and performance-management platform. Its core is a powerful modeling engine paired with an intuitive interface for budgeting, forecasting, scenario analysis, workforce planning, sales planning, and related finance workflows. The product is positioned as a business database for teams, replacing spreadsheet processes that become fragile as data, users, and approvals multiply. That means the system must handle formulas, dimensions, data connectors, permissions, versioning, audit history, and collaborative review. The enterprise buyer also needs security, governance, implementation support, and confidence that the model will still work at the close of a planning cycle. An MVP should not imitate the entire suite. It should solve one painful planning process with a model that is transparent, importable, and easy for finance users to explain to executives. Product quality is both computational and organizational: the numbers must be consistent, and the workflow must make ownership clear. Pigment's design-first approach shows why enterprise software is a methodology, not simply an SMB app with more permissions.
Pigment's exact ARR, pricing, and customer count are not stated, but the business follows an enterprise SaaS pattern: recurring contracts for access to a planning platform, with expansion as more teams, models, data connections, and workflows adopt it. Enterprise pricing should reflect users, model complexity, governance, implementation, and the financial value of faster or more reliable planning. Keep the platform subscription distinct from one-time implementation so customers can see the product's recurring value and the company can measure services separately. The reported 5x ARR growth in six months and 10x customer growth in 12 months are strong directional signals, but they do not establish absolute scale or profitability. Track annual recurring revenue, net retention, implementation time, active models, planning-cycle completion, executive users, support load, and expansion by account. A high-value enterprise sale can support a large team, but only if retention and deployment quality stay strong. The first commercial wedge should be narrow enough to launch, while the contract and data model leave room for workforce, sales, and scenario planning to expand inside the same account.
Pigment's distribution is relationship-led and credibility-heavy. The founders spend time with investors, advisors, partners, and prospective customers; those relationships support customer introductions, senior hiring, and references. Enterprise planning buyers are not reached efficiently by a generic self-serve funnel because finance, legal, security, and operations all influence the purchase. Create content that demonstrates a real planning problem: scenario planning under uncertainty, replacing a brittle budget spreadsheet, connecting workforce and financial plans, or giving executives a trusted version of the forecast. Use named design partners and implementation advisors carefully, with permission to describe outcomes. A strong sales motion can begin with an executive workshop, move to a scoped proof of value, and end with a deployment plan that explains data ownership and governance. Track time from first meeting to pilot, pilot-to-contract conversion, implementation time, active use, reference willingness, and expansion. The company has offices in France, London, and New York, but the repeatable lesson is not geography; it is that enterprise distribution is built from trust networks and useful proof rather than a high-volume lead list.
Build a Pigment-style MVP as a secure planning system, not a spreadsheet clone with a prettier grid. Use Next.js App Router with TypeScript and Tailwind for the application, Clerk for authentication, Neon Postgres with Drizzle for tenants, models, dimensions, cells, permissions, scenarios, and audit events, Stripe for subscription billing, and Vercel for deployment. A serious version may require a dedicated calculation service and warehouse connectors, but start with a transparent model engine and a controlled import path. Add role-based access, row and model permissions, version snapshots, approval states, and an audit log before adding many visualizations. Data model: organizations, memberships, models, dimensions, members, cells, formulas, scenarios, imports, exports, comments, approvals, subscriptions, and auditEvents. Use background jobs for large imports and calculation runs, with visible status and retry handling. The major costs are senior engineering, security, data integration, customer success, implementation, and enterprise sales. AI can help explain a variance or draft a scenario narrative, but it should not silently alter financial models. The reported 170-person organization illustrates the capital and operating burden of becoming trusted enterprise infrastructure.
Copy Pigment's decision to understand the enterprise problem before building, its long design phase, its focus on a powerful engine and intuitive interface, and its use of investors and senior hires as sources of trust and introductions. Copy the discipline of long-term commitments and precise ownership: enterprise customers remember every promise. Change the starting scope. A new founder should choose one planning process, one buyer, and one data path rather than attempt to replace every spreadsheet in a company. Prove that the model is accurate, explainable, secure, and usable in a real planning cycle before expanding. Change the financing assumption as well. Pigment raised capital for a long enterprise build, but a bootstrapped entrant should sell a narrow workflow or implementation-supported product before taking on the same cost structure. The reported growth multiples are compelling, yet the absence of absolute ARR and customer counts means they are directional rather than a complete financial case. The opportunity is large; the right copy is the research and trust methodology, not the full enterprise surface area.
The four founder playbooks — first customers, first dollar, the flywheel, the silent stretch — are in the Unicorn Club, on this idea and on all 1,403 others. The story, the numbers, the sources and every later section stay open to everyone.
Join the Unicorn Club — $5/moCancel anytime, in one click