How we price a build: fixed time, flexible scope.

One price for a fixed amount of time, a scope that follows your priorities, and a working first version in about four weeks. What the price includes, what changes it and what we leave out.

ArtursFounder, Visualwise2 November 20261 min read
Breakdown
How we price a build: Visualwise article cover
Intro

The short answer

We price a build as one fixed price for a fixed amount of time, not a fixed price for a fixed list of features. Today that is an introductory €4,750 for a whole three-month cycle in two-week sprints, with a first working version in about four weeks. The scope inside the cycle follows your priorities: the most valuable piece first, then the next, decided together every two weeks.

After the cycle, improvements continue in monthly product sprints that you can pause or stop at the end of any month. Below is what the price includes, the maths behind the model, and what makes a project cost more. Prices are as of November 2026.

Assumptions

What does the price include?

Process Mapping: 60-minute session and a written report in 5 working daysWorth €1,500, free if you qualify
Build cycle: three months of two-week sprints, a demo after each€4,750 in total (introductory, rising to €8,000)
First working version your team usesIn about 4 weeks
Connections to your CRM, ERP or accountingIncluded
Personalised tutorials for the teamIncluded
Product sprints after the cycle€1,500 / month until 1 December 2026, then €2,500

The €4,750 is the total for the three months, not a monthly fee. Current prices are always on the pricing section of each service page.

You own the result. The code goes into your repository and the data stays in your systems or an EU-hosted account in your name. Hosting and the tools you subscribe to therefore run in your own accounts.

The maths

Why fixed time instead of fixed scope?

A fixed price for "everything" makes both sides guess. The vendor guesses how long a list of features will take and adds a buffer for the risk. You guess, months in advance, which features you will need. Both guesses are usually wrong, and the research on software projects shows in which direction.

45%average budget overrun of large IT projects, which delivered 56% less value than predicted (McKinsey and Oxford, 5,400+ projects)
59%of IT projects exceeded their initial cost estimate (Standish Group, CHAOS 2013)
≈ 4 weeksuntil your team uses a first working version in our model, so the next decisions are based on real use

The McKinsey and Oxford study looked at projects far bigger than a small company's, but the pattern holds at every size: the longer you plan before anyone uses the software, the more of the plan turns out to be wrong. So we fix the money and the time, and keep the order of the work open. If something you thought you needed turns out not to matter after the first demo, the time goes to what does.

Result

What makes it cost more, and what is left out

A bigger project does not get a bigger quote. It gets more cycles. If the first cycle covers order intake and a second process is worth automating too, that is a second cycle or a few months of product sprints, decided when the first one has paid back. You never commit to more than one step at a time.

More processes or teamsAnother cycle or product sprints, agreed step by step
Tool subscriptions and hostingPaid directly to the providers, in your name
Changes inside your accounting or ERP system itselfNot included: we connect to it, we do not modify it
Anything not in the agreed planNot included until you swap it for something that is

For what similar work costs elsewhere and how to compare quotes, read How much does custom software cost?. If you want the plan before any price, the free Process Mapping gives you the map, the hours and a build plan in writing, whether or not you build with us.

Next step

Start with the plan

Keep reading

All articles