01 / Interpretation
Acceptance, assumed.
Your ticket says “make it intuitive.” That’s all the specification we need.
Read the docs ↗AlmostRight / AR–1042● Complete
Your ticket
“Make the login easier.”
✓Read ticket
✓Identified friction: passwords
✓Removed passwords
3 files changed · 4 tests persuaded
BUILD PassingQUESTIONS 0
In good companyHindsight®Rework LabsAssumelyRollback & Co.
Everything you asked for.
Including the things you didn’t.
Built for teams whose definition of done is “the sprint ends today.”
02 / Validation
All tests agree.
If a test fails, we update the expectation. It’s important to set realistic expectations.
View benchmarks ↗03 / Continuity
No historical baggage.
That decision lives in a Slack thread from March. We wish it well.
See the comparison ↗04 / Prioritisation
Everyone is a stakeholder.
We treat “just a thought” as an approved requirement. Especially when it comes from the CEO.
Find your plan ↗05 / Estimation
Always on schedule.
If the work doesn’t fit the estimate, we update the estimate. The dashboard stays green too.
View system status ↗06 / Delivery
MVP. Maximum viable product.
You asked for a date picker. We added a calendar service, recurring events, and a reason to hire.
See what’s new ↗4m 12sfrom “tiny change” to migration
0meetings that could have prevented this
100%tests passing after revision
Measured before the retrospective. Methodology ↗
Confessions
“I built the screenshot button.”
The one the team had been declining for years.
Read the story ↗Museum of Why
The old server.
Three months of monitoring. Nothing happened. Then they switched it off.
Visit the museum ↗The puzzle
It passed every test.
A delete button. Four possible issues. One missing decision.
Try it yourself ↗A plan for every team.
Unlimited scope. Predictable billing.
Starter
Free
No procurement required
- Unlimited tickets
- Standard assumptions
- Backlog imported as requirements
Team
$39
per seat / month
- Priority assumptions
- Self-healing tests
- Stakeholder comments treated as scope
Enterprise
Custom
For larger organisations
- Custom assumptions
- SSO and audit logs
- A QBR about the previous QBR
A few questions.
Does AlmostRight ask for clarification?
No. We saw “TBD” and took ownership.
What does it remember?
Your current ticket. Not the comment below it that says “actually, hold off.”
Who is behind AlmostRight?
AlmostRight is a parody by Atono, about the context that gets lost between a decision and the work. More about Atono ↗
From Atono
There’s usually a reason.
Keep the decisions behind the work close enough for your team—and its AI—to find them.