A team you recruit, not software you switch on.
Handley fronts a pod of six specialists. Each one is hired like a staff member: a written charter, training on your business, a probation it has to pass, and your sign-off before it touches live work.
Why “Handley”
Named for the conductor.
Picture a conductor in front of an orchestra. Every section - finance, sales, inventory, the bank - plays its own part, and instead of music it is data flowing. Together, played in time, it is a coherent thing of beauty. Apart, it is a squawk of noise.
That is what a good ERP does: it is the conductor that keeps every part of the business playing from the same score, on shared data. It is why our front door carries a conductor’s name, and why the Handley mark is a conductor’s baton meeting the hand that holds it. Handley plays no instrument. It stands where everything meets, sets the tempo, and brings each specialist in at the right moment.
And the baton waits for your downbeat. Nothing consequential starts until you say go.
The orchestra
Your business, playing in Business Central.
The sections
Debtors, payables, sales, bank, ledger - each with its own specialist.
The conductor
Handley, keeping every part in time.
The music
Your data, resolved into one clear score instead of noise.
The downbeat
Yours. Nothing starts without it.
How an agent is hired.
1
A written charter
Every agent runs from a written job description and charter: what it does, what it must never do, and when it stops and asks. Changing that charter is treated as a control change, with your approval.
2
Training
It learns your rules, your policies and your configuration - not a generic version of them.
3
Probation
A 60-day shadow run: the agent proposes, a person approves, and every decision is scored before it earns any autonomy.
4
Your sign-off
You approve each hire before it starts, with a defined, ring-fenced role and the least access its job needs.
Autonomy is earned, measured and revocable. If an agent’s judgement drifts, its autonomy is wound back - and one command halts the whole pod.
The specialists.
The front door
Handley
The one you talk to, in Microsoft Teams. Handley routes each request to the right specialist, schedules the work, and brings the pieces back as one answer with the evidence attached. It routes; it does not decide - anything consequential lands with you.
If Handley cannot tell with confidence who should own a request, it asks you. It never guesses.
Business Central expert and team lead
Sam
The technical authority on your Business Central estate: every extension, every posting routine, every place standard behaviour has been bent. Sam answers from your actual configuration and cites the object behind the answer - and when your team needs to learn a process, walks them through it on your own setup, then writes the SOP.
Sam’s standing rule is source over memory: “BC does X” means verified in your environment, and “I have not verified that here” gets said out loud.
Debtors and credit control
Ava
Collects what is genuinely owed, as early as reasonably possible, without damaging a relationship worth more than the invoice. Aged AR watched every working day, a chase queue ordered by expected recovery, promises-to-pay followed up the day they break, and credit holds applied early and quietly - released only by a person.
Ava diagnoses before she duns: before any reminder she re-checks delivery, disputes, credit notes and cash applied in the last 48 hours. Chasing money already paid is a small betrayal, and she does not do it.
Sales ops and credit guard
Quinn
Turns interest into accurate, credit-checked quotes and clean orders. Every quote carries live price, real availability and its margin - and exposure is checked at the quote, before the stock is committed. Quinn prepares the credit case; Ava assesses the risk; a person decides. The one who earns the revenue never approves the credit.
A quote is a promise: price, availability and lead time are validated live before it goes out - never from yesterday’s numbers.
Accounts payable
Jade
Pays the right supplier, the right amount, once, on time - and can prove every part of that sentence. Three-way matching, duplicate detection, tax treatment validated for NZ and AU, early-payment discounts captured before they expire. Jade prepares the payment run; a person releases it, always.
Urgency raises Jade’s scrutiny - it never lowers it. And no request, however convincing, gets her to touch a supplier’s bank details: she cannot, structurally.
Bank rec and cash
Riley
The pod’s early-warning system. Every account imported and reconciled daily to the bank’s closing balance, receipts matched to the right invoices, released payments confirmed cleared, and a daily cash position published. Fraud, duplicates and failed payments show up in the bank line first - and Riley is watching it.
Riley never posts a plug to make a reconciliation balance. And a payment in the bank with no approved run behind it is not a reconciling item - it is an incident, escalated to you immediately.
Financial control
Margot
Owns the ledger, the month-end close and the numbers the business acts on. Every balance-sheet account reconciled to evidence, accruals and cut-off done properly, GST and BAS returns prepared and reconciled to the ledger - and a person authorises and lodges. When a director or an auditor asks “is this right?”, Margot’s job is to show exactly why.
Margot holds the line between convenient and correct: a number that is fast and wrong is worse than no number, because people make decisions on it.
Handley teaches your team BC.
Ask “how do I run a bank rec here?” and Sam walks your team through it one small step at a time, on your live system and your own configuration, then writes the process up as an SOP. Most tools do the task and leave your people no wiser. Handley builds capability, not dependency.
The pod grows as you do.
Same operating model. New specialists join the same way, one at a time: charter, training on your business, shadow-run probation, your sign-off.
Nothing changes for you. You still talk to Handley; the new specialist simply starts appearing in the answers.
Sharper over time. Corrections are captured as durable lessons, so the pod improves case by case instead of repeating mistakes.
Start with one agent and add the rest when they earn their place.
See Handley on a Business Central scenario.
Book a demo and watch the team work a real scenario - aged AR, an over-limit quote, a bank rec - and see exactly where you stay in the seat.
Book a demo