Advice · Engineering · Automation
A new world a new beginning
A new world is unfolding with AI, and we are glad to build in it. But not everything should be guessed — some things simply have to come out right, every single time. We do both, and we say so when AI is the wrong tool.
inbox · support@company.com
Lise Hartmann
09:14
Error 32 on our unit — urgent
Hi. Our unit is showing error 32 and we can't get it running again. We have production going …
Draft reply
call · 12 min 04 s
Transcript
- … so we'll need 40 units for week 12.
- We can make that. Shall I send a quote?
- Yes please. Send it to purchasing rather than to me.
Note — ready for the CRM
- Customer
- Nordjysk Montage A/S
- Agreement
- 40 units, delivery week 12
- Deadline
- Quote sent by Friday
- Next step
- Send to purchasing, not to Lars
price configurator
- Units · 40 × 1.450 kr.
- 58.000 kr.
- Installation
- 12.400 kr.
- Service · 24 months
- 9.600 kr.
The customer does the maths. You get a lead that already knows the price.
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
All names and marks belong to their owners. Groq is a trademark of Groq LLC. We are neither affiliated with nor endorsed by the companies listed.
What people actually call about
Three sentences we hear every week
Nobody calls asking for an integration. They call because something takes too long.
We're drowning in email.
We work out which ones can safely be answered automatically — and which ones never should be.
We type the same thing into two systems.
The systems can usually talk to each other. It's just that nobody ever set them up to.
Our website can't do what we need.
After 20 years in WordPress we know when a plugin is enough, and when it has to be built.
Two tracks
With AI. And without.
We pick the tool for the job — not for what's new.
When AI earns its place
Work involving language, variation and judgement. Where no two cases look quite alike.
- Email that needs reading, sorting and answering
- Calls and meetings that need writing up
- Documents where the fields sit somewhere different every time
- Questions about your own documentation
When AI is the wrong tool
Work with fixed rules. Here the answer must be the same every time — and explainable.
- Prices and quotes that follow a formula
- Scheduling under fixed rules and agreements
- Data cleaning where the result has to be auditable
- Website features that simply need to work
Around half of what we solve doesn't need AI. We'll tell you which half you're in — even when that means a smaller invoice.
Try it yourself
You don't have to take our word for it
Three demos you can try in the browser right now. Two of them run for real. The third uses no AI — and that's the point.
- 01Meeting notesPaste a conversation, get a structured summary
- 02Email workflowPaste a customer email, watch it get classified
- 03Price configuratorNo AI. No server. Just the arithmetic
Scenarios
What a job looks like with us
Twelve worked examples of problems we solve — with and without AI.
How we work
Four steps. No surprises.
You know what the next step costs before we take it.
- 1
A conversation
30 minutes, free. You describe the problem, we tell you honestly whether we're the right people for it.
- 2
Scoping
One to two weeks at a fixed price. You get a concrete plan with an estimate — and it's yours, whether or not we build it.
- 3
Build
Fixed price on a scope we both understand. You see something working along the way — not only at the end.
- 4
Running it
We stay if you want us to. If you take it over, you get the documentation and the access without an argument.
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.
Questions we get
Before you call
What does it cost?
The first conversation is free. A scoping engagement is typically in the low five figures (DKK); a built solution depends entirely on scope. We quote a fixed price once we both understand the job — not before.
We don't know whether we need AI.
That's exactly what the first conversation is for. We don't earn more by saying yes to AI, and we advise against it regularly.
What happens to our data?
We sign a data processing agreement for any work touching personal data. The demos on this site don't store or log what you type into them.
Can you take over a project someone else abandoned?
Yes, and it's a large part of what we do. We start by reading the code and telling you honestly what can be saved and what can't.
Do you still work in WordPress?
Yes. It's still the right choice for plenty of jobs — and after 20 years we also know when it isn't.
How quickly can you start?
A conversation usually within a week. When we can build depends on what else is in the calendar — we'll say so plainly on the first call.
What we built ourselves
Cartwright — our own build engine
We don't just advise on building things. Cartwright is open source, written by us, and the engine we reach for ourselves when a client needs a real site with a database and a backend.
You own every line
MIT licensed. No platform lock-in, no per-order fee, no subscription trap.
Real engineering underneath
Next.js 16, React 19, Prisma, Stripe and the Model Context Protocol — not a site builder with limits.
Measured, not claimed
An AI agent with no prior knowledge of the codebase went from command to a finished, verified homepage in 99 seconds.
Try it yourself
$ npx create-cartwright@latest mit-siteOne command. Needs Node on your machine.
Tell us what's taking too long
30 minutes, free, no strings. If all you get out of it is knowing you don't need us, that's a result too.