We're on a mission to make project management tools more humane, ethical and effective — tools that put the humans doing the work first. Here's who we are, how we work and what we're honest about.
Why we built this
Not from a single dramatic moment — from a pattern we kept running into wherever sprint planning happened.
Sprints get committed before anyone asks who is actually available, skilled and at capacity this week. The mismatch shows up later as missed commitments and quiet heroics.
Overload hides in after-hours commits and shrinking review quality. By the time it's visible in a retro or an exit interview, the damage is done.
Velocity leaderboards reward the loudest work and punish care, review and mentoring. Teams stop believing the numbers that are used to describe them.
01
Before JiraVision was a product, it was the thing we kept building by hand for our own teams — capacity spreadsheets, mood check-ins, sprint drafts with the reasoning written next to every item. Every project tool already had a board; none of them could answer 'can this team actually finish this plan, and what is it costing them?'
02
The more we shared the spreadsheets and check-in rituals, the more other teams asked for copies of them. JiraVision is that collection of practices turned into software — capacity-aware planning, wellbeing signals that stay anonymous, and metrics that show their formula. We're still small and still early: see our changelog for what's actually shipped and the status page for how it's running right now.
What we stand for
These aren't posters on a wall. Each one is enforced somewhere in the product, and you can hold us to all of them.
Technology should serve the people doing the work, not the other way around. Plans are sized to humans — availability, skills and load — before they're sized to deadlines.
JiraVision proposes; your team decides. No sprint, reassignment or message is applied without approval. This is a product rule, not a marketing promise.
Wellbeing and load signals are aggregated at team level before anyone sees them. Individual answers are never surfaced raw to managers.
Every AI suggestion links to the data behind it and the model that produced it (IBM Granite). You can read the reasoning, disagree and edit.
We're early-stage. SOC 2 and GDPR alignment are in progress, not certifications we hold today. Planned features are labelled planned. We'd rather say 'not yet'.
Fairness means showing the formula next to the number, and designing metrics that don't quietly punish care, review and mentoring work.
03
It isn't a tagline — it's a set of rules the product has to pass. If a feature would show a manager someone's raw mood answer, we don't build it. If a suggestion can't explain itself, it doesn't ship. If a metric's formula can't survive an angry staff engineer, it doesn't get a dashboard. Small teams can move like this because there's no layer between the person who hears the problem and the person who writes the fix.
How we work
Being small isn't a weakness to hide — it's the operating model. Here's how the work actually flows.
The team
We're a small, independent team — engineers, designers and researchers who have run the projects we now build software for. Named profiles and photos are genuinely coming soon; until then, here's the honest shape of who does what.
Own the AI planning and metrics pipeline end to end, from model choice to board writes — always behind an approval step.
Talk to teams before writing specs, and test that signals actually help before they reach a dashboard.
From problem to shipped
Four gates. Anything that can't clear all four — including features that would make demos look better — doesn't ship.
It starts with a real team hitting a real wall: support conversations, onboarding friction or a workload pattern we can see in aggregate.
The idea goes on the roadmap labelled 'planned'. If it touches people's workloads, the privacy and rationale design is settled before code.
We release the version we can fully explain — methodology visible, human approval intact — and never a black box to fill a gap in marketing.
Every release lands in the public changelog with the reasoning; service reality lives on the status page. You can audit us without asking permission.
Straight talk
In the open
Trust us less, verify more — that's the design. Every commitment below has a public artifact you can look at right now.
Everything we ship is written up at /changelog — features, improvements and fixes, newest first. No buried bad news.
Service health for the site, dashboard, Jira sync and notifications is published at /status, not kept behind a support ticket.
Every fairness and workload metric links to its exact formula and data window inside the product — numbers with receipts.
Integrations and roadmap items are marked 'planned' until they genuinely ship. We don't demo vaporware as a feature list.
Human-in-the-loop approvals, anonymous aggregation and model attribution (IBM Granite) are product defaults. These are our commitments, not certifications.
SOC 2 and GDPR alignment are in progress for an early-stage team. Ask us specifics at /contact and get a straight answer.
Shipped
2026-10-23
Feature
Capacity-aware sprint drafts now ship with a written rationale per suggested item, so planning decisions can be reviewed and edited before approval.
2026-09-30
Improvement
Check-in and workload indicators are now aggregated before display by default. Individual responses are never surfaced raw.
2026-08-28
Feature
Every fairness and workload metric now links to the exact formula and data window behind it.
2026-07-15
Improvement
Gamification paths now include code review, pairing and knowledge-sharing activities, opt-in per team.
2026-06-10
Feature
Initial launch: AI Scrum Master, Team Wellbeing, Gamification and Ethical Metrics for teams connecting Jira workspaces.
This product ships with the platform — Starter, Professional and Enterprise all include it. Pricing scales by seat, annual billing saves 20%.
Verify us
Every release, written up newest-first — the real milestone list, not a highlight reel.
Live service health for the site, dashboard, Jira sync and notifications.
Notes on AI-native project management from the people building it.
Open roles and how a small team works — join us if the honest version appeals.
Whether you're a team that wants calmer sprints, a candidate who wants to ship with a small honest crew, or a partner with an idea — the fastest way to reach a human is a direct message.
The people who answer support mail, run onboarding and carry your questions into the next planning session.
Simple plans, no surprises: pricing scales by seat and every plan includes the core.