The client portal contains no control that changes anything. No pause, no budget field, no approve or reject queue, no switch that reaches the operation. What it contains is the record.
Everything the operation does is written down before it counts as done: what ran, when it ran, what evidence it rested on, what it cost, and who approved it where approval was required. The decision log is open to the client without a request and without a delay. An action that is not in the record did not happen, which is a rule about pipera's own conduct rather than a description of software. And where the one number cannot honestly be produced, because the data is incomplete or the attribution chain is broken or the period is too short to mean anything, the portal says so and says why, in the place the number would have occupied. An empty slot is the honest output. A produced number is not.
The portal is complete on the seeing side and empty on the doing side. That asymmetry is the design, and the reason behind it is accountability rather than control.
The mechanism is worth spelling out. Execution rights, once shared, produce shared responsibility, and shared responsibility makes a single measure meaningless. Suppose the client can pause a campaign. On a Thursday afternoon somebody pauses one, for a good reason or a nervous one, and the following week the number moves. Whose movement is it? The operation points at the pause. The company points at the weeks around it. Both explanations are partly right, neither is checkable, and the argument gets settled by whoever is more insistent rather than by evidence. Set that against thirteen functions running at the same time and the measure stops describing anything at all. It becomes a number two parties negotiate about instead of a number one party answers for.
A measure means something only when a single party owns every decision behind it. That is not a preference about tooling. It is the condition under which the number is worth reporting.
The obvious objection is that this feels like less control, and the feeling is accurate about one kind of control. Two things hide inside that word and they are worth pulling apart.
Control over execution is the ability to press a button and have something change immediately. It is fast, it is satisfying, and it is almost always the weaker of the two, because the operator grants it and the operator can quietly narrow it. Plenty of arrangements hand a company a set of switches and keep everything that matters, the credentials, the data, the record, the ability to walk away, on the operator's side of the line.
Control over the relationship is the ability to decide whether the arrangement continues at all. It is slower, it feels less like control, and it is the form that actually binds the other party.
pipera gives the company the second, withholds the first deliberately, and publishes the trade instead of burying it.
What the client can do is a short and deliberate set. The client grants access and revokes it, on any day, and revocation stops the operation the same day. The client agrees the scope, function by function, before anything runs, and the scope goes into the contract rather than into a conversation. The client supplies insight, which enters the evidence and is weighed with everything else rather than converted into an order. And the client ends the engagement.
That set is not a consolation prize. Between them those powers cover whether the arrangement exists, what it covers, what it knows, and when it stops. What they do not cover is the sequence of daily decisions, and the reason is that the sequence of daily decisions is the thing being bought.
The insight point earns its own line, because it is the one most often misread as exclusion. When the person who has sold the product for a decade says a line is starting to move, that is real information and the operation treats it as such. It is entered as evidence, dated, and weighed against measurement. What it does not do is jump the queue and become an instruction, because an operation that executes on somebody's instinct on request cannot then be held to a measured outcome. Nobody is doing a client a favour by pretending otherwise.
The portal is not a courtesy window into an operation that would rather not be watched. It is the instrument that makes the arrangement checkable from outside, and being checkable from outside is the only thing that makes an operation carrying this much execution authority safe to grant it to.
If you would rather hold the record than hold the buttons, begin with the scope conversation.