16 August 2026
Project profitability with bandwidth and day hours
Studios lose margin when fee is clear but people cost is fuzzy. Beech models cost from CTC, the hours someone marks on a day, and how much of them belongs to each project.
Three inputs
- CTC — monthly employer cost for each person (Settings → Finance).
- Day hours — My Hours week grid: enter 8.5, or 4 for a half day. Fill by end of week if you prefer.
- Bandwidth % — on the project Financials tab, how much of that person’s day goes to this job (e.g. 60%).
The allocation
Hours on a project = day hours × bandwidth. Cost uses hourly rate from CTC ÷ (working days × standard day hours), then the firm’s loaded cost multiplier. Example: 8.5h × 60% = 5.1h costed to that project.
Timers are for tasks, not rupees
The global timer dock (pause, multi-task, stop) writes task time logs for effort detail. Profitability uses day hours + bandwidth — so forgetting a timer no longer breaks the P&L.
Burn and invoices
Expected revenue comes from lump sum, per-sqft, or % of budget. Burn % = cost so far ÷ fee. Managers see the burn signal only; Admins see rupees, stages, GST invoices, and the firm ledger.
Full reference: Finance in the user guide