Home/Product/Estimate & budget

Estimate & budget

Price it before you sign it. Then watch it.

The estimator and the margin calculator sit above the projects rather than inside one, because you size an engagement before it exists. When it becomes real, the same numbers become the budget you are measured against.

Estimator

Pick the modules in scope and get hours, price, duration and gross margin out the other side. Creating a project from an estimate carries the module complexity straight into the plan as scope multipliers, so the plan starts where the estimate landed.

  • Module list in, hours out
  • Respects the advisory or delivery multiplier
  • Returns duration, not just cost
  • Shared across every project you run

Margin calculator

Test what a discount actually does. Rate, hour count, discount and cost of acquisition against your cost basis, so the answer to "can we take ten percent off" is a number rather than a feeling in the room.

  • Rate and hours against real cost basis
  • Discount modelled explicitly
  • Acquisition cost included
  • Answers the question before the call, not after

Budget

Four assumptions, and then arithmetic.

The budget tab does not ask you to maintain a second model. It takes the planned hours already in the WBS and applies your assumptions to them.

LineHow it is calculatedDefault
LabourPlanned hours × hourly rate$250/hr
Travel & ExpenseLabour × expense contingency10%
Scope ContingencyLabour × scope contingency15%
Planned vs ActualBy phase, from actual hours recorded on tasks

Defaults are the shipped starting point. Every one of them is yours to change per project.

Contingency is carried, not buried. Scope contingency sits on its own line rather than being smeared across task estimates. When a client asks what the number is made of, you can show them — and when you burn into contingency, you can see that happening instead of discovering it at 90% complete.

Planned against actual, by phase

Actual hours are recorded on tasks and roll up by phase. Design running 40% over while build runs under is a very different conversation from a project that is simply over, and the phase split is what makes that visible early enough to act on.

Why it sits above the project

Because you price things you do not win.

Estimator and margin calculator are shared tabs, not per-project ones. Size five opportunities, win two, and only those two ever become projects — without five abandoned workspaces to tidy up afterwards.

Check the two agree once the project exists. The estimator carries its own module hours and the WBS carries its own task hours. They start aligned and they can drift as you trim tasks and set multipliers, so the setup routine ends by comparing planned hours and planned cost against what you sold. If they have separated, that is worth knowing in week one.

Find out what the discount costs before you offer it.