ETHDOS from ethos. a way of working.

Half of a PM's week disappears into admin nobody sees.

I got tired of being the bottleneck in my own week, so I built an AI assistant to run the admin half of my PM job. I call it EDOS. Now I show builder-curious PMs how to build their own.

Real system. Run every day. No synthetic gurus.
The problem

Status updates. Minutes. Recaps. Chasing things down. Rebuilding context every morning.

a typical week, roughly
Mon
deep work
status + recaps
Tue
deep work
meeting minutes
Wed
deep work
chasing things down
Thu
deep work
rebuilding context
Fri
deep work
status + recaps
the work only I can do the admin half
→ this is the half EDOS runs for me now.
What it does

The senior busywork most assistants can't touch.

It remembers.

Every decision, every thread, every "we already talked about this" moment, held so you don't have to re-explain your own week.

It drafts.

Status updates, recaps, and follow-ups start as a first draft in your voice, not a blank page at 6pm.

It chases.

The nudge, the follow-up, the "still waiting on this" that eats twenty minutes of your attention for ten seconds of value.

It handles.

The parts of the job that require judgment but not you specifically, delegated to a system built around how you actually work.

The ethos

A system built around how I actually work, not the other way around.

This is a real system I run every day, not a theory I'm selling. No fluff, no synthetic gurus, no faceless SaaS pretending to be more than it is.

I built EDOS because I was tired of being the bottleneck in my own week. It remembers, it drafts, it chases, it handles, and I show you exactly how it works, piece by piece.

Real setup. Real receipts. Nothing theoretical.

from the getEDOS build log

If you're the kind of PM who suspects half your job should already be automated, you're in the right place.

Coming soon

The full system breakdown is coming.

Piece by piece, receipts included. No filler, no shortcuts, no synthetic gurus.