Extract discovery insights

Product Findings: Month-End Close & Reconciliation Opportunities

We spoke with eight finance leads at mid-sized companies (70–400 staff) to evaluate appetite for a reconciliation product. Here is what we learned, followed by our confidence assessment.

---

What We Learned

#### 1. Pain is Acute, but Fragmented by Niche Reconciliation is universally recognized as a bottleneck¹, but the root cause varies heavily by business model: * Retail, Hospitality & Construction (High Volume/Messy Data): Companies dealing with multiple store cards (Call 3), complex payment processor payouts (Call 7), or high-volume line items (Call 8) spend up to 40% of their close cycle manually matching data in shared spreadsheets or re-keying PDF statements.³ * Agencies & Multi-Entity (Intercompany): Multi-entity structures suffer from recurring intercompany balancing discrepancies that defy easy automation⁴ (Call 5). * Logistics (Basic Bank Feeds): Basic bank feed drops force manual tick-and-bash routines in Excel (Call 1).

#### 2. Adoption Barriers and Skepticism Run High Even where pain is severe, market entry is fraught with buyer resistance: * Migration PTSD: Switching costs are massive. One CFO noted a four-month migration failure that destroyed custom matching rules and drove staff back to spreadsheets, refusing to switch again unless migration is fully managed (Call 4). * Deep Trust Deficit: Finance leads have been burned by over-promised automation and pristine demo environments. They demand proof on their own messy data before believing claims (Calls 1 & 8). * Budget Freezes & Apathy: Smaller teams (70–95 staff) with clean ERP setups or frozen budgets report no pressing need for new point solutions (Calls 2 & 6).

---

Confidence Assessment: Low-Moderate (Conditional)

• Problem Validation (High Confidence): We are highly confident that reconciliation is tedious, manual, and a major driver of close delays in high-volume, multi-card, or multi-entity businesses.
• Commercial Viability (Low-Moderate Confidence): Despite the pain, we cannot rely on a self-serve, software-only motion.² High switching friction, deep skepticism toward AI/automation demos, and strict migration/implementation requirements mean buyers will churn or bounce without hands-on onboarding.

#### Recommendation Do not build a generic, self-serve reconciliation tool. If we proceed, the product must include a heavy-touch onboarding/migration service to overcome migration PTSD, alongside a "sandbox" feature allowing prospects to test matching rules on their actual messy data before purchasing.

Findings summary

The pain is real, but it is not universal—and it is concentrated in specific reconciliation workflows. Five of the eight interviewees described reconciliation as a meaningful close burden. Their problems were concrete: dropped bank-feed transactions and manual matching (Call 1); high-volume card statements re-keyed from PDFs (Call 3); intercompany balances (Call 5); processor payouts obscured by fees and refunds (Call 7); and repetitive matching at scale (Call 8). One reported finding £14k in duplicate transactions. These examples suggest the opportunity may be less “speed up month-end close” and more “handle particular messy, high-volume matching jobs reliably.”

Company context seems to matter.¹ The clearest pain came from organisations with volume, multiple entities, many cards, or complex payment flows. Two interviewees said close was fine: one had a well-established ERP and mainly struggled with receipts; another was small, knew every transaction, and had frozen budgets. A reconciliation product is therefore unlikely to be equally valuable to every mid-sized company.

Trust and implementation are central adoption barriers. One finance leader regretted a tool switch after a four-month migration, lost matching rules, and a return to spreadsheets. Another would not trust automation until it worked on messy real data. A product that matches well in a demo may still fail if it cannot preserve existing rules, handle exceptions, and prove accuracy on customers’ own data.

Willingness to pay is unproven. One controller said saving two days could justify the cost, but explicitly expressed scepticism based on past promises. Another prospect would not buy this year. These calls reveal value hypotheses, not validated demand or pricing.

Implications for the product team

Explore a narrow, workflow-led wedge rather than assuming a broad reconciliation platform is needed. Card-spend reconciliation may fit our existing product particularly well; processor payouts and intercompany are other distinct opportunities, but may require different data and capabilities. Test which segment has both acute pain and access to usable data. Prioritise messy-data performance, explainable matches and exceptions, and low-friction migration or coexistence with spreadsheets.

Confidence

• Moderate confidence that reconciliation is a significant pain for some complex, high-volume finance teams: several independent, specific examples support this.
• Low-to-moderate confidence on which workflow or customer segment is the best product wedge: each use case appears in few calls.
• Low confidence on market-wide prevalence, willingness to pay, achievable time savings, or product feasibility: eight qualitative calls cannot establish these, and no prototype or pricing was tested.

Treat this as a reason to run targeted workflow and data-validation research—not yet as evidence to commit to a broad build.

Findings: month-end reconciliation

These calls justify testing a focused reconciliation proposition, but do not yet justify building a broad product. Six participants described reconciliation pain or dissatisfaction with their tools. However, their problems differ substantially, and evidence of willingness to adopt or pay is weak.

What we learned

Reconciliation can materially delay close, but it is not a universal problem. The logistics controller reported at least three reconciliation days within an eight-day close. The agency accountant spends 1.5 days on intercompany balances. The construction controller estimated reconciliation at 40% of close, while the hospitality controller said processor payouts are the final blocker.

Conversely, the SaaS and charity participants explicitly said close works well. SaaS’s remaining frustration was receipt chasing, which should not be counted as reconciliation demand. These counterexamples argue against targeting all finance teams simply because they run a monthly close.

“Reconciliation” covers several distinct jobs.

These may require different data integrations, matching logic and workflows. Combining them into one demand signal would overstate support for any particular product.

Spreadsheets persist for different reasons. Logistics uses them to compensate for feed gaps; retail uses them to coordinate work; manufacturing returned to them after a failed tool migration. Spreadsheet use alone does not establish a desire to replace spreadsheets.

Trust and migration could determine adoption. The construction controller wants proof using messy, real data. The logistics controller is sceptical of promised savings. The manufacturing CFO made migration assistance a condition of switching after losing matching rules during a four-month migration. These are specific adoption requirements, although we cannot assume every buyer shares them.

How confident can we be?

Moderate confidence that meaningful problems exist in some of these organisations. Participants supplied concrete workflows, time estimates and one financial example. These remain self-reports: we have not observed the work or verified the figures. The £14k in duplicates does not establish losses incurred or savings our product could deliver.

Low confidence about prevalence, the best segment or a common solution. Eight exploratory calls provide useful hypotheses, not market estimates. Recruitment criteria and customer relationships are unspecified. Each industry appears only once, so differences cannot reliably be attributed to sector, company size or ERP maturity.

Very low confidence about commercial demand. One participant gave a conditional value statement after being asked about price, without naming a budget or committing to buy. Another explicitly ruled out new spending this year. No purchase, pilot commitment or switching decision is evidenced.

Implication for the product decision

Prioritise validation of card-spend reconciliation, given its proximity to our existing spend-management product, while recognising that only one call directly supports this use case.

Recruit more teams with that workflow, inspect actual statements and reconciliation records, and test a narrow prototype on messy data. Measure time saved, incorrect matches and exception-handling effort. Seek concrete pilot commitments and establish budget ownership and migration requirements before committing to build.