What's in a scope file
Not a template. Not a tutorial. A complete blueprint an AI agent can execute.
The problem with starting from scratch
Every software idea dies the same way — not from bad ideas, but from everything that has to be true before a single line of code makes sense. What's the right database schema? How do auth and onboarding connect? Which API patterns hold up at scale? What does the UI system look like?
That's months of architecture decisions made under uncertainty. Scope files make those decisions for you — in advance, in writing, in a format an AI coding agent can act on immediately.
What you're buying
A scope file is a complete MWP workspace — a structured folder of markdown and architecture files that gives an AI agent everything it needs to build a production-ready platform from start to finish.
It's not documentation. It's an execution environment.
What's inside every scope file
Five layers, structured with the Model Workspace Protocol.
Project identity (CLAUDE.md)
The master reference file. Tells the AI agent what it's building, what rules apply, and where to find everything. One read, full context — structured with the Model Workspace Protocol so agents keep context across sessions without losing the thread.
Task routing (CONTEXT.md)
The index. Whatever the agent is working on — a new route, a UI component, a database query — this file points it to exactly where to look and which patterns apply. No guessing, no hallucinating conventions.
Stage specs (/specs)
The build plan, broken into discrete stages: auth and user model, core data model, API routes, UI components. Each stage is a self-contained instruction set with defined inputs, process, and outputs. The agent builds one stage at a time; you review and approve before it moves on.
Working artifacts
Session logs, per-sprint outputs, and running state that give the agent continuity across build sessions. The /checkpoint routine commits progress and carries context forward so nothing is lost between sessions.
Reference architecture (/reference)
Database schema (schema-map.md)
Every table, relationship, and field — annotated with the decisions. Not just what the schema is, but why it's shaped that way.
Tech stack (stack.md)
Framework, database, auth provider, hosting target, and every third-party service — with the exact configuration needed for production.
API patterns (api-patterns.md)
The canonical route pattern — error handling, auth middleware, response format, validation. Consistent from the first route to the last.
UI patterns + design tokens
Component composition, server vs. client decisions, layout conventions, and the design system in code-ready form. The agent follows a documented system instead of inventing one.
Gotchas (gotchas.md)
The traps, in wrong / right / why format. Connection pooling, naming collisions, auth edge cases — the things that cost days when you don't know them.
Architectural decisions (/decisions)
Why key choices were made — auth provider, ORM, hosting — with the tradeoffs documented, so you understand what you're changing six months from now.
The build experience
The scope file isn't read once at the start. It's active throughout the build.
The agent reads the stage spec, builds to the patterns in Layer 3, writes its output, and waits for your review. You approve, it moves to the next stage. If something looks wrong, you edit the output directly before the agent continues — the intermediate output is a file you can open and change.
At the end of each session, the agent runs /checkpoint: commits everything to git, updates the feature index, logs what was done. The next session starts exactly where the last one ended.
Practitioners who've used this structure report a consistent pattern: they intervene heavily at the first stage (setting direction), lightly in the middle (the patterns do the constraining), and do a final alignment pass at the end. The structure earns trust in the middle by being reliable.
What you own when it's done
Full source code — no licensing restrictions, no per-seat fees, no vendor lock-in
A deployed, production-ready platform on your own Vercel account
The scope files — rebuild, extend, or hand off to any developer, any time
The platform business — the market, the audience, the pricing
Sell it as a SaaS. White-label it to other businesses. Use it internally. Sell the source to other builders.The files are yours. The business is yours.
5 copies per platform, then it's gone
Each platform is limited to 5 scope-file purchases, then it's removed from the catalog. This isn't marketing urgency — it's structural.
The value of owning a platform in a specific market depends partly on not competing with 500 other people running the same platform in the same market. 5 buyers means 5 possible competitors — across a global market, that's close to no competition.
The scarcity is backed by live data. The counter on each platform card is real. When it hits 0, the platform is gone.
Platform quick facts
Two ways in
Common questions
Do I need to know how to code?
You need to open a terminal and follow a setup guide. The AI coding agent does the building — you review outputs at each stage and decide when to move forward. Designed for semi-technical buyers: you don't write the code, but you should be comfortable reading it.
What if I want you to build it for me?
The Full Build option ($1,999) is exactly that. We take the scope files and execute the build, then hand off a deployed, production-ready platform. Book a call from any platform card.
Can I buy scope files for multiple platforms?
Yes — buy as many individual platforms as you want, or get the Lifetime Deal and access all 80+ at once, plus everything we ship in the future.
What happens when a platform sells out?
When the fifth copy is purchased, the platform is removed from the catalog. We may re-release platforms in the future, but there are no guarantees — the live counter on each card is your signal.
What AI agent do you recommend?
The scope files are structured for Claude Code (Opus orchestrating, Sonnet for sub-tasks). They also work well with Cursor. Any agent that can read files and follow markdown instructions will work — the structure does the heavy lifting.
What if something breaks after I build it?
You own the source code — fix it, extend it, or hire anyone to maintain it. Every scope file includes a pnpm validate script for self-serve environment debugging, and community support is included.
Pick your market. Buy the files. Build the platform.
80+ B2B platforms, scoped and ready. 5 copies each, then they're gone.
Browse the platforms