Skip to content

User profile metadata as B2B sales channel

Date parked: 2026-06-02 Triggered by: Devin observation after profile-schema audit (school/discipline/licensure_state) Status: PARKED — note for later strategic use

Concept

public.profiles already captures school, discipline, licensure_state, exam_path, exam_date, pe_number, cred_type. As StampReady's user base grows, this becomes a B2B revenue channel:

  • Universities / engineering programs — sponsor Pro access for their seniors; gain visibility into pass-rate signals tied to their school's name. Outcome data is currency for ABET reporting + recruitment marketing.
  • Engineering firms — recruit by discipline + state. "20 FE Mech candidates in Texas approaching licensure" = high-value funnel for hiring partners.
  • State licensing boards / regional sections of ASCE/ASME — sponsorship for state-specific cohorts.
  • Bar-prep model precedent — Themis/Barbri sell to law schools who pay for their students.

Current data status (2026-06-02)

  • 36 total profiles
  • school filled: 4 (11%)
  • discipline filled: 18 (50%)
  • licensure_state filled: 25 (69%)
  • exam_path filled: 17 (47%)
  • exam_date filled: 18 (50%)

Pre-requisites before this is monetizable

  1. Tighten onboarding wizard to require school + discipline + state at signup (currently optional)
  2. Push these as PostHog person properties via identify() (~30 min) — enables native HogQL slicing
  3. Add a consent_school_share flag if we plan to expose data back to a school sponsor (privacy)
  4. ToS / Privacy Policy needs language for B2B aggregate-data sharing
  5. Build an aggregate-stats dashboard that can be shared with a sponsoring institution

Revival triggers

  • ≥500 active users with school + discipline + state filled, OR
  • First inbound interest from a university / engineering firm / state board, OR
  • Mid-2027 — once organic growth stalls and B2C ceiling becomes visible

Cost when revived

  • ~2 hours: tighten onboarding wizard (require fields)
  • ~30 min: PostHog identify() with person properties
  • ~1 day: aggregate-stats dashboard (schools/disciplines/states cohort view)
  • ~2 days: legal review of ToS aggregate-data clause + privacy policy update
  • ~$0: data is already being collected