We design, build and run web platforms and native Apple apps for companies that need them to work for years, not just on launch day. Five products of our own are the proof. Yours could be next.
A few lines about your project are enough. One of us reads it and replies, usually within a day.
Four things companies hire us for, each of them something we built for ourselves first. Design, code and servers from one team, so nothing falls between the cracks.
Customer portals, booking systems, internal tools and subscription products, with the accounts, roles, billing and admin a real product needs. We take it from the first sketch to the first paying customer, and on from there.
SwiftUI apps for iPhone, iPad, Mac, Apple Watch and Apple TV that feel like part of the device rather than a website in a box. Push, iCloud, widgets and App Store review are all part of the job.
Public registers, payment providers, accounting systems and webhooks, cleaned and joined into one schema you can query and trust. Bilero runs on the Danish vehicle register, which we normalised from scratch.
Servers in the EU, a deploy on every push, backups you can actually restore, and alerts that reach a person before a customer notices. We run everything we build, and we take over systems built by somebody else.
Fewer people between you and the code means faster answers, fewer handovers and no part of your project that nobody owns. Here is what that buys you.
You talk to the people writing the code, so a question asked in the morning is settled by the afternoon, not parked until the next status meeting.
We put the hours into the schema, the migrations and the edge cases, so the feature you ask for in year three costs what a feature should, not a rewrite.
Code, servers, domains and App Store accounts are registered to you. If we ever part ways, you keep a working system and every key to it.
Every tool we recommend already runs one of the five products we own and pay for. You get the choices that survived real customers, not the ones we wanted to try.
Each one began as something we needed and could not buy. Three are in production. Acciti and MealFoundry are still being built and are not out yet.
Your servers, run like a platform.
Read moreThe alert that refuses to be ignored.
Read moreDinner, decided once a week.
Read more
Every library in one app.
Read more
Everything about the car, from the plate.
Read more
No surprises. You see the scope and the price before we start, and working software every week after that.
You describe what you need and what it has to do for the business. We keep asking until we understand the problem behind the wish list.
Scope, timeline and price, in plain language. If the budget is tight, it says what we would leave out first and what that would cost you.
A working version on a real address within the first weeks, updated every week after. You give feedback on something you can click, not on a slide deck.
We watch the first weeks closely and fix what real users find. After that we keep running it, or hand it to your own team with everything written down.
If one of these sounds like yours, it probably fits. If none of them does, write anyway: the first conversation is free and commits you to nothing.
Let customers see their orders, invoices and documents themselves, instead of emailing you for them.
Replace it with something several people can use at once, which remembers who changed what.
For staff who work away from a desk: offline, with photos, signatures and a push when something needs them.
Connect the shop, the accounting system and the warehouse, so nobody types the same order twice.
Sign-up, payment, invoices and the admin behind it, ready for your first paying customer.
Built by somebody who has moved on. We read it, run it, and tell you what to fix first.
It depends on what you need, so we price it after the first conversation, in writing, before any work starts. You know what the money buys before you commit to anything.
Yes. We read the code and run it, then tell you honestly what state it is in and what we would fix first. Laravel, PHP, Swift, Node and React are all familiar ground.
No. We work in Danish or English, and most meetings are video calls. If you are in North Jutland, we are happy to come by the office.
Probably not. An integration, an update to an existing app or a site that needs to get faster are all good places to start. Many of our longer collaborations began with one of those.
Three or four lines are enough: what it is, who it is for, and when you need it. One of us reads it and replies, usually within a day.