Work and proof
Avenvero is a new studio, so there are no client case studies here yet. This page shows what you can check today, and what a case study has to pass before it appears.
What you can check today
None of this asks you to take our word for it.
The software, on sample data
Interface examples for each service: a job tracker, the intelligence portal, an integration monitor and a data assistant.
See the softwareA full sample audit report
Written for a fictional machining business, so you can judge the depth of the work before paying for one.
Read the reportOur written commitments
How we access your systems, what we never do with your data and what you own at the end.
Read the commitmentsThe person who builds it
On the first call you talk to the engineer who would scope and build your system.
Meet the studioHow a case study gets published
The same five steps for every client, so a result here means the same thing each time.
Agreed first
A client says yes at kickoff or at acceptance, and chooses to be named or anonymised.
Measured before
We record the starting point before anything changes.
Measured after
The same measures, taken the same way, about 30 days and about three months after handover.
Approved word for word
The client approves the headline, every figure, every quote and any image. An edit means approval again.
Published here
A client can withdraw approval later, and we take the case study down.
What a case study has to pass
Every case study shows
- The situation, in the client’s words
- What we built, on which systems, and how long it took
- A before-and-after table, measured the same way both times
- How and when the figures were measured
- The date the client approved the text
You won’t see here
- A logo or name used without written permission
- A figure the client hasn’t confirmed
- Estimated savings presented as results
- Sample data presented as a client’s
- Invented or composite clients
The first case studies will come from founding clients
Founding clients get design-partner terms on their audit and first build, in return for a case study they approve and an occasional reference call.
Have a problem worth building software for?
Start with a free 20–30 minute discovery call with the engineer who would build it. If there's no project worth doing, we'll tell you.
On the call
- The problem that costs your operation most
- Your ERP, databases and spreadsheets
- Whether a fixed-fee audit makes sense
- A straight answer, even if it is no