Whatever trade you’re in, connect the AI you already pay for and hand it the paperwork. Invoicing the backlog, chasing what's owed, writing the quote, opening the callback — the jobs that eat your evenings, done by asking.
Nobody forgets to invoice on purpose. It loses to a no-cool call at 4pm, and then it's Friday, and then it's next month. An assistant that can actually do the work — not just tell you about it — is the difference.
Where the hours actually go. One operator, one evening a week on invoicing and follow-up, is fifty evenings a year. That's the thing this replaces — not a report you could already run.
It matters most if you're on your own. A ten-truck shop has a dispatcher and a bookkeeper. A two-truck shop has you, at nine at night, with a shoebox.
Name it something you'll recognise later, like "Claude on my laptop".
The key can never do more than that person can. One made for a field tech sees their jobs and no financials.
Read-only answers questions and changes nothing. Run it that way for a week before you let it write.
Shown once. We store only a hash, so we genuinely can't show it to you again — lose it and you revoke it and make another.
Paste the server address and the key. In Claude that's Settings → Connectors → Add custom connector. Then start asking.
| Answers questions | What it tells you |
|---|---|
| get_today | Who's where, who's en route, what's unassigned |
| find_client | Search by name, phone or email |
| get_client | Full history, equipment, warranty status, balance |
| find_open_time | Real gaps in each tech's day |
| list_jobs | Filtered by date or status |
| get_money | Collected, outstanding, aging, who owes most |
| get_pipeline | Open opportunities, weighted, days stalled |
| get_cases | Rework and callbacks, cost, whose fault |
| get_unbilled | Completed work with no invoice |
| Does the work | What it actually does |
|---|---|
| invoice_unbilled | Invoices a whole backlog — previews first, always |
| invoice_visit | Invoices one completed visit |
| create_quote | Builds a quote and returns the customer link |
| record_payment | Logs a cash or check payment against an invoice |
| schedule_job | Books new work onto the board |
| reschedule_visit | Moves or reassigns a visit |
| create_client | Adds a client, and their first site |
| open_case | Opens a callback, linked to the job that caused it |
| add_opportunity | Adds work you're chasing to the pipeline |
| move_opportunity | Moves a deal a stage, with a note |
| add_note | Appends a note to a visit |
The write tools only appear if you switch on "allow changes" when you create the key. Read-only keys can't see them at all.
Reading your data is one thing. Creating invoices is another, and you should want to know exactly how it's fenced.
Your data goes to whichever assistant you connect, under your own account and your own terms with them. We don't route it through a model we chose, because we don't choose one.
Every key acts as a real person and inherits their permissions. A tech's key gets refused on revenue and pipeline the same way the tech is.
Settings shows what the assistant did and when. Revoke a key and it stops working immediately — no waiting, no support ticket.
Read-only is the default, and it's the right default. Start there for a week. Ask it things, see whether the answers match what you know. Turn on writes once you trust it.
Anything bulk previews first. Invoicing a backlog shows you the list and the total and waits. An assistant should never create twenty invoices on a maybe, and this one can't.
You don't need AI to use Everglow. Every shop on the platform gets this at no extra cost, and plenty will never switch it on. The board, the quotes and getting paid are the product. This is for the operators who want it.
Fourteen days free, no card, all 58 trades. Connect your AI in five minutes and hand it the invoicing.
Start free