Blog › Follow-ups

Approval Workflow for Custom Pergola Quotes

A customer says, “We like it, but can you change the roof color and send the revised price?” Two days later, another message arrives: “Can we make it 20 cm wider?” The original PDF is still in the email thread, a revised file sits on someone’s desktop, and nobody is fully sure...

Dariusz Mazur ·

Approval Workflow for Custom Pergola Quotes

A customer says, “We like it, but can you change the roof color and send the revised price?” Two days later, another message arrives: “Can we make it 20 cm wider?” The original PDF is still in the email thread, a revised file sits on someone’s desktop, and nobody is fully sure which version the customer is considering.

That is where an approval workflow earns its keep. It does not need to be a large CRM project or a customer portal. For a company selling custom pergolas, terrace roofs, or patio enclosures, it is a simple method for answering four practical questions: What is the current offer? What did the customer decide or request? Who needs to act next? When?

What an approval workflow should control

An approval workflow is the path a quote takes from “sent” to a clear commercial outcome. That outcome may be an approval, a rejection, a request for changes, or a decision that needs further discussion. The point is not to force every customer into a formal online process. Many customers will continue to call, text, email, or send a WhatsApp message. That is normal.

The workflow should capture the result of those conversations without relying on memory. A customer who says, “Call me after I speak with my wife,” has not approved the quote. A customer who says, “Please use the anthracite roof from the revised offer,” may be close to approval, but the scope still needs confirmation. These distinctions prevent expensive assumptions later.

A useful workflow also separates customer approval from internal approval. The customer may agree to the design and price, while your team still needs to verify measurements, production lead time, or installation conditions before work is handed over. Treating both as one vague “won” status creates confusion.

A practical approval workflow in five stages

The best workflow is usually the smallest one your team will use consistently. Start with five stages that match what happens after a quote is prepared.

1. Quote sent

Record the date the quote was sent, the version identifier, and the planned follow-up date. The version identifier can be simple: “Pergola Kowalski v1 - May 6.” It does not need to be a complicated numbering system, but it must let anyone identify the document being discussed.

Set a specific next action, not a vague reminder such as “follow up.” Write what you will do and when: “Call Mr. Kowalski May 10 to ask whether the roof color and side screen options are clear.”

This matters because a sent quote is not a completed task. It is an open commercial case.

2. Customer reviewing

Once the customer has the quote, the most common mistake is leaving the case in a general “waiting” pile. Waiting is not an action. The customer may need time, but your team still needs a planned date to check in.

The follow-up should reflect the situation. If the customer asked for a weekend to discuss the project, calling the next morning is unhelpful. If they said they would decide by Tuesday, do not leave the case untouched until the end of the month.

A simple note gives the next person enough context: “May 8: Customer comparing two roof colors. Wants to decide after speaking with installer. Follow up May 13.”

3. Change requested

A requested change deserves its own stage because it changes the commercial reality of the case. Do not leave the original quote marked as awaiting approval while someone is preparing a new scope.

Record the request in plain language: “Customer wants white frame instead of anthracite and one additional sliding glass panel.” Then assign the next action: “Prepare revised quote by May 14.” If a measurement or supplier check is needed first, say so.

When the revised quote is ready, create a clear new version. Keep the earlier version in the case history, but make it obvious that it is no longer the current offer. The goal is not document bureaucracy. It is avoiding the familiar question: “Did they approve the $12,400 version or the $13,150 version?”

4. Decision recorded

A decision should be recorded as what actually happened, not what you hope happened. If the customer approves by phone, write the date, who spoke, and what was agreed. For example: “May 16, phone call with Anna Kowalski: approved v2, including white frame and one sliding panel. Asked for an installation timing call next week.”

If the customer rejects the quote, record the reason if they volunteered one. “Chose a lower-priced option” is useful. “Lost” is not very useful when you review cases later.

If the customer has not decided, record that too. “Needs landlord approval, asked for a call June 3” is a live case with a clear next action, not a dead lead.

An approval workflow should not turn a phone conversation into a legal signature. If your contract process requires a signed agreement, deposit, or separate written confirmation, keep that requirement clear. Commercial approval and legal acceptance are not always the same thing.

5. Handoff or follow-up

After a clear approval, the commercial work is not finished until the next owner knows what to do. A good handoff includes the approved quote version, the agreed configuration, customer comments that affect delivery or installation, and any unresolved item.

For example: “Approved v2. Installation access needs confirmation because the side gate is narrow. Sales coordinator to call customer May 20. Do not order side screens until access is confirmed.”

If the outcome is not approval, the handoff may simply be another follow-up. The key is that every open case leaves the day with one credible next practical action.

Use one case record, not scattered clues

A small team can run this process with a notebook, a spreadsheet, or shared notes if the volume is manageable and everyone can see the current status. Software adds work when it asks people to duplicate everything they already do without making the next action clearer.

Once several personalized quotes are open at the same time, scattered information becomes costly. The PDF may be in email, the color change in WhatsApp, the promised callback in someone’s head, and the latest decision in a phone conversation. No individual item is hard to find. The problem is reconstructing the truth when a customer calls unexpectedly.

Use one commercial case per customer project. The case should contain the current quote version, a short history of meaningful changes, the latest customer response, the owner, and the next action with a due date. Avoid copying every message word for word. Capture the information that changes what your team should do next.

AwiFin is designed around this kind of post-quote discipline: keeping a commercial case, recording updates, and showing the next practical action in a Today view. It should support your existing estimating system and preferred customer communication, not require you to replace them.

A sample record your team can copy

Case: Kowalski terrace pergola 4 m x 3.5 m Current quote: v2, sent May 14 Customer request: White frame, one sliding glass panel Latest update: May 16 - customer said v2 is acceptable but wants to confirm installation timing Current status: Decision pending Owner: Marta Next action: Call May 20 at 10:00 to confirm timing and ask whether customer approves v2 If approved: Send agreed installation requirements to the installation coordinator

This format is deliberately plain. A coordinator covering for a colleague should understand it in under a minute.

Where approval workflows commonly fail

The first failure is using broad statuses that hide the real condition of the case. “Proposal sent” may mean the customer has gone silent, requested a revision, verbally approved, or is waiting for a follow-up. Those are different situations and need different actions.

The second is treating a revised quote as an attachment rather than a new commercial version. If the changes affect price, dimensions, color, components, or installation scope, identify the revised offer clearly. Otherwise, approval can attach itself to the wrong document.

The third is allowing a case to end with no owner and no date. “Customer will think about it” should trigger a question: when will we contact them again, and who will do it? The deal may not have died. You may simply have never followed up.

Start with the cases already on your desk. Pick five open quotes, identify the current version for each one, record the last real customer response, and give every case one next action with a date. That small habit is often more valuable than a bigger system nobody has time to maintain.