Somebody called on Tuesday. You said you would send a number. It is now the following Wednesday and nobody is sure whether that happened. The lead did not go cold because the work was bad. It went cold because it lived in a head, a text thread and a sticky note at the same time. A pipeline fixes that by giving every lead one record, one owner and one visible next step, on a board where anything stuck shows up from across the room.
A pipeline is not a to-do list with better colours. Every column is a promise about what happens next, and most of those promises should be keeping themselves. Here is one job moving across a real board.
Most systems fail here rather than at the board. The stages look tidy and the cards are empty, so every conversation starts from nothing. These are the fields worth setting up, and there are fewer of them than people expect.
Filled in automatically or not at all. Ask a human to remember and within a fortnight everything is marked Other, and then nobody can tell you what is worth doing again.
The one field the most other things hang off. It decides which quote goes out, who picks up the work, and how fast anyone needs to move.
Not a team. A person. A card owned by everyone is a card owned by nobody, and it will sit there proving it.
Follow up soon is not a next step. Call Thursday morning is. This is the field that turns a board into something you can run a Monday off.
So anyone can open the card, read down, and pick the conversation up without saying remind me what we discussed.
The only reason a forecast is anything more than a feeling. It also tells you which stuck card to go and rescue first.
Parked has a wake-up date attached. Done leaves the working board. A board that keeps everything forever gets ignored within a month.
Tags and fields do different jobs and mixing them is the most common mess we walk into. A field is something every record has one of: job type, owner, value. A tag is something that either happened or did not: came from the spring campaign, asked about financing, left a review. Fields sort the board. Tags decide who gets which message. Keep them separate and the system stays readable two years from now, when there are eleven hundred records in it and none of them are yours.
Every gap below is a moment where information changes hands. Each one is a place a job quietly stops. Closing them is most of the work, and none of it is glamorous.
A missed call becomes a card with the number, the time and a text already sent. Nothing depends on someone writing it down while driving.
Forms, chat, calls and every ad platform land in the same place with their source attached. One inbox, not five tabs and a phone.
Won means the job appears on the build side carrying the notes, the quote and the promises already made. The client should never have to explain it a second time.
The moment you hand leads to somebody else, whatever lives in your head stops working. A record is what makes the handover possible without you hovering over it.
Two people on the same lead, or nobody on it, both come from the same missing thing. Ownership and visibility fix both at once.
Whatever is in the sheet, the notes app and the phone comes across, deduplicated and tagged with where it came from. Starting empty is how a new system dies in week three.
Most reporting screens are decorative. Charts nobody acts on. A useful one tells you what to do this morning, and it fits on a phone in the van.
Every card that has not moved in longer than it should, sorted by what it is worth. This is the list that pays for the whole system, and it is usually shorter and more embarrassing than anyone expects.
Live jobs and their value, split by stage. Not a guess about the month. The number that is already sitting on the board waiting to be closed or lost.
Which sources turn into paid work rather than which ones make the phone ring. Volume flatters. Won jobs by source is the only version worth budgeting against.
One more that rarely makes it onto a screen and should: how long a lead waits for a first reply. It quietly predicts everything else. Businesses that answer inside five minutes win work from businesses that answer inside five hours, and the board is where you find out which one you have been.
Everything on this page runs on software. Ours. SimpleCRM is part of Mindset Affiliates, which is why we can be specific about what it does instead of vague about it, and why there is a version of this where you skip the build entirely and set it up yourself.
If you read the pipeline above and thought you could set that up yourself, you probably can. SimpleCRM is where we do it. Pipelines, records, tags and the dashboard, in one place. You can open an account and run it on your own without hiring anybody, and plenty of people should.
The other door is that we set it up around how you already work, hand you the login, and keep building inside it as you need more. Workflows, routing, extra pipelines. Both doors land on the same board. The only difference is who does the setting up, and how much of it you want to own.
Same software. The difference is who does the setting up.
Everything listed here is something shown on this page, not a feature sheet.
Not a licence and a login. A system with your work already in it, set up around the way the jobs really run.
Named the way your team already talks, with the number of columns the work needs and not one more. Two extra stages nobody updates will take a board down faster than no board at all.
A short list of fields that get filled every time, filled automatically wherever that is possible, and a tag structure that still reads clearly after a thousand records.
Calls, texts, emails and form replies in a single thread, so nobody has to open three apps to work out what was already said and by whom.
The automations tied to each column, so moving a card is the trigger rather than the paperwork. This is the part that makes people keep using it.
Stuck work, live value and where the paid jobs came from. Short enough to read in the van, honest enough to change what you do that week.
Cleaned, deduplicated, tagged with where they came from, and imported before launch day. A system that opens empty gets abandoned inside a month.
The setup is quick. Agreeing what a stage means, and who owns a card once it lands there, is the part that takes the conversation.
What a lead goes through from first contact to finished job, in your words. Usually five or six columns. If it takes eleven, something is being tracked that does not need a stage.
Column by column, what should happen the moment a card lands. This is where a board stops being decoration and starts saving somebody a morning.
Contacts out of the sheet, the phone and the old system, cleaned and merged. Then a handful of live leads run through so the gaps show up before anyone depends on it.
Real work on the board, fields adjusted where they were wrong, one stage usually renamed. A system nobody has used yet is still a guess.
That is the usual starting point, and it is rarely a software problem. It is either asking for fields nobody has time to fill, having stages that do not match how the work runs, or giving people no reason to move a card because moving it does nothing. Fix those three and the same tool gets used. Sometimes the answer is a different system, but that is a decision worth arriving at rather than starting with.
Automations is what fires. Advanced Workflows is what decides. This is where all of it is written down, and the place anyone can go and look. Automations without a record leaves you with messages going out and no way to tell what happened after. A record without automation leaves you with a very tidy filing cabinet. They are built together for a reason.
They will if it is faster than what they do now, and they will not if it is extra typing. So the setup pushes as much as possible onto the system: source filled in on arrival, notes typed once, the next step suggested rather than demanded. The rule of thumb is that any field a human has to remember to fill will eventually be empty.
They come with you. The spreadsheet, the phone, the old system, whatever has been collecting names for years. Deduplicated, tagged with where they came from, and in place before the board goes live, because a fresh empty CRM is the single most common reason one gets abandoned.
Yes, and you should. Stage names, fields, tags, who owns what: those are yours to move as the business changes. The parts wired into automations are worth a conversation first, because renaming a stage can quietly stop something firing three steps away. Ask rather than guess, and nothing breaks.
Book a call and bring one job that stalled somewhere in the middle. We will walk it back through the stages and show you exactly where it stopped, and what would have caught it.
Set up so nothing needs remembering