SoloChief
A weekly operating system for founders, on web and WhatApp
I'm building SoloChief, a weekly operating system for solo founders who are good at planning but struggle to protect the plan once the week gets busy.
Most productivity tools help you add more tasks. SoloChief is designed to do the opposite: help you decide what matters, limit work in progress, ask you to name the reason when you switch focus mid-week, and keep a record of what actually happened against what you planned.
The workflow is simple:
- Plan your three most important outcomes for the week
- Receive daily check-ins on web and WhatsApp
- Surface follow-ups before they go quiet
- Name the reason before a new priority replaces the original plan
- Review what was completed, slipped, switched, or parked
The idea came from my own experience of planning strong weeks and then losing them by Wednesday. Every new request felt urgent, so the original priorities stopped mattering.
I'm still early and would really value feedback from other solo founders: what usually causes your weekly plan to fall apart?
SoloChief is being built for that exact moment.
8 Comments
This is definitely a good idea. I'm currently just trying to build and promote my own application. The several related tasks with the actual build are one thing, but when you add in marketing, soliciting feedback, billing concerns etc.. Its nice to have one pleace to put everything. I've only just created an account, but I'll check back later with some feedback after I get a chance to learn how it works. Nice job!
Thanks, Brian. That's exactly the itch I was scratching, too many separate places holding pieces of the same week. Would genuinely love your feedback once you've poked around, especially anything that feels clunky or unclear. No pressure on timing.
I like that you're treating changing priorities as something worth understanding rather than simply preventing.
Sometimes the most valuable record isn't what got done—it's why something important stopped being important in the first place.
That's a better description of it than I've written myself, honestly. You're right that the goal isn't to prevent the switch, it's to make the reason for it visible. Most weeks don't fail because priorities changed, they fail because nobody wrote down why, so by Friday it just looks like nothing got done. Naming the reason at the moment it happens turns that into information instead of just drift. Stealing your framing for how I talk about this feature going forward, credit to you.
Thanks! I actually sent you an email from hello@beryxa.com a few days ago.
Would you mind checking your inbox (and your spam folder, just in case)? I'd be interested to hear your thoughts once you've had a chance to read it.
Weekly OS is a cool concept. What’s making founders actually stick week to week instead of falling back to their existing stack?
Honestly, nothing forces it, and I don't think it should. There's no lock-in and no penalty for lapsing. What I'm betting on instead is friction. Most planning tools ask you to build a new habit around opening them, and that's the exact habit that breaks first when a week gets busy. SoloChief's morning brief and reminders show up on WhatsApp, so the app you check anyway is already carrying the plan. Staying on track costs one reply instead of a context switch. Whether that's enough to beat the pull of an existing stack long term, I genuinely don't know yet. It's early days for me too.
You’re thinking about this the right way — reducing context switching is a much stronger lever than trying to ‘force’ discipline.
One thing I’ve seen though: even low-friction systems drop off unless there’s a moment of consequence attached (e.g. something breaks, or they feel the cost of not replying).
Have you noticed any patterns yet around when users ignore the WhatsApp prompt vs engage? That line is usually where retention is won.