The cost of a "blank workspace."

Every first-time founder I've ever watched run a seed round has done some version of the same thing. Before the first cold email, before the first deck, definitely before the first investor meeting, they spend a weekend "setting up the workspace."

A Notion page with twelve sub-pages. A Sheets file with three tabs. A homemade investor CRM with a Kanban view that took ninety minutes to format. Maybe a Linear project, just for the fundraising work. The weekend ends, the workspace looks beautiful, and they feel productive.

I want to be careful here, because the impulse is good. Founders who are organized about their round close their round faster. Structure matters. The instinct to build a workspace is not wrong.

But the cost of the way most founders build it is invisible and substantial, and I think it's worth naming.

The first-weekend tax.

The Notion page does not exist when you start the round. You make it. Making it well takes a weekend, conservatively. You will pick a page template, decide on a hierarchy, build the investor CRM table, decide which fields you want on the investor record, decide whether to use a Kanban or a Gallery view, decide whether to track tasks in Notion or in Linear, decide what colour the headers should be.

Each of those decisions is a tiny design exercise. None of them is the round. None of them produces a meeting. None of them moves a partner one step down your funnel.

I think of this as the first-weekend tax. It is the time you pay to use a blank-canvas tool before you can begin the actual work.

The tax compounds. After the first weekend, every month or so, you will spend another half-day reorganizing — adding a column, renaming a stage, splitting a database. The cumulative cost across a four-month round is closer to a week of founder time than to a weekend.

A week of founder time at seed is a meaningful percentage of your runway.

The second-weekend tax.

The harder, less-obvious cost is the second weekend. The one where you abandon the workspace.

It happens about ten weeks in. The investor CRM you built has gone stale — there are 22 investors in "Outreach" and three of them are actually already in "Diligence," but you forgot to drag the cards over because you were in back-to-back meetings. The Notion page for the deck has v3, but the version you actually sent yesterday is v5, which lives in your Google Drive. The Sheets file has a "stages" tab that you stopped updating in week four.

You realize the workspace is no longer a source of truth. You realize you have, in some sense, two workspaces — the Notion you set up, and the real one that lives in your head, your inbox, and your screen. The Notion now creates more friction than it removes.

So you stop using it. You don't delete it; deleting it feels like failure. You just stop opening the tab. The investors who close get tracked by hand for the rest of the round.

The cost of this is not the wasted weekend. The cost is that you ran the back half of your round without any system, after running the front half on a system that was decaying. The decay is the part nobody warns you about.

The Notion page you set up in week one looked organized. The way you actually ran your round in week ten was not.

Why blank canvases feel like rigor.

The reason this pattern is so common is that setting up the workspace feels like rigor. You are doing structured work. You are choosing categories, designing taxonomies, naming columns. Your brain rewards you the same way it would for writing a model.

But model-building has an output that lives — the numbers exist after you stop typing. Workspace-building has an output that decays — the structure exists only as long as you actively maintain it.

A useful test: at the end of any given weekend, does the work you did move forward an outside-facing artifact? A deck the investor will see, a meeting that will happen, an email you will send? Or does it move forward an inside-facing artifact — a CRM column, a Linear board, a Notion taxonomy?

The outside-facing artifacts compound. The inside-facing ones rot.

What good defaults give you.

Software with good defaults gives you a starting point. Not "do it our way or not at all" — but "if you don't know what columns your CRM should have, here are seven that work for almost everyone." If the defaults are good, you can start your round on day one instead of day eight. If the defaults are bad, you change them, and you have lost maybe an hour.

The asymmetry is large. Bad defaults cost an hour. Building from blank costs a weekend, plus the maintenance tax, plus the eventual abandonment.

This is not a Notion-specific complaint. Notion is excellent at what it does. The same argument applies to Coda, to any spreadsheet, to any framework where the maker hands you a primitive and says "configure it." For founders with infinite time and a clear sense of how their round will run, the primitive is a gift. For first-time founders with eleven weeks until close, the primitive is a tax disguised as a gift.

Where structure actually pays.

It is worth being clear about where structure does help. The investor brief — the one-page document we wrote about in the eight-steps piece — that document is worth a weekend. The deck is worth several weekends. The data room packet is worth a careful week. The forecast model is worth real time.

These are outside-facing artifacts. They get sent. They get seen. They produce decisions.

The inside-facing scaffolding — the CRM, the task tracker, the Notion hierarchy — should be something you adopt off the shelf, not something you build. The hours you save go to the artifacts the outside world will actually see.

The honest version.

I'm a designer. I love building beautiful inside-facing artifacts. I have done it on every round I have ever been part of. I am writing this piece because I have, several times, done it badly, and lost time I could not get back.

The honest version is: do not build the workspace. Use something with defaults, change the defaults if you must, and start the round. The week you save will be more than enough to compensate for any minor adjustment you wish you could have made to the column order of your homemade Kanban.

A round runs on the artifacts the world sees. Build those. Adopt the rest.