How we quote a project
We don't publish a price list because we don't have one. What we can do is explain exactly how a quote is calculated, what pushes it up, and what is always included.
Possition quotes by the hour and by the resources a project requires, and the final price varies with complexity. Every proposal details which roles are involved, how many hours are estimated, and on what basis it's calculated. All projects include one month of warranty and the code is hosted on the client's server.
The model: hours and resources
We charge for working hours and for the resources a project needs. That means two projects that sound alike can cost differently, because what changes isn't the description but the amount of real work behind it.
- Every proposal details which roles are involved and at what dedication.
- Estimated hours are presented per stage, not as a single number.
- If the scope changes mid-project, it's quoted separately and agreed before being carried out.
- Large projects are split into stages: one is approved and paid, delivered working, and only then is the next defined.
What makes the price vary
These five factors explain almost all the difference between one quote and another. If you want a tighter estimate before talking, check how many apply to your case.
Number of integrations
Connecting to a system with a documented API is predictable work. Connecting to an old one, with no API and no documentation, can take longer than building the new system. It's the factor that throws off the most quotes.
State of the data
If the information is organized and accessible, it gets used. If it's spread across spreadsheets with different formats, duplicates, and empty fields, there's a normalization stage to account for.
How autonomous the system is
A system that informs costs less than one that executes actions. The more it decides alone, the more validation, permissions, and supervision work it requires.
Security and compliance requirements
Role-based access control, traceability of every operation, and personal data protection obligations add real work to the project.
Volume and number of cases to cover
Covering the main workflow is one thing; also covering every exception is another. Defining how far the scope goes is part of the budget conversation.
What's always included
- Mapping the process before proposing a solution.
- Development, testing, and going live.
- One month of warranty, on every project, without exception.
- The code hosted on the client's server.
- Documentation and handover to the team that will operate it.
What we don't charge for
- The first conversation to understand the problem.
- The initial assessment of whether automating makes sense, and at what scope.
- Later maintenance, if your team handles it. It's entirely optional.
- Per-user licences on software we build for you.
Warranty and maintenance
Every project includes one month of warranty. After that, maintenance is optional: if your company has its own team, the code sits on your server and your team can maintain it without depending on us. If you'd rather we did it, that's agreed separately and you can cancel whenever you want. We don't work with arrangements that force you to stay.
How we get to a number
Initial conversation
You tell us how the process works today, which systems you use, and where it stalls. No cost.
Mapping
We document the real workflow and identify what can be solved and what is better left alone.
Proposal
Detailed scope by stage, roles involved, estimated hours, and what is explicitly excluded.
Staged agreement
The first stage is approved, delivered working, and with that in view the next one is defined.
Frequently asked questions about quotes
Why don't you publish a price list?
Because price depends on the real complexity of the project, and publishing ranges that don't hold up later causes more problems than it solves. We'd rather explain how it's calculated and give you a concrete number after understanding the case.
Do you charge for the first meeting or the assessment?
No. The initial conversation and the assessment of whether automating makes sense are free. If the conclusion is that nothing should be done, we'll tell you that too.
How do I know the budget won't blow up?
Because projects are split into stages with defined scope, and any change is quoted and agreed before it's carried out. No work happens without prior approval.
What happens after the warranty month?
Maintenance is optional. The code is on your server, so your own team can maintain it. If you'd rather we did it, that's agreed separately.
Does the code belong to my company?
Yes, and it sits on your server from the outset. We don't retain the code or the access: if tomorrow you want to change vendors, you can.
Can we start with something small?
That's what we recommend. A bounded scope that works end to end is delivered quickly, can be measured, and lowers the risk on both sides before committing to a large project.
Tell us which process you'd like to improve
We'll look at how it works today and send back a concrete diagnostic: what to automate, how, and what result to expect. No cost, no commitment.