HoneyBook Pipelines Explained in Plain English

If you open HoneyBook, look at your pipeline, and immediately wonder why half your projects are sitting in stages that make zero sense, we need to talk.

Because HoneyBook pipelines are supposed to make it easier to see where every lead and client stands.

You shouldn’t have to click into five projects, search your inbox, and consult a sticky note from three Tuesdays ago to figure out who still needs to sign a contract.

A good pipeline gives you that answer at a glance.

But there’s a catch.

Your pipeline needs to match how you actually run your business. Not how you think a CRM should work. Not a complicated 17-stage process you copied from someone else.

Your process.

I’ve been a certified HoneyBook Pro for five years, and this is one of those parts of a setting up HoneyBook that looks simple until you start connecting it to everything else.

If you’re tired of trying to piece your HoneyBook system together yourself, check out my HoneyBook services. I offer done-for-you setup, done-with-you help, and consulting depending on how much support you actually need.

Now, let’s make your pipeline make sense.

What Is a HoneyBook Pipeline?

A HoneyBook pipeline is the place where you track your projects based on where they are in your client process.

Think of it like the status board for your business.

A new inquiry might start in an Inquiry stage. Once you send information, it could move to Follow Up. After the client signs their contract, it could move to Booked or Planning.

HoneyBook describes pipeline stages as the steps in your business process. You can add, rename, reorder, and delete pipeline stages to fit the way you work.

The exact names aren’t the important part.

What matters is that when you see a project sitting in a stage, you know what has happened and what needs to happen next.

That’s the job of your pipeline.

Why Do HoneyBook Pipelines Matter So Much?

Your pipeline isn’t just there to make the Projects page look organized.

It helps answer a very practical question:

Where does every project stand right now?

That’s especially useful when you’re handling several inquiries and booked clients at once.

For example, you might want to know:

• Who just inquired?
• Who needs a follow-up?
• Who received a proposal?
• Who signed?
• Who paid?
• Who is actively working with you?
• Which projects are finished?

If your HoneyBook pipelines don’t reflect those points in your process, you lose that quick overview.

Then you start keeping the missing information somewhere else.

Maybe it’s in your head. Maybe it’s your inbox. Maybe it’s a notebook on your desk with handwriting you’ll need forensic equipment to decode later.

That’s usually a sign your HoneyBook systems aren’t doing enough of the organizing for you.

What’s the Difference Between HoneyBook Pipeline Stages and Automations?

This is where people can get tangled up because pipeline stages and automations do two different jobs.

A pipeline stage tells you where a project is.

An automation tells HoneyBook what to do when certain criteria are met.

For example:

Your pipeline might include a stage called Proposal Sent.

Separately, an automation could send an email, create a task, send a Smart File, add a tag, or move a project to another pipeline stage based on its trigger and setup.

HoneyBook’s current Automations 2.0 system uses triggers, actions, waits, and conditions. It also includes a “Move pipeline stage” action. So your automations and pipeline can work together without being the same thing.

There’s another distinction worth knowing. HoneyBook also has pipeline automations, which automatically move projects between stages when certain events happen. HoneyBook specifically separates these settings from its broader Automations feature.

The simple version?

Stages organize the project. Automations perform actions.

Once you understand that difference, building your HoneyBook setup gets a whole lot easier.

Want to know what HoneyBook automations can actually do now? I break down Automations 2.0, including triggers, conditional logic, wait steps, integrations, and what you can finally stop doing manually. Read my HoneyBook Automations 2.0 guide.

How Do You Build a HoneyBook Pipeline That Matches Your Process?

Don’t start inside HoneyBook.

Seriously.

Start by writing down what happens from the moment someone inquires until the project is finished.

Keep it simple.

For example:

Inquiry → Follow Up → Call Booked → Proposal Sent → Onboarding → In Progress → Project Complete

Your process might look completely different, and that’s fine.

Then ask yourself one question for every stage:

Does reaching this stage tell me something useful about this project?

If the answer is no, you probably don’t need it.

You also don’t need a separate stage for every tiny task you complete.

“Questionnaire Sent,” “Questionnaire Opened,” “Questionnaire Completed,” and “Reviewed Questionnaire” might look beautifully detailed on paper. In practice, you may have created four stages you’ll now have to keep track of.

Your HoneyBook pipeline should give you visibility without creating more admin work.

This is also why I map the client’s actual process when I’m handling a done-for-you HoneyBook setup. The goal isn’t to shove every business into the same template. The system needs to fit the way that business sells, books, and works with clients.

If you’d rather have your HoneyBook systems, workflows, Smart Files, and automations built around your business instead of figuring out every setting yourself, my HoneyBook Full Setup starts at $2,197 USD / $3,049 CAD and takes 3–4 weeks.

What HoneyBook Pipeline Mistakes Create the Most Chaos?

Most pipeline problems aren’t because you need more stages.

They’re usually because the stages don’t have a clear purpose.

Too many stages

More detail isn’t automatically more useful.

If you can’t explain the difference between two stages in one sentence, ask whether you need both.

Vague stage names

A stage called “Working On It” might make sense today.

Three weeks from now? Good luck.

Use names tied to a clear point in your process.

Building around HoneyBook instead of your business

Your process should determine your HoneyBook systems setup, not the other way around.

Map what needs to happen first. Then decide how HoneyBook can support it.

Forgetting about automatic stage movement

HoneyBook can automatically move projects between pipeline stages after certain events. Automations 2.0 can also include a Move Pipeline Stage action.

That means you need to think about how projects are moving instead of assuming you’ll always drag them around manually.

Otherwise, you can end up with projects sitting in the wrong place while your automation is happily doing something completely different behind the scenes.

When Should You Create Multiple HoneyBook Pipelines?

Here’s where the wording gets important.

Within one company, HoneyBook currently gives you a main pipeline plus custom pipeline views, rather than a bunch of completely separate pipelines.

Custom pipeline views can hide or show certain stages and save filters, columns, and sorting preferences.

So if you’re trying to separate different types of work, you may need a custom view, project type, or filter instead of another pipeline.

For example, HoneyBook allows you to filter pipeline projects by project type, tags, and lead source.

If you operate separate companies or brands inside one HoneyBook account, that’s different. HoneyBook allows multiple companies under one HoneyBook account, and each company can have its own project pipeline, branding, templates, and bank accounts.

Before adding more structure, ask what problem you’re trying to solve.

If the answer is simply, “I don’t want to see all these projects at once,” a custom view or filter may solve it without making your HoneyBook setup more complicated.

How Do You Know If Your HoneyBook Pipeline Is Actually Working?

Open your pipeline and try this test.

Can you tell what needs your attention without opening every project?

If yes, you’re headed in the right direction.

If not, look for the friction.

Ask yourself:

• Do I know what every stage means?
• Does each stage represent a useful point in my process?
• Are projects moving into the right stages?
• Can I quickly find leads that need follow-up?
• Can I tell which projects are booked?
• Am I manually tracking information somewhere else because my pipeline doesn’t show me what I need?

That last question is a big one.

Your pipeline doesn’t need to contain every piece of project information. But if you’ve built a second tracking system because you don’t trust the first one, it’s worth looking at why.

Sometimes the pipeline needs a small cleanup.

Sometimes the problem is bigger and involves your automations, Smart Files, project types, or overall client workflow.

Not sure if your pipeline is the only thing causing problems? Start with my guide to 5 HoneyBook Features You’re Probably Using Wrong (And How to Fix Them). If you already have HoneyBook but aren’t sure what’s causing the bigger mess, my HoneyBook Audit is designed for exactly that. I review your workflows, automations, and client experience, then give you clear recommendations for what to fix next.

HoneyBook Pipeline FAQs

Can clients see my HoneyBook pipeline?

No. Your HoneyBook pipeline is an internal tool for you and your team. Clients don’t see your pipeline stages or where you’ve placed their project.

That means your stage names should be useful to you. You don’t need to make them client-facing or worry about whether “Needs Follow-Up” sounds pretty.

Clear beats cute here.

Can I move a project backward in my HoneyBook pipeline?

Yes. You can manually move a project from one pipeline stage to another, including back to an earlier stage.

This can be useful when a client’s project doesn’t follow the neat little path you expected (because clients do occasionally have other plans).

Just keep your automations in mind. If you’ve set up automation based on pipeline movement or other project activity, make sure manually changing a stage won’t create an action you didn’t intend.

What happens to completed projects in HoneyBook?

Once you’re finished working with a client and no longer need the project sitting in your active pipeline, you can archive it.

Archiving helps keep your active pipeline focused on the leads and clients you’re currently working with without deleting the project and its history.

It’s a simple cleanup step, but it makes a big difference when you’ve been using HoneyBook for a while and your project list starts getting crowded.

Why is a project in the wrong HoneyBook pipeline stage?

There isn’t one answer because it depends on how your account is set up.

Start by checking whether the project should have moved manually, through a pipeline automation, or through an action inside one of your HoneyBook automations.

Then look at what actually happened in the project.

If projects regularly end up in the wrong stage, don’t keep dragging them back and calling it fixed. That’s a sign you need to review how your pipeline and automations are working together.

Your HoneyBook Pipeline Should Tell You What’s Happening

A good pipeline is pretty boring.

You open it.

You know where your projects stand.

You know what needs attention.

Then you get back to running your business.

If your HoneyBook pipelines leave you with more questions than answers, don’t start randomly adding stages and hoping something clicks.

Look at your actual process first. Then build HoneyBook around it.

And if you’ve reached the point where you’d rather have a HoneyBook expert sort out the system with you, you have options.

If you want me to build the system for you, start with my HoneyBook Full Setup. If you already have an account and want to fix or improve it together in real time, my 2-hour HoneyBook Intensive is the better fit. And if you want a professional review before making changes yourself, choose a HoneyBook Audit or Strategy Call.

You can also contact me and we can figure out which level of support makes the most sense for you.