Bauhaus Software

Sizing

A price with the team and the schedule in plain sight.

Four questions turn an idea into an order of magnitude: what gets built, how much it covers, under which engagement and on what timeline. At the end you can move each role’s hours and watch the number move with them.

Before you start

This is an estimate, not a quote.

You should know what this number is before you see it, not after.

  • It comes from a public model —hours per role times their rate— and not from a review of your case. Nobody on the team has seen your system yet.
  • Rates are indicative and exclude taxes, third-party licenses, hosting and recurring cloud services.
  • The scope you pick here is the scope you assume, and the expensive part of a project usually shows up once it is opened.
  • Nothing you type is sent anywhere: the whole calculation runs in your browser and nothing is stored.

See scope and conditions in the terms and conditions.

Step 1 of 5

What needs to be built?

Pick the closest match. If you are torn between two, pick the larger one: finding out mid-project that the scope was smaller is far easier than the reverse.