Your team’s working memory
for positioning.
Strategic Context is the layer every Stratridge capability reads from and writes to. Audits, signals, decisions, launch notes, win/loss patterns — one tenant-isolated store, structured by type, full-text searchable.
Without a shared memory, every audit is one-off and every decision evaporates. With one, each new finding compounds the value of every previous one.
Sign in or create a free account. Per-workspace isolation; no cross-tenant reads.
“Our institutional memory lives in fourteen places.”
Pillars in a Google Doc. Decisions in Slack threads. Win/loss notes in a Drive folder. Competitor intel in someone’s inbox. The Q1 offsite deck on a Confluence page nobody can find. Every decision gets re-litigated because nobody can see what was already settled.
Most teams try to solve this with a wiki. Wikis die the first time someone doesn’t update them. The fix is a memory layer that auto-ingests from the tools the team is already using — every audit, signal, launch, and review writes back automatically.
Strategic Context is that layer. Structured types, not free-form pages. Tool-assisted, not human-maintained. The context for every other capability in the suite.
Six memory types. One schema.
Every entry has a type, an origin tool, a timestamp, tags, and quoted evidence. The Analyst reads structure; humans read prose. Both work from the same source.
Pillars
Your three to five positioning claims, versioned. Every change logs a diff and a trigger — ‘Pillar 3 updated v0.7 → v0.8 on launch of gov-RLS.’
Decisions
Every non-trivial positioning call, with the context and the alternative. Six months later anyone can answer ‘why did we go this way?’ with a receipt.
Audit findings
Positioning Audit and AI Visibility findings auto-ingest here. Priority issues become memory entries tagged by lens and severity.
Signals
Material competitor moves ingest with severity and recommended action. Tag space is shared across the suite so nothing orphans.
Win/loss patterns
Objection patterns, positioning gaps, and competitor frames from Win/Loss Review. Patterns aggregate across reviews automatically.
Free-form notes
Manual entries when the tools don’t cover it yet. Typed, tagged, searchable — and if a tool starts covering the pattern, the manual notes can be merged in.
Structured. Quoted. Re-readable.
Three lost deals (Globex, Initech, Soylent) tagged competitor=a, segment=mid-market, stage=evaluation. Common thread: buyer said governance story was ‘aspirational’ while competitor’s felt concrete. Competitor shipped governance whitepaper 14 days ago; coincidence timeline is tight.
Globex note (2026-04-05): ‘gov conversation ended the deal in week 2.’ Initech note (2026-04-11): ‘they asked "show me the security page"; we don’t have one.’ Soylent note (2026-04-17): ‘CISO pushed back; rep had nothing to forward.’
competitor=a, segment=mid-market, cause=governance-trust, lens=proof, priority=high
Positioning Brief v0.9 (What just changed), Battle Card ‘Acme vs Competitor A’ (Proof block), Analyst answer 2026-04-18 (‘Why are we losing mid-market to Competitor A?’)
Short answers.
No. Your workspace data stays in your tenant. LLM queries go to Anthropic/DeepSeek under our accounts; your context is not used for training.
No. Every read is scoped to your account ID. Anonymous scans are never attributed to any workspace, including ours.
Postgres full-text search with GIN indexes. Fast, cheap, and deliberately not vector embeddings — we’ll add embeddings only if FTS stops being enough.
Yes. JSON export per type or the whole workspace. Your memory is yours; we don’t lock it.
Yes, with audit trail. Deletions soft-delete by default (30-day recovery window), hard-delete on request.
You get a full export of Strategic Context on the way out. We retain nothing beyond the retention window in our Terms.
Related capabilities.
Analyst
Reads Strategic Context to answer strategic questions. Writes drafts back when you ask. The chat surface over the memory.
See Analyst →Positioning Brief
Regenerated from Strategic Context whenever inputs change. The one-page living view of what the memory currently says.
See Positioning Brief →Positioning Audit
The on-ramp. Every audit writes pillars, snapshot, and priority issues to Strategic Context automatically.
Run a free audit →One place. Structured. Yours.
Open Strategic Context in a workspace and start capturing pillars, decisions, and notes. Every audit, signal, launch, and review writes back automatically — so the memory compounds without anyone maintaining a wiki.
Further reading
The Strategic Context Manifesto: Memory as a Moat
The strongest moat a modern company can build is the accumulated memory of its strategic reasoning, made legible and reusable. A long read on why — and how.
Strategic Context: The First 30 Days of Memory
A strategic-context system is worth nothing empty and worth everything full — but the first 30 days is where most founders give up. Here's what to log, when, and the five-minute daily ritual that makes the system durable.
Strategic Context for Marketing Teams: An Implementation Guide
Marketing teams generate enormous amounts of strategic context and almost none of it survives past the current campaign. Here's the implementation that converts campaign learning into company memory — three artifacts, one ritual, one owner.