Less to-do. More to-did.
A task manager we built for ourselves, then opened to everyone.
ToDidIt is an &Pixels Labs product, so we were the client, the designers and the engineers. It ran our own sprints for months before it had a pricing page.
Visit todidit.com- Client
- ToDidIt
- Role
- Branding to MVP, a 0-to-1 product build
- Type
- SaaS product
- Year
- 2026
- Timeline
- 4.5 months, internal tool to public beta
- Team
- One Sr. UX Engineer, design through build
- Platforms
- Web app
- Progressive Web App
- iPhone and iPad apps
- Android app
- Status
- Public beta
Can a task manager make finishing feel better than planning?
01Overview
ToDidIt started as our own sprint tooling. The tools we ran sprints in were built for teams far larger than ours, so we built the same rituals with fewer steps, and it held up when we imagined it past us.
02Problem
Every task app is a record of debt. It shows what is left, and finishing is rewarded by the row vanishing. With no funding in the most saturated category in software, we could not win on feature count, and AI costs money on every call.
03Solution
Invert the record. Finished work lands in a To-Did Log that never deletes, a celebration layer shipped before feature parity, and pricing charges a flat rate per account with AI metered by the outcomes you keep, not by headcount.
Don't read about it. Finish something.
This is ToDidIt's own Today card, with the markup, tokens and motion that ship on todidit.com. Check a task off, add one of your own, and watch where finished work goes.
- 01Checkbox pop and strike-through
- 02Today's wins tally and chips
- 03Hype lines from the real celebration pool
- 04The To-Did Log, which never deletes
0 of 4 done
Today
More to-did.
Today's wins
0To-Did Log
Nothing yet. Go on.
The first week, plotted by how it feels.
Seven moments from signup to a first invite. The orange marks are where the product celebrates on purpose.
- ArriveSign upEmailed code, no passwordTurnstile, then one code
- ArriveWelcome5-screen wizard, all skippableMeet Didi, meet the Log
- First winsAdd 3, finish 3Quest chapter 1First celebration fires
- Go deeperBreak it downSubtasks, then the parentNav reveals as you go
- Go deeperOrganizeProject, priority, due dateThe friction dip
- Look backOpen the LogTo-Did Log and streakFinished work, kept
- Bring peopleInvite a teammateRoles chosen at inviteGraduation confetti
Four zones, one record underneath.
- Marketing/
- Home
- Pricing and Ledger
- Features (8 pages)
- Pillars: Capture, Clarify, Compose, Celebrate
- Lifetime deal
- Field Notes
- Happiness Center
- Onboarding/welcome
- Sign up and log in
- MFA
- Welcome wizard
- Invite and referral links
- Checkout
- App/today
- Dashboard
- Today
- Horizon: Kanban, Calendar, Sprint
- Tasks and To-Did Log
- Projects
- Blueprint
- Reports and Streaks
- Templates
- Settings/settings
- Workspaces and roles
- Integrations: Slack, Calendar
- Notifications
- Security
Needs sign-in. Horizon, Tasks and Projects read one task record, so no view needs syncing.
One sprint, three ways to see it.
A software team two weeks into usage-based billing, planned in Horizon. Drag a task to another day or column, or check it off. Every view reads the same task record, so the change shows up in all three.
Horizon
Drag a card to move it. Check it off to finish it.
Works on every screen you own.
What it runs on.
Framework
- Next.js 16
- React 19
- TypeScript
- Tailwind 4
Data
- Supabase Postgres
- Row-level security
- Realtime
- Auth with MFA
AI
- Claude Haiku 4.5
- Gemini 2.5 Flash
- MCP server
Billing
- Stripe plans
- Metered refills
Integrations
- Slack app
- Calendar
- Web push
Ship and test
- Vercel
- Vitest
- Playwright
- PostHog
One engineer took ToDidIt from internal tool to public beta in four and a half months, with a perfect desktop performance score.
- 0.0
- Months, internal tool to public beta &Pixels Labs build log
- 0
- Pages live and indexed todidit.com/sitemap.xml
- 0
- Product surfaces shipped Feature set
- 0
- PageSpeed, desktop PageSpeed Insights, Aug 2026
ToDidIt is in beta, so these numbers describe scope, not adoption. Traction figures land here once they will hold.
The brand library behind it.
Palette, type, eight logo variants, 25 named motions, seven animated ads, a social kit per platform, three carousels and 41 email templates. All running, all the real exports.
Open the brand libraryShort answers.
Is ToDidIt a client project?
No. ToDidIt is an &Pixels Labs product: we own it, fund it and carry the consequences of every decision in this study. Revlr is the other one.
How long did ToDidIt take to build?
Four and a half months from internal sprint tool to public beta, designed and built by one senior UX engineer, from the brand through the production app.
How do people sign in to ToDidIt?
With an 8-digit code sent by email. There is no password to create or forget, and the code expires after 10 minutes.
Why does the study report scope instead of user numbers?
ToDidIt is in beta. Signup or retention figures this early would not hold, so the study reports what can be measured today and sources each number.
Can &Pixels build something like this for us?
Yes. The same team that designed and built ToDidIt does client work, most often as an embedded product team on a subscription rather than a fixed-scope project.