title: "Kill the twelve-tab morning: one company memory instead of a dozen dashboards" slug: "kill-the-twelve-tab-morning" dek: "The solo founder's speed advantage doesn't erode in bad decisions — it erodes in the twenty minutes every morning spent reassembling company status from a dozen dashboards that don't talk to each other." audience: "Solo and small-team founders running a company with AI agents, tired of checking a dozen tools before coffee." tags: [solo-founders, ai-agents, git, self-hosted, founder-tools]

The twelve tabs

Open Mercury to check the balance. Open Stripe to check MRR and failed charges. Open GitHub to see what shipped overnight. Open the support inbox to see who's angry. Open a spreadsheet, because none of the above knows your actual burn rate. That's five tools before coffee, and none of them talk to each other.

A founder on r/smallbusiness described the same morning in a post titled "I feel overwhelmed as solo founder": "I had to check four different dashboards every morning." Four is a good morning. Add analytics, payroll, and a cap table tool to the rotation and eight is closer to typical.

The Indie Hackers community has the other half of this problem on record. One founder wrote about ending up with 20 SaaS subscriptions and put the cost plainly: "every subscription is a dashboard to check, a login to manage — twenty tools is a part-time job of overhead." That's not a complaint about any one tool. It's arithmetic. Each tool you adopt to save an hour costs you a recurring few minutes of attention, every day, indefinitely.

Where the speed goes

The whole pitch of running solo, or as a two-person team, is speed. No meetings to schedule. No consensus to build. No handoff latency. But that advantage doesn't erode all at once. It erodes in twenty-minute increments, every morning, spent reconstructing a picture of the company that existed in your head yesterday and evaporated overnight — because none of your tools remembers anything across sessions, let alone across each other.

Each dashboard is good at its one job. Stripe is the right place to look at Stripe data. But your company isn't a Stripe problem, or a Mercury problem, or a GitHub problem. It's all of them, correlated: a pull request that touches billing, a burn number that changes what you can promise in the investor update, a support ticket that's actually a compliance deadline in disguise. No vendor builds that correlation layer for you. It isn't their data to connect.

What Lycato actually does

Lycato doesn't replace Mercury, Stripe, GitHub, or Plain. It reads them.

A Lycato company is one git repository. Adapters pull from Mercury (transactions, balances), Stripe (subscriptions, failed charges), GitHub (issues, PRs, releases), and Plain (support threads), and write what matters into plain markdown: a ledger, a CRM, a decisions log, a KPI snapshot, an obligations list with compliance deadlines. A tax filing deadline that used to live only in your memory becomes a line in a file instead — not a fact stored in one person's head.

The mechanism is deliberately boring. It's markdown and git — no new database, no proprietary export format, nothing you can't read with a plain text editor five years from now. If Lycato disappeared tomorrow, you'd still have a folder of files and a commit history. That's the point of building a company's memory on a format older and more durable than the tool reading it.

AI agents read this repo to do real work: draft the investor update from the KPI snapshot and decisions log, flag a compliance deadline that's ten days out, reconcile the ledger against the latest Mercury pull. But agents don't get to just ship changes to your company's record. Every proposal is a git diff:

--- a/company/obligations.md
+++ b/company/obligations.md
@@ -12,6 +12,7 @@
 ## Q1 filings
 - [ ] Delaware franchise tax — due 2026-03-01
+- [ ] Annual report (state of incorporation) — due 2026-03-15
+      source: agent scan of sos.delaware.gov

You review it. You merge it, or you don't. Nothing lands in your company's record unreviewed — the same discipline you'd want from a new hire, applied to an agent.

The Cockpit — the local web UI — is deliberately one dashboard, not another to add to the pile: Today, Work, Company, Review, Settings. Today is the morning read: what changed overnight, across every adapter, on one screen. Not because Lycato renders Stripe data better than Stripe does. Because Lycato is the only thing in your stack that already read Stripe, Mercury, GitHub, and your inbox before you sat down, and can tell you what's actually different since yesterday.

What this isn't

Lycato doesn't replace Mercury, Stripe, or GitHub — you still need the tool of record for banking, payments, and code; Lycato reads them, it doesn't own them. It isn't autonomous — every agent-proposed change sits in Review until you merge it, same as any pull request. It isn't hosted — Lycato is self-hosted and AGPL-3.0, so your company's memory lives on your infrastructure, not a vendor's database. And you bring your own API key, Anthropic or OpenAI or Gemini, so you pay raw token cost with no per-seat markup on top. It won't take you from twenty tools to zero. It takes you from twelve tabs to one.

Takeaway

You didn't start a company to be its systems integrator. The fix for tool sprawl isn't a smarter dashboard, and it probably isn't fewer tools either — most of them are doing their one job well. The fix is one place that already read all of them before you sat down, with changes you review as a diff instead of a login you have to remember. Check that once. Skip the other eleven tabs.