Our Draft Quote Made the Softener Sound Like a Liability. We Had Already Solved It.

This is a note about one sentence I took out of our own quotation, and what taking it out taught me about how we write the rest of them.

The job was a commercial building here in Cebu with a kitchen heavy enough that we were pricing a softener alongside the wastewater plant. The deal is live, so I am not naming it. The engineering was settled and I still think it was right. What was wrong was the document.

Our draft had a paragraph explaining what hard water does to a kitchen and to the grease line downstream of it, and what happens if the softener is not maintained, and what the consequences are for the plant if it falls over. Every clause in it was true. Read end to end, it made buying the softener sound like taking on a liability rather than removing one. I said so at the time, roughly in these words: we are making buying the softener worse than it actually seems. If we do not do this job, somebody else will get it any which way.

A risk and a warning are not the same thing

I want to be careful here, because the easy misreading of this post is that we decided to tell clients less. We did not. Our quotes and presentations carry the risks and the assumptions they have always carried, and a client has the right to see all of them before he signs. That has not moved and it is not going to.

What I found in that draft was something else. It was not a risk. It was a warning about a problem we had already solved, three pages before, inside the price he was being asked to approve. The softener was in base scope. The sizing was done. The consumable was a locally available salt. There was no decision left for him to make about it and no outcome left hanging on his answer. We were describing the disease at length to a man already holding the cure in his hand, and charging him for both.

So the distinction we now use is plain. If a thing is unresolved and the client has to choose, it goes in front of him, with the numbers behind it. If a thing is unresolved and only we can act on it, it goes into our design and into our internal costing, and he sees the result. And if the thing is already solved inside the scope he is buying, it is not a risk at all, and writing it up as one is just bad drafting.

The test I now apply to our own paragraphs

The test is short: would this sentence hand him a soundbite to repeat against us? Not against the problem, against us. Because that is what happens. A client reads a well-written warning about hard water and what he retains is not I should get this treated. What he retains is the softener is a headache, and six weeks later, in a meeting we are not in, that is the sentence that gets said out loud. We wrote it. We handed it over. We even typed it under our own letterhead, which gave it authority.

The same drafting failure shows up in other parts of our work and I have learned to look for it. A long passage on how fast dosing pumps wear out, in a quote where we have already chosen the pump to reduce that. A page on sludge bulking in a quote whose clarifier is drawn to our standard detail. A note on what happens if aeration is interrupted, where we have already specified a machine quiet enough that nobody switches it off. In each case the engineering is sound and the writing undoes it.

What stays in, and why we do not thin it out

Plenty stays. The assumptions stay, because they are load-bearing: the flow we designed to, the wastewater strengths we drew the plant at, the occupancy ramp we assumed, the receiving water and its class. Those are not warnings. They are the statement of what the plant was built to do, and if one of them turns out to be wrong the plant's duty changes, so he needs to be able to check them against his own building.

The estimates stay, and stay marked as estimates. Sludge hauling and third-party laboratory are always shown as estimate prices and never as firm ones. Alkalinity correction and powdered activated carbon are shown as an estimate and marked if required, because we may never dose them. Pretending those are fixed numbers would be the opposite error.

And the genuine open decisions stay, because they are his. Whether he builds the concrete himself or we do or his contractor does under our supervision at a stated fee. What he actually wants the treated water for, which is the one input that decides how far up the ladder we treat. Whether his building will be at full occupancy when the commissioning sample is taken. Those are business decisions with technical consequences and we do not make them for him. We also do not choose his technology for him; we put the options side by side on equal footing and let him pick.

If you want to see the regulatory side of that stated plainly rather than argued at you, our compliance page lays out what the limits actually are, and the price estimator will give you a band before anybody talks to you.

Where the solved problem goes instead

It goes into the scope, and then it gets presented as a feature, which is what it is. That is not spin. A thing we fixed at the drawing stage is a better outcome than a thing we warned about, and the client paid for the fix either way.

Concretely, on that job: the softener sits in base scope rather than as an option he could decline, because a kitchen on hard water will turn its own grease into calcium soap and a trap full of crust is a harder problem than a tank of water. The interceptor is a poured concrete chamber on its own separate quote, so neither number hides inside the other. The salt is a commodity available from any supplier in Cebu, because we do not let compliance depend on a chemical that might not be on the shelf. None of that is described as a danger averted. It is described as what the building is getting.

There is a related discipline in how the operating cost is written. The number that matters to an owner is the cost per cubic metre, and we show it, because it is the ownership argument and it belongs in the technical narrative. What we do not do is build a ten-year cost of ownership table. It makes a sound decision harder to take and it tells him nothing the per-cubic-metre figure has not already told him.

How we ask for the facts behind a risk

Some risks need information we do not have yet, and this is where the drafting problem gets subtle, because the request itself can carry the warning. If we write please send your water hardness, as high hardness will cause the following problems, we have delivered the warning anyway, with a question mark on the end. So we ask for hardness as a survey data item, in the same list as the pipe diameter and the number of floors and the kitchen's operating hours. It is a number we need. It is not an accusation about his water.

We also do not volunteer the fallback remedy before we know whether we need it. If the hardness comes back at a level the base design handles, there was never anything to discuss. If it comes back high enough to change the design, then it is a real decision, with a real cost, and it goes in front of him properly — with the arithmetic, not with adjectives. The same approach governs how we ask for an influent result, which almost nobody has, and why we ask for the industry's characteristic parameters off our own list rather than asking the client to self-diagnose.

Where the nutrients are concerned the same rule holds. Ammonia and phosphate are the two that actually fail a test, so we design for them properly and say what the design achieves. We do not frame ammonia removal, nitrate removal or phosphate removal as threats; the field guide is written as what each one is and how it behaves, and the reader can decide what applies to him.

The part that still makes me uncomfortable

I do not want to leave this sounding tidier than it is. There is a real edge here and I have not found a rule that removes it.

A problem we have solved in the design is still a problem in the world. If the client stops maintaining the softener, the hardness comes back, and the crust with it. So at some point he has to be told that the thing has to be looked after — and the honest place for that is the operation and maintenance scope and the handover, not a paragraph in the middle of a sales document. That is a different document with a different job, and it exists. Moving the sentence there is not hiding it.

Where I would still get this wrong is a case where the remedy depends on the client doing something we cannot do for him and he has not yet agreed to. Then it is not solved, whatever our drawing says, and it belongs in front of him. I check that before I delete anything.

Anyone reading a quote from us, or from anybody else, is entitled to be suspicious of the opposite error too. A quote that reads smoothly because the problems were left out is worse than a quote that reads badly because they were all included twice. The four questions I would ask before signing are the ones that force a supplier to say what is actually in scope, and running our design past an AI is a reasonable thing to do before you commit money to it. We also design and build the same plant, which creates a conflict we have written about openly rather than waited to be asked about.

Where this does not transfer

This is a drafting position, not an engineering one, so it travels less well than most of what we put on this blog.

It assumes the problem really is solved inside the price. On a job where the scope is thinner than ours — equipment supply only, say, with the civil works and the equalisation volume outside the contract — a lot of what we would call solved is genuinely still open, and the warnings belong in the document. Read our quote and a supply-only quote side by side and the second one should look more cautious, because it is.

It assumes an owner who reads. Some of our clients read the quote and nothing else; some read only the last page. A paragraph that misleads a careful reader may be the only paragraph a quick reader sees, which cuts both ways and is an argument for writing fewer sentences rather than more careful ones.

And it rests on our own position. We hold stock positions in Cebu, we have our own fabrication and civil network, and we can put a remedy into base scope without the price moving much. A supplier who would have to import the fix cannot absorb it the same way, and for him the honest thing may well be to present it as an option with its own price and its own warning attached. That is not worse drafting. It is a different commercial reality producing a different document.

What I would hold on to, wherever you sit: before a warning goes into a document a client is going to keep, check whether the thing it warns about is still a question. If the answer is no, you are not disclosing a risk. You are writing your own competitor's sales line for him.

If any of this is close to a job you are looking at — in Cebu or anywhere in the Philippines — you are welcome to book a free 15-minute consultation. You can also see what we have built, read how we size and specify a plant, or start from getting an STP if you already know roughly what you need.