The estimate lives elsewhere
It starts in a spreadsheet, the project starts in a task tool, the hours end up in a third place. Sold against spent arrives once the project is closed.
Custom development and maintenance retainers in one system: from quote to actuals, and people’s hours landing on the margin of the project they were spent on.
It starts in a spreadsheet, the project starts in a task tool, the hours end up in a third place. Sold against spent arrives once the project is closed.
Maintenance, hosting, resold licences: small recurring items nobody re-bills until someone notices at year end.
The change agreed over a call never reaches the contract and never reaches the invoice. It becomes work given away.
The risk for a software house is not selling too little: it is selling at a price set on an estimate nobody checked again.
Quote lines become project tasks with the estimated days already in them. Actuals compare against the estimate without rebuilding it.
One contract holds the fixed-price project and the recurring fee. The billing queue proposes each when it matures, on its own cadence.
Cost of hours, external costs and expenses land on the single project. You know which client pays and which one you are funding.
Per-person capacity, dependencies and critical path. If the developer holding the critical path is on holiday the week of the release, the plan shows it while you still have time to move something.
They are all in the core. These are the ones a company like yours opens first.
You can open a trial workspace on your own, or write to us and we will show it to you starting from the problem you have.
No newsletter. We only write to set up the demo.