17hats Pipelines: Why Workflows Have to Come First

Have you ever been in the middle of something completely unrelated to work and suddenly wondered whether you followed up with that lead from last week? Or whether a client ever signed that contract you sent? It happens because your brain is doing a job your system should be doing. That’s exactly the problem a pipeline is built to solve.

That’s not a focus problem. It’s a sign that something in your business doesn’t have a clear home except your memory. A pipeline can fix that. But before we get into what a pipeline does, I want to be upfront about something I tell almost every client who asks about them – pipelines are not where you start.

A Pipeline Is a Filter, Not a Tracker

Here’s the distinction that trips people up. A pipeline doesn’t do anything. It doesn’t send an email, move a project forward, or remind anyone of anything. A pipeline simply shows you, visually, where things already stand based on what’s already happened. It’s a filter sitting on top of your business, not an engine running underneath it.

That matters because it changes what a pipeline is actually for. It’s not there to track every detail of a client relationship. It’s there so nothing falls through the cracks, no matter what stage or phase something is in. A lead that’s gone quiet, a contract that’s been sitting unsigned a little too long, a project that should have moved to the next stage by now and didn’t. A pipeline is the thing that lets you glance at your business and catch those moments before they become a problem, instead of discovering them three weeks later when a client mentions it themselves.

Why Workflows Have to Come First

This is the part I want to be direct about, because I see business owners get excited about pipelines and want to build one before they’ve laid the groundwork that actually makes it work.

A pipeline only knows where to place something because of the tags attached to it. And those tags only get applied reliably, consistently, every single time, when they’re built into a workflow. If your workflows aren’t dialed in yet, you don’t actually know which step in your process should be adding a tag, which step should be removing it, or what the right trigger point even is. Trying to build a pipeline before that groundwork is laid usually means guessing at your stages, guessing at your tags, and ending up with a pipeline that looks organized but isn’t actually reliable.

This is why I almost always tell clients to hold off on pipelines until their workflows are solid. Get the engine running first. Know exactly what happens at each step of your process and make sure your workflows are working correctly. Once that’s happening, the pipeline becomes almost effortless to set up, because the information can easily be added to the right step of your workflow. Build it the other way around, and you’ll end up reworking the pipeline every time you realize your workflow was missing a step.

Your Process Already Has Stages. A Pipeline Just Shows Them to You.

Every client who works with you moves through the same basic arc, whether you’ve ever written it down or not. They start as a lead. They book. There’s a stretch of time before the service happens. The service itself happens. And then there’s everything that comes after.

I think about the client journey in five stages – the lead stage, the booking stage, the pre-service stage, the service itself, and the post-service stage. Most business owners know these stages exist, but without a system to track them, it’s easy to lose sight of where any given client or lead actually stands. Someone might be sitting in the booking stage waiting on a contract while you’re mentally treating them as already booked. A pipeline makes those distinctions visible so nothing gets ahead of itself or falls behind without you noticing.

Instead of a mental list of “people I’m thinking about,” you can create a visual filter that shows you, at a glance, exactly where every lead and every project actually stands. Not where you think they stand. Where they stand.

What Changes When the Map Exists Outside Your Head

The real value of a pipeline isn’t that it looks tidy. It’s that it takes a question you used to have to answer from memory and turns it into something you can just look at.

Did I follow up with that inquiry? Look at the pipeline. Is the contract out for the Petersons? Look at the pipeline. Who’s been sitting in the same stage longer than they should have? Look at the pipeline. None of that requires you to scroll through your inbox or try to reconstruct what happened from a string of old text messages. It’s just there, the way a whiteboard in a project room is just there for anyone walking by.

Having that visual display matters more than it sounds like it should. The mental load of tracking client status isn’t usually one big thing. It’s dozens of small things, stacking up across every active relationship you’re handling at once. A pipeline doesn’t make the work disappear. It moves the tracking part of the work out of your head and into a system, which frees up the part of your brain that was doing that job all day long to do something else instead, like actually being present with the person in front of you.

How a Pipeline Actually Moves

This is the part that surprises people. A pipeline isn’t something you update by hand every time something happens. It can move on its own, based on the tags your workflows apply.

When a lead comes in, a tag gets applied. When they sign a contract, another tag gets applied, automatically, as part of the workflow doing its job in the background. The pipeline is simply watching those tags and placing each contact or project in the stage that matches. You’re not the one dragging projects from column to column. The system is doing that based on what’s actually happened, which is exactly why the workflow has to be the part you trust first. A pipeline can’t be more reliable than the tags feeding it, and the tags can’t be reliable until the workflow applying them is solid.

I wrote more about keeping tags organized, including a simple way to track them, in this post on 17hats tags. If you haven’t read that one yet, it’s worth doing before you think much further about pipelines. Tags are the engine. Workflows are what fuel the engine consistently. The pipeline is just the dashboard that shows you what’s already happening inside of your system.

What to Look At in Your Own Process

Before you think about building a pipeline, it’s worth asking a more basic question first – are your workflows actually doing what they’re supposed to, every time, without you having to double check? If the honest answer is “mostly” or “it depends”, that’s not a pipeline problem. It’s a workflow problem. And that’s the place to start.

Once your workflows feel solid, building a pipeline starts with one question – what are the things in your business you absolutely cannot afford to drop? For some people that’s the stages of the client journey, making sure every lead, booking, and active project is accounted for and moving forward. For others it’s something more operational. They might need to see whose product order has been placed, whose has come in, and whose is still waiting to go out. A business with multiple service types might need a pipeline that shows where every project stands across all of them at once. There’s no single right answer, and honestly that’s the point. A pipeline should be built around what your specific business needs to keep visible, not borrowed from someone else’s setup that kind of, almost fits.

The most useful starting point is usually your own pain points. Where do things tend to slip right now? What do you find yourself checking manually because you’re not confident it won’t get missed? That’s how your pipelines should be built.

Frequently Asked Questions

Should I set up a pipeline before or after my workflows?

After. A pipeline depends on tags, and tags depend on workflows applying them consistently. If your workflows aren’t dialed in yet, a pipeline will end up reflecting guesswork instead of what’s actually happening. Get your workflows solid first, and the pipeline will come together quickly once you do.

Do I need a complicated pipeline for this to work?

No. A simple pipeline with four or five phases that reflect your actual process will do far more for you than an elaborate one that tries to capture every possible scenario. Start simple and adjust as you learn what you actually need to see.

Does a pipeline replace tags, or work alongside them?

It works alongside them, and depends entirely on them. Tags are what tell 17hats where a contact or project belongs in the pipeline. Without consistent tagging coming from a solid workflow, a pipeline doesn’t have reliable information to work from.

Can a pipeline track more than one type of process?

Yes. Many business owners build separate pipelines for different parts of their business, such as one for new leads and another for an ongoing client relationship. The right setup depends on how distinct those processes actually are in your business.

What if my process changes over time?

That’s normal, and a pipeline isn’t something you set up once and never touch again. As your business evolves, it’s worth revisiting your setups to make sure they still reflect how you actually work now, not how you worked when you first built it.

Where You Go From Here

A pipeline isn’t really about the visual. It’s about not having to be the one holding all of that information at once, no matter what stage or phase something is in. But that only works once the engine underneath it, your workflows, is doing its job consistently. Build the pipeline too early and you’re just adding a nicer-looking version of the same guesswork. Build it after your workflows are solid, and it becomes the simplest, most reliable filter you have for catching anything that might otherwise fall through the cracks.

If you’re not sure whether your workflows are ready for a pipeline, or you want a clear picture of what’s working and what isn’t before you build one, that’s exactly what a 17hats Audit is for. We’ll take a close look at your process as it actually runs today and figure out what comes next, in the right order. If that feels like the right next step, but you’re not quite sure, you’re always welcome to start with a free Discovery Call and we’ll talk it through.

---

---

---

Disclaimer: Some of the links are affiliate links, which means that if you choose to make a purchase, I will earn a commission. This commission comes at no additional cost to you. Please understand that I have experience with all of these companies, and I recommend them because they are helpful and useful, not because of the small commissions I make if you decide to buy something.  Please do not spend any money on these products unless you feel you need them or that they will help you achieve your goals.