Propuesta Viva exists so you can explore a commercial proposal and say what works for you without losing negotiating power. These rules are fixed, enforced by the system's design (not by anyone's goodwill), and have no exceptions. Prospecta operates the mechanism as a neutral third party between provider and buyer.
What the provider receives
The provider who sent you the proposal receives only what you explicitly confirm:
· The structure you decide to take to internal evaluation, with the volume (or range) at which you confirmed it and your contact details if you provided them.
· Any adjustment requests you send (dimension + your comment).
· The structured “none of these works” (problem dimensions + optional comment).
· If you complete the fit-check: the compatibility verdicts. To be precise about what those are: each verdict restates what you answered as a compatibility statement (“preference: variable by usage — compatible: structure B; not compatible: A”), and the scope verdict names the items you marked as must-haves. So the provider can read your preferred model, your budget shape, the scaling you expect, your comparison point and your must-haves. That is deliberate: without it they cannot adjust anything, and it is exactly what you get in exchange for the reading we give you.
Before every send you see a mirror screen with the literal message that reaches them. No mirror, no send.
What they never see
· Which structures you looked at, in what order, or for how long.
· How you moved the volume slider while exploring.
· The full order of your model ranking: only your first choice travels, not how you ranked the rest.
· The budget cap you enter (see below).
This page uses no cookies and no third-party scripts, and the system records no navigation telemetry. The absence of that record is part of the product: neither Prospecta nor the provider can request it later, because it does not exist.
How sealing works
When the proposal is published, the full set of terms (structures, prices, curves, inclusions, exclusions and assumptions) is serialized to canonical JSON, its SHA-256 fingerprint is computed, and it is frozen with a UTC timestamp.
Editing a published proposal does not exist as an operation in the system. If the provider wants to change something, they can only create a new version: the new version declares that a previous one exists and since when, and the old link shows a notice that it was replaced.
At /verificar you can re-compute the fingerprint over the content you are seeing and compare it with the sealed one. If they match, what you see is exactly what was frozen — exploring cannot be used against you, because nothing you do can change what is already sealed.
How fit-check verdicts are computed
Verdicts are fixed, public rules — no AI evaluates your answers, and the same answers always produce the same verdicts:
· Pricing model: each structure is classified by its curve (fixed monthly → “fixed”; linear or banded unit price → “variable”; success with floor → “success”; base + variable → “hybrid”). Your top-ranked model is compared against that class: it matches or it does not.
· Budget shape: closed annual aligns with fixed structures; flexible monthly with variable and hybrid; per outcome with success-based; per project with fixed.
· Scaling: if you expect proportionality, linear, floor-based and banded curves meet it; fixed does not. If you expect tiers, only banded curves. If you expect fixed cost, only the fixed one.
· Scope: each item you mark as must-have is looked up in each structure's sealed breakdown: included in all, only in some (named), or in none.
· Reference: your comparison point travels exactly as you chose it.
The reading you see at the end (“which structure fits best”) uses exactly the same rules, is for you only, and is never sent.
The budget cap is ephemeral
The last fit-check question (cap of your monthly range) is optional. If you enter it, the server uses it exactly once to answer a single question: does any structure cost less than or equal to that cap at the volume you indicated?
The provider receives only “there is a zone of agreement” or “there is no zone” — no numbers, no distances, not even which structure.
The value is discarded once that computation ends. It is not stored in any database, neither in clear nor transformed: the only thing recorded is that you entered a cap, not which one. We used to keep a cryptographic fingerprint “for auditing”; we removed it after verifying that, with the salt stored beside it and such a small space of monetary amounts, that fingerprint was reversed in milliseconds. A promise the code cannot keep is worth nothing.