All originals

In daily use

Panda HQ

A web app I run the whole business from. Rough notes go in from the desk or the phone and come back sorted into tasks, ideas and notes against a detailed profile of me, alongside every client, project and payment, and every proposal, quote, invoice and signed agreement the studio sends.

Example: a rough note typed on the phone lands on the desk a second later, sorted into two tasks, an idea and a note, one link flagged Unsure.
Status
In daily use
Built
Web app, desk and phone
Stack
React · Supabase · Vercel · Claude
Since
Aug 2026

The problem

My business lived in six places. Clients and income were in spreadsheets and Airtable, plans in Notion, thinking in Obsidian and half-finished documents in Google Docs. The things that actually mattered that day were in whichever notepad file I'd opened last.

Every morning started the same way. I'd sit down at the PC and go looking through five notepad entries, a doc I might have updated and forgotten about, and a Notion board and an Airtable base that were already out of date, because keeping them current was a job of its own and nobody was doing it. It took ten to fifteen minutes of searching before I knew what the day needed, and even then I was trusting that nothing had fallen through a gap between two apps.

None of the tools were bad, they just weren't built for me. Each one wanted me to work its way, and I was bending my week around six different designs to fit them.

So I built my own.

The approach

It started small, with one place for clients, projects and income. It got a lot bigger once I asked myself what else I kept losing, and the answer was thoughts. The call I had to make, the idea from a walk, the thing someone asked me to do while I was out. So Panda HQ ended up as two things at once, the ledger of the business and a second brain that never forgets anything.

There were three big decisions.

The first was that capture has to be rough. I think a second brain only works if putting something into it is faster than deciding where it goes, so I don't file anything. I write the way I think, twenty bullet points at once if that's what the day produced, with two projects and some life admin tangled together, and the system does the filing.

The second was that the AI has to know me rather than the internet. I wrote a detailed profile of myself covering the work, the clients, the people, how I talk about them and what matters, and every capture is read against it. So "call him back about the invoice" lands on the right client, and a rough note gets a sensible due date and priority instead of a generic one.

The third was that it must never be confidently wrong. When the system's sure where something belongs, it links it. When it isn't, it still links it but flags it as Unsure, and I confirm or fix it in one place. Money gets a stricter rule, so a figure it can't place waits for me rather than being filed somewhere plausible.

It used to be a desktop app

For the first couple of months Panda HQ was a Windows app with its own copy of the database on the machine and a sync layer keeping that copy and the server in step. The sync was the hardest thing I'd built and I was pretty proud of it. I've since deleted most of it, and the app is better for it.

Two things changed my mind. The first was setting up a second machine so I could work away from my desk for a few weeks. It took most of a day, and almost none of that day was Panda HQ being difficult. It was disk encryption, a hand-built config file, the backup folder, a passphrase, a secrets file and the git identity. A web app has no second machine to set up. You open a browser and sign in.

The second was a bug. A fresh install couldn't finish its first sync, because a project whose parent hadn't arrived yet turned up first and the local database refused the row. The fix was one line and it isn't really the point. That whole class of bug only existed because there was a local copy being filled in order, and no local copy means no pull, no cursor and no arrival order to get wrong.

So Panda HQ runs in a browser now and the database is the only copy. It installs like an app on the phone and sits on the home screen. It still works with no connection: every screen shows the last thing it saw, and anything I capture waits on the device and gets read the moment I'm back online. I gave up the piece of engineering I liked most and got a simpler app that I can open anywhere.

What I built

A home screen that answers one question, which is what I need to know right now. Tasks due today come first, so the first thing I see is what to focus on, and anything needing a decision from me is on it rather than buried in a screen I'd have to think to open.

The whole business behind that. Clients, projects and when they were completed, retainers, salary and freelance income, invoices, and financial reports that show the business progressing month by month. Money is held in dollars, pounds, euros and lira, always as whole minor units and never as a floating-point number, because a rounding error in money is the kind of bug you don't find out about until late. Two currencies are never added together. The one total that crosses them is the roll-up on the home screen, and that uses the rate held for the day the money actually moved.

A capture brain that reads my profile. A rough note gets sorted into tasks, ideas and notes, linked to the right client or project, and given a due date, priority and effort level based on what I actually wrote. It's not magic and it doesn't invent anything. If a note doesn't say what it's about, it can't know, so anything it isn't confident about gets linked but flagged for me to check. You can see this in the demo at the top of this page, where four rough lines go in and two tasks, an idea and a note come out, with the one link it wasn't sure of flagged.

Questions, not just storage. Because everything I've captured is structured, I can ask it things in plain language. What ideas have I had in the last three months that I didn't act on? How many times did calls get rescheduled this month? It answers from my own records, read against the same profile.

Every document the studio sends. Proposals, quotes, invoices, agreements, work summaries and retainer summaries, written in the app and rendered to PDF on the server. The numbers come out of one sequence with no gaps in it, and the number is spent, the PDF is drawn and the document is marked issued in a single transaction, so I can't end up with an invoice number that exists twice or a gap I can't account for. Issued documents are filed into the client's folder on Google Drive by a job that runs every ten minutes.

Agreements get signed online. Issuing one emails every signer their own link to a signing site, which draws the document from the same shared code the app does, so what they sign and what I wrote can't drift apart.

Claude can write a document, but it can never send one. I'm in my code editor most of the day, so Panda HQ hands its document tools to Claude there and it can draft a quote or a work summary from inside the repo the work is actually happening in, with the client and the project already known. What it can't do is issue one. Nothing it writes spends a number, draws a PDF or emails anybody, and there's deliberately no tool that would. I open Panda HQ, read the document and press Issue myself. The worst a mistake can cost me is a draft I delete.

Milestones log themselves from my commits. I'd rather not write up what I did at the end of a day. So every commit carries a short trailer saying which milestone and project the work belongs to and whether it was part of what was agreed, and Panda HQ reads it when I push and logs the work against the project. A webhook catches the push and a sweep every ten minutes catches anything the webhook missed. Work that falls outside what was agreed turns up on my home screen as something to decide about, rather than quietly becoming an invoice.

The sites I look after report back. Each site I've built sends its own traffic figures into Panda HQ, so I can see how a client's site is doing in the same place as their projects and their invoices.

The front door is this website. When someone sends a brief from the contact page, it lands in Panda HQ as an enquiry, and one click turns it into a client and a project with a follow-up task already set. So the form on this site is part of the system this page describes.

Backed up every night. Supabase keeps daily backups for a week, and on top of that an encrypted export of every table goes to a folder on my Drive at half two every morning. It holds the whole of my business, so I want a copy somewhere I control as well as a copy where it lives.

Locked to one person, and tested that way. Every record is fenced to my account by the database itself rather than by the app asking nicely, and that fence is tested with a second real account trying to get through it. Making sure only my app shows my data isn't enough. I need to know nobody else can reach it.

Panda OS, the phone half. Before any of this ran in a browser, I built an Android launcher that replaced the home screen on my work phone. Its home screen is a three-by-three grid, with the time, today's agenda and this month's income in the centre, the workspace of tasks, notes and ideas to the left, the money side to the right, and the normal app list below. It's still on that phone and it still works. I use it a lot less now, because the web app installs on the phone I actually carry and does the same job there.

The outcome

What used to take ten to fifteen minutes at the PC now takes about thirty seconds. I open the home screen, see what's due and start. There's no morning search any more, because everything's in one place.

It replaced all six of them (spreadsheets, Airtable, Notion, Obsidian, Google Docs and the notepad files), and it's taken on a lot the six never did. Every client, project, payment, captured thought and sent document is in one system that I can open anywhere I can open a browser.

It's about three months old. I capture at least one set of tasks every day, every document the studio sends now comes out of it, and I'm still building it. Next on the list are notifications on the phone and another pass over the screens I use most on it, because a screen that works at desk width isn't automatically a screen you can use standing up.

The way I usually put it is that I have an app I operate my entire business from. I designed it, I built it, and it works the way I think, because it was only ever built for me.