Use “Record a quote you sent” in Recued. A quote you sent yourself — what, to whom, how much, and how long it stands. It starts undecided and counts towards no rate until you hear back.
Record a quote you sent
Use “Record a quote you sent” in Recued. A quote you sent yourself — what, to whom, how much, and how long it stands. It starts undecided and counts towards no rate until you hear back.
Complete workflow
Quote Pipeline
4 pinned recipes
Use Quote Pipeline in Recued for quotes, win rate, sales, and small business. It includes 5 built-in actions and 3 ready-to-run workflows. Actions that change data use Recued's approval controls.
You are viewing one recipe in this workflow. Installing it opens the complete pack so its other recipes and background automations arrive together.
Use “Record what happened” in Recued. Won, lost or withdrawn. It uses the connections and settings you choose when you run it.
Use “Where the quotes stand” in Recued. What is still out, what expires soon, what expired unanswered, and the win rate computed only over quotes you actually got an answer on.
Use “Records runtime” in Recued. It helps you complete this workflow using the connections and settings you choose.
Recording one
A quote you sent by email, PDF, or over a counter. Nothing here needs the customer to come through a form or pay through Recued — that is what seller-quote-request is for.
⛔⛔ A NEW QUOTE IS UNDECIDED, AND UNDECIDED IS ITS OWN STATE — not a loss in waiting. It counts towards neither the win rate nor the loss rate until you record what happened. A pipeline that treats silence as a loss reports a worse business than you have; one that treats it as a win reports a better one. Both make you price the next job wrong.
⚠ valid_until is derived from the day you sent it plus the days you said it stands — dates here never round-trip through date_format, which renders in the server's local timezone and would move a calendar date by a day west of Greenwich.
⚠ Expiry is DERIVED at read time, never stored. A quote does not become a different record when the clock passes it; storing expired would need something to run and would be wrong the moment it did not.
How it works
Inspect the data fetches, transforms, gates, and output this recipe runs.
Process (27 steps)
label
trim
Trim whitespace from setting label
customer
trim
Trim whitespace from setting customer
contact_raw
trim
Trim whitespace from setting customer contact
customer_contact
lowercase
Convert contact raw to lowercase
reference
trim
Trim whitespace from setting reference
job_ref
trim
Trim whitespace from setting job ref
note
trim
Trim whitespace from setting note
currency_raw
trim
Trim whitespace from setting currency
currency
uppercase
Convert currency raw to uppercase
now_iso
date_add
Add 0 seconds to
today_parts
split
Split now iso into parts
today
default
Apply default
sent_in
trim
Trim whitespace from setting sent on
sent_on
default
Apply default
sent_len
string_length
Apply string_length
sent_seg
split
Split sent on into parts
sent_segs
count
Count items in sent seg
sent_year
string_length
Apply string_length
valid_iso
date_add
Add setting valid days days to
valid_until_parts
split
Split valid iso into parts
valid_until
default
Apply default
amount_positive
compare
Check if setting amount is greater than 0
valid_positive
compare
Check if setting valid days is greater than 0
inputs_valid
all
Check if all conditions are true
inputs_guard
guard
Stop if inputs valid equals
create
?
card
to_summary
Format results as a summary card
Settings
Configurable at install. Defaults shown — change them anytime in Recued.
note
setting
=
label
setting
=
[object Object]
amount
setting
=
0
job ref
setting
=
sent on
setting
=
currency
setting
=
GBP
customer
setting
=
[object Object]
reference
setting
=
valid days
setting
=
30
customer contact
setting
=