Questions
What people ask before the mapping call.
Cost, time, data, control, and fit, answered the way we answer them on the call. If your question is not here, ask it on the call or text the number below.
01Cost and terms
One set price. Then a monthly line.
What does it cost?
We do not publish fees. After mapping you get one set price in writing, changed only by a scope change. Ongoing operation is a separate monthly line, disclosed with the build price.
What about our data and security?
Least access, every connection documented, sensitive data stays in your environment, and high-risk actions wait behind a person. We build to your security requirements and document every connection.
Do we end up dependent on Echelon?
You own the outcomes, the data, and the documentation. We run the system because that is what keeps it working, not because you are locked in.
Do we have to replace our tools?
No. We build into the CRM, inbox, phone line, and payment tools you already run. Nothing gets ripped out and nothing gets migrated.
What happens when it gets something wrong?
Consequential actions wait for a person, so the usual failure is work waiting, not work sent. Every action leaves a record, so we can show you exactly what happened and why.
How much of our team's time does this take?
A few hours a week during mapping, then far less. Your team keeps doing their jobs. The build happens around them.
We tried AI before and it didn't stick.
Usually that was a tool nobody owned. We name an owner for every decision, put approvals where they belong, and report every week on what ran and what is waiting.
Do you bill by the hour?
No. Hourly billing charges you for the builder's uncertainty. One set price for the build, in writing after mapping, means you know the number before anything is built, and it moves only if the scope does.
What is in the monthly line?
Hosting, monitoring, maintenance, the weekly report, and the next system built on the same layer. It is disclosed with the build price, runs month to month, and ends with thirty days' notice. No minimum term.
What changes the price after it is set?
Only the scope, and only in writing. If mapping finds the one process is really two, or you want a second system before the first is live, that is a scope change with its own price. Nothing gets absorbed silently.
What is the smallest engagement?
One process, one clear outcome. Usually it is inbound: the leads that go unanswered. The first working build is in your hands within two weeks, it goes live in weeks, and it gives you something real to judge us on before the next system.
Are we locked in?
No. Operation is month to month with thirty days' notice and no minimum term. If you leave you keep every outcome the systems produced, all of your data, and the documentation and runbooks.
02Time and process
A first build in two weeks. Launch in 30 to 90 days.
How long does it take?
The first working build is in your hands within two weeks, ready to test. From there it runs in review mode on real work while we make changes, and the sprint closes with a measured launch between day 30 and day 90, depending on scope. Your dates come in writing with the price.
What happens on the mapping call?
Bring one process your company still runs by hand. We map it with you on the call. You leave knowing what we would build, what it would cost, when the first build lands, and when it would go live. If we are the wrong fit, we tell you on the call.
How long before something works?
Two weeks. The first working build is in your hands by the end of week two, running in review mode on real events with your team approving every result. Then we make changes every week until launch, which lands between day 30 and day 90 depending on scope. Launch is the end of the build and the start of Echelon running it, not the first day something works.
What are the four stages?
Week 1: Map. The operating map, the baseline, the first system chosen by value, and the price in writing. Week 2: First build. The first working build, in your hands and ready to test: wired to the tools it reads, running in review mode on real events. Week 3 on: Review mode and changes. Real work, your team approving every result, a round of changes every week, and narrow authority earned one proven action at a time. Day 30 to 90: Launch, then Echelon runs it. A measured launch on the date agreed in writing, by scope. Then weekly reports, monitoring, and the next system built on the same layer.
What do we need ready before we start?
Not much. Mapping surfaces what we need. What helps: read access to the tools the process moves through, and the person who knows where the exceptions and the workarounds live.
What if we change direction?
Reordering what we build happens in the weekly review. A new system on top of the agreed scope gets its own scope and price in writing before it is built. That is how the price stays set and the launch date stays the launch date.
What happens after launch?
We stay on and run it. Hosting, monitoring, maintenance, the weekly report, and the next system built on the same layer. A separate monthly line, month to month.
03Data and control
Your environment. Your approvals.
Where does our data live?
In your environment and your accounts. Least access on every connection, every connection documented, sensitive data stays where it is, and high-risk actions wait behind a person. We build to your security requirements and walk through every connection before we touch anything.
What is review mode?
The system reads real events and prepares real work, and a person approves every result before it goes out. It is how the first system runs, and how every new action class starts.
What is narrow authority?
Routine actions that have proven stable in review mode start running on their own, one action and one channel at a time, inside written limits, with escalation rules and a full record. Never blanket autonomy. Never moving money.
Can the system move money?
No. Money waits for a person. The operations view is read-only on the money by design, and that does not change when other actions earn authority.
Is there a record of what it did?
Every action leaves a record: what came in, what the system proposed, who approved it, and what went out. When something needs explaining, we show you exactly what happened and why.
Does our data train your models?
Your data does not train our models or anyone else's, and it is never pooled with another client's. Per-client isolation is a build standard, not an upgrade.
04Working with Echelon
A direct line and a weekly report.
What does Echelon do?
Echelon builds and runs AI infrastructure inside established companies. We map how the work actually moves, build systems into the tools you already use, and launch them with approvals in place. Every build gets one set price, in writing, after mapping. Then we stay on and run it, and you own every result.
Who do we talk to?
The people on your build, on a direct line: Yadel, who runs the engagement and reads the weekly report with you, and the development manager who runs the pod day to day. There is no ticket queue between you and the person who can fix something.
Who builds it?
Yadel maps and runs every engagement. The build is staffed from Echelon's engineering bench: 100+ engineers, building since 2015, composed into a pod sized to your scope, from two engineers for a focused system to a full programme team. A development manager runs the pod day to day, on the same direct line as Yadel.
Can you take on something large?
Yes, in phases. Up to 20 to 30 engineers can work one programme, staffed against a written ramp plan with an architecture baseline agreed before the pods ramp. The first working build still lands in two weeks, and the first system is still live inside the sprint. Nothing is staffed all at once.
Do we meet the engineers?
Yes. The people on your build are introduced by name on the first call, and the development manager is on your direct line from kickoff. Credentials are given in aggregate on this site on purpose.
How do we reach you when something breaks?
On the same direct line. Alerting is wired to us too, so most issues are fixed before you notice. Every action leaves a record, so when something does go wrong we can show you what happened.
How do we know what the system is doing?
The weekly report: what ran, what it handled alone, what is waiting on you, and who owns it. Every decision that waits on a person sits in one queue with a named owner.
What if we want another system after launch?
That is what the operation line is for. The next system is scoped and priced in writing and built on the layer already in place, without starting over.
Who owns what you build?
Echelon builds and operates the AI systems we deploy for you. You license access to those systems for as long as we work together, and you retain full ownership of every outcome, result, and work product they generate: every lead answered, every quote sent, every dollar collected. We run the engine. Everything it produces is yours.
05Fit
Established companies. One process first.
Who is this built for?
Established companies, mid-market to Fortune 500, with working operations, too many tools, and a leader still routing work by hand.
Where do you start?
If your process still changes every week, we start by making it repeat. If the bottleneck is getting customers, we start with the system that answers and follows up with every lead. If nobody inside owns the work yet, we name the owner in the map. If one small tool already solves it, we tell you, and build what sits between the tools.
Do we have to be a technology company?
No. The system is built into the tools your team already runs, and your team keeps doing their jobs. Nobody on your side needs to understand how the models work to approve a result in the queue.
What if we are not sure a system is the right move?
That is what the mapping call is for. We map one process with you and tell you on the call what we would build and whether we are the right fit. If we are not, we say so on the call.
What if it does not pay off?
If at least one system we deploy does not measurably save time, reduce a cost, or support revenue, we keep working until it does.
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.
How it works
From the first call to a system in production.
The six steps, the sprint shape, and where we start.
See how it works