How the commercial flow works

A great supplier with a sloppy commercial process loses money every month. Late proposals, unsigned contracts, forgotten invoices, payment links sent to the wrong inbox — every friction point bleeds revenue quietly.

The B2B Growth Hub commercial layer removes that friction. Proposals, contracts, invoicing and payment flows are all native to the platform and connected to your lead pipeline. You never have to leave the ecosystem to close a deal.

Every deal moves through a five-stage commercial pipeline:

1. Proposal sent · digital proposal, tokenised public link, viewable and acceptable in-browser.
2. Proposal accepted · the buyer ticks accept, the system locks the version, audit trail begins.
3. Contract generated and sent · contract pulls forward from the accepted proposal automatically.
4. Contract signed · supplier signs first, then the counter-party signs · contract becomes fully executed.
5. Invoice and payment · invoice generated · payment link issued · webhook confirms payment received.

Each stage carries forward the information from the previous one. You enter the deal data once. The system reuses it for every subsequent step.

Proposals inside the ecosystem are not PDFs sent over email. They are:

• Live web documents · the buyer opens a tokenised URL · views your proposal in their browser · accepts or declines with one click.
• Tracked · you see exactly when they viewed it, how long they spent, and whether they returned to read it again.
• Versioned · if you need to revise before they accept, you do so without losing the audit trail.
• Printable · they can also print or save the proposal as a PDF if their procurement team needs a copy on file.

When you build a proposal, the system pulls forward from the underlying lead: company details, registered office, VAT number, contact name. You spend your time on the offer — not on data entry.

Contracts use the same digital signing pattern as proposals. The difference is that contracts carry legal weight, so the audit trail is more rigorous:

• Supplier signs first · this is intentional. You commit before asking the buyer to commit.
• Counter-party signs second · buyer receives a secure link · signs in-browser · signature is timestamped and IP-recorded.
• Audit certificate · at the back of every signed contract sits an audit page showing exactly who signed when from which device.
• Read-only after signing · once countersigned, the contract body is locked and cannot be edited.
• PDF export · either side can download the signed contract as a real PDF (built client-side, no print dialog).

Once a contract is signed, you raise a payment link directly from the lead detail page. Here is what happens behind the scenes:

1. You click 🪙 Create payment link on the contract row.
2. The modal pre-fills with the contract amount, the buyer's company name, VAT, and description.
3. Confirm and submit · the system creates a customer record in our payment partner, generates a hosted payment URL, and returns it to the lead detail page.
4. You share the link via WhatsApp · Email · SMS, or send it server-side from the platform.
5. When the buyer pays, the payment webhook fires · status updates instantly in the Payment Request History panel.
6. An invoice is generated automatically for every payment request · viewable and printable from the panel.

You can also manually update the status if a payment was made offline (bank transfer, cheque) · admin users have an override picker for that case.

Watch out for these five common pitfalls:

• Sending a proposal without an underlying lead · you lose the audit thread. Always start from the lead detail page.
• Forgetting to mark the proposal as ACCEPTED · the buyer might tick it · if you generate the contract before, the link never gets locked. Always confirm acceptance first.
• Editing a sent contract · the system locks it once sent. If you need to change terms, reset it (admin only) and resend.
• Sending the payment link to the wrong email· the pre-fill uses the buyer's contact email from the lead. Double-check before clicking Send Email.
• Not reconciling offline payments · if a buyer paid by bank transfer, manually update the status. The Payment Request History is your single source of truth.

Memorise this sequence and you will never lose a deal to friction:

1. Lead → Discovery captured
2. Build proposal from lead detail → send public link
3. Mark ACCEPTED when buyer ticks accept
4. Generate contract → supplier signs → buyer signs
5. Create payment link → share → wait for webhook
6. Status flips to PAID → invoice is auto-generated

Six steps. One platform. No external email. No spreadsheet reconciliation. The commercial flow is the layer that pays for everything else you do inside the ecosystem.

Head back to the journey and tick I've read this. The final module covers how My Calendar drives all of this momentum.