The Investment group of Context has two tabs. Investment balance shows where your teams' time and cost went, by category. CAPEX/OPEX shows which part of that cost your accounting can record as an asset (CAPEX) and which part is the month's expense (OPEX), at the level you pick: initiative, epic, label, asset or item. Leanmote measures the time and the cost and decides what is CAPEX with the evidence it finds; a person in your company can always review that decision.
CAPEX — the cost of building new software. Your accounting records it as an asset, not as the month's expense.
OPEX — the month's expense: research, fixes, support and maintenance.
The tabs
Investment balance uses the categories of your Work Classification (for example Feature, Improvement, Bug and Support):
Cost of the period — the time people spent on the view's work × their cost per hour, plus AI tools. A bar splits it into People and AI tools. See details opens its Work, People and AI tools, a tab each; its ⋯ menu exports the tab shown to CSV, or the three in one file with Export all tabs to CSV.
Top category — the category that took the most time.
Against target — the category most over its target, in points; being under a target is fine. With none over, it says On target, and No targets while no category has one.
Without a category — the share of the cost that went to work with no category. Categorize the work gives it one.
Cost by category — one bar per month, and the whole period as a donut beside it. Each category shows everything it cost: its people and its AI tools. Cost, % of time and Full-time people (FTE) switch the unit; 1 FTE is one person working the whole month. Hovering a bar or the donut shows each category's % of time and its target. View as table shows the same figures as rows. Categories picks the classification the tab is measured by. An epic has no cost of its own: its cost is the cost of what is inside it. Work logged on the epic itself counts in the categories of its items, by what each of them cost that month, or in the whole period when it had none that month; an epic with no items is Without a category. Items never take their category from an epic. The total does not change. A filter on Cost of the period also measures this chart.
By team — each team's people, cost (with its AI tools) and a bar of where its time went, with every category named.
Each figure shows its change against the previous period of the same length; hover it to see the dates it compares.
CAPEX/OPEX:
Capitalized (CAPEX) — the cost that is CAPEX.
Expense (OPEX) — everything else, with its main reasons.
Decided by Leanmote — the CAPEX nobody has reviewed yet: Leanmote decided it with the evidence of each condition (merged pull requests, finished items, people working).
CAPEX vs OPEX by month — one bar per month with the share that is CAPEX. Select a month to see its work.
Classification — what decides the CAPEX of each part of the work, at the level you pick, with its cost, treatment and decision.
Every card with a table has Export to CSV in its ⋮ menu.
Who sees the tabs
Owners see both tabs. To give them to someone else, give their access level the View Investment permission in Settings → Access levels. Whoever sees them sees every amount, and can review decisions, categorize work and set both tabs up. Pick the Investment and CAPEX/OPEX idea in New view to create a view with both tabs, or add either one from Add a tab → Templates → Investment. They are never shown on a view's public link.
Categorizing work
In Without a category, select Categorize the work. Each row is an epic, which categorizes all its work, or an item without an epic. Choose its category in Category. Pull requests not linked to a task can't be categorized.
Classification
In the card's title, Classify by picks the level: the levels of your tool (for example initiative or epic), Label when a label groups your work, Asset when assets are on, and Item. Every level adds up to the same CAPEX and OPEX. Each view remembers the last level picked.
Cost — select it to see where it comes from: the measured time or the logged hours, the people, the AI tools and the source. Work logged directly on an epic, not on an item under it, shows as Own work.
Phase — Research, Building, After launch or Maintenance.
Treatment — CAPEX, OPEX, Mixed when only part of it is CAPEX, or Pending.
Decision — who decided it, and in grey why. Its (i) explains each kind.
Select a row's name to see its items. Each column has a filter.
The Decision of a row is one of these:
Manual — someone changed it by hand, with their reason. It beats everything else.
Rule — a rule of Always OPEX sends it to OPEX.
Inherited — it takes what was decided for its epic or the level above.
Leanmote — Leanmote decided it with the evidence of each condition, and nobody has reviewed it yet.
Pending — Leanmote lacks evidence for some condition. It counts as OPEX until there is evidence or someone reviews it.
By item — the row decides nothing: each of its items decides. That is the case of an epic that groups a period, and of the No … row, which gathers the work with nothing at that level.
Category — its category is always OPEX.
In service — its in-service date is confirmed.
How a decision is made
An epic decides for all its work, and its items inherit that decision. A change by hand comes first; then the rules of Always OPEX; then what the epic or the level above decided; otherwise Leanmote decides, with the evidence for each condition of your accounting standard. The work of a category set to Yes, it can be CAPEX counts as Building while the epic is open, and as After launch, which is OPEX, from the month after it is done.
To review a decision:
In Classification, select its decision. The window has a tab for the epic and one for its Items.
Decided by Leanmote · see reasons shows the evidence Leanmote found for each condition.
Check its Category. Changing it also changes where its cost shows in Investment balance.
In What kind of work is it?, pick Research, Building, After launch or Maintenance. After launch and maintenance are always OPEX; under IFRS, research is too.
Confirm the conditions of your accounting standard: six under IFRS, two under US GAAP. Select all ticks them all. The last one, that its cost can be measured reliably, is always met because Leanmote measures it. Its cost is CAPEX only when all of them are confirmed.
Lower Share of its cost that is CAPEX if part of the epic is not new functionality. It is usually 100%.
In From, pick the month the decision counts from. Before it, Leanmote decides with the evidence.
An epic that gathers unrelated work, such as the work of a quarter, should not decide for it: tick Groups the work of a period (container epic) and each of its items decides.
In Items, each item has its Treatment: pick CAPEX or OPEX and write the reason. ↺ takes it back to what it inherits.
To change many items at once, pick Item in Classify by and tick their rows; the box in the header selects everything filtered. In Change treatment to…, pick Make CAPEX, Make OPEX, Remove override (back to inherited) or Change category, write one reason for all and select Apply. Undo reverts the whole change.
Always OPEX
Support, production bugs and incidents are an expense even when their epic is CAPEX. In Settings → Organization Settings → Tabs → CAPEX/OPEX → Rules, Always OPEX lists the rules that send that work to OPEX: External and production bugs, Support and request types, Support tools, Linked to an incident, These labels and These boards. Turn on the ones that apply and choose the labels and boards. If an item matches more than one, its row shows the reason highest in the list; the arrows change the order. An item can still be changed by hand.
Epics that group a period: an epic named after a month or a quarter («oct2026», «Q4») gathers unrelated work, so it decides nothing and each of its items decides. In Also an epic of a period when its title contains, add other words, separated by commas.
Assets
If your accounting capitalizes by asset (the payments platform, the mobile app), turn on Classify by asset in Settings → Organization Settings → Tabs → CAPEX/OPEX → Assets. It is off by default, and while it is off the tab shows nothing about assets.
Select Add asset and fill in its Accounting code (the one in your ERP), its Name in Leanmote and a Description of what belongs to it. Leanmote compares the description with the title, board and labels of each epic to suggest an asset.
Optionally, in Rules, select Add rule to send everything on a board or with a label to an asset.
In Classification, the Asset column shows each row's asset and where it comes from. Pick another to change it: its items follow. No asset leaves it without one, and ↺ takes it back to the inherited or suggested one.
Classify by then also offers Asset, Set asset… changes many items at once, and the accounting export groups the CAPEX by asset, with its code. Archive stops offering an asset and keeps its history.
In-service date
Once the date a unit went into use is confirmed, its cost is OPEX (After launch) from the following month, or from that same month if the date is the 1st. The In service column shows each unit's date at the biggest level (at Asset when assets are on), with where it comes from: the release that shipped it; if there is none, its first production deploy after its last merged pull request; otherwise the day it went to Done.
A Proposed date changes nothing until someone confirms it. Select the date, change it if needed, and select Confirm. A Confirmed date applies to everything under that unit or asset.
Discarded work
When work with CAPEX is discarded, its CAPEX is written off in the month of the discard. Its row shows Discarded with the amount written off and the date, and the row of its epic shows Items written off. The accounting export lists them in a Write-offs sheet.
Exporting for accounting
The ⋮ menu of Classification has Download for accounting (XLSX), Previous exports and Download timesheets (CSV).
The XLSX has a summary, the classification, the items, the decisions and your accounting standard, plus Assets when assets are on and Write-offs when work was discarded in the period.
Leanmote keeps a copy of each download. Previous exports lists them with when, who and the period, and downloads each one again, identical.
When the figures changed since the previous export of the view with the same filters, the download says so, and the file has a Changes sheet with each change and its cause: Decision changed, Cost or rate recomputed, New item, Item reassigned, Item no longer there or Configuration changed.
The timesheets name people, so they take access to the Investment tabs or permission to see cost.
Settings
Whoever sees the tabs sets them up in Settings → Organization Settings → Tabs, one page per tab. A change applies to every view of the organization.
Investment balance has Target by category: optionally, the most % of time you aim for each category to take, from 0 to 100. By team then says On target, Over target or Over target 3 months in a row, Against target shows the category most over its target, and Cost by category draws it as a dotted line in % of time.
CAPEX/OPEX has four tabs:
Levels — how the types of work in your tool stack up, from the biggest to the smallest: Initiative or project, Epic or parent and Item. Leanmote suggests it from your tool; change a type if it does not fit. The types that are just items wait under Other types. Classification opens at picks the level the card opens with; Automatic is the biggest level with at least half of the cost. Label that groups work adds a Label level, one group per value (for example «product:»).
Rules — Always OPEX and Epics that group a period, explained above.
Accounting policy — in Accounting standard, pick IFRS · international or US GAAP · United States. If you are not sure, ask your accountant: most companies outside the United States use IFRS. In Categories, each row is a category of your Work Classification; in Can it be CAPEX?, pick Yes, it can be CAPEX when its work can be building new software, or No, always OPEX for fixes, support or maintenance.
Assets — explained above.
With the Roadmap classification, Feature, Improvement and Epic start as Yes, it can be CAPEX, and Bug, Support, Task and Research as No, always OPEX. In your own classification every category starts as Yes, it can be CAPEX. In Work Classification, Create Balance framework breakdown creates a classification with Build new, Improve existing, Productivity and KTLO and selects it for these tabs; everything stays editable.
Where the numbers come from
Time — the option chosen in Users → Roles & salary → Time used to calculate cost, one for the whole organization: the time logged in your tools that log hours (Jira, Azure DevOps, ClickUp or Monday), or Effort from activity, which works out each person's time from their commits, pull requests, reviews, comments and tasks in progress, with nobody logging hours. Until someone chooses, Leanmote uses the one with more data and says why.
Cost per hour — each person's salary in Roles & salary. Someone without a salary costs the Hourly cost set at the top of that page.
Time not linked to a task shows as Not linked to a task, and a business day with no activity as No recorded activity. Both count as OPEX.
Shared accounts — an account (Git, board, calendar) that belongs to more than one person counts for nobody. The tab names those accounts; they are fixed in Users.
Salaries stay private — owners and access levels with View Investment see every amount. Anyone else who reaches these figures without permission to see cost gets no amounts for a row of fewer than 3 people (Hidden: fewer than 3 people).
Figures are recalculated once a day. Every See … link opens the rows behind its figure, with a filter on each column and Export to CSV. Filtering those rows measures the figure with the filter for everyone who opens the view: the card shows the filter under its title, and its × removes it. By team can be filtered by team, and Classification by each column.
Related articles
