Approach
How the engagement works, and why the number can be trusted.
The commercial model, the one measure, and the controls that sit under both.
Engagement
There is no price on this site because there is no single price. What is missing differs per company, so the scope differs, and so the fee differs. It is set on the call and written down.
Billing is monthly and paid in advance. Payment opens execution: the system does not take work into the queue before the payment is recorded.
If a payment passes the grace period, the system pauses. Panel access is suspended, automations stop, non-critical work in progress halts, and reporting stops. When the payment lands, it continues from where it stopped. Data is kept and work is not lost.
That pause is an automatic operating rule and not a sanction. Nobody decides it in the moment, and every client knows it from the start.
One measure: return on investment
The client’s total revenue, against the total spend pipera directs. That is the whole definition.
Revenue is read from the commerce platform’s own order data. The conversion API is a secondary source and is used when platform data is unavailable. When the two disagree, the platform order data wins and the gap goes into the report instead of being smoothed over.
Spend is everything pipera moves, including the fee itself. Leaving the fee out would flatter the number, so it stays in.
This is an accounting definition and not a target. The number can sit flat for a period. It can be negative. It goes in the report either way.
Counted as spend
- Media budget across every platform
- Production of everything that ships
- The monthly fee
Not counted as revenue
- Channels pipera does not run
- Orders that predate the engagement
- Any figure without a record behind it
Control and audit
How the system is kept honest, in the plainest terms available.
Every action is a record
What was done, by which part of the system, and why. The whole sequence can be replayed afterwards.
Money and one-way actions need a person
Anything that spends budget or cannot be undone goes through human approval before it happens.
Autonomy is earned, not granted
It rises with evidence and with a signature. It drops immediately and automatically on an incident. The asymmetry is deliberate.
No single model holds the system
Providers can be swapped. If one changes its terms or disappears, execution continues.
The data belongs to the client
Export and deletion rights are written into the legal pages rather than promised on a marketing page.
What we do not build
The boundaries are deliberate. Focus comes from what gets refused.
Not an agency
An agency grows by adding human hours. We grow by removing them.
Not a SaaS
We stopped selling the tool. A client does not rent an interface here.
Not a model lab
We combine capabilities that already exist. We do not train foundation models.
Not a workflow builder
Workflow tools can sit at the edge. The core is code, contracts and events.
Not a substitute for legal judgment
Rules are encoded in the system. A jurisdiction call belongs to a person.
Book a call.
Thirty minutes. You bring the business. We come back with what it would take.
Scope and price are set on the call. Monthly, paid in advance. Payment opens execution.