Back to Projects
Case Study 01·Marketing Strategy · Information Architecture · Website Design · ConversionShipped

Website Revamp.

Marketing & Product Design Case Study — HireBound.io

Role
Positioning · IA · Homepage UX · Product Marketing
Timeline
2025
Company
HireBound
Status
Shipped
01 · Snapshot

At a glance.

Pain-led
Repositioning
Killed 'AI Agents That Actually Hire' for 'Hiring is broken. We fixed it.'
3-Ring
Product Architecture
Platform → Products → Features → Channels
Rebuilt
Homepage
Hero · Problem · Solution · Proof · Conversion
6+
Pages Designed
Homepage · 4 agent pages · Smart ATS · signup · demo
Restructured
Navigation
Platform promoted; agents and channels demoted
10+
Competitors Dissected
Juicebox · Spott · ModernLoop · LANDED · Candidately …
Start for Free
Conversion-focused CTA
Replaced 'Book a Demo' on the homepage hero
Lovable
Built & Shipped
Every section written as precise, implementation-ready prompts
Pull Quote

"Agents shouldn't explain themselves. They should explain what the recruiter no longer has to do."

02 · Project Overview

What it is, why it exists.

What

HireBound had a real product but a website that undersold it. The old framing led with the technology — "AI Agents That Actually Hire" — which asks a visitor to care about how it works before they've felt why it matters. Worse, the site had no coherent architecture: the platform, the agents, and the channels all sat at the same level, so a first-time visitor had to make a decision (which agent?) before they even understood what HireBound was.

Why

The revamp was a ground-up rebuild of both the story and the structure. On the story side: reframe everything around the recruiter's pain, and let the product show up as relief rather than as a spec sheet. On the structure side: establish a clear architecture — the platform is the gravity, the agents orbit it, the channels are how it reaches out — and make the navigation, the homepage, and every product page express that same hierarchy.

Problem

The result had to be a site that walks a visitor through an emotional arc — that's exactly my problem → they get it → the searching stops → the chasing stops → the coordination stops → I can finally trust what lands in my inbox — until the only thing left to do is sign up.

CEOCTOProductDesignGTM
03 · Positioning Strategy

From technology-first to pain-first.

Before a single section was designed, I fixed the foundation: rejected the product-first headline for a pain-first one. Technology-led framing asks the visitor to care about how it works before they've felt why it matters — pain-led framing meets them where they already are.

Previous Positioning

"AI Agents That Actually Hire"

Technology-first — leads with the product's mechanism before the visitor has felt the pain the product resolves.

New Positioning

"Hiring is broken. We fixed it."

Pain-first — names the recruiter's daily reality first, then lets the product appear as relief rather than a spec sheet.

What the visitor hears
Before

"They've built AI agents." — a category claim that requires the visitor to already believe AI agents are the answer.

After

"They understand what's broken." — an emotional handshake that earns the right to explain the product next.

What the page has to prove
Before

That the technology is real, novel, and trustworthy — an uphill proof burden before value is even implied.

After

That the pain is real and the fix is credible — proof burden shifts from the mechanism to the outcome.

How the rest of the site inherits it
Before

Every downstream page has to keep re-selling the AI premise before it can sell the workflow relief.

After

Every downstream page inherits an emotional starting point — agents, channels, and the platform become answers, not claims.

04 · Information Architecture

How 54 permissions are organized.

The three-ring model separated what customers buy the outcome of, what are merely features, and how the product reaches out — one mental model that finally made HireBound legible. Nav, homepage, and every product page inherit this hierarchy.

Level 01

Platform

The gravity. Smart ATS as the intelligence layer that sits on top of the recruiter's existing stack — not another ATS to migrate to.

Level 02

Products

What customers actually buy the outcome of — Sourcing and Screening. These earn a page each and a place in the primary story.

Level 03

Features

Scheduling, Evaluation, Analytics. Powerful, but they support the products; they don't lead the story.

Level 04

Channels

WhatsApp, Email, SMS, Voice. Delivery mechanisms — demoted to their proper level so a visitor never has to pick a channel before understanding the product.

How the hierarchy reads end-to-end
Smart ATSSourcing / ScreeningScheduling · Evaluation · AnalyticsWhatsApp · Email · SMS · Voice

Once this hierarchy existed on paper, the navigation, the homepage, and every product page collapsed into obvious decisions — because they were all expressing the same idea.

05 · Homepage Strategy

Five sections, one emotional arc.

The homepage was rebuilt as five sections engineered to flow as a single emotional arc. Each section moves the recruiter one step closer to "no reason left not to try this."

Stage 01

Hero

"I have a hiring problem."

Pain-led headline names the recruiter's reality on line one. No mechanism, no acronym, no self-congratulation.

Stage 02

Problem

"They understand my pain."

A scroll-driven section on a sticky dark canvas — word-by-word reveal — makes the visitor feel the cost of the status quo instead of reading about it.

Stage 03

Solution

"They have a solution."

Four agents on a Juicebox-style sticky-tab pattern. Each heading attacks a pain, not a feature — "Stop Searching. Start Choosing." over "AI Sourcing Tool."

Stage 04

Social Proof

"I trust them."

Proof placed exactly where doubt would otherwise creep in — after the promise, before the ask.

Stage 05

Conversion

"I'll try it."

"Start for Free" as the primary action — the arc ends with the shortest possible distance between conviction and action.

Read top-to-bottom, the page dismantles every excuse not to act — ending with "no excuses left → sign up."

04 · Research

What we learned, card by card.

Competitor Navigation Teardown

Challenge

How do 10+ recruiting-tech competitors organize their nav and IA — not their feature lists?

Observation

Candidately leads with a platform-first single dropdown; ModernLoop uses outcome-first labels ("Zero Click Scheduling"); LANDED offers a self-selection grid; Spott's "migrated off" logo strip does social proof and competitive positioning at once.

Outcome

Directly shaped HireBound's nav restructure — Platform promoted, agents grouped as products, channels demoted, and outcome-worded labels throughout.

30-Second Visitor Psychology

Challenge

What is a first-time visitor actually thinking, second by second?

Observation

0–3s: "what is this?" · 3–8s: "do they get my pain?" · 8–15s: "is it complex?" · 15–30s: "can I trust this?"

Outcome

The nav and homepage sequence were designed to answer each question in that exact order — one section per doubt.

Positioning-Clarity Audit

Challenge

Why does the product feel less clear than it actually is?

Observation

HireBound had genuine architecture — two real products feeding one platform — that most competitors lacked. It just hadn't been communicated.

Outcome

Reframed the whole project from "write better copy" to "express the structure that already exists."

Emotional-Arc Mapping

Challenge

How should each homepage section move the recruiter emotionally, not just informationally?

Observation

Feature-lists don't move people; shifts in felt experience do — from "I'm buried" to "I'm rescued."

Outcome

Mapped each section to a specific emotional shift so the page reads as a narrative that dismantles excuses one by one.

08 · Conversion Strategy

From 'Book a Demo' to 'Start for Free'.

The homepage hero CTA changed from "Book a Demo" to "Start for Free" — and a dedicated signup flow was built to receive it. Demo requests still exist, but on their own surface, with their own social proof and success state.

Old CTA
Book a Demo

Forced every high-intent visitor through a sales conversation before they could touch the product — high friction, one path, sales-team dependent.

New CTA
Start for Free

Opens a purpose-built two-column signup flow. Self-serve visitors go straight to product; sales-led visitors still find the demo path on its own surface.

Why the change matters
  • Serves the visitor whose intent is "let me try it" — the audience the old CTA quietly turned away.
  • Separates signup and demo into two considered journeys rather than one compromised one.
  • Keeps ICP landing pages on their existing CTAs so paid-media conversion paths stay intact.
  • Gives the site a self-serve motion the whole GTM can compound on.
Conversion funnel

Two considered journeys, not one compromised one.

Step 01

Homepage

Pain-led hero + emotional arc — earns the click.

Step 02

Start for Free

Primary CTA on the homepage hero.

Signup Flow

Two-column signup with its own social proof and a considered success state.

Book Demo

Dedicated demo surface — separate journey, separate proof, separate success state.

Step 03

Sales Conversation

For demo-path visitors — a qualified, high-intent conversation instead of a forced one.

The change wasn't just a button label — it was a decision about who the site is for on the first visit.

06 · Impact

Contribution and business outcomes.

My Contribution
Positioning Strategy

Reframed the entire site from product-led to pain-led — "Hiring is broken. We fixed it." and the emotional arc beneath it.

Information Architecture

Authored the three-ring architecture (Platform → Products → Features → Channels) that set the hierarchy for nav, homepage, and every page after.

Navigation Design

Restructured the nav — promoted Platform to its rightful anchor, resolved the flattened-hierarchy problem that forced premature decisions on visitors.

Homepage UX

Designed the full homepage as a single conversion arc — including the scroll-driven problem section and pain-first agent headings.

Conversion Design

Changed the hero CTA to "Start for Free" and designed the dedicated signup flow and book-a-demo experience as separate journeys.

Product Marketing

Designed the four agent pages on a shared skeleton, the Smart ATS "intelligence layer" positioning, and the "Meet June" spotlight.

Lovable Implementation

Carried the work from strategy through to a live site — every section shipped as precise, implementation-ready prompts.

Clearer
Messaging
A story a visitor understands in seconds
Coherent
Website Structure
Nav, homepage, and pages express one hierarchy
Unified
Marketing Consistency
Same pain-led architecture anchors cold email, Meta ads, SEO
Distinct
Competitive Positioning
The intelligence layer, not another ATS
Self-Serve
Conversion Foundation
"Start for Free" opens a purpose-built signup
Single
GTM Narrative
Every channel points at the same site with the same story
Callout

Placeholder — add signup / conversion-rate lift here once analytics stabilizes.

Callout

Placeholder — add pipeline / demo-request movement here once attribution is wired up.

Quantitative outcomes are held as placeholders until the site has enough runtime for honest attribution. No numbers are fabricated.
07 · Reflection

Learned, improved, next.

What I learned

A website should not explain a product. It should progressively remove every reason a visitor has not to act. Once the positioning was pain-led and the architecture was clear, the homepage, the product pages, the nav, and the conversion flows all fell into place — because they were expressing the same idea.

What I would improve

Wire conversion instrumentation on day one, not after launch. The strategic work is only half of the loop; the other half is watching where the arc still leaks and closing those gaps in weeks, not quarters.

What happened next

Everything downstream — cold email, Meta ads, SEO, sales collateral — now inherits the same pain-led architecture. The site is the spine; the rest of GTM compounds on it.