Key takeaways
- Service-based budgeting splits one client budget into services, each with its own billing model, estimate and value: for example a fixed-price discovery phase, Time & Materials development and a monthly support retainer.
- It solves the mixed-billing problem. A single project-level budget can only tell you the total burn. Service-based budgets show which deliverable is on track, which is overrunning and which is profitable.
- It works best when services are tied to the work. Linking each service to Jira epics and work items means every worklog lands on the right service automatically, with no manual allocation at month-end.
- In Worklog360, the budget is the backbone of the client project. Worklogs fill it, the Scheduler forecasts it, and invoices are generated from the budget and the worklogs within it.
Most client projects don’t come with one price tag.
The proposal says discovery is a fixed €8,000. Development is billed by the hour. Support after launch is €2,000 a month. Three commercial agreements, one client, one Jira project.
Then the project starts, and all of it gets tracked against a single budget number. By month two, the dashboard says the project is 40% spent. But nobody can tell whether that is healthy or a disaster, because 40% of what? The fixed-price phase might already be underwater while development is comfortably on track.
This is the gap service-based budgeting closes. In this guide, we explain what it is, why a single project budget breaks for mixed-billing work, and how to set it up in Jira so every logged hour lands in the right place.
What is service-based budgeting?
Service-based budgeting is a way of structuring a client project budget as a set of services or deliverables, each with its own billing model, estimated effort and financial value. Instead of tracking one total for the whole project, you track spend, progress, profitability and invoicing separately for each service.
A “service” is any part of the work that the client buys on its own terms. Typical examples in software and digital agencies:
- Discovery and requirements, sold as a fixed price
- UX/UI design, sold as a fixed price
- Software development, billed as Time & Materials
- Testing and QA, billed as Time & Materials
- Support and maintenance, billed as a monthly retainer
Each service carries its own estimate (hours or quantity), its billing type and its value. Together, the services add up to the total project budget, but each one can be monitored, forecast and invoiced on its own.
The idea is simple: budget the project the way you sold it. If the proposal had five lines with three different pricing models, the budget should too.
Why one budget per project breaks for mixed billing and multi-phase projects
A single project budget works well when the whole project is sold one way. The moment a client deal mixes billing models or spans multiple project phases, it starts hiding the numbers that matter.
1. Fixed-price overruns disappear into the total. If the €8,000 discovery phase has consumed €11,000 worth of hours, that loss is real. But inside a €60,000 project budget it looks like normal progress. You only find out at the end, when the margin is gone.
2. T&M and fixed-price work behave differently. On Time & Materials, more hours mean more revenue. On fixed price, more hours mean less profit. Mixing them in one number means you can’t tell if a busy week was good or bad news.
3. Retainers need their own rhythm. A retainer is consumed month by month. Tracking it inside a project-level budget makes it hard to see whether this month’s allowance is used up, or whether the client is getting more than they pay for.
4. Invoicing becomes a spreadsheet exercise. At month-end, someone has to work out which hours belong to which part of the deal, which fixed amounts are due, and which retainer fee applies. That’s where hours go missing and invoices get delayed.
5. Profitability is only visible at project level. Leadership can see that a project made 18% margin, but not that development made 30% while design lost money. Without that, the next proposal repeats the same pricing mistake.
As we’ve seen running software delivery teams for nearly 20 years, the problem is rarely that agencies don’t track time. It’s that the time isn’t tracked against the commercial agreement it belongs to.
Simple budgets vs service-based budgets
Not every project needs services. A simple budget is still the right choice when the whole project is sold one way.
| Simple budget | Service-based budget |
|---|
Structure | One total for the project or client | Several services that add up to the total |
Billing models | One (T&M, Fixed Price or Retainer) | Different per service |
Tracking | Overall hours or value consumed | Hours and value per service, plus the total |
Overrun visibility | Project level | Per deliverable |
Profitability | Project level | Per service and project |
Invoicing | From the budget’s worklogs | From the budget and the worklogs within each service |
Best for | Pure T&M projects, single retainers, internal budgets | Proposals that mix fixed price, T&M and retainers |
A simple rule: if your proposal or statement of work has more than one pricing model or multiple phases use a service-based budget. If it has one, a simple budget is enough.
How to run service-based budgeting in Jira with Worklog360
Jira tracks the work, but it has no concept of budgets, billing models or client invoices. Worklog360 adds that financial layer inside Jira Cloud. Here is how a service-based budget is set up and run, step by step.
- Add the client. Keep one client list in Worklog360 and link each client to its projects, budgets, reports and invoices.
- Create the budget. In the Budgets tab under Financials, create a budget for the client project and choose a service-based budget instead of a simple one. Decide whether progress is tracked by hours, by monetary value, or both.
- Add the services. Break the budget into services that match the proposal. For each one, set its billing type (Time & Materials, Fixed Price or Retainer), estimated effort or quantity, and financial value.
- Link services to Jira work. Connect each service to the Jira epics and work items that deliver it. From then on, worklogs are associated with the right service automatically as people log time.
- Set your rates. Define billable and cost rates by user, role, project or even individual worklog, so every hour converts into revenue and cost correctly.
- Schedule the team. Plan people against the project’s issues in the Scheduler. The budget’s forecast is based on who is scheduled, so you can see where each service is heading, not just where it is today.
- Log and approve time. The team logs time from Jira issues, timers, the calendar or timesheets, as usual. Managers approve timesheets or individual worklogs before anything is billed.
- Monitor each service in real time. The budget dashboard shows hours logged, budget consumed, percentage used, remaining budget, and amounts ready for invoicing or already invoiced. If time landed in the wrong place, reassign it to the correct budget.
- Invoice from the budget. At the end of the period, generate the invoice from the budget and the approved worklogs within it. Invoices carry your company logo, export to PDF or Excel or sync to QuickBooks Online, and the included worklogs are marked as invoiced so nothing is billed twice.
- Review and learn. When the project closes, compare budget vs actual per service. It shows exactly which deliverables were estimated well and which need different pricing next time.
Worked example: the same project, two ways of budgeting
Pixelforge Studio, a software agency, signs a 4-month customer portal project with Northline Retail worth €60,000. The proposal has four lines:
Service | Billing model | Budget |
|---|
Discovery and requirements | Fixed price | €8,000 |
UX/UI design | Fixed price | €12,000 |
Development | Time & Materials (400 h at €80/h) | €32,000 |
Support after launch | Retainer, €2,000/month for 4 months | €8,000 |
At the end of month two, with a simple budget
The dashboard shows €28,800 consumed out of €60,000, or 48%, halfway through the project. Everyone relaxes. On paper, the project is exactly on track.
At the end of month two, with a service-based budget
The same €28,800 looks very different once it is split by service:
Service | Consumed | Used | What it tells you |
|---|
Discovery (fixed) | 110 h, €8,800 | 110% | Overran by €800. On a fixed price, that comes straight out of margin. |
UX/UI design (fixed) | 120 h, €8,400 | 70% | Delivered and approved under budget, protecting €3,600 of margin. |
Development (T&M) | 120 h, €9,600 | 30% | On track. Every hour here is billable revenue. |
Support (retainer) | €2,000 | 25% | First month of four, as planned. |
For fixed-price services, “consumed” is the value of logged hours at Pixelforge’s rates, which shows the internal cost of delivering them.
Now the delivery lead knows something the 48% hid: discovery was underestimated. The design savings cover it this time, but the next proposal needs a bigger discovery estimate. And because the Scheduler forecast shows development staffing for the next two months, the team can check whether the remaining 280 development hours fit the plan before the client asks.
At month-end, finance generates Northline’s invoice from the budget and its approved worklogs, including the 120 development hours (€9,600). The included worklogs are marked as invoiced, so next month starts with a clean slate.
Questions to ask before you set up service-based budgets
1. Does the budget mirror the proposal? Use the same service names and values the client signed. When budget lines match the statement of work, invoices and client conversations get much simpler.
2. How granular should services be? Group work into services the client actually pays for separately. Five clear services beat twenty tiny ones that nobody can keep track of.
3. Is every service linked to Jira work? A service without linked epics or work items won’t collect worklogs automatically. Check the links before the team starts logging.
4. Are rates set before work begins? Fixed-price profitability depends on cost and billable rates being right from day one. Changing them mid-project makes the history hard to trust.
5. Who reviews service health, and how often? A weekly look at each service, especially fixed-price ones, catches overruns while there’s still time to act.
6. What happens when scope changes? A change request is often a new service. Adding it as its own line keeps the original estimates honest and makes the extra work easy to invoice.
Final thoughts
A single project budget answers one question: how much have we spent? Service-based budgeting answers the questions that actually protect your margin. Which deliverable is overrunning? Which pricing model is working? What can we invoice this month, and for which part of the deal?
The principle is simple: budget the project the way you sold it, connect each service to the Jira work that delivers it, and let worklogs do the rest. Agencies that work this way catch fixed-price overruns in week three instead of month three, and they price the next project with real data instead of memory.
Worklog360 is built around this approach, with service-based budgets, scheduling, approvals and client invoicing in one app inside Jira Cloud. It’s free for teams of up to 10 users, and larger teams can evaluate it free for 30 days.
FAQ
What is service-based budgeting? Service-based budgeting structures a client project budget as a set of services or deliverables, each with its own billing model, estimated effort and value. Spend, profitability and invoicing are tracked per service instead of only for the whole project.
What is the difference between a simple budget and a service-based budget? A simple budget tracks one total for a project or client under one billing model. A service-based budget splits that total into services that can each be Fixed Price, Time & Materials or Retainer.
When should an agency use service-based budgeting? Whenever a client deal mixes pricing models, for example a fixed-price discovery phase, hourly development and a monthly support retainer. If the whole project is sold one way, a simple budget is enough.
Can Jira do service-based budgeting on its own? No. Jira records worklogs but has no budgets, billing models or rates. You need a Jira app such as Worklog360 to add budgets, services and invoicing on top of Jira worklogs.
How do worklogs get assigned to the right service in Worklog360? Each service is linked to Jira epics and work items. When someone logs time on that work, the worklog is associated with the service automatically.
How is a service-based budget invoiced in Worklog360? Invoices are generated from the budget and the approved worklogs within it. They can carry your company logo, export to PDF or Excel or sync to QuickBooks Online, and the included worklogs are marked as invoiced.
Is Worklog360 free? Worklog360 is free for teams of up to 10 users. Larger teams can evaluate it free for 30 days through the Atlassian Marketplace.
