A few years ago I ran a small freelance design operation. On any given Monday my browser had twelve tabs open: Trello for projects, Notion for notes, Todoist for daily tasks, plus a calendar app, a time tracker, and a password manager. Each tool had its own login, its own notification system, and its own way of breaking down. I spent more time maintaining the system than using it. The breaking point came when a Trello power-up failed and erased an entire client board. I decided then to strip everything back to the simplest possible setup: a single HTML file on my desktop.
That file became my daily command center. Over time I shared the concept with a few colleagues, and one of them sent me a link to Marsheepy.net—a one-page site built on the same principle but executed far more elegantly than anything I had hacked together. No databases. No JavaScript frameworks. Just a clean mix of plain text, a few lists, and small inline scripts that track the day’s priorities. That site proved that a personal dashboard could feel polished without resorting to complex software. So I rebuilt my own version. Four years later I still use it.
The real cost of app subscriptions
I used to believe that paying for productivity tools equaled paying for productivity itself. The logic seemed sound: if you invest money, you will use the tool. In practice the opposite happened. Each subscription added a layer of friction. I needed to remember the web address, log in, wait for the interface to load, and then navigate through menus designed for teams, not for one person. The monthly fees accumulated quietly. $15 for Trello. $10 for Notion. $8 for Todoist. $5 for a time tracker. That is $38 a month, or $456 a year, for tools that solved problems I could fix with a text editor and a spreadsheet. The real trade-off was not money; it was attention. Every extra click during the day pulled me out of the work itself. The few apps I kept—a calendar, email, a code editor—no longer need subscriptions because I only use their free tiers or local alternatives.
What my single-page dashboard includes
Instead of a dozen services, I now open one HTML file in my browser. It lives on my local machine and syncs via a free cloud folder. Nothing is more than a tab away. The structure is brutally simple: a header with the date, a text area for notes, and a set of sections that update based on the current time. Here are the six components that matter most to me:
- A daily note block where I paste links and quick thoughts. If I type something, it stays till I erase it the next morning.
- A priority list with three slots. I set these at the end of the previous workday and never rearrange them while the day is running.
- A small clock that shows the next three scheduled blocks of time. I hard-code these as plain text; if a meeting shifts, I edit the file directly.
- A check-in counter. Each hour I note whether I am focused, distracted, or in a meeting. That gives me a rough log without any tracking software.
- A project backlog that contains only the names of active projects and the one next action for each. No descriptions. No due dates—only the name.
- A memory section with the phone numbers I use often and the license plate of my car. Silly, but I no longer search my email for those.
Total file size: 4 kilobytes. Zero external requests. Zero ads. Zero auto-updates.
Four mistakes I made when switching
The transition was not smooth. I tried to move too fast and ended up with a file that was just as cluttered as my old app setup. Other people who tried the same approach made similar errors. If you want to build a one-page dashboard of your own, avoid these four common pitfalls:
- Over-designing the layout before you know what needs to go there. I spent two evenings picking fonts and colors without writing a single task. That delay almost broke the habit before it started.
- Copying someone else’s structure blindly. Marsheepy.net works for its owner because it matches how they think. My first copy-paste attempt failed because I forced my work into categories that did not match my actual day.
- Adding sections for things you only update every few weeks. I included a « reading list » that I touched once in three months. The empty section created a feeling of incompleteness that annoyed me every time I saw it.
- Treating the file as permanent instead of iterative. I kept the same version for six months because I thought changing it would undermine the whole idea. In reality the file needs to evolve. I rewrite mine twice a year from scratch, keeping only what survived the previous period.
Why this method sticks when others fade
I have watched colleagues cycle through Asana, Monday.com, Basecamp, and a dozen others. Each new tool feels promising for the first two weeks. Then the notifications become background noise and the board turns into digital landfill. The static HTML approach avoids that cycle for a simple reason: it forces you to make decisions about what goes into it. You cannot create a list of fifty subtasks without typing each one by hand. That friction is actually the point. It trains you to keep only what matters. Because the file lives on your own machine, you own the data completely. No company can change the terms of service. No feature can be deprecated. No pricing plan can shift. The only cost is your willingness to type plain text. That may sound like a regression, but for many people it is the first step toward a system that does not demand to be managed. The feeling of opening a file that loads in 0.2 seconds, has no loading spinners, and shows exactly what you wrote the night before—that feeling cannot be replicated by a subscription dashboard. It is the quiet payoff of letting go of complexity.