Audit · Assess & Decide · Writing & Content
Online-presence audit for demand, trust, and journey impact
I get a structured audit of my online presence: each surface, across website, branded search, social media, and review sites, rated on create-demand, build-trust, and potential-impact using fixed scales, with a short written note per surface and every negative-impact surface flagged.
You receive: A JSON object { company: string (must match the company you name), surfaces: [ { name (non-empty, unique), category (enum: website|branded_search|social_media|review_sites), url (well-formed http(s), required for website and review_sites), create_demand (enum: yes|somewhat|no|na), build_trust (enum: yes|somewhat|no|na), potential_impact (enum: positive|neutral|negative|na), notes (at least 5 words) } ], flagged_negative: [names of exactly the surfaces rated negative] }
Part of Distribution, Grow Partnerships
Example
A sample of what this play produces. Your result is generated for your inputs.
- Company
- STUD.com
Surfaces
stud.com homepage
- Category
- website
- Url
- https://stud.com/
- Create demand
- yes
- Build trust
- somewhat
- Potential impact
- positive
- Notes
- The living-system frame lands in the first screen: STUD knows your business, does the work, and learns from every result. Demand story is strong; trust would deepen with named founder presence and a visible changelog on the page.
stud.com play catalog
- Category
- website
- Url
- https://stud.com/plays
- Create demand
- yes
- Build trust
- yes
- Potential impact
- positive
- Notes
- 265 plays across 14 playbooks is the concrete proof behind the one-liner. Browsable depth with per-play outcomes creates demand and the specificity of each contract builds trust on its own.
stud.com credits page
- Category
- website
- Url
- https://stud.com/credits
- Create demand
- somewhat
- Build trust
- yes
- Potential impact
- positive
- Notes
- Prepaid credit packs (500 credits for $20 up to 5,000 for $200, plus annual prepay packs, 1 credit always 4 cents) with a 250 to 1,000 credit play cost range read honest and simple, and purchased credits never expire. Demand is secondary here; the page's job is removing price anxiety and it does.
stud.com play detail pages
- Category
- website
- Url
- https://stud.com/plays
- Create demand
- yes
- Build trust
- somewhat
- Potential impact
- positive
- Notes
- Each play page states the outcome, the intake, and an example artifact. Pages where the sample artifact is thin convert worse; the example is the trust load-bearer and should be treated as such.
Branded search: STUD.com
- Category
- branded_search
- Create demand
- somewhat
- Build trust
- somewhat
- Potential impact
- neutral
- Notes
- Searching the full brand with the .com suffix returns the site and the GitHub organization. Coverage is shallow but clean; no hostile or confusing results appear for the exact phrase.
Branded search: stud (bare term)
- Category
- branded_search
- Create demand
- no
- Build trust
- no
- Potential impact
- negative
- Notes
- The bare word is dominated by unrelated dictionary, fashion, and hardware results, so a prospect who drops the .com cannot find the company. Until domain authority grows, every outbound mention should carry the full STUD.com form.
GitHub organization stud-com
- Category
- social_media
- Create demand
- somewhat
- Build trust
- yes
- Potential impact
- positive
- Notes
- For the developer-lead segment of the target customer, visible engineering activity is the strongest trust surface STUD has today. It creates little direct demand but converts skeptics who check whether the product is real.
X (Twitter) presence
- Category
- social_media
- Create demand
- no
- Build trust
- no
- Potential impact
- negative
- Notes
- No active branded account exists at soft launch, so launch-community conversation about AI agents happens without STUD in it. For a content-led acquisition motion this is the cheapest gap to close and the most visible one left open.
LinkedIn company page
- Category
- social_media
- Create demand
- no
- Build trust
- somewhat
- Potential impact
- neutral
- Notes
- A placeholder-level page is expected at pre-seed and buyers discount its absence. It neither drives demand nor damages trust yet; it becomes a repair item only when outbound founder content starts.
Product Hunt listing
- Category
- review_sites
- Url
- https://www.producthunt.com/search?q=stud
- Create demand
- na
- Build trust
- na
- Potential impact
- neutral
- Notes
- No listing exists yet, which is correct sequencing for a pre-revenue soft launch. Launching here before retention proof would spend the one first impression the channel allows.
G2 category presence
- Category
- review_sites
- Url
- https://www.g2.com/search?query=stud.com
- Create demand
- na
- Build trust
- na
- Potential impact
- neutral
- Notes
- Absent, and appropriately so at this stage: review velocity needs a paying base first. Revisit once activated buyers from the launch cohort have run enough plays to review honestly.
Flagged negative
- Branded search: stud (bare term)
- X (Twitter) presence
Opens soon
STUD opens runs for everyone soon, on every play at once.
Scope of the check
What's verified: STUD verifies that the deliverable parses as a JSON audit object within a 100,000-character size bound, that the company field matches the company you name (ignoring case and spacing), that there is at least one surface, that every surface uses the fixed category and rating scales, that every surface carries a written note of at least 5 words, that website and review-site surfaces carry a well-formed http(s) URL, that surface names are non-empty and unique, that the count of website surfaces stays within your page cap (which must be between 1 and 100), that all four categories are present when you set that requirement to yes, and that flagged_negative lists exactly the surfaces rated negative potential impact. STUD does NOT verify that the ratings or notes are accurate or fair, that the audit covers every surface that exists for your business (including the ones you list in the intake), that any URL actually resolves or belongs to you, or that flagged surfaces are really harming your buyer journey. Your company description, target customer, and surface list intake fields are context for the operator, not enforced acceptance criteria.
Get early access to STUD the day it goes live.