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.
Industries / Software houses
The estimate said 40 days. What did the project actually cost?
Custom development and maintenance retainers in one system: from quote to actuals, with people’s hours feeding the margin instead of a spreadsheet.
Book a demo Measured in days estimated against days spent
How it goes today
Retainers get forgotten
Maintenance, hosting, resold licences: small recurring items nobody re-bills until someone notices at year end.
Change requests vanish
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.
With Hakubase
01
The estimate becomes the plan
Quote lines become project tasks with the estimated days already in them. Actuals compare against the estimate without rebuilding it.
02
Retainers and projects together
One contract holds the fixed-price project and the recurring fee. The billing queue proposes each when it matures, on its own cadence.
03
Margin per project, not per year
Cost of hours, external costs and expenses land on the single project. You know which client pays and which one you are funding.
04
Planning that knows about holidays
Per-person capacity, dependencies and critical path. Overload shows before the delivery date, not after.
The modules that matter here
The core includes everything: these are the ones you open first.
Quotes From catalog to tracked PDF Contracts Value, recurrence, signature Projects and tasks List, kanban, Gantt, hours Planning Gantt, capacity, critical path Costs and margins Actual margins, measured Billing A queue fed by the cycle
All features → Built to stay.
Start on your own with the trial, or let us walk you through it.
No newsletter. We only write to set up the demo.