The pages#
The studio site at atlas-venturestudio.com recruits builders and stands for experiment 000. Every page shares the Meridian header — the "A" tile and serif name linking Home, then Home, How it works, Guide and a dark Apply button — and a footer with the trading name and the privacy notice link.
| Page | Address | What it shows |
|---|---|---|
| Home | / |
The pitch in a large serif headline ("Test demand for your prototype. Then take it to production."): builders run the offer test with the studio's page, links and guidance, and ventures that pass are taken to production with the studio — production hardening, deployment and launch — for a capped revenue share. Then a card with Apply with your prototype and How it works. |
| How it works | /how |
Five numbered cards: apply; plan the test together (brief and pass thresholds); the builder runs the offer test (about six weeks, with the studio's page, personal or tagged links and outreach log); review the results together (continue, revise or stop); take it to production (after feasibility checks: production hardening, deployment and launch, for a capped revenue share). |
| Apply | /apply |
The application form, in a card (below). |
| Guide | /guide |
This platform guide, readable by anyone. Guide pages are not counted as studio visits. |
| Privacy notice | /privacy |
Rendered from docs/privacy-notice.md as a readable page. Covers the studio and every experiment page. |
The application form#
A builder fills it in once; it lands in the Inbox as a new application.
| Field | Required | What it is for | Rules |
|---|---|---|---|
| Your name | Yes | Who is applying; becomes the partner name if accepted. | Up to 200 characters |
| Yes | Where you reply; becomes the partner email (it receives the close notice). | Must look like an email; up to 320 | |
| Link to your prototype | No | Something a buyer could see working. | Must start with http:// or https:// |
| Who buys it? | Yes | The paying buyer and their company type; prefills the brief's Buyer. | Up to 4000 |
| What problem does it solve for them? | Yes | Prefills the brief's Problem. | Up to 4000 |
| How can you reach those buyers? | No | Named contacts, a community or an audience — this suggests the test type. | Up to 4000 |
| (hidden) spam trap | — | A honeypot field, invisible to people. Any value means a bot, and the post is rejected. | Must be empty |
| (hidden) utm_source, utm_campaign | — | Copied from the Apply page's own address, so a tagged link attributes the application. | Filled automatically |
When the builder clicks Send application:
- invalid fields re-show the form with a red banner and a message under each field, and nothing is saved;
- a valid application is stored with status new and the builder sees a "Thank you" card;
- five submissions per 10 minutes are allowed from one visitor; the sixth gets "Too many submissions".
Link to /apply, not the home page. UTM tags are read from the Apply page's own address. A tagged link to Home still counts the visit, but the tags are lost when the visitor clicks through to Apply. Share
/apply?utm_source=…&utm_campaign=….
Visit counting#
Every studio page, and every experiment page, loads one small first-party script that sends a visit record to the app: which experiment, the ?r= prospect ref, the UTM tags and the referring page.
- It sets no cookie.
- The visitor's IP address is turned into a one-way code that changes daily and is never stored.
- Obvious bots (crawlers, link previews, scripts) are ignored.
- One visitor can send at most 60 visits per 10 minutes.
Studio-page visits count under experiment 000; see Evidence.