Structuring Institutional Trust Partnerships
Before making any claim involving a government, police, municipal, or licensing body, run it through this gate:
- What is the actual evidence status? True now / on roadmap / aspirational only.
- Which PRS pillar does it serve? Prestige (association/legitimacy), Reliability (operational process), Security (protective/enforcement capability).
- Which milestone gate are we in? Pre-incorporation / post-incorporation / post-traction.
- Which tier can this claim live in? User-facing guidance → Internal reporting SOP → Formal MOU.
If evidence status doesn't support the tier, downgrade the claim, don't upgrade the evidence.
Prestige — Association value: does this relationship signal legitimacy or endorsement to users/investors? (e.g., "recommended by," logos, badges)
Reliability — Operational value: does this relationship create a repeatable internal process that improves how the company functions? (e.g., an escalation path for fraud reports)
Security — Protective value: does this relationship create real enforcement or risk-mitigation capability? (e.g., a direct reporting channel to a cybercrime unit)
Every institutional relationship should be mapped against all three pillars independently — a relationship can be strong on Reliability (you have a working internal SOP) while being zero on Prestige (you cannot say "endorsed by police") because no formal agreement exists.
| Tier | What it requires | What you may claim |
|---|---|---|
| 1. User-facing guidance | Nothing formal — publicly available info (e.g., "here's how to report fraud to Policía Nacional") | Generic educational/process guidance, no implied relationship |
| 2. Internal reporting SOP | An internal process, even informal (a documented contact, a known escalation email) | Internal ops language only ("we have a process to escalate to authorities") — never user-facing "partnership" language |
| 3. Formal MOU / signed agreement | Signed, dated, scoped document with the institution | Named partnership claims, logos, "official collaboration with X" |
Rule: A claim can only live at the tier its evidence supports. Aspirational relationships live in the roadmap doc, not in copy, decks, or SOPs.
| Gate | What's realistically available | Default posture |
|---|---|---|
| Pre-incorporation | No legal entity, no signing authority | Tier 1 only. No outreach implying institutional capacity. |
| Post-incorporation | Entity exists, can sign, can approach institutions credibly | Tier 1–2. Outreach for MOUs can begin, but don't announce until signed. |
| Post-traction | Data/users to justify institutional interest | Tier 1–3. MOUs become realistically achievable and claimable. |
Rule: Never let ambition about a future gate leak into present-tense claims. "We are pursuing a relationship with X" (roadmap, internal) ≠ "We work with X" (Tier 3 claim, forbidden without signed MOU).
Progress:
- Step 1: Log the candidate relationship (institution, contact, purpose)
- Step 2: Classify evidence status — true now / roadmap / aspirational
- Step 3: Map against all three PRS pillars independently
- Step 4: Identify current milestone gate for the company
- Step 5: Assign the maximum permissible tier (1, 2, or 3)
- Step 6: Draft claim language strictly within that tier
- Step 7: Route to correct artifact — public copy (Tier 1), internal SOP doc (Tier 2), or legal/MOU tracker (Tier 3)
- Step 8: Set a re-evaluation trigger (incorporation date, first signed contact, traction metric) to revisit tier
Example 1: Input: "We want to say on our landing page that we work with the Spanish police's cybercrime unit." Output:
- Evidence status: Aspirational — no contact made yet.
- PRS mapping: Prestige (high value if true), Reliability (none yet), Security (none yet).
- Milestone gate: Pre-incorporation.
- Permitted tier: 1 only.
- Approved claim: "If you believe you've been the victim of fraud, you can report it to Spain's Policía Nacional cybercrime unit (Brigada de Investigación Tecnológica) via [public link]." No mention of "we work with."
- Action: Log aspirational MOU in roadmap doc, not in copy.
Example 2: Input: "We've had two informal calls with a municipal licensing office and now have a named contact we escalate provider-verification questions to." Output:
- Evidence status: True now, informal.
- PRS mapping: Reliability (medium — a working escalation path exists), Prestige (zero — no agreement to cite), Security (low — informal, not codified).
- Milestone gate: Post-incorporation.
- Permitted tier: 2.
- Approved language (internal SOP only): "Provider licensing discrepancies are escalated to [named municipal contact] for verification." Not user-facing, no naming the municipality publicly as a "partner."
- Action: Add MOU pursuit to roadmap; re-evaluate at post-traction gate.
Example 3: Input: "We signed a formal MOU with the municipality for a verified-provider registry integration." Output:
- Evidence status: True now, formal.
- PRS mapping: Prestige (high — can be named), Reliability (high — process is now contractual), Security (medium-high depending on scope).
- Milestone gate: Post-traction.
- Permitted tier: 3.
- Approved claim: "In official collaboration with [Municipality Name] to verify local service providers," with logo use per MOU terms.
- Keep a single source-of-truth tracker (spreadsheet or doc) with columns: Institution, Pillar(s), Evidence status, Tier, Gate, Claim language, Re-eval trigger.
- Write claim language for each tier in advance so marketing/legal don't improvise under pressure.
- Treat verbal or emailed goodwill from a government contact as Tier 2 at most, never Tier 3 — only a signed document unlocks Tier 3.
- Re-run the full gate check whenever the company crosses a milestone (incorporation, first paying users, first press) — don't wait for someone to ask.
- Separate "roadmap ambition" documents from "current state" documents so aspirational relationships never accidentally get copy-pasted into live materials.
- Claim creep: starting with accurate Tier 1 language and letting later drafts (investor deck, PR) quietly upgrade it to Tier 3 phrasing.
- Conflating a meeting with a relationship: one exploratory call is not Reliability or Prestige evidence — it's aspirational until there's a repeatable process or signed document.
- Using logos before MOU terms permit it — always confirm logo/brand usage rights are explicit in the signed agreement, not assumed.
- Letting internal SOP language leak to users: an internal escalation process ("we can flag this to our contact at X") is not the same as a public claim of partnership.
- Skipping the milestone gate check: assuming pre-incorporation ambition justifies post-traction-tier claims because "we'll get there eventually."