How to prepare your software project (and get an accurate quote)

We do not publish fixed prices, because every project is different. What makes a quote accurate is not a long specification, but clear answers to a handful of questions. Here is what helps most, in order of importance.

1. The problem, in one sentence

"Our onboarding takes two weeks because documents arrive by email" is far more useful than "we need a portal". Describe what goes wrong today and what it costs you in time, money or customers.

2. Who will use it

List the user types: customers, staff, managers, partners. For each: what is the one thing they must be able to do? This shapes roles, permissions and the amount of screens more than anything else.

3. Must-haves versus nice-to-haves

Make two lists. The first version should solve the core problem with only the must-haves. Nice-to-haves come later, once real users have tried it. This is the single biggest lever on cost and timeline.

4. Existing systems

Which tools must it connect to? Think of accounting software, a CRM, payment providers, email or an existing database. Integrations are often where the hidden work is, so name them early.

5. Budget range

A budget range is not a trap, it is a design constraint. With €15k and €80k you can solve the same problem in very different ways. Sharing a range lets us propose the best solution within it, instead of guessing.

6. Timeline and deadlines

Is there a hard deadline (a season, a contract, an event)? Or is it "as soon as possible, but done right"? Both are fine, as long as we know.

What you do not need

• A complete technical specification
• Wireframes or designs (nice if you have them)
• Knowledge of frameworks or hosting

That is our job. In the free intro call we go through these six points together, and within two business days you receive a proposal with a clear scope, a planning and a fixed price.