For founders applying to a16z speedrun
Your Speedrun application review By a panel built on how the partners read, and by alumni who got in.
Share the one you have, or build one from scratch in a conversation, and it tells you where it is strong, where it is thin, and what would change a reviewer’s mind.
About ten minutes · No account · Kept seven days, then deleted
The form asks for four paragraphs and a page of facts.
The hard part isn’t the writing. It’s knowing what you’re building well enough that the paragraphs write themselves: who it’s for, what changed, what’s working, why you.
Structure asks those questions first. The application is what falls out of the company.
Build the company. Then apply.
The conversation, the questions, the verdict, and the company to keep.
- 01
The conversation
Tell Structure what you’re building. Name, mission, who it’s for, how it decides. Ten minutes, and the company stands.
company/mission.mdcompany/positioning.mdcompany/voices/company.mdwritten as you talk - 02
The questions under the application
Six questions. The form’s paragraphs come out of the answers.
- What changed that makes this possible now.
- What you know that others don’t, and how you came to know it.
- Who exactly the user is, and what they do today instead.
- What’s working, with the number.
- Why you.
- How the founders know each other.
- 03
The verdict
Structure reads the application it compiled and says one of three things.
- Ready · two things to check before you apply
- Not ready yet · three things to strengthen
- Not ready · one thing missing
The third one is the point. It keeps the other two honest.
- 04
Yours to keep
At the end, the company leaves with you, the application inside it: a folder to download, or one commit in a private repository on your GitHub. You choose then, not before. Open it in Claude Code, Codex or Cursor and keep building.
AGENTS.mdCLAUDE.md.cursorrulesa download, or one commit on your GitHub
A second read, when you want one
When it says ready, ask for a read. Eleven readers, each a different lens on the same application. Each says the date it reads as of. Feedback, never a rewrite. Your voice stays yours.
Not affiliated with a16z. Just alumni.
- the strongest reason to advance
- the strongest objection
- three hard questions
- what would change the verdict
Who this is from
We went through speedrun and built the thing we wished we had. Structure isn’t part of the program, and nothing you write here goes to it. We run our own company on it.
applications started here.
Questions
Is Structure part of a16z speedrun?
No. We went through the program and built this on our own. Structure isn’t endorsed by the program, and nothing you write here reaches it.
What do you keep?
The conversation and the documents for seven days, and your email if you leave one, so the link we send you works. Nothing you answer is logged.
Do I need GitHub?
No. The folder you download is the same company, file for file. At the end you can put it on your GitHub instead, as one commit in a private repository of yours.
What does it cost?
Nothing. The conversation and the readers run on our model, at our cost.
What are the readers?
Eleven ways of reading the same application, each from a different angle: the reason to advance, the objection, the hard questions, what would change the verdict. They give feedback on your document and never rewrite it.
Can the verdict be wrong?
It can be incomplete, never flattering. It reads what is on the page by the same rules for everyone and names what is missing; it is not a prediction of what the program will decide.