How it works
See what your teams are doing without asking them.
An event goes in, a card comes out. Your teams already close, ship, sell and resolve things; that is the input. Nobody logs anything or fills in a form.
The loop
How it works
- 01
Someone does the work
A pull request goes in. A ticket closes. A deal lands. It happens where it already happens, in the tool your team already uses.
- 02
It counts, immediately
Within seconds it is on a board. No overnight batch, no waiting until Monday to find out how last week went.
- 03
It only counts once
Systems send things twice. Yours will. Nobody gets credit for the same piece of work twice, and you never have to think about it.
- 04
Sometimes it pays out
Your rules decide what earns a card and how often. A merge might always pay; shipping on a Friday with no incident might pay better.
Numbers you can defend
The board is right, so nobody argues about it.
A leaderboard loses a team’s trust the moment someone notices a colleague’s number is inflated. Retries, re-imports, reopened work and renamed accounts never reach the board.
- Re-import your last 90 days as often as you like; nobody’s total moves
Adaandadaare one person, not two rows- Link someone’s second account and the work they already did comes with it
- Bots stay off the board, and a deploy credits whoever’s work shipped
What happens when
- The same event arrives twice
- Counted once
- A re-import overlaps live work
- Counted once
- Someone reopens and re-merges
- Counted once
- Someone changes their username
- Still the same person
- A bot opens the pull request
- The author gets the credit
What you control
A rule is four clauses and no code.
When this happens, and this is true, award that, to them. Written in the product in about a minute, and changed the same way, with no support ticket, no call, and no release.
What earns what
Say what earns a card and how good a card it should be. Two rules can fire on the same event and reward two different people, such as the reviewer and the author.
What counts
Whatever your team measures, named however you name it. No list of supported metrics to be missing from.
Who is ranked, and how
Metrics and weights, a window, individuals or teams, a comparator chain and a visibility mode.
PacksWhat the cards are
The deck we ship, a public catalogue, or a pack you build from a spreadsheet with your own art and your own rarities.
SourcesWhere events come from
GitHub installs in a click and loads the last 90 days. Anything else sends us an event and ranks beside it.
VisibilityWho can see whom
Team-only, opt-in, or open to everyone. Whatever you choose holds everywhere, so nobody sees a name you said they could not.
CompetitionsA board with an end date
A board with a start and an end. When it finishes the result is settled, and it stays settled.
Slack and email, off by default
Tell the team when something good happens, in the channel they are already in. Off until you turn them on, and they never fire for something that did not actually happen.
Two surfaces, not one
The exec question and the personal one are different questions.
A leader wants to know whether a team is moving. A person wants to see their work was noticed. Only the first is a surveillance tool nobody renews; only the second is a toy.
- Teams view, showing movement by team over two windows, computed in one pass so the periods cannot overlap and double-count
- Personal profile, showing your own work, your own cards and your own streak
- Binder, showing everything you have pulled, and anything still waiting to be opened
- A team with no prior activity shows no trend, rather than a triumphant 100%
By department
What it looks like for your team
The measure that matters is different in every function, which is the whole reason a board is configurable rather than shipped.
For support teams
Resolutions and escalations rather than ticket count, and why that distinction decides whether it helps.
SalesFor sales teams
Rank the pipeline behaviour that produces the revenue, not just the revenue itself.
EngineeringFor engineering teams
Make review work visible without the board reading as surveillance.
In detail
How each part actually works
Written for somebody evaluating this rather than somebody who has already bought it, so they say what is not built yet too.
Leaderboards
What you can rank, how you choose it, and why a metric you invent works as well as one we shipped.
CardsCards and packs
Where cards come from, how a pull is decided, and how to build a pack from a spreadsheet.
SourcesIntegrations
What each source sends, what it can never do, and what is not built yet.
Connect one repository and watch it fill.
Free for your first 50 people. No card, no sales call.