Stratum Client Outcome Case Study Template

Stratum Client Outcome Case Study Template Author: Adam Bishop. Publisher: XOps360 LLC. Date: 2026-04-28. Fingerprint: fp-ent-20260428-casestudy-tmpl. URL: https://xops360.com/research/stratum-case-study-template/ Purpose: This template standardizes how XOps360 documents outcomes for Stratum-integrated clients. Each completed case study is seeded as a Stratum entity with full provenance (OpenTimestamps, Archive.org), making client outcomes publicly verifiable and referenceable in federal capability statements. Template Structure: Section 1: Client Entity Declaration - Client canonical name and Stratum fingerprint - Schema type (LocalBusiness, Organization, etc.) - Entity class (class 1 self or class 2 client) - Date entity was declared in Stratum graph - Number of same_as corroboration links at declaration - Tier (Tier 1, Tier 2, or Tier 3) Section 2: Baseline Measurement (pre-Stratum) Capture before any entity work begins: - Google Search Console: impressions, clicks, average position for primary keyword targets - LLM discoverability test: query Claude, ChatGPT, Perplexity with "find [service] in [location]" and document whether client appears, and if so, with what accuracy - Cross-graph presence: how many external graphs reference the client at baseline (Google Business Profile, Yelp, Facebook, SAM.gov if applicable) - Entity structure: does any structured JSON-LD exist on the client site at baseline? Section 3: Stratum Integration Deliverables Document what was built: - Entity declaration date and Stratum URL - Schema type and properties declared - Number of same_as links established at launch - Niche namespace targets defined (specific keyword + location combinations, not generic terms) - Provenance surfaces activated (OpenTimestamps, Archive.org, IPFS if Tier 2+, Nostr if Tier 3) - Cross-graph references established (Wikidata, Google Business Profile, OpenStreetMap, industry-specific graphs) - Any AGORA investigations seeded for this client (Tier 3 only) Section 4: Outcome Measurement (post-Stratum, 90-day) Measure at 30, 60, and 90 days after entity goes live: - GSC impressions delta: [baseline] to [current] for primary namespace targets - GSC clicks delta: [baseline] to [current] - LLM discoverability: re-run baseline queries. Document change in appearance rate and accuracy of information returned - Cross-graph citation count: how many external graphs now reference the entity - Same-as corroboration links: total count at 90 days vs launch - Entity authority signal: is the entity appearing in "also known as" or "related to" relationships in external graphs? Section 5: Niche Namespace Performance For each niche namespace target defined at launch: - Target phrase (e.g., "Somerset WI laser engraving") - GSC impressions at 30/60/90 days - GSC average position at 30/60/90 days - LLM appearance: does the client appear when queried with this phrase? - Competitor presence: how many entities compete in this namespace? Section 6: Client Attestation - Client contact name and role - Date of attestation - Qualitative outcome summary (client's own words, 2-3 sentences) - Permission to reference in XOps360 capability statements (yes/no) Section 7: XOps360 Assessment - Did Stratum integration produce measurable outcomes in the 90-day window? - What was the primary value driver (LLM discoverability, GSC, cross-graph, or provenance)? - Recommended next step (renew Tier 2, upgrade to Tier 3, expand namespace targets, add AGORA investigation) - Estimated annual value of discoverability gains to client (conservative estimate) Provenance Note: Each completed case study is archived at Archive.org at time of completion and OpenTimestamped. The Stratum entity for the case study includes same_as links to the Archive.org snapshot and OpenTimestamps proof. This makes client outcomes cryptographically verifiable -- a capability no traditional web agency can offer.