Things we learn while shipping.
Field notes from real client builds. No ten-step listicles, no thought leadership. Just what we figure out as we ship — and what it means for people running businesses in Australia.
Why we don't bill by the hour, and what we charge for instead
Most agencies bill by the hour. The problem is that model rewards slowness and punishes expertise. Here is how we price our builds, why the retainer model is better for both sides, and what the 12-month maths actually looks like.
Roster-aware voice agents: why it changes everything for service businesses
Most AI receptionists are built on static knowledge. If yours does not know who is on shift today, it cannot actually book the call. What we learned wiring live roster data into the Bodyline build — and why this one feature separates a real system from an expensive demo.
Tiered approval: the autonomy dial nobody talks about
Full automation sounds great until the bot sends the wrong thing to the wrong person. How we built a three-tier approval system for JMJ Homes — and why starting conservative and earning autonomy over time is the only way to deploy AI ops that actually sticks.
How we ship a working system in 5–12 days
It is not a guess and it is not aspirational. Here is exactly how the 5–12 day timeline breaks down — phase by phase — and why the discovery period is where the real work happens before a line of code gets written.
The honest discovery call: why we sometimes say you don't need this yet
Some businesses are not ready for automation. The process is too immature, the volume too low, or the problem is actually a people issue not a systems issue. Selling them a bot anyway is how you build a business that churns. The questions we ask to spot it early.
Posts are scheduled.
We write when we have something to say. Sign up and get new posts delivered when they go live — no newsletter cadence, no filler.