Avota Start free Sign in

For distributors, manufacturers and wholesalers

Your system already knows when something went wrong.

It should be the thing that asks. Not a spreadsheet upload, not a survey every Tuesday — a question after the order closed short, the invoice finally cleared, or the quote went to somebody else.

Start free — 21 days See exactly what we'd read Read-only. Nothing installed in your ERP.

Why timing beats frequency

A survey on a schedule asks a question nobody was thinking about.

Send it on the first of the month and you get a shrug. Send it four days after a shipment arrived two weeks late and you get the truth, in detail, from someone who still remembers the part number.

The moments that decide whether somebody keeps buying from you are already recorded in your system: an order finished, an invoice cleared, a return resolved, a quote lost. Nothing else reads them.

The moments

Ask after these, not on a calendar.

WhenWhat you learn
An order closes outWhether the thing they bought actually did the job
An invoice clearsWhether the whole transaction went smoothly, paperwork included
You lose a quoteWhy they went elsewhere — almost nobody asks this, and it's the most useful answer you'll get
A first order landsWhether a new relationship started well, while you can still fix it
A return is resolvedWhether you actually made it right, or just processed it

You choose which of those fire, and how long to wait after each. We read your account first and tell you how many that would be a month — using your numbers, not a benchmark.


Three problems specific to your business

Things a general survey tool gets wrong.

Problem one

Your accounts aren't equal, and averages hide it

The median account is small and one is often a quarter of the business. Count them as one vote each and you get a number that describes nobody. Avota ranks by what you're willing to tell us — your own A/B/C tiers, how often they order, or revenue if you'd rather.

Problem two

Your system doesn't know who bought anything

On the first real ERP we connected, 97% of orders carried an email address — and 77% of those were the company's own staff. The rest were shared accounts-payable inboxes. Build the obvious thing and you email your own accounting department. We don't use that field, and we tell you why using your figures.

Problem three

An account isn't one person

A buyer, a maintenance lead, a plant engineer and a controller all have different opinions and only one of them signs the PO. Scores roll up to the account, and the screen tells you when you've only heard from one voice — which is not the same as good news.

And the guardrail

Your accounts order constantly

A good customer might order 30 times a year. Ask every time and you've trained them to delete your emails. Each person hears from you once every six months, however much they buy — and we simulate every rule against your history before it can be switched on.


Connecting

Twenty minutes, and nothing goes into your ERP.

  • Your admin creates a read-only role and an integration record, then pastes two values. No bundle to install, no scripting, no consultant, nothing running inside your system.
  • Revoke it in one click, from your side, whenever you like.
  • We read about eight fields. The list is published — check it against what you'd actually be granting before you grant anything.
  • We never need your sales figures. If you'd rather not share amounts, ranking uses your own account tiers or an order count instead, and nothing about what customers spend leaves your building.
  • Then we read your setup and fill the form in — the moments worth asking about, the monthly volume, and the rules we refuse to build, each with your own numbers explaining why.

NetSuite today. Front for working out which human to ask, if you use it. A spreadsheet works too.