A practical guide to async work
How to write updates people can act on, make decisions in writing and save meetings for the conversations that need them.
Status updates write themselves from the work in Halo Works, so the Monday stand-up becomes a five-minute read.
Discover moreProduct, engineering and support see the same roadmap, deadlines and numbers, updated the second anything changes.
Discover moreImport from spreadsheets, email and old tools in one click, then see every task on one timeline with owners and dates.
Discover moreSpecs, tasks, reviews and release notes live in one place, linked from the first comment to the final deploy.
Start nowShare files with clients through expiring links, passwords and download limits.
Cycle time, workload and blockers for every team, refreshed every fifteen minutes.
Connect chat, code hosting, calendars and 140 more apps without writing code.
For solo founders trying it out
For small teams of up to 10 people
For companies that need SSO and audit logs
How to write updates people can act on, make decisions in writing and save meetings for the conversations that need them.
We moved from monthly releases to two a week. Here is what changed in our branching, reviews and testing, and what we dropped.
Routing rules, saved replies and a shared queue took their first response time from four hours to twenty minutes in six weeks.
Trials, plan changes, security and imports: the answers our support team gives most often.
One short email a month with release highlights and practical async tips.
Every feature free for 14 days, and no card until you decide to stay.