A category-balanced register of answers to standard investor due-diligence questions, structured as data-room-ready JSON, with category coverage, answered-count consistency, and per-answer length floors machine-checked.
You receive: A JSON object { company, round_stage, items: [ { id, category, question, answer, evidence_refs: [..], status } ], category_coverage: [ { category, answered_count } ] }. category must be exactly one of: financing, technology, product, market, business_model, team, financials_returns. status must be exactly one of: answered, na, pending. Each category_coverage answered_count must equal the count of answered items in that category.
What's verified: STUD verifies structure and internal consistency of the register, not the truth of its contents. Specifically, STUD verifies: the submission is a JSON object of at most 200000 characters with at most 200 items; company and round_stage are non-empty strings; items is a non-empty array where every item has a non-empty id, category, question, and status plus a string answer; ids are unique; every status is exactly one of: answered, na, pending; every category is exactly one of: financing, technology, product, market, business_model, team, financials_returns; every answered item has an answer of at least min_answer_chars characters after trimming whitespace (default 40, clamped to 1-2000); each required category has at least min_per_category answered items (default 1, clamped to 1-20); at least min_items_total items are answered overall (default 7, clamped to 1-200); no item in a required category is left pending; evidence_refs, when present on an item, is a list of non-empty strings; and category_coverage is present as a list where each answered_count equals the answered count recomputed from the items. That recount is the ONLY arithmetic checked: no valuations, totals, or financial figures inside the answers are computed or verified. Names in required_categories outside the seven-name list are dropped, and an empty selection falls back to all seven. STUD does NOT verify that any answer is true, accurate, or complete, that evidence_refs point to real documents, that the questions match what a specific investor will ask, or that meeting the length floor makes an answer substantive. company, round_stage, company_context, and known_gaps are operator context only and never change the machine verdict.
Opens soon
Cost20 credits
ProtectionHeld until verified delivery
This play is verified and ready. It opens soon, once sign-in and payments are live.
Example
A sample of what this play produces. Your result is generated for your inputs.
CompanySTUD.com
Round stagepre-seed
Items
Idfin-01
Categoryfinancing
QuestionWhat is the current round and how much is being raised?
AnswerSTUD.com is targeting an illustrative pre-seed raise of $1,000,000 to extend the founder-operator runway, grow the catalog of plays, and add judge-worker capacity. This target is a planning figure, not a committed raise; no capital beyond founder time has been secured to date.
Evidence refs
Fundraising plan (internal)
Statusanswered
Idfin-02
Categoryfinancing
QuestionWhat is the company's legal and funding status today?
AnswerSTUD.com is pre-seed and pre-revenue, currently in a soft launch. Entity formation is pending, since the company has not yet incorporated. The business has been funded by founder time only, and there is no external capital committed.
Statusanswered
Idtech-01
Categorytechnology
QuestionWhat is the core technology and how does it establish trust in delivered work?
AnswerA buyer commissions an outcome called a play. An agent produces the deliverable, and a platform-owned judge verifies the submission against the buyer's frozen acceptance criteria before any money settles. Verification runs in a process-isolated judge harness, so the acceptance check cannot be altered mid-run.
Evidence refs
Judge harness README
Statusanswered
Idtech-02
Categorytechnology
QuestionWhat is the technical stack and where is delivery risk concentrated?
AnswerThe buyer-facing platform is a Next.js application backed by a Postgres database (Neon in production). The judge and its reference oracles run in an isolated Python harness invoked per submission. The concentrated risk is judge coverage: each play needs a validator or oracle proven to enforce its own published contract before it can settle payment.
Statusanswered
Idprod-01
Categoryproduct
QuestionWhat problem does the product solve and how does it solve it?
AnswerAgents can now produce real knowledge work, but buyers have no way to trust or verify the output is correct, so they cannot safely pay for it. STUD freezes each play's acceptance criteria up front and has a platform-owned judge verify delivered work against them, so payment settles only on verified delivery.
Statusanswered
Idprod-02
Categoryproduct
QuestionHow broad is the current product catalog and how does it grow?
AnswerThe live catalog spans roughly 265 plays across 14 playbooks. New supply is added by mining reference sources for candidate designs, authoring validators or reference oracles for each one, and integrating a verified batch onto a preview branch before it ships to the production catalog.
Evidence refs
Catalog seed data
Statusanswered
Idmkt-01
Categorymarket
QuestionWhat is the addressable market and how is it sized?
AnswerSTUD sits in the AI agents market, cited externally at roughly $8B in 2025 and growing at a 42 to 50 percent CAGR. The addressable slice is verifiable knowledge work that agents can already produce but that buyers cannot yet safely pay for without a trust layer.
Statusanswered
Idmkt-02
Categorymarket
QuestionWho is the target customer and how is STUD positioned against alternatives?
AnswerThe target customer is solo and early-stage founders and small product teams commissioning verifiable knowledge work, with ops and engineering leads adopting agents as a secondary segment. The comparison set is general-purpose AI chat assistants, freelance marketplaces, and static documentation tools, none of which verify delivered output before payment.
Statusanswered
Idbm-01
Categorybusiness_model
QuestionHow does the company make money?
AnswerRevenue comes from monthly subscription plans plus one-time credit packs. Buyers spend credits to run plays: Standard at $20 per month for 500 credits, Pro at $60 per month for 1,500 credits, and Ultra at $180 per month for 5,000 credits, with lower annual pricing. Each play costs 10 to 40 credits at a $0.04 credit peg. A take rate on third-party supply is planned for a later phase.
Evidence refs
Pricing page
Statusanswered
Idbm-02
Categorybusiness_model
QuestionWhat is the gross margin profile of the business?
AnswerGross margin is estimated at roughly 87 percent, modeled in an 85 to 90 percent range. This is a modeled estimate rather than an audited figure, since the company is pre-revenue.
Statusanswered
Idteam-01
Categoryteam
QuestionWho is the founding team and what is their role?
AnswerSTUD.com is founded and operated by Dan Schmitz, who currently serves as the sole founder-operator across product, engineering, and delivery.
Statusanswered
Idteam-02
Categoryteam
QuestionWhat is the composition of the advisory board and its equity terms?
AnswerNo advisory board is in place at this pre-seed stage, so there are no advisor equity terms to disclose.
Statusna
Idfr-01
Categoryfinancials_returns
QuestionWhat do early launch economics look like?
AnswerIllustrative launch-scenario planning uses 200 launch signups, 40 buyers activated in month 1, and 25 retained by month 3, with a Standard to Pro to Ultra mix of 70:25:5 and roughly 12 plays run per Standard buyer per month. Planning assumes a $40 content-led CAC, 6 percent monthly logo churn, and 108 percent net revenue retention. These are illustrative planning figures, not actuals, since the company is pre-revenue.
Statusanswered
Idfr-02
Categoryfinancials_returns
QuestionWhat are the trailing twelve-month historical financial statements?
AnswerThere are no trailing financial statements to provide; the company is pre-revenue and has not yet generated historical results.