What she does, and what she doesn’t.

Both lists, on one page, because the second one is the one that tells you whether to believe the first. If you ask her for something she can’t do, she’ll say so straight away rather than ask you three questions and then let you down.

Ask her for these

  • “Draft a quote for the Wilson job.”

    She writes it in your voice, reads it back, and nothing goes out until you say so.

  • “Follow up with Dave about that quote.”

    She drafts the email and reads it to you. If she does not have his address she asks for it rather than guessing.

  • “Remind me to chase the council on Tuesday.”

    Set against your own working week, and she raises it with you when it comes around.

  • “What’s in the bank?”

    Balance on each account and the total, read out of Xero once you have connected it. She reads only — she cannot move a cent, and she cannot see your bank directly, only what your bookkeeping says.

  • “Who owes me?” · “What do I owe?”

    She reads it straight out of your accounting system and tells you — how much is outstanding, how much of it is overdue, and who the oldest ones are. She reads only; she cannot move a cent.

  • “Did that quote ever go out?” · “Anything waiting on me?”

    She tells you what she has drafted, what is waiting on your go-ahead, what has already gone, and how long each has been sitting. Keeping that list is her job, not yours.

  • “What did we agree with the surveyor back in March?”

    She remembers what you have told her and searches the documents you have given her, and tells you where the answer came from.

  • Nothing at all

    She chases an invoice that has gone past thirty days, follows an unanswered quote, and flags an insurance or licence about to expire — checking each is still true before she acts.

She can’t do these

Not “not yet, ask us nicely”. There is no setting that turns these on, and where something genuinely is coming, it says so.

  • Talk you through your profit and loss

    She can reach the report and currently reads only the income line out of it, which is half an answer and worse than none. Until she can give you the whole picture she will not pretend to.

  • Move money

    No payments, no transfers, no card. She can read your accounts and cannot change them by design — not by a setting we could switch on tomorrow.

  • Raise or send an invoice

    She can write the email about one. Creating it in your accounting system is not something she does.

  • Touch your bank, your calendar or your job software

    She connects to Xero and, if you let her, your Google Drive and contacts — you choose which, and you can see and revoke each one in Settings. She has no link to your bank itself, cannot see your diary, cannot book anything and cannot move a job.

  • Order materials or make bookings

    She can draft the message asking someone to. She cannot place the order herself.

  • Send anything without you

    This one is deliberate and it is not adjustable. Everything she writes is read back and waits. A wrong quote that goes out is worse than a slow one.

  • Listen in the background

    She hears you only when you open a conversation and press the button. Waking on her name, with a pause you control, is on the roadmap and is not built — you should know exactly that before you say a word to her.

  • Learn a new trick because you asked

    If you ask for something she cannot do, she says so and writes it down, and that list decides what gets built next. She will not promise to come back to you about it, because nothing yet would.

If you’re introducing a client

You’re reading the same list your client will. What you’ll also want is what holds each limit in place, because “we wouldn’t do that” and “it cannot do that” are different promises.

She cannot change anything in your client’s accounts.

What holds it: The connection is read-only in the code that carries it, not in a permission that could be widened. Adding a write would mean rewriting that module.

Nothing is sent without your client’s approval.

What holds it: Drafting and sending are separate steps with separate calls. There is no configuration in which drafting sends.

You see progress, never their conversations.

What holds it: Your dashboard reads through a database function that cannot select the content columns — a property of what your role can query, not a promise we observe.

If she cannot do something, your client is told immediately.

What holds it: She states the limit before asking anything else, then records the request. She is instructed never to say she will follow up, because no mechanism would.

If there’s something you’d want her to do that isn’t on the first list, tell her anyway. She writes it down, and that list is what decides what gets built next.

See what your business is worth →
Report a problem