Bondi field notes
Build the operation. Understand the tradeoffs.
Practical essays from product, engineering, security, delivery, and partnerships—written for the people who own the system after launch.
Why AI usage needs two wallets, not one disappearing balance
Separate monthly funded AI credit from customer-purchased balance to make consumption and expiry predictable.
A fair way to count multi-step automations
Why Bondi exposes Automation Runs while retaining action-level metering for per-item work, pagination, retries, and AI calls.
Choose the first modernization slice by risk, not by screen count
A bounded modernization project should prove data mapping, rule recovery, validation, and cutover—not merely reproduce UI.
The client system is bigger than the project board
A practical data model for agencies and service companies coordinating clients, briefs, production days, approvals, deliverables, and margin.
The customer should own the system—even when a partner builds it
A healthy implementation-partner model keeps account, data, subscription, and production authority with the customer.
Humans, portals, agents, and service accounts are different identities
A useful permission model distinguishes how people and machines enter an operational system and what each can do.