Quotes built from your deal, signed through a link

The call went well. The buyer says: "Send me a proposal." Then the work starts. The rep looks up prices in an old quote, copies them into a Word file, adjusts the discount, exports a PDF and emails it. Two days later the buyer calls about a line that no longer matches what was agreed. The rep fixes it and sends version two, while the CRM still shows the deal value from version one.

Then the signature. The buyer prints the PDF, signs, scans and sends it back. Or does not, because the printer is at the office and they work from home. Nobody knows if the quote was even opened. And when there is a dispute about the terms six months later, someone searches three mailboxes for the version that was actually signed.

So the problem is not making a document. The problem is that the quote lives apart from the deal. Prices sit in two places, versions sit in mailboxes and the signature sits on paper. Every step in between is manual, and manual is where things stall.

In Lumo the quote starts on the deal. The product lines with quantity, price, discount and billing frequency are already there, because you use them for the deal value in your pipeline. The quote takes a snapshot of those lines. You can keep updating the deal afterwards without changing the quote you sent. Sending goes from your own mailbox, the customer signs online, and the proof comes back to the same deal. One place shows what was offered, when it went out and who signed it.

That is not a big promise. It is one place instead of four. For the steps around it, from first proposal to signed deal, read the guide from quote to signed deal.

This is a made-up example to show the flow, not a customer case.

Say a software reseller with six account managers sells licences to mid-sized firms, with a support plan on top. Account manager Tom has a call in the morning with the operations lead of a logistics company. They agree on 40 user licences billed monthly, a one-time onboarding package and an annual support plan for two years.

After the call Tom adds the products to the deal. Forty licences, monthly, ongoing. Onboarding, one-time. Support, annually, two cycles. Lumo works out the deal value from the lines, and his manager sees the deal with the right value in the Proposal stage on the board.

Then he creates a new quote. The lines are already there. The default introduction and terms come from the settings, and validity is set to 30 days. He adds two sentences about the call to the introduction, previews the PDF and sees the customer's logo next to his own company's. He sends it from his Gmail with the operations lead as the signer.

At four o'clock the buyer opens the link. In the audit log Tom sees quote viewed, then code sent and code verified. Ten minutes later it says quote signed. The signed PDF with its evidence page is on the deal and in the buyer's inbox. Tom marks the deal as won and schedules an activity for the kickoff.

Had the buyer asked for a change, Tom would have voided the quote and created a new one with refreshed lines. The old signing link would have stopped working.

A quote is the end of a route that starts earlier. The product lines come from the deal in your pipeline, and the deal value on the board is the same sum as on the quote. The customer and their organization come from contact management, including the logo printed on the PDF. The email goes through your connected Gmail and then sits on the deal timeline.

If you want fixed steps after signing, such as a task for the project lead once a deal is won, you set that up with automations. They react to the deal stage, not to the signature itself. That is why the rep moves the deal after signing. The revenue you win shows up in reports on won deals.