Notion Free SOPs for indie founders: watch the solo block rules

Indie founders rarely lack notes. They lack notes another person can follow. When a contractor joins or you take a week off, release checks and support wording drift. Notion fits repeatable SOPs you can open under pressure. This article is not about using Notion as a light CRM, and not about NotebookLM-style deep reading. It covers how a solo Free workspace can hold an ops knowledge base, and when Plus is the rational upgrade. Pricing and block rules are anchored to Notion’s pricing page and block usage help observed on 2026-09-26.

Where Free actually pinches for one person

Pricing lists Free for individuals organizing personal projects and life, with pages and blocks unlimited for individuals and limited for two or more members. File uploads cap at 5MB each. Page history is 7 days. Block usage help clarifies that Free with only one workspace owner stays unlimited; once two or more workspace owners exist, the workspace gets a 1,000-block ceiling, after which you must upgrade to keep adding content, with a three-day grace period. Deleting content does not rewind the lifetime block counter.

For a solo builder, the first wall is often large images, demos, and outbound attachments, not blocks. If a contractor is added as a workspace owner instead of a guest, you inherit the 1,000-block rule. Guests are free per pricing language but only see invited pages, not the full teamspace tree.

Build one SOP database you will actually open

Create a database named Ops SOPs. Keep properties lean. Title the executable action, such as pre-release checklist. Status select uses Draft, Live, and Needs review. Trigger is a short sentence for when the page must open, such as before merging to main. Owner defaults to you until contractors arrive. Related tools names the apps you truly open. Last reviewed is a date. Related SOPs uses relations so one page does not swallow every topic.

Two views are enough at first. Live this week filters Status is Live. Review due filters Last reviewed older than ninety days or Status is Needs review. Do not invent five boards on day one. Add fields such as compliance tags only after a real pain appears.

Write each SOP body as ordered steps with a checkable outcome. Compress screenshots under 5MB or host them outside Notion. For secrets, write that values live in repository secrets. Never paste live credentials into Notion.

Week one: only five high-frequency actions

Do not draft a corporate manual. Write the five things you already do at least weekly. Common sets are release checks, defect escalation wording, content publishing, invoice or payout reconciliation, and contractor access onboarding. Stop when another person can finish the job with checkable outcomes. If a step depends on a missing SOP, link a draft title with a relation and fill it later.

A ninety-day review cadence is enough. When a payment webhook changes or support wording gets complaints, flip Status to Needs review immediately. SOP value is opens, not page count.

Structure the release checklist in three blocks. Code and tests names who merges and who watches Actions. Config and secrets names which environment variables changed. Outbound notice names who updates the status page, email, or changelog. Only then cut a tag. The support wording SOP must list promises you refuse, calm phrases you allow, and when a thread escalates to you.

Split the publishing SOP by channel. Site, docs, and social each need an entry point and a reviewer. Do not treat published as done without link checks and a place to store error screenshots. Keep payout reconciliation tied to the processors you actually use. Contractor access must list repository roles, Notion pages, whether production consoles are read-only, and the offboarding revoke list.

Keep meeting notes and idea scraps out of the SOP database. Notes are not SOPs. Ideas are not SOPs. Park them elsewhere so review views stay trustworthy.

When not to stay on Free, and when not to use Notion

If two or more owners already hit 1,000 blocks and you still need new content inside the grace window, compare Plus. Pricing lists Plus around $10 per member per month with stronger collaboration and upload headroom than Free. Solo users who constantly ship files above 5MB should upgrade or move binaries elsewhere. If you need more than about ten steady guests, re-read guest rules on the pricing page instead of promoting everyone to owner.

If your core need is relational ops CRM and automations, an Airtable-class tool may fit better. If the job is Q&A over a PDF stack, a NotebookLM-class tool is closer. If documents must stay on-prem and out of SaaS, Notion is not the default. If you only need tasks, a lighter todo app beats opening a knowledge base for ceremony.

If occasional large uploads are the only pain, external object storage can beat per-seat billing. If a second person edits the same database daily, Plus buys collaboration and history, not vanity. Enterprise audit marketing is not a week-one indie trigger.

Scenario defaults

A solo newsletter or plugin shipper should default to a Free single-member workspace, one SOP database, five high-frequency docs, and external file hosting. A solo SaaS with a steady contractor should invite guests to specific pages and avoid extra owners. Two partners editing the same knowledge base daily should price Plus per seat against the cost of repeated ceilings. If a company wiki already owns permissions, do not migrate for templates.

The narrow recommendation stays. For indie SOPs, default Notion Free with unlimited solo blocks, one database, two views, and five living documents. Upgrade on owner count, 5MB uploads, and collaboration intensity, not template-market anxiety. Recheck live pricing the day you change plans.

On a contractor’s last day, revoke page invites before you debate deleting their private drafts. Keep the access checklist inside the contractor onboarding SOP so verbal rules do not expire in a week. Secret rotation, production switches, and customer data exports each deserve their own list instead of a footnote on the release checklist.

If you ship bilingual products, title SOPs by task and keep one status and review date as the source of truth. Marketplace templates are for property ideas, not for cloning endless unused fields that punish every future fill-in.

Leave one acceptance test. Hand a Live SOP to someone who does not know the process this week and see whether they can finish checkable outcomes without pinging you. If they cannot, edit the document. That test beats buying another template pack.