NOT A CLIENTThis is a rebuild we made to show how we would do it. The payroll API company has not hired us and has not endorsed this work. We describe its public website only to explain what we would change.

ADVERTISEMENT · CASE STUDY · REBUILD
NOT A CLIENT · A rebuild we made to show how we'd do it

We rebuilt a payroll API company's website to show how more technical buyers could get answers and book a demo the same day.

Technical buyers who found the old site could not get a straight answer without booking a sales call first. Here is the journey a buyer takes on the old site, what we changed and why.

BUSINESS
Payroll API for HR software
SELLS THROUGH
Demos and sales calls
WHAT WE CHANGED
Messaging, qualifying, AI assistant, demo booking, follow-up, smart pages
BEFORE · THE OLD SITE
AFTER · OUR REBUILD
THE BUYER'S JOURNEY ON THE OLD SITE

Follow one buyer, Nina, a product lead at an HR software company, through the old site.

Nina is an illustrative buyer, but every step below is something the old site does today. Each one is a point where a good deal can slip away.

  1. STEP 1

    She searches for a payroll API and lands on the homepage.

    WHERE IT LEAKS

    The homepage says “The all-in-one payroll infrastructure platform”. It does not say who it is for or what the API does, so she has to dig to find out whether it fits her product.

  2. STEP 2

    She has a technical question about off-cycle payments.

    WHERE IT LEAKS

    The answer is not on the site, and the only way to ask is the “Talk to our team” button.

  3. STEP 3

    She clicks “Talk to our team”.

    WHERE IT LEAKS

    The page says a rep will reach out to schedule a call. It never asks what she is building, so the rep cannot tell how ready she is.

  4. STEP 4

    She waits to hear back.

    WHERE IT LEAKS

    Finding a time takes several emails. Meanwhile another vendor's docs answer her question, and she books their demo instead.

  5. STEP 5

    She has the demo and takes it to her team.

    WHERE IT LEAKS

    Nothing on the site keeps the conversation going, so the deal goes quiet while her team decides.

WHAT WE CHANGED, AND WHY

We changed six things, and each one closes a step where Nina could slip away.

None of it needs a bigger marketing budget. It changes what the site says, how fast it answers and how easy it is to book a demo.

  1. CHANGE 1 OF 6 · MESSAGING

    Say what it does and who it is for

    BEFORE

    The all-in-one payroll infrastructure platform.

    AFTER

    Add payroll to your HR software with one API.

    WHY

    Technical buyers decide in seconds whether a product fits. A first line that names the job and the buyer saves them the digging.

  2. CHANGE 2 OF 6 · QUALIFYING

    Ask four questions before the demo

    BEFORE

    Contact sales, and a rep will reach out.

    AFTER

    Company size, role, what you are building and when you want to launch.

    WHY

    The answers tell sales who is ready to buy, and send students and vendors to the docs instead of onto the calendar.

  3. CHANGE 3 OF 6 · AI ASSISTANT

    Answer technical questions from the docs

    BEFORE

    Every question goes through “Talk to our team”.

    AFTER

    An assistant that has read the docs answers questions like “Can we run off-cycle payments?” at any hour, and hands over to an engineer when a person is needed.

    WHY

    Buyers comparing vendors want answers the same day. The vendor whose docs answer first is often the one that gets the demo.

  4. CHANGE 4 OF 6 · BOOKING

    Book the demo straight onto an engineer's calendar

    BEFORE

    A rep will reach out to schedule a call.

    AFTER

    Qualified buyers pick a time, such as Thursday at 2:00 PM, and invite their own colleagues.

    WHY

    Every email spent finding a time is a chance for the buyer to book with someone else.

  5. CHANGE 5 OF 6 · FOLLOW-UP

    Keep the deal moving after the demo

    BEFORE

    Nothing on the site after the demo.

    AFTER

    A recap and the recording the same day, a security pack for IT and answers for the finance team.

    WHY

    Payroll is a decision several people make. Short, useful notes keep the deal from going quiet while they talk.

  6. CHANGE 6 OF 6 · SMART PAGES

    Write a page for each use case

    BEFORE

    One product page for every kind of buyer.

    AFTER

    Payroll for HR platforms, off-cycle payments, contractor payouts, and so on.

    WHY

    Buyers search for their own use case. A page written for each answers the search and leads to the same demo booking.

HOW WE WOULD KNOW IT WORKED

We have not run this on their site, because they are not a client. Here is what we would measure if we did.

We would watch three numbers: how many visitors finish the qualifying questions, how many of them book a demo, and how many demos turn into signed contracts. On a client's site, these are the numbers we report every month.

SEE WHERE YOURS LEAKS

Start with the free test.

Ten questions about how your leads come in and what happens next. You get a free result straight away, and a full plan with a review of your own site if you want it.

Take the Lead Leak Test → 2 minutes · Free · No call needed
WANT YOURS REBUILT?

Get the same teardown on your site.

In a Leak Audit we record a walk through your site as a buyer, then send a ranked list of what to change and why. You can make the changes yourself, or have us rebuild it with you.

Book a Leak Audit → $497 · Recorded teardown and a ranked fix list

A full rebuild is part of the website overhaul, priced after a short conversation.

See all case studies →