How we built Runation's own lead route

This is a case study about Runation's own production system. It is not an anonymised client story and it does not claim a conversion lift or a number of hours saved.

What we can show is simpler: the complete route was tested from a first-party booking to one business record, one owner alert, and a Runation-branded invitation.

The problem

A lead route can look tidy on a diagram while still leaking in production. A booking may create a calendar event but no commercial record. A form may send an email but leave no visible owner. A shared account may also carry the wrong brand into the prospect's inbox.

Runation needed one route that answered five questions:

1. What did the prospect submit?
2. Where is the current record?
3. Who has been notified?
4. What happens when the booking changes?
5. Which decisions still require a person?

The system

The route is deliberately bounded:

1. A prospect chooses a time through Runation's first-party booking interface.
2. The booking carries the agreed qualification answers and creates a meeting invitation.
3. A signed event updates one customer and opportunity record.
4. The owner receives a non-sensitive alert with a route to the full record.
5. Reschedules and cancellations update the same opportunity rather than creating duplicates.
6. Failures are logged instead of returning a false success.
7. Qualification, the proposed solution, pricing, and follow-up remain human decisions.

The client's experience does not depend on knowing which internal products move the data. The useful promise is that the route has one visible state and one owner.

What we verified

On 14 July 2026, a labelled production test completed the full route:

• the external inbox received a Runation-branded invitation;
• the booking produced the expected customer and opportunity record;
• the owner alert arrived with the correct event context;
• cancellation updated the same opportunity and produced the expected alert;
• a retired shared event was excluded before it could trigger the wrong business's follow-up.

The internal event and record identifiers are retained in the launch evidence log. They are not useful to a prospective client and are not published here.

This proves that the tested route completed. It does not prove a conversion rate, revenue result, or time saving. Those require a longer measurement period and a documented baseline.

What stays human

The system does not decide whether a lead is commercially suitable. It does not write a proposal, promise a result, or send an invoice without review.

A person still owns:

• qualification;
• the recommended package or custom scope;
• unusual privacy or access requirements;
• proposal and payment terms;
• sensitive follow-up;
• the decision to close or nurture the opportunity.

What we will measure next

The useful operating measures are:

• completed bookings;
• duplicate-record rate;
• time to owner acknowledgement;
• reschedule and cancellation handling;
• failed events and retries;
• leads with no recorded next action.

If those measures become a public result, the period, sample, source system, and limitations will be stated beside the number.

The operator lesson

The route is not valuable because it connects several systems. It is valuable because a prospect can book, the team can see what happened, and a failure cannot quietly masquerade as success.

Book a free systems review if your lead route still relies on somebody copying information between tabs.