Most of our Devonport engagements start the same way: a 20-minute call where the owner describes a workflow we've heard before in shape but never in detail. AI content generation is then designed against the detail, not the shape.
Built and supported here - the way a Devonport business would actually use it.
What AI content generation actually does
A content engine trained on your voice, not generic SaaS-speak. Service pages, blog posts, social captions, and email sequences that sound like you wrote them at 2am - but didn't.
- 01 Voice and tone trained on your past content
- 02 Built-in NZ-specific spelling, terms, and slang
- 03 Auto-publishes to your CMS, scheduled across channels
- 04 You approve before anything goes live
Built on: Claude Vercel AI SDK Sanity Buffer Ghost
Without Koala Dynamics
With Koala Dynamics
Where Devonport operators actually lose hours.
- Devonport is the freight gateway to Tasmania, where the Spirit of Tasmania sets the clock for a lot of local business.
- Ferry freight, agriculture, vegetable processing and logistics on the north west coast. Timetable-driven dispatch and customer updates are constant and still largely manual.
We work with teams across Devonport: Devonport CBD · East Devonport · Latrobe · Spreyton · Ulverstone.
Talk to us about this →
How we build AI content generation for a Devonport team.
We scope narrow, ship a working pilot, then harden it into production. The first slice is the highest-leverage workflow for your Devonport business, so value lands before the build is finished. AI content engine.
Talk to usThe outcome for Devonport teams
The shape of the result for Devonport teams: Publishes 4x more content per week without adding headcount. Built on Claude, hardened with the rest of the stack as it scales.
Not your typical AI agency.
Honest about what AI can and cannot do
Ships the one workflow that pays for itself
Hours given back, never the size of the invoice
*Every engagement is scoped and quoted up front. Results vary by workflow and business.
FAQ
What's a typical engagement length for Devonport businesses?
Six to twelve weeks for the build, then a short managed-services month while the system goes from "shipped" to "owned by your team". After that you keep us on retainer if you want, or take it from there yourself.
Are there hidden costs we should plan for?
Three to know about: model/API spend (which we set up under your own account, not ours, so you see and control it), any new SaaS subscriptions we recommend, and your team's time during rollout. We surface all three in the quote so there are no surprises.
Can you walk us through a comparable build?
Yes - on the first call we'll pick the closest engagement we've shipped to what you're describing and walk through the outcome, the headcount and the time it took. Publishes 4x more content per week without adding headcount.
Can you work with our existing systems?
Yes. The default AI content generation stack we reach for is Claude, Vercel AI SDK, Sanity, Buffer, Ghost, but we'll bend it around whatever you already run - Xero, HubSpot, Shopify, Cin7, your own in-house apps. The discovery week maps every data source before any build starts.
Skip the pitch.
Tell us the workflow and we'll come back with what we'd build first.
Talk to us about this
Tell us what you're trying to do and we'll reply with how we'd build it - no obligation.