The reason we take on work in Changi is that the businesses here tend to be sharper about what they want than the brief lets on. Semantic search (RAG) for a Changi team almost always ends up looking different to semantic search (RAG) for a downtown Auckland one.
Semantic search (RAG) designed around the way a Changi team actually runs.
Our goal is to give Changi businesses a three-day weekend, so people can spend more time with their families and the people they love :)
What semantic search (RAG) actually does
Search that understands intent, not just keywords. Your team types what they mean - and gets the right document, ticket, or product from across every system, with citations.
- 01 Indexes Drive, SharePoint, Notion, Slack, your CRM
- 02 Returns answers with source links - no hallucinations
- 03 Permissioned so staff only see what they should
- 04 Re-indexes nightly so results stay fresh
Built on: Pinecone Claude Postgres pgvector Vercel AI SDK
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 semantic search (RAG) 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 Changi 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 semantic search (RAG) 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 |
Our field notes from Changi builds.
- Changi runs on aviation, logistics and air cargo as one of the world's busiest air hubs - AI here means keeping freight, scheduling and compliance moving at airport speed.
- Changi Airport and its surrounding air-cargo and logistics ecosystem move an enormous volume of freight and passengers on tight schedules. Businesses here want AI that handles logistics coordination and compliance documentation without becoming the bottleneck.
We work with teams across Changi: Changi Airport · Changi Business Park · Loyang · Pasir Ris · Tampines.
Talk to us about this →
How we build semantic search (RAG) for a Changi team.
We scope narrow, ship a working pilot, then harden it into production. The first slice is the highest-leverage workflow for your Changi business, so value lands before the build is finished. AI search over your data.
Talk to usHow the work runs
- Find the one workflowWe look for the job costing Changi 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 Changi teams
The shape of the result for Changi teams: Average search time drops from 6 minutes to 12 seconds. Built on Pinecone, 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
How fast could we have semantic search (RAG) in production?
Eight to ten weeks for most Changi businesses. Faster if your data is in good shape and slower if we're untangling a legacy integration first. We'll give you a realistic number on the scoping call rather than the optimistic one.
What's the smallest engagement you'd take on?
A two-week paid discovery for Changi businesses that aren't sure whether the build is worth doing at all. You get a one-page write-up of what we'd build, what we'd skip, and what it would cost. About 30% of those discoveries end with us recommending you don't proceed.
What's the realistic outcome for Changi businesses?
Average search time drops from 6 minutes to 12 seconds. We don't promise tenfold lifts because we don't see them outside of marketing decks.
What if our Changi doesn't have any data ready?
Most don't. Getting the data into shape - ingestion, cleaning, the lightweight contracts you need before any model is useful - is part of the engagement. For semantic search (RAG) specifically, we typically run that work on Pinecone, Claude, Postgres pgvector, Vercel AI SDK and assume messy starting conditions from day one.
One short call.
Tell us what you're trying to fix. We'll come back inside a working day.
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.