Budgeting per deliverable in Jira Cloud: fixed fee, T&M and retainer in one deal
Also published on Atlassian Community
In this guide
A typical client deal rarely has one billing shape. Discovery is a fixed fee, the build runs Time and Materials, and support sits on a monthly retainer. The work still lands in one Jira space. The question is how you mark each deliverable, read hours against it, and bring money and revenue modes in.
MarginRadar is a Forge app from Radrly that turns Jira Cloud worklogs into cost, budget and margin. This guide starts with what native Jira already gives you for splitting one client's work into deliverables, then covers what the app adds when the same deal mixes billing models. Advanced-only features are labelled (Advanced).
Mark the deliverables in native Jira
Jira does not know about fixed fees, retainers or billable rates. It does let you group work so each deliverable has a stable handle you can filter on.
Epics. An epic is a larger body of work that spans several sprints. Put discovery, build and support under separate epics (Manage epics in team-managed spaces).
Versions. A version is a set of features and fixes released together. Use versions when a deliverable lines up with a release, then filter with fixVersion (Configure versions in a scrum space).
Components. Components group work items around features, departments or workstreams. They suit a long-running stream such as support.
Labels. Labels are open tags on the work item (How to create and use labels in Jira Cloud). They work for a deal code shared across spaces, with the caveat that anyone can invent a new spelling.
Pick one primary axis per deal and stick to it.
Hours against each deliverable
Native time tracking covers estimates and spent time (Configure time tracking, Log time on a work item): Original Estimate, Remaining Estimate and Time Spent. Each worklog belongs to one work item.
Useful filters look like space = ACME AND parent = ACME-12, fixVersion = "2026-Q1 build", component = Support, or labels = "acme-retainer". JQL fields lists those fields. Save each query as a filter and pin it to a dashboard with Time Spent and Original Estimate columns.
Σ Time Spent, Σ Original Estimate and Σ Remaining Estimate roll up one level only. A story includes its sub-tasks; an epic includes its stories and leaves out the sub-tasks under those stories. For a deliverable total, sum plain Time Spent on the filtered list, or use Automation to look up matching work items and store the sum in a number field. Lookups are capped at 100 work items (Automation service limits), and the number is only as fresh as the last run.
None of this is money. Jira has no rates, no revenue mode and no included retainer hours. The commercial model lives in a spreadsheet or a contract PDF.
What MarginRadar adds
MarginRadar reads native Jira worklogs and multiplies them by rate cards (cost and billable rates for roles, people or a space default). Every rate has an effective date, so a worklog is costed at the rate valid on the day it was logged.
Space budget (Standard). One space has one space-level budget. Units can be money, hours or both. On Standard the revenue mode is billable rates (Time and Materials via the rate cards) or none. The space page shows spent, remaining, burn and margin.
Clients (Standard). Admin > Clients holds reusable client labels. Each space budget can carry one client key, and Portfolio can filter or group by client. Clients are labels for reporting, not a CRM or billing module.
Epic budgets and scoped budgets (Advanced). Advanced adds a budget per epic, and scoped budgets that take a version, label, component or custom JQL. Every scope is AND'd with the current space. Scoped budgets track spend against their own money and hours limits.
Fixed fee and retainer (Advanced). Advanced also adds fixed fee, and retainer (monthly fee, included hours, overage rate, optional hour rollover) on the space budget. Billing periods follow the billing day and timezone. Space budgets can have start and end dates and do not reset each month. The period report still covers this month, last month and this quarter.
Revenue mode per deliverable (Advanced). An epic budget or a scoped budget can set its own revenue model (billable rates, fixed price, retainer, or inherit the space), so one space can mix those models. A fixed price on a deliverable inside a fixed-price space is a share of the space contract, not added on top. A retainer on an epic or scope uses the monthly amount and a start date; it does not have included hours, overage or rollover.
Invoice-ready CSV (Advanced). The Report tab can export an invoice-ready CSV for one billing period, by client and deliverable, with Generic, QuickBooks, Xero and wFirma formats. The file is built in the browser. MarginRadar does not number, send or store invoices.
Forecast (Advanced). Burn forecast gives a run-out date and an estimate at completion when an end date is set. Hybrid forecast combines recent burn with remaining estimates on open work and shows a P50 to P90 run-out range.
Modelling a mixed deal in one space
The space budget still has one default revenue model. On Advanced, an epic budget or a scoped budget can override it, so one space can mix fixed price, Time and Materials and retainer deliverables. A fixed price on a deliverable inside a fixed-price space is a share of the space contract (the space fixed price plus approved change orders), not added on top. Time and Materials and retainer deliverables inside a fixed-price space are billed outside that contract. If you would rather keep each model in its own space, you can still do that and share a client label across them.
A practical pattern: one space, client ACME, Time and Materials or fixed price as the space default, a fixed-price epic budget for discovery, a version-scoped Time and Materials budget for the build, and a component-scoped retainer for support.
Honest limits
- No invoice generation. Exports include an invoice-ready CSV (Advanced) for import into an accounting tool, plus CSV, PDF (print or Save as PDF) and Markdown. MarginRadar does not number, send or store invoices.
- No resource scheduler and no capacity planner.
- One space-level budget per space. Several deliverables means epic budgets or scoped budgets (Advanced), or separate spaces.
- A retainer set on an epic or scoped budget has no included hours, overage or rollover. Those stay on the space retainer.
- Tempo and other trackers are not read directly. Their time counts once it lands in native Jira worklogs.
- Most figures live in the app and are not Jira fields. Exception (Advanced): the read-only MarginRadar budget status field on budgeted epics can be used in JQL, filters and dashboards. See Which epic is eating the budget?.
Quick answers
Does Jira Cloud know about fixed fees or retainers?
No. Jira has no rates, no revenue mode and no included retainer hours. Epics, versions, components, labels and JQL filters mark the deliverables; hours come from Time Spent and Original Estimate.
Can one Jira space have several MarginRadar space budgets?
No. One space has one space-level budget. Several deliverables at once means epic budgets or scoped budgets (Advanced), or separate spaces that share a client label.
How do you model a mixed fixed fee, T&M and retainer deal in one space?
On Advanced, set a default revenue model on the space budget, then override it on an epic budget or a scoped budget so discovery, build and support can use different models in the same space. A fixed price inside a fixed-price space is a share of the contract, not added on top. You can still put each part in its own space and share a client label if you prefer.
Does MarginRadar generate invoices?
No. Advanced can export an invoice-ready CSV for you to import into an accounting tool. MarginRadar does not number, send or store invoices. Other exports are CSV, PDF (print or Save as PDF) and Markdown. There is also no resource scheduler.