How we put together estimates without a price list

Every system differs in modules, users, and flow, so we put together an estimate once your needs have been discussed.

What shapes an estimate

• Scope: which processes go into the system.
• The number and complexity of modules.
• Build stages and staged payments.

What the written proposal covers

The proposal covers scope, timeline, and staged payments. It is usually structured like this:

1. A summary of your needs and the processes that go into the system.
2. The list of modules, with the user roles that work with each one.
3. Build stages, each with a result you can check.
4. Staged payments tied to the build stages.
5. The support period after go-live and how bugs are handled.
6. Source code ownership after the final payment.