Most of our Blenheim 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. MCP integrations is then designed against the detail, not the shape.
Marlborough · Applied AI
Built and supported here – the way a Blenheim business would actually use it.
What MCP integrations actually does
Wire Claude, ChatGPT, or Gemini directly into your tools with the Model Context Protocol. Your team uses AI in their existing inbox, CRM, or chat – with your data, your permissions, your guardrails.
- 01 Custom MCP servers for your CRM, ERP, or in-house tools
- 02 Permission-aware so AI only sees what each user can
- 03 Tool-call audit log for compliance
- 04 Works with Claude Desktop, ChatGPT, Cursor, and more
Built on: MCP Claude TypeScript Vercel
Without Kiwi Dynamics
With Kiwi Dynamics
Marlborough
The Blenheim context, plainly.
- Marlborough is wine, aquaculture, and tourism – three industries running on tight margins where AI quickly pays for itself.
- Vineyards, cellar doors, mussel farms, and a thriving cycle-trail tourism economy. AI here means forecasting the season and never missing a booking.
We work with teams across Blenheim: CBD · Renwick · Picton · Havelock · Seddon.
Talk to us about this →
How we build MCP integrations for a Blenheim team.
We scope narrow, ship a working pilot, then harden it into production. The first slice is the highest-leverage workflow for your Blenheim business, so value lands before the build is finished. Connect Claude to your stack.
Talk to usThe outcome for Blenheim teams
What changes for Blenheim teams after this lands: the work that used to need a person stays done, the work that needs a person gets done with their attention undivided. Existing AI tools become 10x more useful with real business context.
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.
Questions
FAQ
What's a typical engagement length for Blenheim 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.
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. Existing AI tools become 10x more useful with real business context.
Can you work with our existing systems?
Yes. The default MCP integrations stack we reach for is MCP, Claude, TypeScript, Vercel, 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.
The honest version of a sales call.
No deck. No discovery doc. Just whether this is worth building and what it would cost.
Get in touch
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.