The joins

One lead list, one calendar, one record.

Every service on this site produces the same three things: somebody who wants something, a time in a diary, and a record of what happened. When each one lives somewhere different, you are the join — and the join is where things get lost.

Book a call See all seven services

This is the least exciting page on the site and usually the one that pays for itself first. “Book a call” opens an email — send us a time that suits and we will confirm it.

ALG / SYSTEM MAP WHAT WE DRAW ON THE CALL

SYSTEMS · ONE OPERATION Where a lead lands, whichever door Every way somebody can reach you, where each one currently ends up, and the one place it should end up instead.

ROUTES01 / 03

STATUSREADY TO JOIN

PHONEWEBFORM

01Drawn from your actual doors, including the ones nobody remembered.ONE PLACE, DECIDED ONCE

01One place a lead landsWhichever way they came in, they arrive in the same list, in the same shape.

02One calendar behind itOne diary that is the real one, so two things cannot be booked into the same hour.

03One record of what happenedOne history per customer, so nobody has to ask around to find out what was said.

Where the joins break

It is never the tools. It is the gaps between them.

Each of your tools is probably fine on its own. Every one of the faults below happens in the space between two of them, which is why nobody owns it.

Two calendars, one of them wrong

One on the phone, one somebody keeps for the crew, and a whiteboard nobody has photographed. Sooner or later two jobs are booked into the same hour and the argument is about which diary is the real one.

Two versions of the same customer

One spelling in the invoicing, another in the phone, a third in the email thread. Nobody can answer "have we worked for them before" without three searches, so nobody asks.

Nobody knows who followed up

Two people ring the same customer on Tuesday; nobody rings the next one at all. Not carelessness — there is simply no shared place that says what has already been done.

The delivery path

Draw → Pick → Join → Watch.

One verb a step, four steps, and the first is just drawing it. You cannot fix a system you have never seen on one page, and most of the value here shows up during step one, before anything is built at all.

Draw what you actually have

Every door somebody can come in through, every tool that holds a piece of the answer, and where each one currently sends things. On one page. Almost everybody finds a door they had forgotten about.

Pick where each thing lives

One place for leads, one calendar that is the real one, one record per customer. Not the most features — the one you will actually keep up to date. Everything else becomes a copy, and copies are allowed to be wrong.

Join them one at a time

One join, proved, before the next. The order is decided by what is costing you most, not by what is easiest to demonstrate, and each one runs alongside the old way until it agrees.

Watch it, because tools change

A join breaks the week a supplier changes something, and it breaks quietly. So it is monitored and fixed, and changed when the business changes. Monthly, no contract.

Where to start

Three joins worth making first.

In this order, for most small businesses. Written as work we would deliver for you — what we already run is on the left of the next section, and kept separate on purpose.

Every door into one list

The phone, the website, the form, the message. Whatever door somebody comes through, it lands in one list with the same fields filled in and a stage you can move on the row itself.

ONE LISTSAME FIELDSSTAGE ON THE ROW

Every booking into one calendar

One diary is the truth and everything else reads from it, so availability offered anywhere is availability that genuinely exists. Nothing gets double-booked because two systems disagreed.

ONE TRUTHREAD BEFORE OFFEREDNO DOUBLE BOOKING

Every conversation into one record

One history per customer — what was asked, what was quoted, what was done and by whom. So the answer to “what happened with these people” takes ten seconds and does not depend on who is in today.

ONE HISTORYSEARCHABLENOT IN SOMEBODY’S HEAD

What already joins up

Some of this already runs — and two things do not.

The left-hand card is the only present tense on this page, and it describes our own platform rather than a customer’s. The list beside it ends with the two joins that genuinely do not exist.

On our own platform, these joins already run every day.

A call finishes and a lead is written. A booking is made and it appears in a real calendar. A confirmation goes out, a reminder follows, and every conversation — spoken or typed — ends up in the same list with what came of it.That is ours, and it is the shape we would build for you. Everything above this section is written as work we would deliver, because that is what it is.

RUNNING DAILYOURS, NOT A CUSTOMER’STHE SAME SHAPE

A lead arrives in one list however the person reached you.
A stage on every lead, changed on the row itself — no second system.
Availability is read from a real calendar before a time is offered.
Every conversation is written up and searchable afterwards.
Someone can be given access without sharing a password.
More than one line reports separately, so you can tell them apart.
Exportable to CSV whenever you want it. If you leave, you take it.
No native CRM connector — a webhook to a URL you own, and the export above.
WhatsApp is not a joined door — waiting on WhatsApp’s own verification.

The final two lines are joins that genuinely do not exist. They stay on this page until they do, and then they move up into the list above.

How we define progress

What gets counted, and what you end up holding.

Everything above turns into one list, one diary and one history you can check yourself. No figures anywhere on this page, on purpose — a joined-up operation is the easiest thing on this site to describe and the hardest to prove.

What gets counted

Every lead, in one list. However the person reached you, on a row with the same fields filled in.
Where each lead has got to. The stage, moved on the row itself, with no second system to keep in step.
What is actually booked. One calendar that is the truth, read before a time is offered — so nothing is double-booked because two systems disagreed.
What was said, per customer. One history, searchable, so “what happened with these people” is a lookup rather than an ask-around.
Where a join disagreed with the old way. Each one runs alongside what you did before until the two agree — the disagreements are the list that gets it right.

What you end up holding

The map. Every door somebody can come in through and where each one currently ends up, on one page — including the door nobody remembered.
The decision. One place for leads, one calendar that is the real one, one record per customer. Everything else is a copy, and copies are allowed to be wrong.
The joins themselves. Made one at a time and proved before the next, in the order of what is costing you most.
Your data, and the way out. A CSV export whenever you want it and a webhook to a URL you own. If you leave, you take it.

Not one of those is a figure. Nothing here counts hours saved or leads recovered, because the only joined-up operation we can point at is our own — which the section above says outright, and which is the one place on this page allowed the present tense.

The other six

The joins are one of seven.

This page is the one that makes the other six fit together. If the joins are not what is costing you the most, one of the other six is — and each of them has a page like this one.

Systems is 07, and you are standing on it. Start with whichever of the other six is costing you the most.

See all seven services

Bring us the two lists that never agree.

Book a call