Pluvo — ICP Use-Case Map
DECISION MAKERS
These are the economic buyers who sign the contract. They evaluate Pluvo against the cost of inaction (staying in spreadsheets) or switching from a legacy tool.
Title Map — Decision Makers
Ranked by likelihood of being the contract signer and budget holder for a tool like Pluvo. Probability reflects both how often this title exists at Pluvo's target company size and how likely they are to champion and authorize the purchase.
| Rank | Title | Probability | Why This Title |
|---|---|---|---|
| 1 | Chief Financial Officer (CFO) | ●●●●● | Primary buyer in every signal — testimonials, investor angels, messaging. At 80M companies, the CFO owns all finance tooling decisions outright. |
| 2 | VP of Finance | ●●●●○ | Common at Series B–C companies that haven't elevated to a full CFO yet, or where the CFO title is reserved for a future hire. Same authority, same pain points. |
| 3 | Fractional / Part-Time CFO | ●●●●○ | Explicitly targeted in Pluvo's multi-entity feature. They buy for their practice, not a single company — high LTV if each client becomes a separate instance. |
| 4 | Finance Director | ●●●○○ | At 100–300 person companies, the Finance Director often holds budget authority for sub-$20K tools without CFO sign-off. Straddles buyer and user. |
| 5 | Head of Finance | ●●●○○ | Startup-native title (common at 30M companies) where one person runs all of finance. Functionally identical to VP Finance but signals a leaner org. |
| 6 | Chief Operating Officer (COO) | ●●○○○ | At smaller companies where finance rolls up under ops, the COO may own the budget. Also champions the purchase when they experience live scenario demos. |
| 7 | CEO / Founder | ●●○○○ | At sub-50 person companies, the CEO may directly authorize finance tooling — especially founder-led companies pre-CFO hire. Rarely the evaluator, but holds the checkbook. |
| 8 | Controller | ●●○○○ | At companies without a CFO, the Controller is often the most senior finance person. More accounting-oriented, but owns the ERP relationship Pluvo plugs into. |
CFO / VP Finance / Head of Finance
Profile: First or only senior finance hire. 80M revenue, 30–300 employees, Series A–C. Reports to CEO, sits on board. Both strategist and operator.
Pain Points:
- 40%+ of week spent assembling data, not advising the business
- Board prep takes days; can't answer live "what if" questions in the room
- Models are brittle Excel files only they understand — institutional knowledge lives in their head
- Decision context scattered across email, Slack, docs — nothing compounds over time
- Too small for enterprise tools ($30K+ ACV), too complex for spreadsheets alone
Use Cases:
| Use Case | What They Need | What Pluvo Delivers |
|---|---|---|
| Variance analysis | "Why did we miss by 12%?" — answered in minutes, not a day | Agentic AI decomposes by driver, classifies structural vs. one-time, traces root cause |
| Live scenario planning | Base/downside/upside ready for board; adjust assumptions on the fly | Branches from grounded data; verified numbers build trust with investors and board |
| Fundraise & data room | Clean financials, cohort metrics, scenario models for diligence — in hours | Replaces weeks of manual model-building; extends runway visibility |
| Strategic decision support | "Can we afford 10 new engineers this quarter?" — answered in the meeting | Collapses question-to-answer loop from days to minutes |
Buying Triggers: Approaching a fundraise, first institutional board meeting, inheriting undocumented models, monthly close >5 days, CEO frustrated by slow answers.
Fractional / Part-Time CFO
Profile: Independent or firm-based. Managing 3–8 clients (30M revenue each). Bills hourly or on retainer. Value tied directly to insight-per-hour.
Pain Points:
- Context-switching across clients with different charts of accounts burns hours
- Loses the thread between engagements — can't recall what was decided two weeks ago
- New client onboarding takes a full week just to build a baseline
- Margins collapse when data-pulling crowds out advisory time
Use Cases:
| Use Case | What They Need | What Pluvo Delivers |
|---|---|---|
| Multi-entity management | One workspace across all clients | Per-client QBO/Xero connections; switch contexts without separate spreadsheet environments |
| Institutional memory | Pick up exactly where you left off across a two-week gap | Decisions, assumptions, reasoning retained — looks deeply attentive even across gaps |
| Rapid client onboarding | First-meeting insights within hours of engagement | Agentic analysis generates financial health baseline without manual model construction |
Buying Triggers: Taking on a 4th+ client, losing a client due to slow turnaround, scaling a practice and needing leverage.
END USERS
These are the day-to-day operators in the platform. They influence the purchase, evaluate during trials, and determine renewal. At Pluvo's target company size the decision maker and end user are often the same person — but at slightly larger orgs these roles separate.
Title Map — End Users
Ranked by likelihood of being a regular, active user of Pluvo. Probability reflects how often this title would log into the platform weekly and how central Pluvo is to their workflow.
| Rank | Title | Probability | Why This Title |
|---|---|---|---|
| 1 | FP&A Analyst | ●●●●● | Core power user. Builds analyses, runs scenarios, maintains forecasts. Pluvo directly replaces their most tedious daily work. At larger orgs in Pluvo's range, this is the person living in the tool. |
| 2 | Senior Financial Analyst | ●●●●● | Same as above with more seniority. Owns specific analytical domains (revenue, opex, headcount). First to evaluate the tool in a trial. |
| 3 | Finance Director / Head of FP&A | ●●●●● | At 100–500 employee companies, this person still does hands-on analytical work while also managing the reporting cadence. Both builder and consumer. |
| 4 | Finance Manager | ●●●●○ | Mid-level role that owns a specific financial domain (revenue ops, cost center management). Uses Pluvo for recurring analyses and departmental reporting. |
| 5 | Financial Controller | ●●●○○ | Owns the close process and GL accuracy. Uses Pluvo's variance analysis to validate close results and investigate anomalies before signing off. |
| 6 | CFO / VP Finance | ●●●○○ | At smaller companies (sub-100 employees), the CFO is also the primary analyst. At larger orgs, they consume shared analyses and run ad-hoc scenarios before board meetings. |
| 7 | Accounting Manager | ●●●○○ | Adjacent user. Doesn't build models but uses Pluvo to validate that reported numbers reconcile to the GL. First line of defense on data accuracy. |
| 8 | Revenue / Sales Operations Analyst | ●●○○○ | Cross-functional user who needs pipeline-to-forecast reconciliation. Uses Pluvo to bridge CRM data with financial actuals. |
| 9 | Chief of Staff | ●●○○○ | At founder-led companies, the Chief of Staff often serves as the connective tissue between finance and the CEO. Consumes analyses, prepares board decks, routes questions to the finance team. |
| 10 | CEO / Founder | ●●○○○ | Consumes shared analyses, runs what-if questions during strategy sessions, reviews scenarios asynchronously. Doesn't build — triggers and reviews. |
| 11 | COO / VP Operations | ●●○○○ | Consumes operational financial analysis — headcount planning, departmental spend, capacity modeling. Uses Pluvo outputs to make operational decisions. |
| 12 | VP / Director of Strategy | ●○○○○ | At companies with a dedicated strategy function, this person uses scenario planning outputs for M&A evaluation, market entry decisions, and long-range planning. |
| 13 | Department Head (VP Sales, VP Eng, VP Marketing) | ●○○○○ | Occasional consumer. Reviews budget vs. actuals for their department, comments on shared analyses, requests scenario branches for headcount or spend changes. |
| 14 | Board Member / Investor | ●○○○○ | Lowest-frequency user. May receive read-only analysis links before board meetings. Doesn't log in regularly but seeing Pluvo outputs builds brand awareness for future portfolio companies. |
| 15 | External Accountant / Bookkeeper | ●○○○○ | For companies using outsourced accounting, the bookkeeper may interact with Pluvo's connected data layer or validate that integrations are pulling correctly. Fringe user. |
Finance Director / Head of FP&A / Senior Analyst
Profile: Senior Finance Manager or Director. 150M revenue, 100–500 employees. Owns models, monthly close, reporting cadence. May manage 1–2 junior analysts but does most of the work. Reports to CFO.
Pain Points:
- They are the bottleneck — every department wants a custom analysis, CFO wants board materials by Friday
- 15-tab Excel model takes a week to update each quarter
- Only person who understands model logic — single point of failure
- Meetings produce "let me get back to you" instead of real-time answers
- Can't hire another analyst; needs to 2–3x their own output
Use Cases:
| Use Case | What They Need | What Pluvo Delivers |
|---|---|---|
| Report interrogation | "Why did enterprise close rate drop?" — answer in the meeting, not after | Real-time drill-down during leadership discussions; shifts from report-producer to insight-provider |
| Driver-based forecasting | Quarterly forecasts in hours, not a week of formula maintenance | Constructs forecast logic from connected data; auto-updates as new data flows in |
| Repeatable analysis templates | Monthly variance, dept spend, pipeline reconciliation — standardized and automatic | Eliminates the repetitive first-two-weeks-of-every-month grind |
| Collaborative outputs | Share with CFO and dept heads; iterate without email ping-pong | Tagged stakeholders, threaded comments, shareable links replace Excel-over-email |
Buying Triggers: Forecast cycle >5 days, key-person risk on models, recurring "get back to you" moments in leadership meetings, CFO asks them to evaluate tools.
CEO / COO / Chief of Staff
Profile: Founder-CEO, COO, or Chief of Staff. Relies on finance team for strategic input. Doesn't use FP&A tools directly — asks the questions that trigger analysis. Consumes outputs, not builds them.
Pain Points:
- Decides on gut because proper analysis takes too long
- By the time the scenario model arrives, the decision window has closed
- Reports feel backward-looking; wants forward-looking trade-off analysis
Use Cases:
| Use Case | What They Need | What Pluvo Delivers |
|---|---|---|
| Live what-if exploration | "What if we delay hiring a quarter?" — answered in the room | CFO runs Pluvo simulation in real time; CEO sees trade-offs immediately |
| Async analysis review | Review financials on own schedule, leave comments, request new scenarios | Interactive shareable links replace forwarded Excel attachments |
Buying Triggers: Rarely a direct buyer. Champions the purchase after experiencing a live scenario demo in a leadership meeting. Hears about Pluvo from their CFO.
Persona × Use Case Matrix
| Use Case | CFO / VP Fin | Fractional CFO | FP&A Analyst | Finance Director | Finance Manager | Controller | Rev Ops | CEO / COO | Chief of Staff | Dept Heads | Board |
|---|---|---|---|---|---|---|---|---|---|---|---|
| Variance analysis | ● | ● | ● | ● | ● | ● | |||||
| Live scenario planning | ● | ● | ● | ● | |||||||
| Fundraise / data room | ● | ● | ● | ● | |||||||
| Multi-entity management | ● | ||||||||||
| Institutional memory | ● | ● | ● | ● | |||||||
| Report interrogation | ● | ● | ● | ● | |||||||
| Driver-based forecasting | ● | ● | ● | ||||||||
| Repeatable templates | ● | ● | ● | ● | |||||||
| Collaborative outputs | ● | ● | ● | ● | |||||||
| Async analysis review | ● | ● | ● | ● | |||||||
| Budget vs. actuals | ● | ● | ● | ● | ● | ||||||
| Data validation / reconciliation | ● | ● |