End-to-End Flow
Solvren presents a simple product experience while preserving a full revenue protection engine underneath.
1. Setup: connect systems and invite people
Start in Setup. Connect systems such as Stripe, Salesforce, HubSpot, Jira, GitHub, NetSuite, Snowflake, BigQuery, PostgreSQL, or MySQL. Invite decision makers and configure security, access, rules, and license scope.
2. Problems: find revenue risk
Solvren watches connected systems for problems such as billing mismatches, CRM routing failures, integration drift, failed automation, or revenue workflow gaps.
3. Decisions: make the next action obvious
The Decisions area combines approvals, assigned problems, missing proof, overdue work, and system follow-up. It is the short list of what a person should do next.
4. Change review: protect risky changes before they ship
Revenue-sensitive changes have a plain-language decision page:
- What happened?
- Why does it matter?
- What should happen next?
- Who owns it?
- What proof exists?
Technical logs, source signals, scoring details, and audit records remain available in details sections.
5. Proof: show the value
The Proof area brings together revenue protected, risks prevented, decisions accelerated, incidents avoided, outcomes, reports, and executive proof packets.
6. Safe automation and verification
Where enabled, playbooks can recommend, simulate, or execute actions through governed write-back. Verification checks outcomes using system data and attributes recovered revenue or avoided loss.
What Changed From Earlier Docs
Older Solvren docs may describe the product primarily as a pipeline: signals -> detectors -> issues -> actions -> verification -> ROI.
That pipeline still exists, but it is now surfaced through the simpler app model: Home, Decisions, Problems, Proof, Setup.