cosmic on jwogrady

Presence, platform, product

Mon, 19 Oct 2026 16:39:52 -0500

I believe every local business needs to build three things, in this order.

Presence. Platform. Product.

Three things to build, in order, on one foundation.Drawn

That sounds like a slide. It started as a voice note, and I want to explain it properly, because for most of my career I would have told you the list had one item on it.

Your agency isn't slow, it's locked out

Wed, 23 Sep 2026 12:41:21 -0500

Here is the thing nobody tells you before you sign.

The best predictor of whether a local marketing engagement produces anything is not the agency’s talent. It isn’t your budget, your industry, or how good the pitch deck was. It is something much more boring:

How many things can they do without stopping to ask you?

That number is the whole relationship. And almost nobody negotiates it on purpose, which is why so many of these arrangements feel like wading.

Call them at nine on a Sunday

Wed, 23 Sep 2026 12:06:10 -0500

The most useful number I know of in a local competitive analysis is not in any tool, costs nothing, and you collect it with a telephone.

Call your competitors at nine o’clock on a Sunday night. Count how many of them answer.

That’s it. That is the measurement. If you sell anything with an emergency in it — water where water should not be, no heat in February, a door that won’t lock — then some meaningful share of the money in your market is moving at hours when a tool’s dashboard is a flat line and a human being is standing in a hallway deciding who to try next. Competitor after-hours answer rate. Nobody sells it to you because nobody can; it isn’t in a database anywhere. It is, however, entirely knowable by anyone willing to spend forty minutes and look slightly odd.

The database that held no data

Tue, 22 Sep 2026 15:35:31 -0500

Before you move a business’s data anywhere, you take an inventory. It is dull work and it is the only part that is genuinely load-bearing, because everything after it is built on believing you know what you have.

I had a file called wtp.duckdb. Two hundred and seventy-four kilobytes, sat in the archive directory next to everything else, named after the company. If you had asked me what it was I would have said: that’s the database, that’s the historical record, that’s the thing we must not lose.

The number nobody counted

Tue, 22 Sep 2026 15:29:13 -0500

No screenshot on this one. The finding is seven.

I was doing the least glamorous job in software, which is taking an inventory before a move. Two piles of data for the same business — one old, one newer — and the only question that matters before you touch either is: what is actually in each, and where do they already agree?

So I asked the database what it had. The tooling has a perfectly good listing that gives you every table with a row count beside it, which is exactly the shape of answer the question wants. One table came back at 141 rows. The old pile had 134 of the same records.

Set is not the same as works

Tue, 22 Sep 2026 15:19:14 -0500

I shipped a version that promises nothing today, on purpose, and what stayed with me afterwards was how much of it I had to take on faith right up until the moment it ran.

The job was release automation. A bot watches the commits landing on the main branch, and when it sees enough to be worth naming it opens a pull request that writes the changelog, bumps the version, and cuts the tag. It is a good deal. Setting it up, though, is almost entirely configuration — and configuration is just a pile of claims about what will happen later, sitting in a file, looking exactly as confident when it is wrong.

The one that threw an error was the safe one

Tue, 22 Sep 2026 14:40:26 -0500

Here is the thing I had backwards this afternoon. I spent an hour planning around a failure that announces itself, and very nearly walked straight past the one that doesn’t.

The setup is ordinary enough. A static site — pages assembled once, ahead of time, then served as plain files — that pulls its content out of a database while it builds. The database is Postgres, and every table on it has Row Level Security switched on: RLS, a rule attached to the table that runs on every query and decides which rows this particular caller is allowed to see. The build connects as anon, the unauthenticated role, because a build has no user to be. It is nobody, asking politely.