Tech Domain · Book DevProjects
21 projects in Tech Domain · Book DevFocus: Solo Operations
Published counts URLs that respond; each project label shows its evidence level.
Browse by domain
Browse by outcome
21 projects in Tech Domain · Book Dev in Solo Operations
See every project's schedule in one calendar, not six different apps.
Juggling deadlines across projects meant switching between a bloated Google Calendar and ad-hoc reminders with no single visual view.
Turn a one-time workflow into a checklist you can run again in seconds.
Recurring workflows like deployments and content publishing meant recreating the same steps by memory every time.
Give every project a contact form without paying a third-party service per site.
Embedding third-party form tools across 100+ projects meant external tracking and monthly fees multiplying with every new project.
See every error across 100+ apps in one place instead of waiting for user reports.
With 100+ deployed apps, the only way to learn about a bug was a user reporting it days later.
Break a big goal into milestones without the overhead of enterprise OKR software.
Goal-setting tools were either bloated OKR platforms or plain checklists, with nothing built for tracking milestones in between.
See a habit streak the way GitHub shows a contribution graph.
Habit trackers were mobile-only or required an account just to track something as simple as a daily streak.
Generate a client invoice without signing up for accounting software.
Freelancers needed a quick professional invoice, but existing tools were either too complex or locked behind a subscription.
Adapt a kanban board to how a project actually works, not a fixed template.
Different projects needed different workflows, and most task boards forced everything into the same rigid column structure.
Start a focus session without installing an app or making an account.
Pomodoro timers were either native apps or web tools bloated with sign-up flows just to start a 25-minute timer.
Get a browser reminder without creating an account first.
Reminder apps were mobile-only or gated behind sign-up, adding friction to something as simple as a timed alert.
Show service uptime publicly instead of fielding outage emails one by one.
With 100+ services running, users had no way to check if something was actually down without emailing to ask.
Know who's working on what without asking around.
As collaborations grew, there was no single source of truth for who was on a project or how to reach them.
See exactly where the hours went across 100+ projects, not just guess.
Tracking time across 100+ projects by spreadsheet was tedious and never turned into anything actionable.
Add a task in seconds without opening an account-gated app.
Existing task managers were feature-rich but overkill for jotting down something quick without syncing to a cloud account.
Monitor 100+ domains without paying per-monitor pricing.
Commercial uptime monitors charged per site, which became expensive fast once the portfolio passed 100 deployed domains.
Write a draft without breaking focus to switch between editor, preview, and publishing tool.
Writing a blog post meant constantly switching between a markdown editor, a browser preview, and a separate publishing step.
Keep recurring solo-operations work outside the operator's memory.
Running a 45-domain solo operation on manual processes meant every workflow was error-prone and depended on remembering the right steps.
Keep a daily reflection habit separate from polished blog writing.
Daily reflections and idea sketches had no home that wasn't either a public blog post or a private notes app.
Solo Empire CLI
Run a 45-domain personal operation from 11 focused commands, not scattered scripts.
Managing 45 knowledge domains and 21K+ files by hand meant ad-hoc scripts with no shared state, logging, or safety net.
Most projects are standalone Next.js apps deployed independently on Vercel. Mobile apps are built with Flutter.