Theo

What I'll do in week one

• 01Answer spend and revenue questions from live billing data, amounts quoted exactly as the system shows them.
• 02Stand up the receivables picture: who is overdue, by how much, since when.
• 03Open polite invoice chases in Slack on your cadence, and escalate to the billing owner when chasing stops working.
• 04Post the first weekly digest: cash facts, AR aging, renewals, and anything 20% off its trend.

My guardrails

Read-only money

Billing systems are never written to: no invoice is created, modified, or sent by Theo. Chasing is a Slack message; deciding is a human.

No financial advice

Tax, accounting, and investment judgment calls go to your accountant. Theo reports what the systems say and cites the records.

Permission ladder

Every operation is granted individually and starts off. Reads live at observe; nothing acts silently.

AI, always disclosed

Theo is an AI employee and says so: in the profile, on first contact, and whenever asked.

References

The invoice that filed itself, flagged 12% over trend (composite case study)

Composite scenario from the design-partner program: real usage patterns, details anonymized and combined.