Mathias Villadsen
Co-Founder · Senior Fullstack Engineer
Domains: SaaS · Infrastructure · E-commerce · Fullstack
Odense
- mathias@codense.dk
- Phone
- +45 29 87 43 60
Contact
Tell us what is not working.
An hour on a call, no charge and no deck. We will ask uncomfortable questions and give you a straight answer on fit — including, sometimes, that you should be talking to someone else.
-
Mikkel Thygesen
Co-Founder · Senior App Developer & Front-end Designer
Domains: Frontend · Apps · Interface design
Copenhagen
- mikkel@codense.dk
- Phone
- +45 21 71 64 73
Write to either of us.
There is no contact form to fill in and no inbox robot to get past. Mail lands with the two people who would do the work, and one of us replies within a working day.
Worth putting in the first mail
- The system, the symptom, and what you have already tried.
- Roughly when you need it to be better.
- Whether anyone has measured anything yet — an honest "no" is fine.
Two cities, one team
On both sides of the bridge.
Copenhagen and Odense are eighty minutes apart by train, and the Great Belt link has never once dropped a packet between us. If you are in either city, the first conversation can happen in person.
Before you write
Probably asked already.
How much does an engagement cost?
Diagnosis work is fixed price and typically runs between DKK 60,000 and DKK 180,000 depending on system size. Delivery is billed monthly per engineer at a single day rate — no separate rates for senior people we then do not send. You will have the number in writing before anything starts, and we do not quote large work before reading the system.
Do you work on a fixed price for the whole project?
For diagnosis and reviews, yes. For build and modernisation work, no — and we will explain why in the first conversation. Fixed-price delivery moves risk onto whoever is worst placed to manage it and rewards defending the scope instead of doing the right thing. We use monthly rolling terms with one month notice, which gives you the same protection with none of that incentive.
Can you work with our existing team and process?
That is the default. We use your repository, your board, your conventions and your definition of done. Where we think a practice is holding you back we will make the case for changing it, and then we will do it your way if you disagree.
What technologies do you work in?
Deepest in PHP and Laravel, plus TypeScript, PostgreSQL and MySQL, and the usual cloud platforms. We also read and modernise systems in languages we would not choose to start a new project in — that is most of what legacy modernisation is. If it is genuinely outside our range, we will say so in the first call.
How quickly can you start?
Diagnosis work can usually begin within two weeks. Delivery capacity depends on the quarter — we staff engagements from the people who are actually free, and we will tell you honestly when the next real availability is rather than starting late with borrowed time.
Are you remote, or in the room?
Both, deliberately. The team is split between Copenhagen and Odense and works remote-first, but we are on site for the parts that need it — kick-off, event storming, incident reviews and anything where reading a room matters. For Danish clients that is typically a day or two a fortnight; for clients further afield we agree a rhythm up front.
What happens when the engagement ends?
The exit plan written in week one is what happens. The final stretch inverts the working relationship — your engineers write, we review — and we consider ourselves finished when your team has shipped something meaningful without us. After that the phone still works, at no cost for short questions.