Ought to Do It: Building Otto With Otto

Over the past few weeks, we took a big step back from the product we were building. We shared early versions with a few people, listened closely, and realized the same thing kept coming up: the idea was there, but the foundation needed work.

So we rebuilt it. Not as surface polish, but as a product foundation.

The new Otto do it system is built for longevity: a typed React and Vite front end, a Django API, PostgreSQL-backed data, Redis and worker jobs for async work, object storage for media, WorkOS authentication, and product-owned audit trails, migrations, backups, and release proof. The front end is meant to feel designed from first principles: restrained, deliberate, and composed, with enough structure to grow without becoming generic.

The result is a focused Otto do it workspace with a clearer interface, a more durable architecture, and a front end we can keep extending without losing the product's shape.

[block:ought-to-do-it-workspace-comparison]

The product direction has become clearer at the same time. Instead of becoming another bloated project management platform for everyone, Otto do it is being shaped around the individual user experience: one person, their projects, their tasks, and Otto AI acting as a personal project manager when it is useful.

That focus has changed the product in a good way. Otto do it now centers on clearer project boards, task flows, drafts, activity-aware home views, weekly trend insights, project identity, and a clearer interface for moving work forward.

It should help individuals manage projects with more clarity, less friction, and an AI project manager that assists without getting in the way.

There is also a funny part to rebuilding it this way: Otto do it is already being used to manage the work of building Otto do it.

That makes the process more complicated, but also more honest. The product has to hold up under real planning pressure before it asks anyone else to trust it.

The new landing page is up with the broader shape of what Otto do it is becoming, but the product is still under active development. That development work now moves through a real Production Lane.

[block:ought-to-do-it-production-lane-video]

The lane starts with a strategy conversation: what are we trying to change, why does it matter, what could go wrong, and what would prove the work is complete? From there, the work becomes a scoped task with acceptance criteria, review points, and proof.

The details are intentionally disciplined without being public theater. Work is planned, built locally, checked against the real product, backed up before promotion, and verified again after it reaches production. The task carries the evidence, blockers, and closeout so the system stays honest without exposing internal mechanics.

That is the satisfying part. Otto do it is being built with the same discipline it is meant to give its users: clear tasks, visible proof, careful execution, and a clearer way to move work forward.

A private beta will be available soon, so be sure to Sign up for our waitlist.