How we scope and quote

We quote a number before you commit. This is how we get there.

What we need from you#

• What the business does today, in plain language.
• What is not working, and who feels it.
• What you would like to be true in six months.

You do not need a specification. Writing one is part of the work.

What you get back#

• A scope: what is included, and explicitly what is not.
• A number, and what it covers.
• A timeline with the decision points marked.
• The monthly running cost — servers, backups, monitoring, third-party APIs.

Why running cost is in every quote#

A build quote alone is half the picture. Software costs money every month it exists. A partner who cannot tell you that number before building has not sized the infrastructure, and that is where surprise bills come from.

When we say no#

If an off-the-shelf product fits your process, we will tell you to buy it. If the problem is not software, we will say that too. We would rather lose the work than deliver something you did not need.