We've worked with enough operators in San Francisco 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 HR assistant project is sit with your team for a day before we propose anything.
Built and supported here - the way a San Francisco business would actually use it.
Our goal is to give San Francisco businesses a three-day weekend, so people can spend more time with their families and the people they love :)
What AI HR assistant actually does
An AI HR assistant trained on your policies, awards, and the Employment Relations Act. Answers staff questions, drafts contracts, screens applicants, and flags HR risk - without replacing your people lead.
- 01 Answers leave, pay, and policy questions 24/7
- 02 Drafts contracts, warnings, and PIPs from templates
- 03 Screens CVs against role criteria with reasoning
- 04 Flags ER risks before they become disputes
Built on: Claude Employment Hero API BambooHR Vercel
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 HR assistant 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 San Francisco 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 HR assistant 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 |
Why San Francisco businesses are a fit for this.
- San Francisco is where the AI industry itself is headquartered - any AI pitched here is judged against the frontier labs a few blocks away, not against a competitor's landing page.
- The highest concentration of AI research labs and startups anywhere in the world, sitting alongside legacy finance and professional services firms adopting AI for the first time. San Francisco is the least forgiving market for a weak AI product, and the best one for a genuinely strong one.
We work with teams across San Francisco: Financial District · SoMa · Mission District · Marina · Nob Hill · Hayes Valley.
Talk to us about this →
How we build AI HR assistant for a San Francisco team.
We scope narrow, ship a working pilot, then harden it into production. The first slice is the highest-leverage workflow for your San Francisco business, so value lands before the build is finished. AI HR and people ops.
Talk to usHow the work runs
- Find the one workflowWe look for the job costing San Francisco 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 San Francisco teams
What changes for San Francisco 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. HR enquiries drop 65% in the first month - leaders get their week back.
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 San Francisco 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. HR enquiries drop 65% in the first month - leaders get their week back.
Can you work with our existing systems?
Yes. The default AI HR assistant stack we reach for is Claude, Employment Hero API, BambooHR, 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.
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.