Centage
Product · Voice of customer

Customer pain analysis

183
opportunities
Type = New Business or Trial, closed Jul 25 – Jul 26 or open in the window
15
industries in scope
Named canonical industries plus Unknown and Other
141
discovery + demo calls
Titles matched to disco/demo keywords or Gong trackers
675
customer pain mentions
Extracted from Gong AI summaries; customer-side speakers only
24
pain buckets
Emerged from clustering 595 raw phrases from the field
18·84·13
won · lost · open
Outcome split across opps that surfaced at least one disco/demo call
§ 1

What we heard, ranked.

Frequency is measured by the share of the 115 opportunities-with-calls where a customer articulated the pain at least once. A prospect who says it four times in one call counts once.

Dominant (>25% of opps)
Common (10–25%)
Recurring (5–10%)
Long tail (<5%)
  1. Excel / spreadsheets can't scale
    53% of 115 opps · 61 deals · 67 calls
    Spreadsheet-based budgeting/forecasting is manual, fragile, error-prone, hits size limits, breaks formulas, and cannot support the org's complexity.
  2. Data integration and uploads are manual
    37% of 115 opps · 42 deals · 45 calls
    Pulling data from ERP/HRIS/payroll/BI/warehouse is manual, brittle, requires IT, and lacks two-way sync or API access.
  3. Complex revenue and driver modeling
    30% of 115 opps · 35 deals · 39 calls
    Diverse or driver-based revenue (SKU, per-lease, project, grant, membership, rental, commission, PVM) is hard to model.
  4. Reporting lacks drill-down and granularity
    30% of 115 opps · 34 deals · 36 calls
    Cannot drill from summary to transactions, dimensions, sub-ledger, vendor, project, or component level — variance and root-cause analysis blocked.
  5. Reporting is manual and inflexible
    26% of 115 opps · 30 deals · 33 calls
    Standard, ad-hoc, board, and management reporting is slow to produce, static, hard to slice, and lacks dashboarding or drill-down.
  6. Current tool is slow, clunky, or unreliable
    25% of 115 opps · 29 deals · 33 calls
    The incumbent FP&A/BI/ERP tool has poor UX, latency, bugs, high maintenance burden, requires consultants, or is being sunset.
  7. Implementation and buying friction
    23% of 115 opps · 26 deals · 29 calls
    Vendor selection stress, prior failed implementations, IT/legal/security approvals, tight timelines, contract-expiring pressure, budget constraints on the deal.
  8. Consolidation is slow and manual
    23% of 115 opps · 26 deals · 26 calls
    Rolling up P&Ls, closing books, and month-end reporting is time-consuming, macro-driven, and delays finance cycles.
  9. No single source of truth / data silos
    20% of 115 opps · 23 deals · 24 calls
    Data lives in disconnected systems, spreadsheets, and ERPs with no central, trusted source for financial and operational data.
  10. Small / lean team overwhelmed
    19% of 115 opps · 22 deals · 23 calls
    Finance team is too small, stretched, doing manual work on nights/weekends, and cannot free capacity for strategic work.
  11. No scenario planning / what-if
    19% of 115 opps · 22 deals · 23 calls
    Cannot model scenarios, flex assumptions, run what-ifs, or do rolling forecasts and variance analysis in a repeatable way.
  12. Multi-entity / intercompany is painful
    17% of 115 opps · 19 deals · 22 calls
    Multi-entity structures, intercompany eliminations, and cross-entity rollups are difficult with current tooling.
  13. Team collaboration is broken
    16% of 115 opps · 18 deals · 18 calls
    Budget owners, departments, and finance cannot collaborate effectively; hand-offs happen via email/spreadsheets and coordination breaks down.
  14. Growth outpacing current process
    16% of 115 opps · 18 deals · 18 calls
    Company growth, expansion, acquisitions, or new complexity is outrunning the current planning stack and process maturity.
  15. Workforce / personnel planning is manual
    13% of 115 opps · 15 deals · 17 calls
    Headcount, salary, fringe, benefits, overtime, and FTE planning are manual, crude, or lack granularity and HR integration.
  16. GL / chart of accounts is non-standard
    13% of 115 opps · 15 deals · 17 calls
    Chart of accounts, GL strings, project codes, and account structures are inconsistent, poorly configured, or block clean reporting.
  17. Budget owners hard to coordinate
    13% of 115 opps · 15 deals · 15 calls
    Distributing budget input to non-finance managers is hard: low adoption, inconsistent formats, no workflow, no accountability.
  18. Non-finance users can't use current tool
    12% of 115 opps · 14 deals · 14 calls
    Department heads, operational users, and managers can't self-serve — UI is too technical, too dated, or requires finance to intervene.
  19. Enterprise FP&A tools too expensive or heavy
    12% of 115 opps · 14 deals · 14 calls
    Competitor/enterprise tools (Anaplan, Adaptive, NSPB, etc.) are too complex, too costly, or require coding — mid-market can't justify them.
  20. No version control or audit trail
    12% of 115 opps · 14 deals · 14 calls
    Cannot see who changed what, cannot compare versions, no history of edits, no formal audit trail on budgets/forecasts.
  21. No cash flow visibility
    10% of 115 opps · 11 deals · 11 calls
    Cash flow forecasting, weekly cash view, direct-cash-method, and forward cash visibility are weak, manual, or inaccurate.
  22. No role-based access or security
    9% of 115 opps · 10 deals · 10 calls
    Cannot grant granular permissions, role-based access, data-security controls, or manage sensitive data (payroll, IP) safely.
  23. Other
    8% of 115 opps · 9 deals · 9 calls
    One-off pains that don't cluster into a canonical bucket (compliance, data sovereignty, key-person risk, etc.).
  24. Multi-currency / geo complexity
    5% of 115 opps · 6 deals · 8 calls
    FX modeling, multi-currency consolidation, cross-country/geo rollups, and tax allocations across geographies are complex.
§ 2

The six that show up in more than one in four deals.

If a discovery-or-demo conversation surfaced only one pain worth acting on, statistically it was one of these. Verbatim exemplars pulled from the calls themselves — every quote is a real prospect from a real deal.

53%

Excel / spreadsheets can't scale

Spreadsheet-based budgeting/forecasting is manual, fragile, error-prone, hits size limits, breaks formulas, and cannot support the org's complexity.

61 deals · 67 calls

"Current budgeting and forecasting are managed in Excel and Castaway, creating inefficiencies"

Lost Healthcare

"negative feedback from senior leadership regarding current Excel-based FP&A tool's usability"

Lost Non-profit Organizations

"Manual, spreadsheet-based budgeting is inefficient and time-consuming with 60 locations"

Lost Retail & E-commerce
37%

Data integration and uploads are manual

Pulling data from ERP/HRIS/payroll/BI/warehouse is manual, brittle, requires IT, and lacks two-way sync or API access.

42 deals · 45 calls

"Need executive dashboards integrating financial data with operational metrics from Qualia"

Lost Unknown

"Struggle to tie operational metrics to financial outcomes and analyze variance drivers"

Won Utilities

"Manual process, risk of errors, security concerns, and difficulty in creating different scenarios"

Lost Technology & IT Services
30%

Complex revenue and driver modeling

Diverse or driver-based revenue (SKU, per-lease, project, grant, membership, rental, commission, PVM) is hard to model.

35 deals · 39 calls

"concern about forecasting, budgeting, pro forma financials with historical acquisition data"

Lost Construction

"complex expense allocations with varying percentage splits between commercial/residential"

Open Business & Consumer Services

"Lumpy sales cycle, perpetual licensing, and manufacture own units adds COGS complexity"

Lost IT Services and IT Consulting
30%

Reporting lacks drill-down and granularity

Cannot drill from summary to transactions, dimensions, sub-ledger, vendor, project, or component level — variance and root-cause analysis blocked.

34 deals · 36 calls

"most cumbersome aspect is spreadsheet systems for assessing profitability among groups"

Lost Unknown

"limited financial reporting for salary/benefits across grants/programs/departments"

Open Nonprofit & Human Services

"Need to drill down from actuals to transaction-level detail and link to invoices"

Lost Unknown
26%

Reporting is manual and inflexible

Standard, ad-hoc, board, and management reporting is slow to produce, static, hard to slice, and lacks dashboarding or drill-down.

30 deals · 33 calls

"Need high-level summaries for executives and highly detailed reports for budget managers"

Lost Unknown

"Desire for a stoplight report or dashboard view for the board — red, yellow, green indicators"

Lost Nonprofit & Human Services

"need ad-hoc reporting, diverse roll-ups, transactional drill-down for non-finance users"

Open Unknown
25%

Current tool is slow, clunky, or unreliable

The incumbent FP&A/BI/ERP tool has poor UX, latency, bugs, high maintenance burden, requires consultants, or is being sunset.

29 deals · 33 calls

"Current solution has similar security features but UI is not as clean or easy to navigate"

Open Nonprofit & Human Services

"Current budgeting software, PowerPlan, is sunsetting, and we are seeking an alternative"

Lost Nonprofit & Human Services

"QuickBooks is a limited tool for data categorization — garbage in garbage out"

Lost E-Learning Providers
§ 3

Pain by industry — where the shape shifts.

Each cell shows how many opps in that industry surfaced this pain, over the industry's total. Darker shading means a larger share of the industry mentioned it — that's where the industry-specific pitch should lean.

Pain Nonprofitn=21Healthcaren=9Manufacturingn=9Tech · ITn=8FinServn=5Consultingn=5Insurancen=4Real Est.n=4Bus/Cons Svcsn=3Utilitiesn=3Retailn=3Transportn=3Unknownn=20Othern=18
Excel / spreadsheets can't scale1362%556%667%450%5100%480%250%4100%3100%267%267%·525%633%
Data integration and uploads are manual733%444%667%225%360%·250%·133%133%·133%735%844%
Complex revenue and driver modeling629%444%556%338%240%360%··133%133%·133%525%422%
Reporting lacks drill-down and granularity524%333%333%225%·120%··133%3100%133%·1050%528%
Reporting is manual and inflexible629%333%333%112%120%120%125%125%·133%··840%422%
Current tool is slow, clunky, or unreliable524%333%111%112%240%120%··133%·133%133%735%633%
Implementation and buying friction733%333%222%225%120%240%125%·133%133%··210%422%
Consolidation is slow and manual524%333%222%··120%·250%133%133%··735%422%
No single source of truth / data silos629%222%111%225%240%·250%125%133%···315%317%
Small / lean team overwhelmed314%111%444%225%·240%125%125%·133%·133%15%528%
No scenario planning / what-if314%222%444%112%120%240%125%125%133%···420%211%
Multi-entity / intercompany is painful314%·333%112%···250%·133%·133%525%317%
Team collaboration is broken629%·111%112%120%··250%133%133%··210%317%
Growth outpacing current process210%·222%112%120%··125%·133%·133%630%317%
Workforce / personnel planning is manual629%222%111%··120%····133%·315%16%
GL / chart of accounts is non-standard629%··112%·120%······420%317%
Budget owners hard to coordinate629%222%222%····125%····315%16%
Non-finance users can't use current tool419%111%111%225%···125%··133%·420%·
Enterprise FP&A tools too expensive or heavy314%111%111%112%120%240%125%·133%·133%·210%·
No version control or audit trail419%111%111%·120%120%125%125%133%···210%16%
No cash flow visibility210%·111%112%240%120%·····133%·317%
No role-based access or security210%111%····250%·133%··133%210%16%
Other·111%111%112%120%·······210%317%
Multi-currency / geo complexity··111%·········210%317%
§ 4

Won vs lost — the deal-signal read.

Same 115 opps, split by deal outcome. Red-tinted rows mark pains that skew toward Lost deals more than average — worth pressure-testing whether we currently under-solve them. Green-tinted rows mark pains that skew toward Won deals — potential accelerators worth leading with.

Pain (sorted so Lost-leaning pains sit at top) Won (18) Lost (84) Open (13)
Enterprise FP&A tools too expensive or heavy
0
0%
13
93%
1
7%
No version control or audit trail
0
0%
12
86%
2
14%
No scenario planning / what-if
3
14%
18
82%
1
5%
Current tool is slow, clunky, or unreliable
2
7%
23
79%
4
14%
Complex revenue and driver modeling
4
11%
27
77%
4
11%
Other
1
11%
7
78%
1
11%
Reporting lacks drill-down and granularity
2
6%
26
76%
6
18%
Excel / spreadsheets can't scale
11
18%
46
75%
4
7%
Data integration and uploads are manual
6
14%
31
74%
5
12%
Team collaboration is broken
4
22%
13
72%
1
6%
Non-finance users can't use current tool
3
21%
10
71%
1
7%
Implementation and buying friction
7
27%
18
69%
1
4%
Consolidation is slow and manual
6
23%
18
69%
2
8%
Multi-entity / intercompany is painful
4
21%
13
68%
2
11%
Growth outpacing current process
6
33%
12
67%
0
0%
GL / chart of accounts is non-standard
3
20%
10
67%
2
13%
Budget owners hard to coordinate
4
27%
10
67%
1
7%
Multi-currency / geo complexity
1
17%
4
67%
1
17%
Small / lean team overwhelmed
7
32%
14
64%
1
5%
No single source of truth / data silos
5
22%
14
61%
4
17%
Reporting is manual and inflexible
8
27%
18
60%
4
13%
Workforce / personnel planning is manual
4
27%
9
60%
2
13%
No role-based access or security
2
20%
6
60%
2
20%
No cash flow visibility
2
18%
6
55%
3
27%
§ 5

Every bucket — the full taxonomy.

All 24 canonical pain buckets, ordered by frequency, each with a short definition and up to three verbatim exemplars in the customer's own words.

§ 6

How this was built.

Scope

  • Salesforce Opportunities where Type IN ('New Business','Trial') and StageName != 'Renewal'.
  • Closed in the last 12 months (Jul 2025 → Jul 2026), or open and created in that window.
  • Renewals excluded because Centage's Type = 'Existing Business' is renewal-dominated (95%+ of that population).
  • Result: 183 opps · 30 Won · 133 Lost · 20 Open. 115 of those had ≥1 disco/demo Gong call.

Call selection

  • Pulled every Gong call in the 12-month window (945 total), enriched with context.objects for Salesforce Opportunity linkage.
  • Joined to the 183-opp set via Opportunity ID (deterministic — no fuzzy name matching).
  • Classified titles by keyword: discovery = intro / discovery / fit / qualification / first call / exploratory / kickoff; demo = demo / walkthrough / product overview / demonstration / screen share / product tour.
  • 141 calls retained (131 demo, 9 discovery, 1 both). 158 non-disco/non-demo calls on scoped opps (proposals, syncs, onboarding recaps) intentionally dropped.

Pain extraction

  • Pulled Gong AI content for each of the 141 calls: brief + key points + speaker-attributed outline + highlights.
  • Ten parallel extraction agents (14–15 calls each) produced structured mentions with verbatim, normalized_theme, confidence, and speaker_role. Internal Centage speakers were filtered out before extraction.
  • 675 customer-side pain mentions across 134 calls (7 calls had no customer pain expressed — usually short intros or aborted flows). 84% high confidence.
  • Free-form normalized_themes (595 distinct) were then clustered into 24 canonical buckets via a single consolidation pass.

Validation

  • Five-call transcript sample (2 Lost, 2 Won, 1 Open; mixed industries) confirmed extractions trace to real customer language. Example: Certify Health's "QBO class structure is limited" appears verbatim in transcript as "this is one of the limitations of qbo is setting the class structure, is a limitation."
  • Ratio of pain-adjacent transcript lines to extracted pains averaged ~3.5×, i.e., customers restated pains multiple times per call — every extracted pain was grounded.

Confidence & caveats

  • Rests on Gong AI summary fidelity. On the validation sample it captured the substance faithfully, but a short, aborted, or heavily internal-monologue call may under-count pain.
  • Frequency % is over opps with calls (115), not all 183 scoped opps. 40 opps had no Gong disco/demo call — likely cold-lost or fully SDR-driven.
  • Industry crosstab treats industries with n<3 opps as noise ("Other Industries" bucket). 20 opps have Unknown industry — Account.Industry not set in SFDC.
  • The word "pain" here means anything a customer articulated as a problem, gap, or unmet need — regardless of whether Centage solves it.

Refresh

Quarterly at minimum. Re-run when a full quarter of new discovery/demo calls has accumulated, or ahead of any major positioning / roadmap review.