Atlas Venture Studio
Platform guideHow the studio platform works

End-to-end workflows

Step-by-step: your own idea, a builder’s idea, recruitment, deletion, handover.

A. Your own idea as a public-audience test#

The fastest path from idea to live page.

  1. Experiments → New experiment. The Brief editor opens on a public-audience draft.
  2. Fill the requirement chips: Offer, Buyer, Price, a call to action card (Form needs nothing more; Booking or Deposit needs its link), and check the Decision date (six weeks out by default).
  3. Replace the draft-… Product name with the real one (e.g. ledgerfix). All six chips turn aqua.
  4. Check the preview at Desktop and 375 px. Save brief.
  5. Click Publish in the header. On the Evidence tab, confirm all four publish checks show ✓.
  6. On Distribution, add each channel where you will share the offer. Copy each tagged link and post it only in its channel.
  7. Fill in the rest of the brief (problem, outcome, proof, FAQ, feasibility risks) while it runs. These do not change the live page until you republish.
  8. As bookings and deposits come in, log them on Activity as conversation and deposit events. Log your time as intake and test hours.
  9. Check Evidence weekly: tagged visits, conversion and deposits by channel against the thresholds.
  10. At the decision date (the Needs you card will remind you): Review → record a verdict with a memo, then act on it — close, revise, or continue towards a pilot.

B. A builder's idea as a named-prospect test#

  1. Inbox: read the application; Accept → draft brief. The Brief editor opens on a named-prospect draft with the builder as partner.
  2. Outside the platform: agree terms with the builder using the collaboration agreement template (docs/) before publishing.
  3. Complete the brief (the six requirements), add feasibility risks with how each will be checked, and save.
  4. Publish; confirm the checks.
  5. On Distribution, Add prospects from the list the partner can reach (30–50 by default): name, company, email per line.
  6. Create partner link and send it to the partner with the prospects' personal links (Copy links or CSV). Ask the partner to send each prospect their own link and keep the outreach log current.
  7. Log conversations, objections, pilot commitments and deposits as events as the partner reports them. Watch Contacted and Qualified conversations on Evidence, and the amber Needs you card if outreach falls behind near the decision date.
  8. Clear or accept each feasibility risk on the Risks tab as its check completes.
  9. At the decision date: record a verdict. On continue, demo and pilot hours unlock only once every risk is cleared or accepted.
  10. When the test ends: ··· → Close test…, typing the product name (the partner is emailed), then Download export bundle if the partner asks within 14 days.

C. Studio recruitment (experiment 000)#

  1. Share tagged links to the Apply page: atlas-venturestudio.com/apply?utm_source=<where>&utm_campaign=<what>.
  2. Applications arrive in the Inbox carrying those tags; visits are counted too.
  3. Open experiment studio (from Experiments) to compare visits and applications by source and campaign, and accepted applications against the target of 3 in 3 weeks.
  4. Log recruitment time as hours against experiment 000, and record a review on the recruitment effort when useful.

D. A deletion request#

  1. Someone emails the studio asking to be deleted.
  2. People: search their email, and their name if they might be in an outreach log without an email.
  3. Check the pre-selected rows; tick any possible matches that are really them.
  4. Delete the selected rows, and note the counts in your reply.

E. Handover after a venture passes its gate#

  1. Record the continue verdict with the pilot evidence; clear or accept every feasibility risk.
  2. ··· → Download export bundle.
  3. Outside the platform: register the venture's own domain, deploy index.html as a static site in the partner's or venture's own hosting, and point the domain at it.
  4. ··· → Close test… on the studio copy. The studio subdomain keeps showing the closed notice and is never reused.

Common mistakes#

  • Publishing with the draft-… name: it is blocked; set the product name first.
  • Sharing an untagged link: visits then fall under "(untagged)" and cannot be credited to a channel.
  • Linking the home page for recruitment: link /apply so the application keeps its tags.
  • Expecting brief edits to show on a live page: they appear only after Republish with a reason.
  • Forgetting to log Cal.com bookings and Stripe deposits: the platform receives nothing from those services automatically.