The problem: knowledge chaos in financial operations
Financial operations teams — AP clerks, fraud analysts, reconciliation specialists — spend 40–60% of their time searching for procedures. The routine work is automated; it's the exceptions that hurt. And procedures for handling exceptions are scattered, outdated, or in someone's head.
High-complication, low-complexity operations suffer from knowledge chaos: when information is incomplete, the result is errors, delays, and vendor friction.
Digging deeper, four patterns repeat across the industry:
- Scattered documentation. Procedures live across SharePoint folders, email threads, outdated training docs, and tribal knowledge.
- Shortcuts & escalations. Even with 63% automation adoption, organizations still need manual workarounds for exceptions — and senior staff become bottlenecks answering repetitive "how do I handle this?" questions.
- High error rates & rework. 70% of organizations report AP error rates of 5% or more; 88% of manual AP documents include data-entry errors.
- Long onboarding. New clerks take 3–6 months to get proficient. A common complaint, verbatim: "No training, expected to learn on your own."
Where it fits: the gap in the landscape
Knowledge and automation tools cluster into four camps — and one of them is underserved:
Fully automated
RPA / traditional automation (UiPath, Automation Anywhere). 0% human involvement, pure rules: "if invoice matches PO exactly, auto-approve." Requires complete knowledge and no judgement.
Agentic automation
AI decides within bounds (Zora AI, UiPath Agents). Autonomous problem-solving, not exception handling — tolerates some knowledge gaps but will make mistakes.
Knowledge reference
Search & retrieve (Guru, Confluence, SharePoint). Ad-hoc lookup: "what's our vendor dispute policy?" Knowledge exists — but everywhere and nowhere at once.
Guided human work ← the wedge
70–80% procedural, 20–30% judgment. A human decides, with procedural guidance: "vendor dispute + price change + new contact = escalate to manager." Tolerates knowledge gaps because judgement is involved — but today it slows everything down.
The solution
Deliver faster, more consistent support by guiding analysts through clear, interactive procedures, embedded directly in the workflow — eliminating the search through PDFs, outdated wikis, and tribal knowledge.
- AI-supported ingestion & conversion. Ingests scattered SOPs and documents and generates dynamic, clickable flowcharts.
- Live clickable flowcharts. Decision-tree-style guidance, launched natively inside the console — no context switching.
- Auto-prompting with context awareness. Launches the relevant flow based on the detected exception — PO mismatch, pricing issue, or analyst input.
- Standardization & updates. Keeps itself fresh with feedback from real cases; SMEs make live edits without engineering support.
Architecture at a glance
MVP scope, and how it was chosen
Every candidate feature was scored value to customer + KPI impact − effort; 12+ made the MVP, 8+ the second release, 4+ an extended release, and the rest were deprioritized. (The full 31-feature scoring table is in the appendix of the original deck.) What made the cut:
| Cluster | Capability | Why it's MVP |
|---|---|---|
| Content ingestion & authoring | Ingestion wizard | One-click upload of PDFs / DOCX / PPT; NLP parses headings and flowchart arrows into a draft decision tree. Essential component. |
| Auto tree builder | Builds flowcharts with a fine-tuned AI model — eliminates heavy manual re-authoring, a top blocker called out in research. | |
| Drag-and-drop tree editor | No-code visual canvas so SMEs can own content. | |
| Branching logic & required steps | Nodes that block advance until mandatory info is captured — ensures SOP compliance. | |
| In-console guidance | Native web component | Flowcharts launch natively inside the console. Zero context-switching; the key advantage over pop-up tools. |
| Contextual launch rules | Auto-lists the relevant guide based on detected intent — drives adoption through ease of use. | |
| Insight & optimization | Event telemetry | Logs guide opened, node visited, drop-off, completion — feeds the impact dashboard. |
| Impact dashboard | Correlates guide usage with resolution metrics — makes ROI obvious to exec sponsors. | |
| Automation & adoption | In-product coach marks | Walkthrough overlay teaching analysts to launch and use guides — accelerates front-line uptake. |
| Template gallery | Pre-built flows for common scenarios — jump-starts adoption for new customers. | |
| Governance & security | Role-based access controls | Separate creator, approver, publisher roles — meets enterprise IT policies. |
The build: a team of 2 engineers, 1 designer, 1 PM, and 1 data scientist, on a 6–8 month timeline — clusters sequenced across ten sprints (ingestion & authoring first, then in-console guidance, insight, adoption, governance), each with its own integration-and-test block.
Business model
Why the price holds up: an AP clerk's fully loaded cost is ~$50K/year; a 30% efficiency gain is $15K of annual value per user. At $100/user/month ($1,200/year) the customer sees roughly 12x ROI, and the reduction in exception-resolution time pays back in under 6 months. Positioning: below enterprise platforms that demand heavy implementation (ServiceNow, Pega at $100–150), above basic knowledge tools that lack procedural workflow (Guru, Notion at $10–30), comparable to specialized workflow tools (Tonkean) — the mid-market sweet spot.
Market size
How success is measured
Improved ISR reflects gains across four dimensions: accuracy (analysts correctly identify the invoice's issue), procedural compliance (they follow the right steps to fully address it), consistency (new analysts deliver the same quality as veterans), and vendor satisfaction (fewer invoices stuck in the works, fewer escalations delaying payment).
Around the north star, a constellation of supporting metrics:
- Escalation volume — quantifies consistency improvements for guide-adopted cases.
- Analyst onboarding time — the OpEx lever; target an industry-based decrease.
- Guide completion rate — leading indicator of analyst satisfaction; target 90%.
- Average handle time — a guard-rail, not a goal: don't lengthen it beyond ±10%.
- Days payable outstanding — proves customer value; target −20–30%, industry dependent.
Research & validation approach
Discovery — develop the hypothesis. Interviews with 8–10 people across the chain: AP clerks on daily frustrations and time spent searching, AP managers on error rates and training gaps, controllers on business impact. Analyze existing data — exception rates, resolution times, "ask a senior" moments in tickets and Slack. Shadow AP teams to map the current state: where do they search, how long does it take, which exception types recur.
Validation — refine the solution. Show wireframes to 5–6 AP users, build 2–3 prototype workflows for the highest-frequency exceptions, and measure: time saved? increased confidence?
The key questions to answer before building: are 70%+ of exceptions truly procedural (documentable)? Would users adopt this over their current methods? What's the minimum feature set that delivers value?
Deployment & growth
| Stage | Coverage | North star expectation | GTM motion |
|---|---|---|---|
| Pilot — lighthouse customers | Top 3–5 complex intervention drivers | 20% ↑ ISR for guided issues | 1:1 support; PM + design-led rollout; feedback loop launched |
| Expansion in same tenant | >50% of intervention cases have a guide | 15% ↑ overall ISR across the team | Internal case studies; ops teams request new flows |
| Mature deployment | >80% of procedurizable interventions | Sustain 15% ↑ ISR, AHT flat ±5% | Org treats flows as truth; customer becomes reference |
| Adjacent orgs via referral | First flows in new use cases | Pilot-level gains on new topics | Land via playbook; training kits; PM-led onboarding |
| Maturation & revenue | Varies by org maturity | — | Commercial packaging; ARR expansion; CS-led onboarding |
Target customers, in priority order: mid-sized enterprises with high AP intervention rates; industries with long tool-onboarding times and complicated knowledge networks (insurance claims, mortgage approvals); companies struggling with knowledge-management rollouts; enterprises with no knowledge-management owners — then land-and-expand.
Risks & assumptions, stated out loud
| Assumption | If false, the risk is… | Mitigation |
|---|---|---|
| Customers know which intervention types to start with | Slow time-to-value; teams pick low-impact use cases | Starter playbooks; recommend top 5 exception types; PM support for first rollout |
| Flow rollout leads to measurable ISR improvement | No uplift; tool seen as unnecessary overhead | Match guides to real behavior; validate via audits; measure guided vs unguided |
| More steps = better support | AHT increases; analyst frustration; adoption drops | Progressive disclosure; test flows with analysts; optimize for resolution |
| Pilot org will organically champion expansion | Momentum stalls post-pilot | Secure exec sponsor before pilot end; build the case study |
| Internal teams will prioritize this product | Delays from competing priorities | Align with the platform roadmap; position as a revenue driver |
Wrap-up
- The pain is clear. Analysts and finance teams lose when procedures are scattered; when interventions fail, businesses pay in errors and delays.
- The solution is evident. Live, clickable, AI-generated, human-edited flows meet analysts where they work.
- Measurement is simple. ISR lift, procedural compliance, and friction reduction — all visible within 30 days.
- Deployment follows the playbook. Pilot → expand → mature → GA, with built-in telemetry, feedback loops, and governance.