Send a description of what you need and you get a written scope and a fixed price before any work is billed. The first conversation is about the problem and costs nothing. If NUZM is not the right fit, we say so on that call rather than in month four.
What happens after you send this
- A reply within two working days. From a person, not an autoresponder.
- A short call. Thirty minutes about what the software has to do, who will use it, and when you need it working. No presentation.
- A written scope. What is being built, what is not, and what happens when something changes.
- A fixed price against that scope. The number you approve is the number you pay. Changes are quoted separately before they are built.
What to include so the quote is useful
Three things make the difference between a real quote and a guess: what the software has to do, who will use it, and when you need it working. A list of features helps; a description of the process you are trying to fix helps more. If you have an existing site or system, include its address so we can check the technical starting point before quoting.
What drives the price
How much of the work is custom rather than configured, how many other systems it has to talk to, and how much existing data has to be migrated and cleaned. Page count barely matters. Data migration is the most underestimated item in most quotes, so it is scoped and priced separately rather than folded in and discovered in week nine.
Tell us about the project
Enough detail to price it: what it has to do, who will use it, and when you need it working.