HireScout: User Journey Map

Four types of people visit HireScout. Each one needs a different path to their "aha moment." The goal: everyone sees ranked candidates within 2 minutes.

Person 1: Anonymous Visitor (not logged in)

Info:
99% of visitors. They found us via a link, a demo, or word of mouth. They need to be convinced before they sign up.

Their path

1

Landing page: see the interactive demo with mock data

They drag sliders, see candidates re-rank. First taste.

2

"Try with your own job" button goes to /try

No login required. They pick a domain or paste a JD.

3

Progress screen, then pipeline with real scored candidates

This is the aha moment. They see their job, real categories, ranked candidates.

4

Pipeline shows a banner: "Sign in to save this and use with real candidates"

Soft nudge. The demo data is ephemeral. Login to keep it.

Success:
Key: NO friction before the aha moment. Login comes AFTER they are convinced.

Person 2: Just Signed Up (no jobs yet)

Info:
They signed up (Google OAuth). Dashboard is empty. What now?

What they see on /dashboard

Welcome to HireScout

Two ways to get started:

Try with sample data

Generate a demo job with AI candidates to see how HireScout works

Connect Ashby

Pull real candidates from your ATS

Success:
Even after signing up, they might not be ready to connect Ashby. The demo path keeps them engaged.

Person 3: Has Demo Jobs (exploring)

Info:
They created 1-2 demo jobs. They like what they see. Now they want real data.

What they see on /dashboard

Warning:
You are using sample data. Connect Ashby to evaluate your real candidates.

Your Jobs

Senior Backend Engineer

Demo

10 candidates

Product Designer

Demo

5 candidates

Key behaviors

Demo jobs show a "Demo" badge. Clear visual distinction.

"Try another" button available. Let them explore different roles.

No "Generate Candidates" on real pipeline pages. Only on demo jobs.

Banner nudging to connect Ashby for real data.

Person 4: Real Customer (Ashby connected)

Info:
Connected Ashby. Has real jobs with real candidates. This is a paying customer.

What they see on /dashboard

Your Jobs

Software Lead

47 candidates

Product Designer

103 candidates

Key behaviors

No demo badges. No "Try another" button. Clean professional view.

No "Generate Candidates" on pipeline page. Candidates come from Ashby.

"New Job" creates a real job linked to Ashby.

/try still accessible from URL if they want to demo a different role (edge case).

How Demo Jobs Differ from Real Jobs

Demo Job

Created via /try flow

is_demo: true in MongoDB

Shows "Demo" badge in dashboard

"Generate Candidates" button visible

No Pull/Enrich/Score buttons

Export available (for evaluation)

Can be created without login

Real Job

Created via New Job or Ashby import

is_demo: false (or absent)

No badge in dashboard

No "Generate Candidates" button

Pull/Enrich/Score pipeline buttons

Full export with real data

Requires login + Ashby connection

Pipeline Page: Context-Aware Behavior

The pipeline page adapts based on whether the job is demo or real, and whether the user is logged in.

Demo job, not logged in

Warning:
Sign in with Google to save this pipeline and use HireScout with your real candidates.

Demo job, logged in

Info:
This is a demo job with sample data. Connect Ashby to evaluate real candidates.

Real job, logged in

No banners. Clean pipeline view. This is the product.