Copilot vs Autopilot: how much control should you give AI over your money?
An AI that can chase, call and negotiate your overdue invoices sounds like a lot to hand over. The honest answer is that you should not hand over all of it at once. Here is how we think about control, and why co-pilot is the setting we recommend.

The real question is not "can AI do it?"
AI can already run your credit control. It can read every customer, write a chase that sounds like you, send it at the right moment, and pick up the phone when email is ignored. The technology question is basically settled.
The interesting question is a different one, and it is the one that actually keeps owners up at night. Not "can it do the work?" but "how much of this should I let it do without me?"
Money is not a low-stakes place to experiment. A chaser sent to the wrong customer, or in the wrong tone, is not a typo you can quietly delete. So the design problem is not really about intelligence. It is about control, and giving you a way to turn it up only as fast as you trust it.
That is why Penny runs in three settings, not one.
Three levels of trust
Think of it as three seats, from fully hands-on to fully hands-off.
- Sandbox. Penny connects to your real ledger and watches. She works out exactly who she would chase, what she would say and when, and shows you, but she sends nothing. Zero messages leave the building. It is a live rehearsal on your actual customers, with the risk turned off. This is where everyone starts.
- Co-pilot. Penny does all the work and stops just before the send button. Every message is drafted, every call is queued, and nothing goes out until you approve it. One tap to send, one tap to change it. You get the leverage of a full-time credit controller and keep the final say on every word.
- Autopilot. Penny runs the whole sequence herself, within the rules you set. She chases, escalates, sends pay links and calls on schedule, and only comes to you for the things that genuinely need a human. Hands off the wheel, but never off the rails.
Why co-pilot is the sweet spot
If you take one thing from this piece, it is this: start in co-pilot, and most businesses should stay there longer than they expect.
Co-pilot is the setting where the trade-off is best. Here is why.
You get almost all of the time back. The hard part of chasing was never clicking send. It was knowing who to chase, on what day, in what tone, and finding the will to write it. Penny does all of that. Approving a ready-to-go message takes a couple of seconds, and you can do a week's worth over a coffee.
But you keep your judgement in the loop. You know your customers in ways no ledger does. You know the one who always pays but hates being nudged, and the one whose "cheque is in the post" means nothing. Co-pilot lets Penny do the labour while you apply that context, on the rare occasions it matters.
It is also how you build real trust. Watching Penny draft dozens of chases, and agreeing with almost all of them, teaches you far more than any settings page. You learn where she is brilliant and where you would tweak, and you move to more autonomy because you have seen the evidence, not because a toggle told you to.
And it means the odd strange case never slips through. Most invoices are routine. A few are not: a part-payment, a quiet dispute, a customer going through something. A human glancing at the queue catches those in a second. That one catch a month is worth the couple of seconds a day.
Autopilot is something you earn, not something you switch on. Co-pilot is where you earn it.
When autopilot makes sense
None of this is an argument against autopilot. It is an argument for reaching it in the right order.
Autopilot earns its place once the volume is high enough that approving each message stops being a quick coffee-break job and starts being a chore, and once you have watched Penny long enough to trust her on the routine work. At that point, keeping a human in front of every gentle reminder is friction, not safety. The right move is to let the routine run itself and reserve your attention for the exceptions.
Crucially, autopilot is never a free-for-all. It runs inside the rules you set and hands anything sensitive straight back to you. It is delegation, not abdication.
The control you keep at every level
Whichever seat you are in, some things never get automated away:
- Your rules set the boundaries. Payment terms, chase cadence, tone, quiet hours and limits are yours to define, and Penny works inside them.
- Sensitive moments always come to you. If a customer claims they have already paid, or raises a dispute, Penny stops and flags it. She never argues about whether money has changed hands.
- She reads, she does not reach into your bank. Penny works from a read-only view of your accounts. She never moves money or alters your ledger.
- You move at your own pace. You choose when to graduate from one setting to the next, and you can step back at any time.
Start in the passenger seat
The best way to trust an AI with your money is not to read a promise about it. It is to watch it work on your real business with the stakes turned off, then hand over the routine one tap at a time.
So Penny starts in sandbox, shows you exactly what she would do, and moves to co-pilot when you are ready to let the first messages fly, with your approval on each. For most businesses, that co-pilot seat is not a stepping stone to somewhere better. It is the destination: the full leverage of an AI credit controller, with your hand still resting on the wheel.

Stop chasing. Let Penny do it.
Penny reads each customer, sends the right message, and calls the ones who ignore it, so you get paid faster without the awkward admin.