Leanmote reads the tools your team already works in — GitHub, Jira, Slack, your calendar — and turns that activity into a picture of how delivery is actually going. Nobody fills in a form; the data is the work itself.
What you can do with it
See delivery health: cycle time, throughput, where work waits.
Track the DORA metrics without building the pipeline to compute them.
Understand where engineering time and money go, by team and by project.
Measure what AI tooling is actually changing about your delivery.
How it's organized
The sidebar is the map. Two things are the same for everyone:
Actions Hub — what is asking for a decision: Insights (bottlenecks Leanmote detected, what you are acting on, what you resolved), Alerts (rules that notify you when a metric crosses a threshold you set) and Agents.
Administration — the setup: Integrations, Boards, Discoveries, Users, Teams and Settings.
My Metrics, your own numbers, is in your account menu.
Where the metrics themselves live depends on your organization, because Leanmote is in the middle of a change. Look at your sidebar and match it to one of these:
If you see Context. That's the newer layout, and it's what every organization created recently starts on. You open a view: a name, the teams it covers, and the tabs it shows. Delivery, cost and AI are all tabs of one view, sharing one set of filters, and views you pin sit right under it. Strategic Overview stays its own entry. What is Context? covers it properly.
If you see Performance Delivery, Project Financials and AI Return. That's the layout most organizations are still on, and nothing about it is going away under your feet. Each is its own destination with its own filters: Performance Delivery for the weekly operating view, Project Financials for effort and cost, AI Return for AI adoption and impact, Strategic Overview for the executive read.
Both layouts show the same metrics and compute them the same way. What changes is how you get to them — so when an article mentions a screen you can't find, this is usually why.
Setup is guided, and it depends on who you are
The first time you sign in, Leanmote opens a setup that matches your access level. It saves as you go — you can leave and come back.
If you are… | You get |
Owner | Seven steps: name the organization, pick and connect tools, review the people found, build teams, match accounts, and set up a view per team. |
Manager | One step: connect your tools. |
Team Leader | Three steps: connect your tools, your team, your views. |
Collaborator | One step, and you can skip it: connect your tools. |
Only two things can't be left for later: naming the organization and connecting at least one tool — with nothing connected there's nothing to show you. Everything else says so on its own button, and names where the work waits if you skip it.
One thing worth knowing early
Tool credentials are per person, not per organization. Your organization having GitHub connected doesn't mean your work is being read — that happens when you connect your own account. This is why every access level, down to Collaborator, gets asked to connect tools.
What to expect after setup
Leanmote starts pulling history immediately. How far back depends on the tool and what you chose. Your views fill in as the data lands, so the first hours look emptier than the first day.
Two things commonly need a second pass, and both say so during setup:
Accounts that couldn't be matched to a person wait in Discoveries. Until someone is matched, their work counts toward nobody.
Statuses Leanmote couldn't classify wait there too. Those decide what counts as active work versus waiting, so they move your numbers.
Need help?
The Messenger in the bottom-right reaches our team. Include the view and tab, the time range and what you expected to see — it's the difference between a same-day answer and a conversation.
Next steps
What is Context?
Quick start: your first 30 minutes
Connect your first integrations
Run your first sync and open your first view