This website
The one project on this page you can audit yourself: view source, run Lighthouse, tab through it.
- Astro
- TypeScript
- Tailwind CSS
- MDX
- +1
Independent software studio
Remote-first · Built to work everywhere
Software for
the real world.
Behind every smooth operation is software that just works. We design it, build it, and keep it running.
A small, senior team.
From the first sketch to the last mile.
DIGITAL LOGIC. PHYSICAL IMPACT.
01 / Where software meets the world
One connected workflow
Interface→Logic→Device
From the screen to the machine.
Four kinds of work, one team across all of them.
Our everyday stack
- TypeScript
- React
- Next.js
- Astro
- Tailwind CSS
- Node.js
- Python
- PostgreSQL
01 / What we build
Every layer. One team.
Enough range to own a whole workflow, narrow enough that the person writing the code has done it before.
01 / Interface
Web apps and websites
The screens people use all day, and the ones that win you the meeting.
What this involves
02 / Automation
AI agents and process automation
Work that used to need a person watching an inbox.
- Document, email and message intake agents
- Back-office workflow automation with human review steps
03 / Systems
ERP, systems and integrations
Making the systems you already paid for agree with each other.
- ERP setup, extension and integration
- API layers and event pipelines between tools
04 / Machines
Mobile apps and connected machines
Software that leaves the office — in a pocket, or bolted to a machine.
- In a pocketiOS and Android apps, including offline-first field tools
- On the machineVending and kiosk applications with payment and dispense flows
- Reporting backDevice telemetry, remote configuration and diagnostics
- On the support deskFleet dashboards for the people answering the support calls
Product and UI/UX design is part of every one of these, not a separate line item. If the interface is wrong, the integration underneath it does not matter.
02 / Selected work
Built with purpose.
Every entry says what it actually is: an internal build, a reference architecture we build from, or a concept. Nothing here is dressed up as a client delivery.
Vending fleet: telemetry and remote support
A machine 400 km away stops selling. This is the software chain that tells you why without sending a technician.
- Embedded Android
- Kotlin
- MQTT
- Node.js
- +2
Order intake agent for a wholesale back office
Orders arrive as email, PDF and photographs of paper. An agent reads them; a person approves them.
- Python
- Claude API
- Queue workers
- PostgreSQL
- +1
03 / How we work
No month-long silences
- 01
Week one
Scope it in a week
Map the workflow, agree the first version, and leave with a fixed scope, price and date.
- 02
Every week after
Build in weekly slices
A working deployment, a written update and a clear plan. Every single week.
- 03
At launch
Ship, then measure
Track usage, failures and time saved, so you can see whether the work helped.
- 04
Afterwards
Run it, or hand it over
Keep us for maintenance or take it in-house. The code and accounts are yours.
04 / Our standards
Hold us to these
Four commitments, each with the thing you can check to see whether we kept it. A promise nobody can verify is just marketing.
Estimates with the assumptions attached
Ask for the assumption list. Every estimate has one.
Budgets set before the first screen
Run Lighthouse on anything we shipped, including this site.
WCAG 2.2 AA as the floor
Unplug your mouse and try to finish the job.
Yours to leave with
Read the contract. The handover clause is in it from the start.
Your next move
Good work starts
with a conversation.
Describe the workflow and what breaks. You will get a straight answer about whether we are the right team for it — including when we are not.