Otto lives on your board — not in a chat window. It drafts the specs, chases the blockers, and updates the stakeholders, so your team spends standup talking about the work instead of the status of the work.
Free for small teams · Otto asks before it acts · Set up in 4 minutes
Up next 4
Empty states for the planting log
Seasonal reminders — v2 scope
Otto · drafting specRate-limit the share endpoint
In progress 3
Waiting on API contract from platform team
Otto · chasing blockerOnboarding illustrations, round 2
Week 6 release notes & timeline
Otto · updating stakeholdersDone 12
Push notification triggers
Shipped Tue · summary sentMigrate photos to new storage
Closed by OttoDark mode palette audit
Shipped MonTeams that stopped chasing status updates
What Otto does all day
You don't prompt Otto. You assign it cards, the same way you'd assign anyone on the team — and it gets to work.
Drop a rough idea on the board and Otto turns it into a real spec: goals, edge cases, open questions pulled from past tickets and meeting notes. You review, nudge, approve.
Seasonal reminders — v2 scope Otto · v0.3 ready
When a card stalls, Otto notices, finds who can unblock it, and follows up — politely, with context, and never more than your team's norms allow. No more "just bumping this."
Otto · 9:12 AM
Morning Priya! The API contract is blocking 3 cards on Meadow's board. Any chance it lands today? Happy to summarize what the team needs. 🌱
On it — draft by 2pm. Thanks for the nudge, Otto.
Otto writes the update your PM used to lose Friday afternoons to: what shipped, what slipped, what's at risk — tuned to each audience, from exec brief to engineering detail.
Shipped: push triggers, photo migration, dark-mode audit.Weekly digest · to 4 stakeholders
Watch: API contract slipped 2 days — mitigation in place.Flagged early, owner assigned
Timeline: still on track for the June 26 launch.Confidence 87%, up from 81%
Otto studies your velocity, your review habits, your honest estimates versus your hopeful ones. Its plans get sharper every sprint — because they're built from your history, not averages.
How it works
Otto joins like any new teammate — with clear responsibilities and a manager it reports to. That's you.
Point Otto at your board — Linear, Jira, Asana, or Otto's own — plus Slack and your docs. Read-only until you say otherwise.
Choose what Otto owns: drafting, chasing, updating, planning. Set its tone, its boundaries, and who it can talk to.
Every action starts as a suggestion you approve. As trust builds, promote Otto to act on its own — one duty at a time.
Otto never messages anyone outside your workspace without approval. Ever.
"I braced for a gimmick. Six weeks later Otto flagged a slip nine days before it would've hit our launch — and had already drafted the recovery plan. It's just… on the team now."
Pricing
Every plan includes the full Otto — drafting, chasing, updating. Bigger plans just give it more room to work.
For side projects & tiny teams
$0
free forever, honestly
For product teams shipping weekly
$14 / human / month
Otto itself is free — you pay per human
For orgs with many teams
Custom
let's talk about your roadmap
Otto starts working the moment it joins the board. The first spec draft usually lands before your next standup.
Add Otto to your board — free