AI Systems · Operating Model

One employee, and the systems that hold the details.

Everlight is my Etsy shop for small business templates. I'm the only person in it, so I built the systems that keep track of what needs doing, and I run the shop on top of them.

ScopeWhole operating layer
TeamOne
StatusIn use
ScreensSample data
01

The problem I set myself.

A one-person company fails in a predictable way. Not from a shortage of ideas. From the hour a day that goes to remembering what needs attention, chasing what got dropped, and rebuilding the same document for the fourth time.

So I stopped treating that hour as the cost of doing business. The obvious fix is to hire it away, and I couldn't afford to, so I engineered it away instead. Everything below came out of that decision.

02

The morning briefing.

Every morning, before I opened anything else, I got a briefing. Not a checklist I'd written once and stopped reading. It read the current state of the business and told me what needed attention that day, in the order it mattered.

The hard part was never generating text. It was grounding. A briefing that invents a priority is worse than no briefing, because you stop trusting the next one.

01

It was ordered by what changed, not by what's oldest.

02

Every line traced back to a record, so nothing was inferred.

03

It arrived before I asked. A tool you have to remember to open is a tool you stop using.

03

The advisory panel.

When I have a decision I'd normally take to a board I don't have, I put it in front of a panel instead. Several perspectives, argued separately, before I commit.

The value isn't the answer. It's being made to state the decision clearly enough to be argued with. Half the time I change my mind while writing the question.

01

Each perspective answers independently, so they disagree in useful ways.

02

It reads the same business context the briefing did, so the advice is grounded rather than generic.

04

The build scripts.

Every product file comes from one source. The scripts rebuild the workbook, the PDFs, and all ten listing images, so a change gets made once instead of in twelve places.

This is the unglamorous end of the work, and it's where most of the quiet damage happens. Files are where a small brand falls apart: the logo drifts, the spacing changes, someone reuses last season's file and forgets to change the name.

01

The brand lives in the template, not in whoever is typing.

02

One change, rebuilt everywhere, identical every time.

What this proves

  • I don't just specify systems. I build them and then live on them.
  • The interesting problem in AI work is grounding, not generation. Everything here reports what it can see.
  • A small business doesn't need a big team to stay organized. It needs the routine work to happen on a schedule.
Next Step

Tell me what you're trying to finish.

I'd rather build the thing than write a deck about the thing.

Send me the project that has been sitting there. I'll tell you what I'd do with it and whether I'm the right person to do it.