Escargo Growth
Most software asks you to take its word for it. Escargo records how your operation runs when you go live, then shows you the same numbers again at 30, 60 and 90 days — and tells you where each one came from.
Your Growth data is yours. It is visible only to your own business inside Escargo.
A baseline is a snapshot of how the business is running at or around go-live. It is captured once and kept. Later measurements are compared against it — they never rewrite it, because a starting line that moves makes every comparison meaningless.
| Metric | Where the number comes from | What that means |
|---|---|---|
| Jobs and completed jobs | AUTOMATIC | Counted from the jobs actually processed in Escargo. |
| Bookings and no-shows | AUTOMATIC | Counted from your booking diary, including the ones that did not turn up. |
| Invoices issued and average invoice | AUTOMATIC | Taken from issued invoices. If you have not issued any yet, this stays unavailable rather than showing zero. |
| Booking lead time | AUTOMATIC | The gap between taking a booking and the booked date. |
| Review count and score | AUTOMATIC | Published reviews on your Escargo profile. |
| Missed enquiries | UNAVAILABLE | Escargo cannot see a call nobody answered. You can tell us your own figure, and it stays marked as yours. |
| Estimate approval rate | UNAVAILABLE | Approval outcome is not yet recorded against each estimate. |
| Technician and bay utilisation | UNAVAILABLE | Needs labour time measured against real capacity. |
| Parts margin | UNAVAILABLE | Needs cost price on the parts a job consumed. |
| Payment time | UNAVAILABLE | Needs settlement dates against invoice dates. |
| Anything you supply yourself | CUSTOMER ENTERED | Stored as yours. Escargo will not quietly turn it into something it measured. |
Unavailable means unavailable. Where Escargo genuinely cannot see something, it says so rather than showing a zero that looks like a measurement. Several of the numbers a garage most wants are in that column today, and we would rather name them than quietly leave them out.
30 days — adoption. Is it actually being used? Setup finished, staff working in it, jobs going through, modules switched on.
60 days — operating. How the work is moving. Throughput, approvals, payment behaviour, where things are getting stuck.
90 days — comparison. The measured metrics against the baseline, over the same length of window on both sides.
A review that cannot be made yet returns insufficient data and says how long is left. It does not compare a full baseline window against a few days of activity and call the result a decline — and it never returns improved because it had nothing to compare.
We will not tell you Escargo increased your revenue by a percentage, because we have not measured that across enough businesses to say it honestly. We will not turn a number you typed in into something we measured. And we will not publish your results as proof to anyone else unless you have seen them and agreed.
