Zero Friktion · 2026 · v1.0 · 7 pieces
|
z
|
Maja Lindqvist
Founder · Zero Friktion
"Software for teams who'd rather ship than schedule another workshop."
|
|
z
|
Maja Lindqvist / founder
|
{{first_name}},
Saw your post about the dispatch-coverage gap on Friday nights — that's exactly the shape of problem we just solved for Nordkust Logistik (a fleet of 80, similar route density to yours).
We built them a copilot that drafts the night handoff in about 90 seconds, with audit trails their ops director will actually trust. Three months in, dispatchers refuse to switch back. Quote from their CEO is below.
Two things I'd offer:
(a) A 30-minute call to map the friction — no deck, no SOW, just notes.
(b) A fixed-fee, two-day audit if it looks like a fit. You walk away with a plan either way.
Worth a look? 15-min slot here →
— Maja
The honest version: the model isn't the problem. The retrieval, the eval set, and the human-in-the-loop are. We've shipped enough now to know exactly which corner cuts come back as bugs.
Read the essay →A custom routing agent + driver iOS app, replacing a 60-tab spreadsheet and three Slack channels. 31% fewer empty kilometres in the first quarter.
Case study →One paper on retrieval drift, one studio essay on shipping under deadlines, and a YouTube talk by an engineer we admire on observability for LLM systems.
All three →AI agents, mobile apps and bespoke tools — shipped in fixed-scope sprints. No PowerPoint, no agency-of-record.
Book intro ↗AI agents, mobile, web — shipped in 14-day sprints.
Book a 15-min introA small AI & software studio for teams who'd rather ship than schedule another workshop. We build the agents, mobile apps and internal tools that quietly remove the drag from how your business actually runs.
Retrieval, tool-use, evals and the unglamorous plumbing — built around your workflows, not a vendor demo.
iOS, Android, React Native — designed for retention, instrumented from day one.
Dashboards, admin consoles, customer portals. Boring on the surface, surgical underneath.
01 · Map. Two days, on-site or remote — we sit with your team and write down the costliest 3 frictions in plain English.
02 · Cut. One week to a prototype that addresses the single highest-leverage friction. If we can't define a clean cut, we don't take the project.
03 · Ship. Two-week sprints, end of every sprint shipped to a real environment with real users. No staging-forever.
04 · Hand. Or stay embedded — your call. Either way, you walk away with documentation, evals, runbooks.
A senior team — designer, engineer, sometimes one of each — embedded in your repo, your standups, your product. No handoff theatre.
Fixed-scope sprints with a clear demo at the end of each. Source, evals, prompts and runbooks. You own everything.
"They were the only one who arrived with a working thing the second week. Three months in, dispatchers refuse to switch back." — Maja Lindqvist, CEO Nordkust
Software, but with
the friction taken out.
A dispatcher's copilot
that paid for itself
in 9 weeks.
A small team,
shipping on a fixed clock.
Zero Friktion.
An agent is just software — held to the same bar.
Prototype to production in 14 days.
Where the friction actually lives.
Three slots. Q2. No theatre.
A copilot that paid for itself in 9 weeks.