The rule
Every product decision about automation in Treepie comes back to one sentence: if a customer would find the error, somebody should see it first.
It is not sophisticated and it settles most arguments. It also explains a set of choices that otherwise look like missing features, and we would rather write them down than have them discovered as gaps.
Invoices assemble themselves; they do not send themselves
An invoice draft builds from delivered work and approved time. It is accurate more often than a hand-built one, because it is not retyped.
It still does not go out on its own. An invoice is the most-read document your company produces and it goes to the person who decides whether to keep paying you. The cost of a wrong one is a credit note and a small withdrawal from a relationship; the cost of a person looking is thirty seconds.
The assistant drafts; it never sends
There is no auto-send setting for the customer-facing assistant, and it is not a configuration we have chosen to leave off. It does not exist.
The same rule covers what it may state. It will not commit to a refund, a credit, a date or an exception — not because it could not produce the sentence, but because those are decisions and a decision needs somebody accountable. Where a customer asks, it hands over, by rule rather than by the model's judgement about whether it feels confident.
Approvals stay approvals
Access requests raise themselves and route to the right approver; they do not grant themselves. Automations propose themselves with evidence; they do not enable themselves. Leave shows its effect on delivery; it does not get refused by a system.
That last one matters more than it looks. A system that automatically declines leave because a project is tight would be efficient and would quietly teach people not to book time off. We show the consequence and leave it with a manager, because the alternative optimises the wrong thing.
What this costs
It costs demo appeal. "It sends the invoice automatically" is a better line than "it prepares the invoice and waits for you".
It is also, we think, the difference between software you can leave running and software you have to supervise. The automation people regret is rarely the kind that saves an hour. It is the kind that acted confidently on their behalf, once, in front of a customer.