Map the work
We sit with the people who will use it and follow the job they actually do, not the one the org chart describes.
Web applications for internal tools, customer portals and dashboards. We handle the parts that get expensive later — roles and permissions, audit trails, data that holds up.
Get Your WebsiteEvery one of these is live today, and still maintained by the people who built it.
Four things that decide whether a web application still works for you in three years.
No junior hand-off once the contract is signed. The people who scope your web application are the people who build and maintain it.
We design permissions, data and audit trails first, so the tool stays cheap to change as your business grows.
The code, the database and the hosting accounts are yours from day one. Your admins manage users without a ticket.
Launch is the middle of the work. We keep the application patched, fast and supported long after the invoice is closed.
Four stages. You see working output at the end of each one, not a status report.
We sit with the people who will use it and follow the job they actually do, not the one the org chart describes.
Permissions, roles and records come before any screen. This is the part that decides what the tool costs you later.
One working flow at a time, in your hands early, so course corrections cost days rather than months.
Documented, with the accounts and repository in your name, and us on call for the releases after.
Not a menu of everything. These are the pieces we build ourselves and stand behind.
We map the work and design roles, permissions and records before the first screen is drawn.
One team builds your web applications end to end — backend, interface and API — in short slices you can try every week.
The server enforces access, a log records every change, and your admins manage users themselves.
Payments, CRM, accounting and BankID — connected to what you already run instead of replacing it.
The numbers people ask for every Monday, live, with exports that open in Excel.
Patches, monitoring and new features from the same people who built it. For years, not months.
Written down before we start — so there is nothing to negotiate at the end.
The expensive mistakes get made on paper, not in productionWe design data and permissions before the first screen.
Your admins manage access without calling a developerRoles and users live inside the application, not in our inbox.
It connects to what you already run instead of replacing itAccounting, CRM, payments and sign-in stay where they are.
Handover takes an afternoon because everything is documentedLeaving us would take an afternoon and break nothing.
If yours is not here, ask us directly — we answer the awkward ones too.
We quote a fixed price after a short scoping call, usually within three working days. The number you see is the number you pay — if we underestimated the work, that is ours to absorb, not a change order at the end.
Eight to twenty weeks for most web applications, depending on the number of workflows and integrations. You get a working build every week, so you see the date coming rather than hearing about it.
The two people on your first call. Nothing is sub-contracted, and there is no account manager relaying messages between you and someone you never meet.
Time with the people who will use it, examples of the data, and one person who can make decisions. We write the specification with you.
Yes. We design the data model for change and document every release, so a new module does not mean rebuilding the old ones.
We keep it patched, monitored and answered. The same people stay on for the releases that follow — clients from 2019 still email us directly.
Clear scope and requirements before development begins.
A practical approach built around your business needs.
Websites, web applications, and mobile apps under one team.
Clear communication throughout the project.
Practical insights on websites, web applications, mobile apps, and the technology behind better businesses. No noise, no daily emails—just useful things worth reading.