The price comes from scope, not from a list.
We don't sell fixed packages. Here is how a proposal is built, what drives the cost and what never changes from one project to the next.
Same name, different job
- Informational pages
- Contact form
- Login and roles
- Payment integration
- Admin panel
- Data migration
- Multilingual content
Both are called the same thing. The price follows this list, not the name.
Representative scope
Why we have no fixed price list
Same title, different job
A “website” can be a one-page introduction or a platform wired into three separate systems. Under the same name, two jobs can differ many times over.
A fixed package either cuts or oversells
A single price hides that difference: either the scope you paid for gets cut, or you buy scope you don't need. Neither is fair.
Price follows scope, not haggling
We define the need first, then price it line by line. No surprise items; every line carries its reason in the proposal.
The road to a proposal
Four steps. The first two are free and commit you to nothing; at the end you hold a written proposal.
Discovery call
30–45 minutesWe listen to what you want to build. If we think the job isn't a fit for us, we say so in that first call.
Process analysis
FreeWe map how the work runs today: the steps, the data, the roles and everything repeated by hand.
Written scope
Line by lineWe put in writing what will and won't be built. Every item states why it is there.
Proposal
With its reasoningOnce the scope is clear, the price and the timeline follow. If the scope changes, the price is updated in writing.
Free · no commitment · the first two steps bind you to nothing
What's in a proposal?
- Scope, line by line
- Timeline and delivery order
- Who does what
- Acceptance criteria
- Post-launch maintenance terms
Representative proposal structure
How much time does this work take today?
Before talking about the cost of software, it helps to know the cost of the current situation. Get a rough figure for work that runs on paper, spreadsheets or chat.
Repeated work such as data entry, filling forms, preparing reports
Average time spent on this work per day
Gross salary + benefits ÷ monthly working hours
The calculation assumes 22 working days per month and 8 hours per day.
132 hours
roughly €4,620 in labour cost
1,584 hours
roughly €55,440 in labour cost
0.8 people
Across a year, this work equals that many people working full time.
These figures are calculated only from the values you enter; they are not a savings promise. Which steps can be automated — and which cannot — is something we determine together in the process analysis.
Let's review the process togetherWhat drives the number
Most questions that come up in a call land on these six.
Scope and complexity
How many screens, how many flows, how many exceptions. That is the gap between a single-form tool and a three-role system.
Number of integrations
Every external system — accounting, shipping, payment, email — is another connection and another failure case.
User roles
A system where everyone sees the same screen is not the same job as one with role-based permissions and approval flows.
Data migration
Where the current data lives and how it is structured. Moving from a spreadsheet and moving from a system used for years are different jobs.
Number of platforms
Web only, or iOS and Android too, and whether it runs alongside an admin panel.
Post-launch maintenance
Who watches the system after delivery, how fast issues are answered and how the scope is allowed to grow.
If you're wondering how much time your team spends on this, use the time calculator.
The same in every project
Always included
- Technical documentation and a user guide
- GDPR/KVKK compliance and data sovereignty
- Team training
- Post-launch bug fixing (for the term of the contract)
Never happens
- Hidden items appearing later
- Out-of-scope work billed without notice
- Your data going to another client or to model training
- Work started without your approval
About pricing
Why don't you publish a price list?
Two jobs with the same name can carry very different scopes. A fixed package either cuts the scope or sells you more than you need; neither is fair. We map the scope first and then price it line by line.
Is the discovery call paid?
No. The discovery call and the process analysis are free and commit you to nothing. If we think the job isn't a fit for us, we say so plainly.
How long does a proposal take?
It depends on how clear the scope is. After the discovery call it takes a few working days, depending on the size of the job. If anything is still open, we clarify that first.
Does the proposal come as a single number?
No, it comes line by line. You see why each item is there; you can remove one you don't want or leave it to a later phase.
Should I state my budget upfront?
Yes, it helps. Knowing the budget lets us shape the scope around it and decide together what gets built first. If the budget isn't enough, we say that plainly too.
Tell us the process, we'll map the scope together.
The discovery call and the process analysis are free. At the end you hold a written proposal covering what will be built and what it costs.