Kensink Labs is a small lab of senior engineers shipping production AI for SaaS companies. We integrate against the model the same way we integrate against Postgres. No agent frameworks, no orchestration vendors, no migrations every six months. Eight weeks, then it’s yours.
Four overlapping phases over roughly sixteen weeks. Discovery feeds the brief; the brief feeds the build; the build feeds a runbook your team can still understand six months from now.
Three case studies you can read end-to-end, two essays we keep getting asked for, and one running archive of everything else. Pick the one closest to where you are now.
A direct-LLM triage layer over Nuforce's legacy claims pipeline. Reduced human review by seventy-three percent in twelve weeks. No agent framework, full ownership at handoff.
A retrieval copilot threaded into a fifty-person research team's daily workflow. Four hours saved per analyst per week within thirty days of rollout, measured at the team level rather than estimated.
An LLM-powered onboarding flow inside a consumer fitness app. Lifted week-one activation by eighteen points in the first eight weeks post-launch, with the eval suite the team now owns.
Six failure patterns we see in every audit, ranked by how much money they cost, plus the cheap fixes that prevent them.
How a 200-person company restructures its org chart around AI agents without firing anyone, without losing a year of credibility, and without buying a transformation deck.
Internal correspondence we found worth publishing. Mostly things we got wrong on the first pass and how we re-typeset them.
We do three things, and we are honest about what they are. Every engagement starts in one column and usually ends in another. The scaffolding is how the work travels.
Two to four of our engineers join yours for an engagement of twelve to twenty weeks, with a published runbook and a working artefact at the end. We don't do retainers.
You bring a problem; we bring a chapter. Brief, build, ship and a printed companion runbook, by the date we agreed on, at the price we agreed on.
A field-notes practice on the side: short essays, the occasional open-source tool, the occasional public talk. The lab writes more than it speaks.
We publish these quarterly. The numbers don’t always flatter the lab, but they’re falsifiable. Footnoted, source-linked, updated 22 May 2026.
across four years, two coasts, and one stubborn rule about what we don't take on.
senior engineers, designers, and one product lead who keeps everyone honest.
of clients have shipped a follow-on chapter with us. Self-reported.
every engagement ends on the date we agreed on. Then you decide.
Engineering notes, half-finished diagrams, the occasional rant about file formats. New entries every other Wednesday in the Dispatch.
A short brief on why our integrations team starts at the schema, never at the endpoint. Includes a diagram you can print at A4 and a fourteen-line Postgres migration.
Story points are an honest unit if you treat them like word counts. Here is how we write a feature like a chapter: outline, draft, edit, set, ship.
Why every engagement ends with a physically printed runbook, and what changed about our work the day we started doing it.
