Client portal
What you see once it is running.
Every build comes with a weekly report and an owner's queue. This is the shape of both, on sample data, before you commit to anything.
Clients sign in at portal.echelon-advising.com.
The weekly report
Four lines, every week.
The same report on every install. It is how you know the system is doing the work, and how we know when to improve it.
- 01What ranEvery action the system took this week, by module, with a count. Nothing is summarized away; each line links to its record.
- 02What it handled aloneActions inside the narrow authority you granted. Routine, proven, inside limits, and never moving money.
- 03What waits on a decisionAnything above an approval gate sits here until a person clears it. The usual failure is work waiting, not work sent.
- 04Who owns itA named owner on your team for every system and every open decision. Nothing runs without one.
Weekly report
Sample data212
Actions this week
- Handled alone184
- Waiting on a decision6
- Escalated to a person3
- Owner: sales leadNamed
Sent every Monday. Every line opens to its record.
The owner's queue
Everything waiting on a person, in one place.
Consequential actions wait for a decision. The queue shows each one, who owns it, and how long it has been waiting.
Owner's queue
Sample data6
Waiting on a decision
- Quote for a three-site rolloutApproval
- Refund request on invoice 2291Held
- Clinical question from a callerEscalated
- Reply to a lead aged 14 daysApproval
- Reschedule a no-showApproved
Approve, edit, or hold. Money never moves from here.
Each item shows the event that triggered it, what the system prepared, and the approval that sits above it. The owner clears it in one step, edits it first, or holds it.
Anything that touches money, a sensitive decision, or a person in distress escalates to a named owner every time. That boundary is set in writing before launch and does not widen on its own.
The consoles on this page are mockups on sample data. Your queue shows your systems, your owners, and your boundaries.
Also in the portal
The map, the record, and the agreement.
The system map
What each system reads, what it does alone, where it stops, and which approval sits above each action.
The record
Every action leaves a record you can open: the event that triggered it, what the system prepared, who approved it, when it went out.
The agreement
The scope, the set price in writing, the acceptance criteria, and the separate monthly line for ongoing operation.
Your first department
Bring the process you still run by hand.
One mapping call. You leave with the system design, the price in writing, and the date it goes live. The first build lands in two weeks.
The process
See how a system gets to the weekly report.
Six steps from the mapping call to a system running in production, with the output and the control at each one.
How it works