top of page
Won by building its FP&A platform inside Microsoft Excel rather than replacing it — removing the single biggest objection CFOs had to every prior planning software vendor.
1
MODEL
BUSINESS MODEL
SaaS, Platform Ecosystem
model bm
HOW THEY BUILT IT
- Founded 2011 in Toronto; raised $115M Series B led by Vista Equity Partners in 2020 (valuation ~$1B+).
- Core differentiator: planning engine runs inside Excel (via add-in), so finance teams work in the interface they already know while Vena manages data, version control, workflow, and collaboration in the cloud.
- Targets mid-market and enterprise finance teams at companies with 500–10,000 employees running complex budgeting, forecasting, and reporting cycles.
HOW TO ARCHITECT IT
1. If your target buyer is deeply attached to an existing tool, build your platform around it rather than asking them to abandon it — the attachment is not irrational, and fighting it costs you deals.
2. Position the new platform as solving the problems the existing tool creates at scale (version sprawl, broken formulas, email chains) rather than as a replacement.
3. Sell to the CFO by quantifying time wasted in the current process — a finance team spending 40% of planning cycle time on consolidation is a concrete cost the CFO can calculate.
4. Partner with Microsoft deeply (Azure hosting, Teams integration, Excel brand alignment) to inherit enterprise trust and IT procurement comfort.
DISTRIBUTION MODEL
Enterprise Sales, Inside Sales, Partner Distribution
dm
HOW THEY OPERATIONALIZED
- Direct enterprise sales team targeting CFOs, FP&A Directors, and Controllers at mid-market companies ($100M–$2B revenue).
- Microsoft partnership drives co-selling through Microsoft's own enterprise sales team.
- Inside sales team handles the mid-market segment with a structured demo-to-close motion.
HOW TO REPLICATE WHAT WORKED
What worked: the Microsoft co-selling relationship giving Vena access to enterprise accounts Microsoft's own team was already managing — effectively piggybacking on a global sales force without the cost.
The trap: Microsoft partnership dependency creates strategic risk if Microsoft decides to build competing functionality natively into Excel or Power BI.
| PATTERNS OF THIS MODEL
PATTERNS IN PLATFORMS BUILT AROUND AN INCUMBENT INTERFACE:
1. IF YOUR BUYER IS DEEPLY ATTACHED TO AN EXISTING TOOL, BUILD AROUND IT RATHER THAN AGAINST IT. The attachment is rational; fighting it costs deals.
2. POSITION AGAINST THE PROBLEMS THE EXISTING TOOL CREATES AT SCALE — version sprawl, broken links, email chains — not against the tool itself.
3. QUANTIFY WASTED TIME IN THE CURRENT PROCESS. A percentage of cycle time lost to consolidation is a number the finance buyer can calculate themselves.
4. PARTNER DEEPLY WITH THE INTERFACE'S OWNER to inherit enterprise trust and IT procurement comfort you could not build alone.
What companies with this model reveal
| OPPORTUNITY INTELLIGENCE
GOLDMINE 1 — BUILD AROUND THE TOOL YOUR BUYER REFUSES TO ABANDON.
Standard: finance teams are attached to Excel for rational reasons. Running the planning engine inside Excel while managing data, versioning and workflow in the cloud wins deals that asking them to leave loses.
GOLDMINE 2 — SELL AGAINST THE PROBLEMS THE EXISTING TOOL CREATES AT SCALE.
Standard: version sprawl, broken formulas and email chains — not the spreadsheet itself. Position as fixing, not replacing.
GOLDMINE 3 — QUANTIFY WASTED CYCLE TIME.
Standard: a finance team spending 40% of the planning cycle on consolidation is a cost the CFO can compute.
THE PIT — THE EXCEL DEPENDENCY IS THE MOAT AND THE CEILING.
You inherit Microsoft's roadmap, file-format constraints and performance limits, and you cannot outrun a cloud-native rival on collaboration or AI-native modelling. The attachment you built on is generational.
THE SECOND PIT — $115M FROM VISTA (2020) SETS AN EXIT CLOCK.
MOVE WITH CAUTION — DEEP MICROSOFT ALIGNMENT INHERITS ENTERPRISE TRUST AND MICROSOFT'S OWN FP&A AMBITIONS.
Untapped Business Model / Gaps / Goldmines / Pits
Patterns & Insights
2
MARKET
mkt mt es
MARKET TYPE
Fragmented Market
WHY THEY WON
Enterprise FP&A software has multiple credible competitors — Anaplan, Adaptive Insights (Workday), Planful, OneStream — none of which had dominant mid-market share because they all required replacing Excel, which procurement and finance teams resisted. Vena won by being the only credible vendor that made Excel the interface rather than the enemy.
ENTRY STRATEGY
Greenfield Entry
EXECUTION
Vena entered directly into the Canadian and US mid-market FP&A category through a purpose-built direct sales motion without a channel or reseller strategy in its formative years. Evidence: the company was profitable and growing before taking Vista Equity money in 2020, suggesting a sustainable direct-sales engine was built before adding the Microsoft partnership layer.
FOOTHOLD STRATEGY
fs
Beachhead Strategy
Mid-market Canadian companies in Toronto with 500–2,000 employees running complex Excel-based budgeting were the founding beachhead. The Toronto finance community is tight-knit, and reference selling within that network allowed Vena to accumulate 50+ logos before expanding into the US and Europe.
GROWTH CAMPAIGN
CAMPAIGNS THAT WORKED
- 'Excel is not going anywhere' thought-leadership content positioning Vena as the pragmatic choice for CFOs tired of being told their existing tools were wrong.
- ROI calculators quantifying time saved in the budgeting cycle, used as primary sales collateral to convert CFO interest into budget approval.
- Microsoft partner co-marketing campaigns surfacing Vena within Microsoft's financial-services and enterprise customer programs.
KEY LEARNING
If the incumbent tool in your category is loved by end users but creates operational chaos at scale, your positioning should validate the user's love while solving the operational problem — 'Excel, done right' sells faster than 'replace Excel with something better' because the buyer doesn't feel criticised for their existing choices.
gc
Market Context
| MARKET INTELLIGENCE
THE STANDARD: Where every competitor requires replacing the tool the buyer refuses to give up, making that tool the interface removes the category's single biggest objection.
RULE 1 — YOUR REAL COMPETITOR IS THE INCUMBENT BEHAVIOUR, NOT THE INCUMBENT VENDOR. Finance teams resist abandoning spreadsheets more than they resist changing vendors.
RULE 2 — MEET THE USER IN THE INTERFACE THEY ALREADY MASTERED. Governance, audit and workflow behind a familiar front end removes retraining entirely.
RULE 3 — THAT DEPENDENCY IS PERMANENT AND SOMEONE ELSE OWNS IT. Your product's surface is controlled by a company that could change it.
RULE 4 — REMOVING THE OBJECTION SHORTENS THE SALE MORE THAN ANY FEATURE. Deployment speed becomes the differentiator in a category defined by long implementations.
MARKET TYPE: Fragmented Market (enterprise FP&A), won by embracing the incumbent behaviour.
| MARKET ENTRY PLAYBOOK
THE STANDARD: PROFITABILITY BEFORE CAPITAL CHANGES WHO SETS THE TERMS — and in mid-market finance software it is achievable because the sales motion is short.
RULE 1 — BUILD THE DIRECT ENGINE BEFORE ADDING A PARTNERSHIP LAYER.
Channel amplifies a working motion; it cannot substitute for one.
RULE 2 — EMBRACE THE SPREADSHEET INSTEAD OF REPLACING IT.
Finance teams will not abandon Excel. Governing it wins the deals that "kill the spreadsheet" positioning loses.
RULE 3 — MID-MARKET FP&A IS A REPEATABLE SALE, NOT AN ENTERPRISE ONE.
Standardise implementation to a fixed number of weeks; bespoke delivery destroys the segment's economics.
How to enter
| FOOTHOLD STRATEGY PLAYBOOK
THE STANDARD: The blank canvas is a conversion killer. Opinionated defaults capture the customers who abandon flexible tools out of decision fatigue.
SEQUENCE:
1. Target the abandoner, not the builder.
2. Remove choices deliberately — wizard, fixed structures, minimal cognitive load.
3. Localise into languages where the leaders' content is thin.
4. Plan for the customer to outgrow you; that is the model working.
WORKED: Simplicity converting a segment the leaders lose silently, plus cheap multilingual reach.
CAUTION:
1. AI BUILDERS ATTACKED THIS WEDGE FROM INSIDE THE LEADERS' PRODUCTS. Removing blank-canvas anxiety is now a feature of the tools you positioned against.
2. THE LIFECYCLE CEILING IS BUILT IN — don't bloat the product trying to retain customers who have outgrown the premise.
How to get the first strong position
MARKET PATTERNS & PLAYBOOK
3
MONEY
money rev pri
REVENUE MODEL
Subscription
PRICING MODEL
Tiered Pricing, Value-Based Pricing
WHY THEY WON
Annual SaaS subscriptions priced per user (finance team members accessing the planning system), with additional fees for implementation services and premium support. Deal sizes typically range from $30K–$300K+ annually depending on company size and module count.
Tiers differentiated by feature module (core budgeting vs. full suite including consolidation, reporting, analytics) and user count. Enterprise tier custom-quoted. Value anchor is the CFO's calculation of time saved in the budgeting cycle (a 10-week process reduced to 4 weeks has a quantifiable dollar value).
TARGET AUDIENCE
CUSTOMER BUYING BEHAVIOUR
tg cb
CFOs, FP&A Directors, and Controllers at mid-market companies ($100M–$2B revenue, 500–10,000 employees) running manual or semi-automated Excel-based budgeting and forecasting processes.
Committee-led (Finance, IT, department heads), triggered by a budgeting cycle that ran over time or over budget. Evaluation typically involves a proof-of-concept using the company's own data, with a 3–6 month sales cycle.
| PRICING INTELLIGENCE
What makes this model effective & make customers pay
Build on the tool the buyer refuses to abandon. Excel-native planning is priced against a migration that never has to happen.
RULE 1 — PRESERVING THE FAMILIAR INTERFACE REMOVES THE LARGEST COST IN ENTERPRISE PLANNING SOFTWARE.
Retraining finance teams is the hidden expense that kills competing deals.
RULE 2 — TIER ON ENTITIES, MODELS AND DATA COMPLEXITY, NOT ON USERS.
Finance headcount is small and static. Complexity grows with acquisitions and reporting obligations.
RULE 3 — SPREADSHEET RISK IS THE ANCHOR, AND EVERY CFO HAS A STORY.
Broken links and untraceable errors in board reporting are a vivid, remembered cost.
RULE 4 — MID-MARKET IS A DELIBERATE BAND BETWEEN ENTERPRISE SUITES AND CHAOS.
Naming it and pricing to it is more durable than competing upward on features.
A CFO is buying governance without asking their team to work differently. Price against the change-management programme avoided — usually larger than the licence itself.
PRICE & REVENUE
| Revenue Risk - The biggest threat to revenue stability
Pricing per finance-team seat bills the function AI automation is targeting first, and deal sizes in the $30K-$300K range mean each loss is material.
Building on a spreadsheet interface is the wedge and the ceiling: it wins adoption from Excel users and invites the comparison that the spreadsheet is free.
Implementation and premium support revenue is low-margin and depresses the multiple.
Mid-market FP&A is the most crowded segment in finance software, with several well-funded entrants and two bundled incumbents.
No official ARR or retention published; third-party estimates only.
Where the model can break
4
MOTION
LinkedIn: https://www.linkedin.com/company/vena-solutions, Twitter: https://twitter.com/venasolutions
GROWTH EXPANSION MODEL
COMPETITIVE STRATEGY
motion ge cs
Geographic Expansion, Product Line Expansion, Market Development (New Customer Segments)
HOW THEY EXPAND
After establishing the Canadian mid-market beachhead, Vena expanded into the US, then UK and EMEA. Product expansion into scenario planning and workforce planning deepened ACV within existing accounts. The Vista Equity investment funded both the US sales build-out and the push into the enterprise segment above its traditional mid-market sweet spot.
Differentiation, Focus Strategy
HOW THEY COMPETE
Vena's differentiation — Excel-native architecture — is also its focus strategy: by committing to Excel as the interface, it voluntarily excluded the segment of enterprise buyers that IT departments want to move away from Excel, in exchange for exclusive ownership of the segment that explicitly wants to stay in Excel. That focus prevented Anaplan and Adaptive Insights from counter-attacking effectively.
GROWTH ENGINE
GTM
ge n gtm
Partnership Growth, Content Flywheel
The Microsoft co-selling partnership is the primary growth engine: every Vena deal closed through a Microsoft AE is a customer Microsoft retains long-term, creating a structural incentive for Microsoft to keep recommending Vena. The content flywheel (FP&A thought leadership, benchmarking reports) generates inbound leads that inside sales converts, compounding over time.
- Direct enterprise sales led by former finance practitioners who speak as peer advisors to CFOs.
- Microsoft co-selling partnership routing Vena into enterprise accounts Microsoft's field team was managing.
- ROI-anchored content marketing (benchmarks on budgeting cycle times, finance team productivity) generating inbound.
- Conference presence at CFO Alliance, FEI, and AFP events targeting the exact buyer persona.
SUSTAINING MOATS
Switching Costs, High Customer Lock-In, Brand Power, Technology Advantage (complex enterprise scenarios)
moat
Once a company's full budget model, chart of accounts, multi-year historical data, and departmental workflow logic are built inside Vena, replacing the system requires rebuilding all of that institutional knowledge from scratch — a project finance teams will refuse mid-cycle and IT teams will deprioritise indefinitely.
| MOAT INTELLIGENCE
THE STANDARD: Meeting finance teams inside the tool they refuse to abandon is a faster route to adoption than asking them to leave it.
RULE 1 — THE SPREADSHEET IS THE INTERFACE, THE DATABASE IS THE PRODUCT. Preserving Excel as the front end removes the retraining objection that stalls every planning implementation, while the governed data model underneath is what actually creates the lock-in.
RULE 2 — WORKFLOW AND AUDIT TRAIL ARE WHAT MAKE IT A SYSTEM RATHER THAN A FILE. Version control, approvals and traceability convert modelling into a controlled process finance cannot revert.
RULE 3 — THE POSITION IS EXPOSED FROM BOTH SIDES. Spreadsheet-native competitors attack the same objection; AI-native planning tools argue the spreadsheet interface is itself the constraint.
THE SIGNAL: reducing the change-management cost is a legitimate and underrated wedge. Its weakness is that it ties your product's ceiling to the limitations of the interface you chose to preserve.
Why this company remains defensible
ARR & TAKEAWAY
ARR Journey - what to do at each stage
PRE-$1M ARR — DO NOT FIGHT EXCEL; PUT YOUR DATABASE UNDER IT
Finance teams will not abandon spreadsheets. A native Excel interface over a governed database removes the single biggest objection in planning software.
Land with mid-market finance teams that enterprise suites price out.
$1–5M ARR — SELL THE CLOSE AND THE BUDGET CYCLE
Attach to a recurring calendar event; products used on a cycle renew automatically.
WATCH: cycles completed in-product per customer per year.
$5–10M ARR — PRODUCTISE IMPLEMENTATION OR IT EATS THE MARGIN
Templates by industry make deployment repeatable; push delivery to partners early.
$10–50M ARR — EXPAND FROM FINANCE TO OPERATIONAL PLANNING
Workforce, sales and operational plans on the same model raise ACV with no new buyer.
$50–100M ARR — TAKE GROWTH CAPITAL WHILE THE STORY IS STRONG
Received a $300M growth investment led by Vista in 2022 at a reported valuation above $1B.
Under growth-equity ownership, retention and efficiency become the operating targets.
$100M+ ARR — THE AI-NATIVE ENTRANT IS THE NEXT DISRUPTOR
You disrupted the suite on usability; someone will disrupt you on agentic modelling. Build it into the core rather than bolting on an assistant.
Rule: meeting customers inside the tool they refuse to leave is one of the most reliable wedges in enterprise software.
COPY PLAYBOOK : What Worked → What Failed → What to Replicate → What to Avoid
THE STANDARD: Co-selling with a platform's own sales force gives you enterprise access without the cost of building it. The dependency is that they can build your function natively.
SEQUENCE:
1. Build natively on the tool your buyer already refuses to abandon, rather than asking them to replace it.
2. Earn co-sell status so the platform's field team opens accounts for you.
3. Convert that access into direct relationships before the dependency matters.
WORKED: Piggybacking a global sales force at no headcount cost, into accounts already under management.
CAUTION:
1. THE PLATFORM CAN NATIVELY ABSORB YOUR FUNCTION. Co-sell status is a commercial arrangement, not a contract for your existence.
2. BUILDING ON A FAMILIAR INTERFACE WINS ADOPTION AND CAPS SOPHISTICATION — the same trade every familiarity-led product makes.
bottom of page