What a spreadsheet quote quietly skips

Most quotes start the same way, whatever's put together the fastest. A spreadsheet formula, a template someone built two years ago, a line in an email. It works, right up until it doesn't: a discount goes out that nobody approved, a customer asks for one change and now there are three versions of the same quote floating around in different inboxes, or the tax line is wrong because whoever built the formula didn't account for the customer's state.

None of that is really about the math being hard. It's about a quote being treated as a document instead of a process.

A quote is a lifecycle, not a number

The moment a quote exists, it's going to move through states, whether or not anything tracks that explicitly. Someone drafts it. Someone (maybe the same person, maybe not) needs to sign off on it, especially if there's a discount attached. It goes out. The customer accepts it, declines it, lets it expire, or asks for something different, which means a new version.

A spreadsheet has no concept of any of that. It has cells. If a discount goes out without approval, there's no record that it should have needed one. If a customer asks for a change, the "new version" is usually just the old file with different numbers, and whoever opens it later has no way to tell which one actually went out.

Clayto's quotes carry a real approval workflow: draft, pending approval, approved, sent, then accepted, declined, expired, recalled, or superseded. Nine states, not two. A discount is a percentage with the actual dollar amount computed and visible, not a manually typed number that might not match the line items anymore. Tax is calculated per quote, and totals are currency-aware if a customer isn't paying in your default currency.

Versions that don't erase each other

The part that matters most in practice is what happens when a customer comes back and asks for a change, which happens on almost every quote that isn't accepted immediately. Clayto tracks version lineage: a revision is linked back to the quote it came from, not a fresh file that quietly replaces it. If someone needs to know what was actually offered three revisions ago, that's answerable, not a search through old emails hoping the right attachment is still there.

Why this is worth building instead of skipping

None of this is complicated in the way an automation engine or an AI feature is complicated. It's complicated in the way that real processes are complicated: there are more states than you'd guess, and a shortcut that works for the first ten quotes usually breaks around the thirtieth, right when a discount gets missed or a customer asks "which version is this" and nobody has a good answer.

This is the kind of depth that doesn't show up until you need it, and by the time you need it, rebuilding it in a spreadsheet is its own project. It's also exactly the gap between a tool that's light because it left things out and a system that's complete enough to hold up once quoting stops being occasional and starts being a real part of how the business runs.