A missing price is not neutral. It removes the buyer's ability to disqualify a supplier quickly, it forces a meeting to obtain something that could have been a line of text, and it hands the seller control over the order in which information is revealed. pipera does not publish a price, and the first honest thing to say about that is that it is a real cost, paid by the buyer, for the seller's convenience. Whether anything is bought with that cost is the only question worth arguing.
The reason is scope, and scope varies for a reason that is easy to state. The engagement is the whole digital side, thirteen functions running at once, and that list does not change from company to company. What changes is how much of it already exists, in what condition, and what has to be built before any of it runs. One company arrives with a store that works and no email programme of any kind. Another has a product catalogue living in three places that disagree with each other. Another has advertising history worth preserving and a site that falls over when traffic arrives. The daily operation across those three is roughly comparable. The construction that has to happen first is not comparable at all, and most of the cost sits there.
A published number would therefore do one of two things. Set as a single figure, it would be wrong for most companies: too high for the ones arriving with a functioning digital side, too low for the ones arriving with almost nothing. The second group is the dangerous one, because a price set too low does not stay too low. It gets recovered afterwards through rescoping, additional line items and quiet reductions in what actually ships, which is a worse outcome for the buyer than never having seen a number. The alternative is a range wide enough to be truthful, and a range wide enough to be truthful for both of those companies communicates nothing.
So the figure is set on a call, and the order of that call is what matters. Scope is established item by item before any figure is discussed. Each function is walked through: what exists, what does not, what has to be built, what runs every day once it is built, and what the business will see in the portal. Deliverables are named specifically enough to be written into a contract and owed. Only after that list closes does a number appear. The order is not politeness. A figure stated first turns everything after it into a negotiation about what can be squeezed inside the figure, and the part that gets squeezed is always the part the buyer could not evaluate.
The fear underneath all of this is rarely the fear that gets stated. It is not that the price will be higher than a list price. It is that the price will be set by how big the company looks rather than by what the work is. That fear is earned. Reading a buyer's revenue off a public signal and setting a fee against it is a common practice with a respectable name, and a buyer who has been through it once recognises the shape of the conversation: questions about turnover, headcount and funding arriving before questions about systems.
The defence is not a promise, because a promise is worth nothing here. The defence is the sequence itself, and the sequence is observable while it is happening. An operator pricing the work needs the state of the digital side early, and spends the first part of the call on what exists, what is broken and what has to be built. An operator pricing the buyer needs the size of the buyer early, and gets there quickly by a route that sounds like qualification. Both conversations end with a number. Only one of them produces a list of items the number is attached to.
That gives the reader a test, and a test is necessary, because no argument rescues the phrase "let us discuss it on a call". It is exactly what a vendor with a weak offer says, and the phrase has been spent by people who use the call to establish willingness to pay rather than scope. Nothing written here cleans it. What can be done is to name the checks that separate the two cases, and they cost the buyer nothing but attention. Does the scope list exist before the number. Are the questions about the buyer's systems or the buyer's size. Are the deliverables written in a form where a failure to deliver one would be decidable by someone reading a record, rather than settled by whoever speaks with more confidence. And does the operator ever say no. pipera declines partial scope, because taking over advertising without taking over creative trades control for speed and then reports a number that no longer means anything, so some calls end without an engagement rather than with a smaller one.
A buyer who runs those checks does not need the price to have been published. A buyer who runs them and finds the answers going the other way has learned something more useful than a number would have told them.
Take the call, and watch which arrives first, the list or the figure.