Field Notes - Build in Public
Build in Public:
What Week One Looks Like
with Zero Audience
I'm going to tell you exactly what week one of TFF365 looked like. Not the highlight version. The real version — including the decisions I second-guessed, the things that took longer than they should have, and the one row that made everything else possible.
If you're thinking about building something in public and wondering what that actually means before you have followers or proof, this is the note for you.
What "Build in Public" Actually Means
Most people think building in public means posting results. Revenue screenshots, growth charts, milestone announcements. That's not what I mean.
Building in public means documenting the process while the outcome is uncertain. It means writing Field Notes when you have zero readers. It means putting the roadmap on the homepage before you've checked off more than one or two rows. It means showing the table with gaps instead of waiting until the table looks impressive.
Week one of TFF365 had no audience. It had a site, a method, two products, and a plan. That's enough. Here's how it actually went.
The Week One Timeline
Day 1
The Domain and the Decision
TFF365.com was already registered. The question was whether to build on WordPress, a hosted platform, or a self-managed server. I chose Google Cloud VM + Caddy. That decision added setup time but gave me full control over performance, deployment, and cost. If I were advising a first-time builder, I'd say start with Beacons or a hosted option. I went harder because I wanted to own the infrastructure. Know the reason for your choice before you make it.
Day 2–3
The First Product Row
The One Row Starter Kit went live first. Free, because the first row needs to remove every excuse. The WooCommerce setup took longer than the product itself. That's always true — infrastructure is 80% of the first-week time. Don't confuse infrastructure time with "not making progress." You're building the table the rows go into.
Day 4
The $17 Reset
The 5-Day Stop Spinning Reset went up. $17. I wrote about the pricing logic in Field Notes No. 2. The short version: low enough for a fast decision, high enough to mean something. The checkout ran through WooCommerce. No upsells on day one. One product, one checkout, one row.
Day 5
The Beacons Page
Built the Beacons link hub at beacons.ai/tff365. This is the one link that goes in every bio on every platform. Instagram, TikTok, YouTube, everywhere. You can't send different people to different URLs from a social bio — you send them to one page that has everything. Beacons is that page. This should be one of the first rows you build, not one of the last.
Day 6
Field Notes No. 1
Wrote and published the first Field Note: how to build your first digital storefront free. Documented the Beacons setup and the $20 credit. Published it at tff365.com/notes/beacons-storefront.html. Zero readers. That was expected. You write the first note for the archive, not the audience. The audience finds the archive later.
Day 7
The Roadmap Goes Public
Added the build-in-public roadmap to the homepage. Two rows checked. Two or three more visible and unchecked. That gap — the visible unchecked rows — is the most important part of the roadmap. It signals: this is real, it's in progress, and you can watch it happen.
The Decisions I Kept vs. Cut
KEPT
Self-hosted infrastructure
More setup time, full control. Worth it for this build. May not be worth it for yours.
CUT
Podcast launch in week one
Too much to stabilize at once. Pinned for later. Right call — the offer path needed to be cleaner first.
KEPT
Free product first
The free Starter Kit launches trust before asking for money. Always lead with the free row.
CUT
Private community
Pinned until the audience is real. A community of zero people is not a community.
KEPT
Beacons as hub
One link for all platforms. First infrastructure row after the site itself.
CUT
Atlas app
Big vision, not week-one infrastructure. Pinned until the simpler products prove demand.
Week One by the Numbers
Zero followers. That's the real week one number. Nobody was watching. Nobody cared yet. That's fine. The work doesn't require an audience to be real. The audience finds the work after the work exists.
What This Looks Like for Your Build
If you're starting something — a digital product, an income stream, a service, a system — week one looks like this:
Row 1: Decide what you're building and who it helps. One sentence. Not a mission statement.
Row 2: Get a place to put it. Beacons if you want to start in under an hour. A site if you want full control and you know how to build one.
Row 3: Build one thing and put it somewhere public. Free is fine. Something is required.
Row 4: Write one Field Note about what you learned in rows 1–3. Publish it. Zero readers is normal.
Row 5: Set up your one link and put it in every bio. Then make one post pointing to it.
That's five rows. That's week one. You don't have to know what week eight looks like yet. You need to know what today's row is.
The One Row That Made Everything Else Possible
If I'm being honest, there was one decision in week one that determined whether TFF365 was going to be real or just another idea I talked about.
It was the decision to put the roadmap on the homepage — with the unchecked rows visible — before I had more than two rows checked off.
Putting an unfinished roadmap in public creates accountability you can't manufacture any other way. Now the build is real. Now skipping a row means skipping it in front of anyone who finds the page. That pressure is productive. It's not shame — it's structure.
That's the whole build-in-public argument. Not followers. Not proof. Commitment made visible before the results exist.
One row. Then the next.
Start your first public row.
The free Starter Kit is the first row. The $17 Reset is the next one if you need more structure to get traction.
GET THE FREE KIT -> PAYDAY RESET