Now. Next. Later.
Every item is tagged committed or exploring. Committed means on us to ship — if we don’t, we owe you an update on this page. Exploring means we’ve heard the ask and we’re considering, no promise.
Now.
Currently shipping · through Q3 2026- iOS TestFlight expansionCOMMITTED
Widgets, share-sheet-to-Project, in-app account settings.
- Content site scale-outCOMMITTED
150+ pages covering every family. Shipping in waves M3 + M4.
- Meals-per-plan calculator embedCOMMITTED
Live on /pricing, /impact, /demo, home.
- Teams pilot onboardingCOMMITTED
Manual onboarding for the first cohort. Waitlist open.
Next.
Q4 2026 · targeted- Android betaCOMMITTED
Native app, feature-parity with iOS TestFlight cadence.
- Mac menu-bar appCOMMITTED
Global hotkey, universal binary. Beta invites when it beats a web pin.
- SSO for TeamsCOMMITTED
SAML JIT. Prerequisite for shipping self-serve Teams tier.
- Voice input on iOSEXPLORING
Anthropic voice API is early. We ship when latency + quality are honest.
- Deep-research modeEXPLORING
Multi-step agentic research with cited output. Under design.
Later.
2027 · likely, not committed- Windows tray appCOMMITTED
Follows Mac by roughly one quarter. Same functional bar.
- Self-serve Teams tierCOMMITTED
Post-SSO. Impact statement export built in.
- Meals directed givingEXPLORING
Per-user 'direct to region' choice once the formal partnership with the hunger-relief charity we select activates. Depends on the partner's API surface and on crossing the $50,000/year partnership threshold.
- Windows desktop widgetEXPLORING
Requested; may ship if the Mac widget lands well.
- APIEXPLORING
Not committed. Meal-math accounting for variable-usage API needs work. See /api for the honest position.
No dates we can’t keep.
Windows are qualitative (“Q4 2026 targeted”) not specific dates, because specific dates on a small team are how you accumulate broken promises. When a committed item slips, the note appears on this page and the changelog the day we know.
When an exploring item becomes committed, it moves columns and gets an entry in the changelog. When something gets dropped, the last state before removal is quoted honestly in the changelog for that period.
Have something to add to the exploring column? Email us. Every request goes in a spreadsheet we actually re-read.
Public roadmap. Public receipts.
Same principle: the details are on the page, not in a NDA.