How we price the work

The contract model follows how well the requirements are pinned down. A fixed price on a fuzzy scope is the surest route to a dispute halfway through.

Risk: changes get expensive Fixed price When the job is specified in detail and unlikely to shift
Risk: scope needs watching Time and materials DKK 895/hour excl. VAT, when requirements settle along the way
Risk: the team may sit idle Dedicated team When a roadmap stretches many months ahead
Hardly any risk Discovery as its own phase When the idea is clear but the paperwork is missing

You own the source code and the rights to it. The contract says so. Once the project ends you may develop it in-house or bring in another supplier. You receive the repository, the documentation and a written guide to deploying the solution.

How the work runs

Every second week we show working software in an online demo. Any drift from your expectations surfaces early, not on hand-over day.

01

Discovery

We map workflows, user journeys and constraints. The output is a requirements document and an estimate. Discovery is paid separately and commits you to nothing further.

02

Prototype

A lean working version covering the core journey. At this point a good few wishes quietly drop off the list.

03

Sprint delivery

Two-week sprints with a demo and sign-off. Priorities can shift from one sprint to the next without rewriting the contract.

04

Hand-over and operation

Documentation, deployment guide and training for your own staff. A period of bug fixing follows, plus further development whenever you need it.

Frequently asked questions

Quite often, yes, and we will say so plainly. A standard system with some configuration is nearly always cheaper and quicker to roll out. Bespoke work pays off when your process is genuinely distinctive, or when the packaged product would force you to reorganise around it, and that reorganisation tends to cost more than people expect.

We do not. Fixed quotes on unwritten requirements miss by a factor of two or three. Instead we suggest a short discovery of about two weeks. It is paid for separately, and afterwards you hold a requirements document and an estimate you can take to any supplier you like.

At least two developers always work on a project, the code sits in your repository or a shared one, and key decisions are written down. A change of personnel slows the pace for a couple of weeks, but nothing grinds to a halt and nothing has to be redone.

We follow privacy by design: only the personal data you need, encryption, logging and access control from the first sprint. Test data is anonymised and hosting stays in the EU. We work to ISO 27001 principles and can supply documentation for your NIS2 obligations.

Yes, after a review. We assess code quality, automated tests and documentation. Occasionally the honest finding is that a rewrite beats a repair, and you get that conclusion in writing too.

Describe the problem in your own words

No specification needed. Tell us which part of the work is causing friction and what should change. We will propose a way to collaborate and size the discovery phase.

Coverage
All of Denmark, delivered remotely

This site uses only essential cookies: they keep pages working and store your chosen town. Read more in our privacy policy.