How a Lead Becomes Cash

What this covers

This is the single most useful flow to understand, because it touches more of Plenix than any other. We follow one enquiry from a stranger's first email to a paid invoice.

Before you start: you should have at least one company record. If not, read Start Here first.

The flow

Enquiry  →  Lead  →  Deal  →  Proposal  →  Won  →  Project / Stock  →  Invoice  →  Paid

1. The enquiry arrives

Somebody wants to buy something. That arrives as an email, a phone call, or a form on your website.

If it came through a web form, Plenix creates the lead for you — nothing to type. If it came by phone, you add it yourself in CRM → Leads.

2. The lead becomes a deal

A lead is a maybe. A deal is a real opportunity with a value and an expected close date.

When a lead looks genuine, convert it. The contact details carry across — you do not re-type them.

3. You send a proposal

Build the proposal in Plenix and send it. The customer can accept and sign it online, so there is no printing, scanning, or chasing a signature by email.

4. They say yes

This is where Plenix starts doing work for you. When you mark a deal as won:

• If the work needs delivering over time, a project is created from the deal automatically.
• If the work needs physical items, stock is reserved against the order.
• The recurring part of the sale, if there is one, starts counting toward your monthly recurring revenue.

That chain is called Quote to Cash, and it is largely automatic.

5. The work gets done

Depending on what you sold, this is a project, a set of tickets, or field visits. Time and materials get logged as people work.

6. You invoice

The invoice is built from what actually happened — the hours logged, the parts used, the agreed fee. You are not reconstructing it from memory or a spreadsheet.

Time is only billed once. If an hour is already covered by a contract or has been invoiced before, Plenix will not put it on a second invoice.

7. You get paid

Send the invoice with a payment link. The customer pays by card or direct debit and the invoice marks itself as paid.

If they do not pay, payment reminders chase them automatically on a schedule you set. Nobody has to remember.

What you actually have to do

Out of all of that, a person does five things: log the enquiry, convert it, send the proposal, mark it won, and send the invoice. The rest happens on its own.

For your IT team

• Website forms post to a public endpoint, so no login is needed to submit one.
• Payments run through Stripe, GoCardless, PayPal or BACS; you connect your own account.
• Every step is written to the audit trail with who did it and when.

Where to go next

• The delivery side → How a Request Becomes a Resolved, Billed Ticket
• Buying things in to fulfil an order → How Procure-to-Pay Works
• Keeping up with a deal without checking it → Following Records and Getting a Digest