Jira Cloud app · For agencies and consultancies
Know which projects make money, before the budget is gone.
Burnwise turns the time your team already logs in Jira into project cost, budget burn, forecasts and profit, in plain words. You get an alert before a project goes over budget, not after.
- Works with
- Native Jira worklogs
- Setup
- About 5 minutes
- Payment types
- Hourly to retainer
- Reports
- 15, plus your own
Acme Corp · Fixed fee
Website rebuild
Work done 48%. Money goes faster than the work.
- Spent so far
- $6,720
- Budget
- $10,000
- Expected cost
- $13,480
- Budget runs out
- in 3 weeks
$6,240 people cost ÷ 48% work done + $480 expenses = $13,480
Where did the money go?
Timesheets tell you where the hours went. Burnwise tells you where the money went.
Your team already logs time in Jira. Burnwise prices every worklog with the right cost and billing rate for its date, adds expenses, and rolls it up by project, client, Epic and person, as the work happens.
No suite to buy, no second timesheet, and no separate capacity planner to get a forecast.
Plain words, finance terms one hover away
Every label in the app has a tooltip with a plain explanation and the finance term.
- Spent so far
- Actual cost
- Earned so far
- Recognized revenue
- Expected cost
- Estimate at completion
- Work done
- Percent complete
- Weekly spend
- Burn rate
- Ready to bill
- Unbilled WIP
Setup
From install to your first numbers in minutes.
- 1
Answer the setup wizard
Your currency, working week, roles with their cost and billing rates, and how far back to import worklogs.
- 2
Create a project
Pick the Jira work (a project, Epics, a filter or single issues), how the client pays, and the budget.
- 3
Read Home
Needs attention comes first, each item with its reason. Then this month, Ready to bill, and missing time.
The owner’s answer up front, the finance detail behind it.
Profit per project, from Jira worklogs
Cost, earnings, profit and margin per project, client, Epic and person, straight from the worklogs your team already writes. No second timesheet.
Alerts before the budget is gone
At 50, 75, 90 and 100% of the budget, when a project is expected to go over, or when the expected margin drops. The alert names the Epic that caused it.
An expected cost you can check
Expected cost at the finish from the work done, remaining estimates or weekly spend. Click ⓘ next to any number to see the sum with the real values.
Rates that respect history
Cost and billing rates by role, person, client or project, each with the date it starts. A raise never changes last quarter’s numbers. Multi-currency included.
Pay rates stay private
Project managers see project totals, never one person’s cost rate. Small groups are hidden too, so a rate cannot be worked out by subtraction.
Ready to bill, never billed twice
Invoice-ready lines by role, person or issue, exported as CSV. Mark the hours as billed and they leave Ready to bill. Budget changes need a finance approval, and every change is in the audit log.
Also in the box: a weekly timesheet with a timer and approvals, missing-time reminders, a Jira issue panel and project tab, dashboard gadgets, and CSV export of any report.
Your data
Built on Atlassian Forge, with the narrowest permissions.
Burnwise’s data lives in your Atlassian site’s Forge storage, one database per installation. It asks Jira to read work and users, and to write worklogs only as the signed-in person, so Jira’s own permissions still apply.
Email alerts are the one thing that leaves Atlassian. When a person turns them on, Burnwise sends their email address, the project name and the alert text to Transactful’s email server, which delivers it through Amazon SES. Individual rates are never in an email.
Do my people need to log time somewhere new?
No. Burnwise reads the native Jira worklogs your team already writes. Its own timesheet is optional, and it saves straight to Jira as ordinary worklogs.
Who is Burnwise for?
Agencies, consultancies and other teams that bill clients for time in Jira, or that run internal projects against a budget. The owner gets plain answers; finance gets the detail behind them.
How do you work out the expected cost?
By default: spent so far ÷ work done, where work done comes from hours logged and the remaining estimates in Jira. You can pick remaining estimates, weekly spend or a manual figure per project instead. Every method is written out in the docs.
Can project managers see what people are paid?
Not with Keep pay rates private on. They see project totals; person and worklog rows show hours only, and groups of fewer than three people are hidden.
What about fixed-fee, retainer and milestone projects?
Each project has its own payment type: hourly, fixed fee, retainer, milestones or internal. Earnings follow the type, so a fixed-fee project shows how much work went beyond the fee.
Where is our data kept?
In your Atlassian site’s Forge storage, one database per installation. The only thing that leaves Atlassian is an alert email, and only for people who turn email alerts on.
See which projects make money.
Install, run the setup wizard, create a project. 3 guides cover the rest.