The watch runs daily. The Bulletin comes to you. So does the fix.
A one-time audit is a snapshot. The work is the watch. Amplify is the push — the weekly Bulletin issue every Tuesday morning; a flash the morning a rival repositions, a citation drops, or a shipped fix regresses; the pre-flight read on every draft before it ships; the signed quarterly synthesis your CEO actually reads.
One issue, every Tuesday. A flash the morning something breaks.
The artifact Amplify is organized around. The weekly issue opens with your score and the week's read, then the lead story, a rotating investigation, the ledger of what you shipped and what it earned, and one prescribed move. Between issues, the watch stays on — and when it catches a genuine break, a flash is in your inbox that morning with the fix already drafted. Lands in email by default; in Slack on Scale and above; on a public link you can forward to a board.
Citation gap
An AI engine answered a query in your category and didn't name you — or named a rival that didn't yesterday. The fix: a homepage rewrite or a citation-gap brief, queued in Amend.
Competitor move
A rival shipped a new /vs/ page, a pricing change, or a launch overnight. The watch summarizes what they changed and why it matters; the rebuttal is queued in Amend.
Drift alert
Your homepage H1 and the deck the SDR team sent Tuesday no longer agree. The Bulletin surfaces the contradiction and proposes which line to keep.
An editor's read where you already draft.
Most of what your team publishes won't land. Not a talent problem — content written for the idea of a reader, not a specific person in a specific moment. Paste a draft into Stratridge and Amplify reads it the way a senior editor would — against your audit findings, your positioning, and the message you've decided on. Four dimensions, three to five line-level edits quoted from your draft.
Resonance
Is the language specific and concrete enough to provoke a reaction, or a stack of abstract benefit claims? ‘Analyze data faster’ reads as nothing. ‘Your CFO at 4:55 PM Friday’ reads as something.
Utility
Will the reader save, forward, or act on this? Content that helps the reader do their job gets shared. Content that celebrates the writer's product does not.
Narrative pull
Is there tension, a curiosity gap, a story shape — or a tour of features? Predictable structure reads as a press release. A line that withholds something reads as writing.
Trigger
Does the piece anchor to a real moment the reader hits in their week — a meeting, a customer question, a seasonal cycle? ‘In today's market’ scores low.
An editorial judgment you can act on.
A paragraph-length read, a four-dimension grid, and three to five line-level edits quoted from your draft — every one with a proposed replacement.
The piece reads as a feature announcement written for nobody in particular. The first two sentences name the feature and the capabilities; neither line anchors to a reader, a moment, or a stake. A finance director scanning LinkedIn has no reason to pause.
The one move that would change the read: open on the 4:55 PM Friday question from the CEO. Everything else in the piece — the dashboards, the real-time updates — becomes a response to a specific, recurring moment the reader already knows.
Feature-first, reader-blind.
Useful in theory; reader has to translate.
No tension. Punchline by sentence two.
No moment in the reader's week attached.
“Our new reporting feature helps you analyze data faster.”
“When the CEO asks ‘how are we trending?’ at 4:55 PM Friday, you have five minutes. Here's how reporting stops being the thing that makes you late for dinner.”
What runs while you sleep.
Four monitors run overnight. Their findings are what compose the Bulletin — the weekly issue and any flash — and what queue fixes in Amend without you opening the app.
Stratridge probes ChatGPT, Perplexity, Gemini, Claude, and DeepSeek for your category queries every morning. Citation share is a tracked KPI, not a one-time read. A real drop lands as a flash in your inbox with the fix already drafted.
Pricing changes, new /vs/ pages, hires, launches. After the baseline audit, the watch runs every night — diff, summary, and a recommended response queued in Amend by 8am.
On a cadence you set, Stratridge re-reads your live surfaces against the strategic context. When your homepage and your one-pager start telling different stories — which they will — you catch it before a buyer does, and the Bulletin flags it.
On the cadence you set — weekly, monthly, or quarterly — the full six-dimension audit re-runs and diffs against the prior result. You see which dimensions improved, which regressed, and which closed work held.
The watch daily. The issue weekly. The synthesis quarterly.
The watch runs every day; the issue lands every Tuesday; a flash lands the morning something genuinely moves. Your score and its weekly components open every issue. Every quarter, a signed synthesis your CEO actually reads. Same source of truth, three cadences, three jobs.
Daily · the Watch
Engines probed, rivals diffed, drift checked every day. When something genuinely breaks, a flash is in your inbox that morning — never a no-news email.
Weekly · the Bulletin
The issue, every Tuesday: your score and the week's read, the lead, the investigation, the ledger, one move. The next issue scores whether it shipped.
Quarterly · Synthesis
Score trajectory, closed work, new threats, recommended next moves. Signed, dated, forwardable to a board.
Short answers.
- What's actually in the Bulletin?
- The weekly issue: your score and the week's read up top, then the lead story, a rotating investigation — one factor of your message read closely, or the buyer queries the engines answered without you — the ledger of what you shipped and what it earned, and one prescribed move with a date. A flash is shorter: the one thing that broke overnight, and the fix, already drafted.
- Where can I send the pre-flight read?
- Paste any draft into Stratridge — a blog post, a landing page, an announcement, a one-pager. The read comes back in the same screen: four dimensions, with the line edits quoted from your draft. An in-editor surface for Google Docs and Notion is on the roadmap.
- Does the pre-flight rewrite for me?
- It reads, judges, and proposes specific line-level replacements. Whether you accept them, hand them to your writer, or use them as a brief is up to you.
- How often do the monitors run?
- AI-engine probes daily across all five engines. Competitor diffs daily. Voice drift on the cadence you set (weekly is typical). Re-audits weekly, monthly, or quarterly — your call.
- Where does the quarterly synthesis ship?
- Email and the workspace. Public link option for forwarding to a board. Markdown and PDF export.
- Will the pre-flight match my voice?
- The read is grounded in your strategic context — your pillars, your tone, your evidence. The voice it nudges toward is yours, not the model's.
- Is this in Spark?
- Bulletin and pre-flight read: yes. Slack delivery of the brief and the signed quarterly synthesis: Scale and above. Portfolio adds founder review on the quarterly.
The audit is the fastest way
to find out.
Connect a URL. Get the full read on how your market sees you — free. Then decide whether the story they're finding is the one you meant to tell.