The moment this becomes a problem is when a new hire or a once-a-quarter traveler sits down to submit expenses after a trip and has no memory of how the approval chain works, where to attach receipts, or what the mileage policy says. They either give up, submit it wrong, or pull in the finance team to walk them through it — every time.

The gap persists because the vendors building these tools are primarily selling to finance teams and CFOs, not to the employees who actually submit. The buyer gets a feature list and a negotiated contract; the end user gets a help center. There's no commercial pressure on the vendor to make the submitter's experience smoother because submitters don't sign the renewal.

What currently exists inside these tools are static tooltips and documentation links — not context-aware guidance that reacts to where someone is stuck. Users explicitly complain about needing 'more in-platform guidance or tooltips' and finding 'complex interface for new users' with no graceful ramp-up. The mobile experience compounds this: 'basic and lacks many options,' making it worse precisely when people need it most, immediately after a trip.

This is a business and not a feature because no expense vendor will build a genuinely good submitter experience — it would require admitting the core product is confusing, and it doesn't move their enterprise sales metrics. Companies pay for this gap in hours of finance team handholding, submission errors that require reprocessing, and policy violations from employees who guessed wrong. That cost recurs with every new hire and every infrequent user, forever.

What to build

Build a browser extension and mobile companion that sits on top of any major expense management tool and injects step-by-step, policy-aware submission flows — pulling the company's actual expense policy rules via admin setup and surfacing the right next action based on what the user is looking at on screen.

Where to start

Start with Amadeus Cytric specifically, which has the most complaints about new-user complexity and is heavily used in corporate travel programs where infrequent submitters (road warriors who travel quarterly, not weekly) are common — the pain is most acute and the customer segment is large enough to sustain early revenue.

The hard part

Getting screen-level context reliably across multiple expense platforms without each vendor breaking the extension through UI updates is a continuous maintenance burden that scales with how many platforms you support.

How it makes money

Charged per employee seat annually, billed to the finance team's budget; pricing scales with headcount tiers, with a one-time setup fee for policy ingestion and admin configuration.

See the evidence. The complaints behind this idea, the products they came from, and similar ideas in Expense Management.

More ideas in Expense Management