About us
Two developers who have been making websites since it was called something else.
Why we work the way we do
We've both spent twenty years building for the web. We hand-wrote themes back when that's what you did. We've cleaned up after plugins that promised too much. And we've seen enough projects go off the rails to know it's rarely the technology that's the problem.
What's changed in the last few years isn't that everything should be made with AI. It's that there's a new tool in the box — a very good one for some jobs and a very bad one for others. Customers can't tell the difference. That's our job.
So we turn down AI work that's better solved with arithmetic. It costs us a little revenue and we sleep better.
Who we are
Two people. Both of us write code.
You talk to the people building it. No project manager in the middle who has to go and ask someone else.
Jonas Bech
Advice and architecture
I always start by asking what the problem costs you — that decides how big the solution needs to be.
- Scoping and estimating
- Integrations
- AI workflows
Rasmus Hald
Engineering and operations
I've cleaned up after enough rushed work to build things that can still be maintained in three years.
- WordPress and plugins
- E-commerce
- Automation
20 years of building for the web — from the first WordPress themes to AI workflows today.
Three things we hold to
We'll tell you when you don't need us
If the problem can be solved with a setting in software you already pay for, we'll say so.
You talk to the people building it
There's no project manager in between who has to go and ask someone else and come back.
You can move on without us
Documentation and access are yours. We don't build dependency in as a business model.
We have experience with
- WordPress
- WooCommerce
- PDF / OCR
- Next.js
- Claude
- e-conomic
- Cartwright
- Groq
- Python
- Blender
- PHP
- OpenAI
- PostgreSQL
- Model Context Protocol
- Microsoft 365
- Gemini
- HubSpot
- Make
- Zapier