Contracts
Value, term, renewal, and retainer periods, with the value it was signed at frozen so scope creep has something to show against.
Bill from what actually happened, not from a spreadsheet rebuild.
Every piece that makes this work, and what each one is actually for.
Value, term, renewal, and retainer periods, with the value it was signed at frozen so scope creep has something to show against.
A slice of contract value with an owning team and its own billing type. This is what lets one agreement carry fixed fee and hourly work at the same time, and it is the unit a project budget draws its funding from.
Drawn from approved hours, milestones, fixed fees, and reimbursable expenses, and pointed at the deliverable they belong to.
Balance and burn per period, calculated from real entries, and visible to the client if you want it to be.
Receipts captured on the go and posted to the right project, with an approval path and a route onto the invoice.
Planned billing laid out ahead of time, so forecast revenue and issued revenue are the same shape.
Payment tracking, account balances, and aging views tied to the client record they belong to. The chase list writes itself.
The other side of the ledger. What you owe subcontractors, tied to the work it paid for.
A won deal converts into a draft contract and its deliverables in one move, and the value it was sold at is frozen at that moment. Every deliverable carries its own billing type, which is what lets one agreement mix fixed fee and time and materials. Invoices point at the deliverable they came from, so recognized, invoiced, and collected stay three separate numbers instead of one hopeful one.
The long version, because this is where the category has real objections.
Yes, and this is the piece most tools get wrong. A contract splits into deliverables, and each deliverable carries its own billing type: fixed fee, time and materials, milestone, or retainer. One agreement can bill a discovery phase at a fixed price and the build hourly, and each invoice knows exactly which slice of the contract it draws down.
Each slice of contract value bills its own way.
Scope creep has something to show against.
Coverage is computed, not asserted.
Approved hours, milestones, fixed fees, and reimbursable expenses, each pointed at the deliverable it belongs to. Nothing is re-typed from a spreadsheet, so the invoice ties back to the work that earned it, line by line, when the client asks where a number came from.
Retainer periods follow the contract anniversary, and the burn is calculated from real approved entries rather than someone’s recollection. You see the balance, the client can see it too if you choose, and the month the retainer stops covering the work is the month you find out, not the quarter after.
Payment tracking, account balances, and aging views sit on the client record, next to the projects and the contract. The awkward conversation about the unpaid invoice happens with the full relationship in view, and the chase list orders itself by age without a Friday spreadsheet rebuild.
Yes. Deliverables slice a contract into billable units, each with its own type: fixed fee, hourly, milestone, or retainer, all on one agreement.
From approved hours, milestones, fixed fees, and expenses. Each line traces to the deliverable and the work behind it, with nothing re-typed.
From real approved time entries per period. Balance and burn are computed, and can be shared into the client portal if you want them visible.
Yes. Payment tracking, balances, and aging views live on the client record, so receivables sit next to the relationship they belong to.
Expenses with receipt capture and approvals, contractor invoices tied to the work they paid for, and suppliers with terms and purchase history.
Yes. Planned billing is laid out ahead of time, so forecast revenue and issued revenue keep the same shape and the gap between them is visible.
Scrambl is one workspace, so the records here are the same records the rest of the platform reads. These pair with it most often.