Skip to content
Coaching and training2026

Sales pipeline and commissions for a coaching provider

Off a no-code tool and onto a domain application that records commercial facts — appointments, sales, payments — then derives the pipeline, commissions and reporting from them.

Interface redrawn from the real mechanic, with neutral data. It is not a screenshot of the client’s system.

Where it started

The entire sales operation lived in a no-code tool where one status field triggered a cascade of automations. The status had become the data: there was no way to know what had actually happened, nor to recompute a commission without replaying history by hand. Signed and collected were mixed into the same table.

What we built

We inverted the causality. The application records facts — an appointment has an outcome, a sale is signed, a payment arrives — and the pipeline stage is now only a projection of that history. Commissions are emitted by explicit rules at the moment of the fact, and become immutable. Signed and collected are finally two distinct notions.

What changed

A commission is justified by tracing back to the sale that produced it. Reporting recomputes from facts rather than from a current state, and fixing a historical error no longer breaks the running month.

The work is described without naming clients: the trade, the order of magnitude and what was built — never the identity.

Let’s talk about your project

Describe what you are trying to build. We answer with an honest first read on feasibility and scope — even when the answer is that you do not need us.

Talk about your project