We've worked with enough operators in Quarry Bay to know that the brief that arrives in our inbox is rarely the brief that ends up shipped. The first thing we do on any AI content generation project is sit with your team for a day before we propose anything.
Built and supported here - the way a Quarry Bay business would actually use it.
Our goal is to give Quarry Bay businesses a three-day weekend, so people can spend more time with their families and the people they love :)
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 Kiwi Dynamics
With Kiwi Dynamics
What you actually get
Every engagement is scoped and quoted up front. This is what is in the box.
- A working pilot, in productionNot a prototype on someone's laptop. The first slice of AI content generation runs against real work within weeks.
- Your data stays yoursIt runs on your accounts and your tools. If we part ways you keep the system and everything in it.
- The workflow mapped before codeWe write down what good looks like for Quarry Bay businesses first, so nobody is guessing at handover.
- Support after it landsThe people who built it stay reachable when the business changes shape around it.
How AI content generation compares
The two things most businesses do instead, and where each one runs out.
| Hiring for it | An off-the-shelf tool | Kiwi Dynamics | |
|---|---|---|---|
| Fit to how you work | Fits perfectly, costs a salary | You bend your process to suit the tool | Built around the workflow you already run |
| Time to something useful | Immediate, and permanent | Quick to switch on, slow to make fit | A working slice in weeks, then hardened |
| Who owns the data | You do | The vendor, on the vendor's terms | You do, in your own accounts |
| When it breaks | That person sorts it, if they are in | A support queue and a ticket number | The people who built it |
| What it costs | A salary, every year, forever | Per seat, forever, used or not | Scoped and quoted up front |
The Quarry Bay context, plainly.
- Quarry Bay has become Hong Kong Island's secondary business hub, home to regional offices priced out of Central - AI here means Central-grade capability at a lower cost base.
- A dense cluster of regional headquarters and professional services firms that moved east for the rent, alongside a growing media and publishing sector. Businesses here want the same AI standard as Central without the Central price tag.
We work with teams across Quarry Bay: Tai Koo · North Point · Fortress Hill · Sai Wan Ho.
Talk to us about this →
How we build AI content generation for a Quarry Bay team.
We scope narrow, ship a working pilot, then harden it into production. The first slice is the highest-leverage workflow for your Quarry Bay business, so value lands before the build is finished. AI content engine.
Talk to usHow the work runs
- Find the one workflowWe look for the job costing Quarry Bay businesses the most hours or the most leads, and deliberately ignore the rest for now.
- Ship a working sliceA narrow version goes into production in weeks, against real work, so the value shows up before the build is finished.
- Prove it, then widenWe measure it against what the work cost before. If it does not pay for itself, we say so rather than scaling it.
- Harden and hand overLogging, fallbacks and a real handover, so it keeps running when we are not in the room.
The outcome for Quarry Bay teams
We'd call the engagement a success when Quarry Bay teams are using the system without thinking about us. Publishes 4x more content per week without adding headcount.
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 Quarry Bay 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.
Do you do hourly billing or fixed price?
Fixed price for the pilot, every time. After that it's your call - fixed price per milestone or a small monthly retainer for ongoing iteration. We don't run open-ended T&M because it disincentivises us from finishing.
Do you have proof this works for Quarry Bay businesses?
Direct case study: Publishes 4x more content per week without adding headcount. Happy to walk you through full numbers on a call.
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.
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.