AI writes the code. We make sure it never breaks.
Working software in your business in a week. Nobody to hire, and one number to call when something goes wrong.
- You give us
- The job that eats someone's whole week
- You get back
- Software that does that job instead
- It takes
- About a week to the first working version
How it works
Three steps, and the last one never ends.
-
1
You tell us what is slow
Twenty minutes on the phone. You describe the job in your own words. We tell you honestly whether we can fix it, and what it would cost. If we can't help, we say so.
-
2
We build it in about a week
Real software, running on your real orders and your real invoices. Not a slide deck, not a demo that falls over the moment somebody types something unexpected.
-
3
We keep it running
Things break. When they do at six on a Sunday morning, it is our problem and not yours. Fixing it is already in the price, and it stays that way for as long as you're with us.
Who it's for
Somebody in your building retypes numbers all day.
You run a transport, haulage or storage company. You know the person we mean. See how many of these you recognise:
- Orders arrive as PDFs and email attachments, and somebody types them in again by hand.
- The spreadsheet that runs the place has one owner, and no backup if she's away.
- Your system is from 2009 and the company that built it no longer answers the phone.
- The annual reporting takes three weeks and everybody dreads it.
- You've been told you need AI, and nobody has yet explained what that actually means for you.
If none of that sounds like you, we're probably the wrong people. We'd rather tell you that on the first call than sell you something you don't need.
Versus hiring
Nobody new on your payroll.
| Hiring a developer | Working with us |
|---|---|
| Salary, employer's contributions, pension, holiday pay | One invoice a month |
| Three to six months to find the right one | We start next week |
| One person, one set of skills, one set of opinions | A small team and the tools they already know |
| Awkward and expensive to undo | Stop with thirty days' notice |
| Somebody has to manage them | Nobody has to manage us |
It's a service you buy, like the accountant or the workshop. It sits in operating costs, not in headcount.
What it costs
Two ways to pay. One is more expensive on purpose.
Monthly
$18,900
per month
One project at a time, worked on every day. Building, fixing and keeping it running are all included. Stop with thirty days' notice.
Weekly
$4,990
per week
For when you want to see us work before committing. Deliberately dearer per day: one week is rarely long enough to finish something you can genuinely use.
No hourly billing. No charge for changing your mind halfway through. No separate invoice arriving the week after something breaks.
Questions
What people ask on the first call.
Is this going to replace my people?
No. It replaces the retyping. Everything that needs somebody who knows the customer, the route or the driver still needs that person. What goes away is the copying between screens.
I don't understand AI. Do I need to?
No, and that is roughly the whole point of paying us. You describe the problem the way you'd describe it to a colleague. Understanding the machinery is our job.
What happens to us if you disappear?
The code and the data are yours, on your own accounts, from the first day. If you ever want to hand it to somebody else, you can, and we'll help with the handover.
Where does our data actually go?
We go through exactly what touches what before we start, in plain language, and you sign off on it. Nothing gets sent anywhere you haven't agreed to.
What if it stops working?
We fix it. That is included in the monthly price, not billed separately, and there's no argument about whose fault it was.
How small a job is too small?
If one person loses more than a day a week to it, it's worth a phone call. If it's less than that, we'll tell you to keep doing it by hand.
Talk to a person before you decide anything.
Marte takes the first call. She isn't a developer either, which is rather the point: if she can't explain what we'd build for you in plain Norwegian, we've written it badly and we'll write it again.