SutroP | Notion

Goal: Make Sutro the default starting point for ≥80% of Paragon IC searches, not just a place where candidates land after LinkedIn.

High‑level themes

Sourcing & Filters
- Filter completeness (seniority, years of experience, time in current job, skills/tags, sponsorship, location accuracy).
- Data coverage & freshness; fake profiles / AI roles; pre‑built candidate pools.
Workflow & Task Management
- Per‑candidate checklists, tasks, alerts & @mentions instead of tracking work in Google Docs / spreadsheets / Microsoft To Do / Slack.
Outreach & Communication
- Evergreen email templates, scheduled sends, multi‑channel sequences (email + phone + LinkedIn), and the ability to mass outbound even when candidates are “In Process”.
Pipeline Visibility & Analytics
- Clear IC pipeline views, funnel analytics, A/B testing on outbound, and dual ownership (sourcer vs recruiter) for attribution.
Job Setup, Onboarding & Dossiers
- Move onboarding kit, interview plan, scorecards, compensation, alignment docs into Sutro instead of living in Word/Google Docs; support multiple dossiers & “sub‑reqs” per project.
Integrations & Data Enrichment
- Better ingestion from LinkedIn, GitHub integration for eng roles, improved email/contact enrichment (Apollo), and scheduling integrations (Outlook/Zoom).
UX & Adoption
- Filter persistence / saved views, search history awareness, and a UX that makes people want to start in Sutro rather than LinkedIn.

1. Interview Dashboard - call summaries

Person	Rough usage split	What they like in Sutro	Biggest pain points / gaps	Top asks / ideas
Emily	~60% LinkedIn / 40% Sutro
New sourcing updates & alias titles; labels & sequences work OK.	Sutro often missing AI/ML profiles; fake profiles not detected; no “new hire” filter; only one dossier per project; manual tagging per role.	More AI/ML‑specific titles (principal, distinguished, applied research); multiple dossiers per project; label candidates with role at add‑time; filter out very recent job‑changers; sponsorship filter.
Julie	Mixed but LinkedIn‑leaning	Ecosystem & score; Sutro’s scoring system.	Fewer profiles & not up‑to‑date; region “must‑have” bug; weaker IC filters (experience, internal experience); tracking bulk roles & A/B tests via spreadsheets; can’t see funnels/ownership.	Better filters (experience, location); reliable “must‑have” regions; admin ingestion view for new titles/companies; bulk dossier automation; Search Insights with days‑in‑stage; dual ownership fields; outbound A/B analytics.
Kelly	~85% Sutro / 15% LinkedIn	Uses Sutro as source of truth; likes regions, ecosystem, company size filters; loves status calls.	Needs task management & checklists; no tenure/time‑in‑role filter; no skill tags; email templates & sequences are clunky; no scheduled send; limited pipeline analytics; onboarding kit lives outside Sutro; Zoom/Outlook not fully integrated.	Customizable task lists with alerts & @mentions; evergreen email templates + multi‑channel sequences; pipeline dashboards & funnel analytics; interview plan & scorecard + comp stored in req “overview”; better enrichment (Apollo‑like); scheduling integration.
Yates	Very LinkedIn‑first	Sutro OK for review; appreciates status calls.	LinkedIn UX & social graph are far better; Sutro feels clunkier to search; can’t mass email candidates once they’re In Process; uses external tools for tasks; wants richer tech signals (GitHub).	Mass outbound from In Process; sponsorship flag; task/to‑do system; GitHub integration or enrichment; better doc organization in reqs.
Kourtney	N/A (notes via Jurgen)	N/A	Needs customizable per‑candidate checklist of process steps; wants progress % per stage and visibility on outreach attempts and mediums.	Big library of optional “states” attached to stages; per‑candidate checklists with auto % completion; detailed outreach logging (channel, date, template used).
Ridhima & Tanya	Not specified	Expanded sub‑filters, viewed/not viewed, easy scorecard access.	Filter persistence; manual ecosystem selection; missing YoE filter; removed candidate visibility; location bug; desire for matching score and “copy dossier to other jobs”.	Persistent/saved filters; bulk ecosystem input; YoE and senior title filters; separate removed tab with reasons; candidate–job match score; copy dossier across reqs.

2. What’s Working Today (Keep / Amplify)

Across interviews, people do see value in Sutro:

Ecosystem & Company/Person sub‑filters – Seen as a differentiator vs LinkedIn when configured well.
Viewed / Not Viewed filters – Help manage which profiles still need attention.
Scorecards & scoring – Holistic view of candidate pedigree and easy access to scorecards is praised.
Status call objects – Kelly in particular loves these as a structure for client conversations.
Saved search history & saved searches – Exists but under‑discovered; PMs should treat this as a feature‑discovery/education problem, not a net‑new build.