Flood Content Engine

Meet Socrates.

Socrates is Flood's content engine — it researches a client and a topic, then writes content that ranks in search, gets cited by AI, sounds genuinely human, and stays on-brand. Nobody starts from a blank page.

What it is

One engine, two jobs done well.

Socrates takes a client and a topic and produces a fully SEO- and GEO-optimised piece in that client's voice — a blog post, article, location page, or service-area page. It keeps everything it knows about each client organised in our shared drive, so the work compounds over time instead of starting fresh every time.

It remembers each client

Every client gets a living knowledge base — brand voice, target customers, competitors, a map of internal links, and page templates. Built once, improved with every piece.

It writes to our standard

Direct research, real sources, on-brand voice, internal links, matching schema, and a built-in quality check that strips out "AI slop" before you ever see a draft.

You stay in control the whole way: Socrates works through three drafts and pauses for your approval at each one. Nothing publishes without you.

How to use it

From client name to finished piece.

Open a chat in our Claude Team workspace and talk to Socrates plainly. No special commands — just say what you want.

Set up the client (first time only)

For a brand-new client, say Set up a new client: [Name], [their website URL]. Socrates researches the site and builds their full knowledge base in the shared drive. If the client already exists, skip this — it just loads what's there.

Ask for the piece

Say what you need, e.g. Write a blog post for [Client] on [topic]. Add any constraints in plain English — word count, keywords to include, links to specific pages. Socrates echoes back a short plan so you can catch anything before it starts.

Review the First Draft

You get a complete draft focused on substance and angle. Tell it what to change — depth, tone, sections, direction. This is the moment to steer; be specific.

Check the Optimized Draft

It folds in your feedback and adds the full optimisation layer: internal links, SEO + GEO structure, FAQs, schema, and a quality score. Give it any last notes.

Approve the Final Draft

Once you approve, the piece is done — and Socrates automatically updates that client's knowledge base (link map, run log, and anything it learned). No copy-paste, no manual filing.

Tip — Not sure what to write? Ask "What should we write for [Client] to win in AI search?" and Socrates pulls the prompts where the client is losing visibility and turns them into a prioritised list.

Good to know

Questions & deeper detail.

Open any of these for more — the full documentation is linked at the bottom of the page.

Who can use Socrates?

Socrates is internal use only, but anyone on our Claude Team workspace can access and use it — Account Managers, CSMs, Project Managers, Strategists, SEO, and Engineers alike. You don't need to be technical and you don't need special access; if you're in the workspace, just start a chat and ask. It's built for the whole team, not only power users.

Optimize token usage — which model, and when

Our Team plan shares usage across everyone, so a little care keeps Socrates fast and available for the whole team. The biggest lever is matching the model to the task:

SituationUse
Onboarding a new client, or the Final Draft quality passOpus 4.8 / 4.7 — heaviest reasoning and research
Routine article drafting and edits (your default)Sonnet 4.6 — the everyday workhorse, fast and strong
Quick questions, small tweaks, formattingHaiku 4.5 — fastest and lightest

A few habits that go a long way:

  • Onboard each client once. It's the most expensive step — never re-onboard a client who already has a knowledge base; Socrates just loads it.
  • Spread articles out. Don't batch ten pieces in one sitting. Steady pacing keeps usage available for everyone and gives each piece your full attention at the gates.
  • Let the knowledge base do the work. The whole reason Socrates is efficient is that it reuses what it already knows — so the more a client's profile fills in, the less each new piece costs.
  • Let a stage finish before piling on. Re-running or interrupting mid-draft wastes work already done.

When in doubt, draft on Sonnet 4.6 and reach for Opus only when the task is genuinely heavy.

How it keeps content from sounding like AI

Before any draft reaches you, Socrates runs it through a scored quality gate checking directness, rhythm, specificity, authenticity, E-E-A-T signals, density, and brand fit. Anything below the bar gets rewritten automatically. It removes the tells that make readers (and search engines) distrust AI copy — detached "textbook" voice, overused phrasing, uniform structure — and leans on real first-hand experience and a named author instead.

How it optimises for AI search (GEO)

Ranking on Google no longer guarantees being cited by AI answers. Each piece is built to be quotable by ChatGPT, Perplexity, Google AI Overviews, and Claude: direct-answer openings, self-contained sections, named statistics with real sources, FAQ blocks matching how people actually ask, and matching schema markup shipped with every piece. It also flags off-site opportunities — the reviews, communities, and publications AI engines lean on — that go beyond the client's own pages.

What lives in a client's knowledge base

Each client has a folder in the Flood — Client Content Profiles shared drive containing Brand Guidelines, ICP Personas, a Competitors & Gap Analysis, Page and Blog templates, an Internal Linking Webmap, a Target Prompts & Visibility tracker, and a Content Run Log. They're all normal Google Docs and Sheets — open and edit any of them by hand whenever you like.

The guardrails it never crosses
  • No invented facts — it never makes up addresses, pricing, stats, or testimonials. Anything unconfirmed is flagged [CLIENT TO CONFIRM].
  • Real sources only — every statistic traces to a page it actually read.
  • You approve every stage — it never skips ahead or publishes on its own.
  • Voice is matched, not faked — it writes in the client's tone rather than announcing it.
Help Socrates evolve

Socrates gets better with use, and your feedback is how that happens. Found something great, something off, or have an idea to improve it? Please post in the #claude channel on Slack, or reach out to Steven directly — so we can make Socrates better for everyone. The more specific the feedback (what you asked, what it did, what you expected), the faster it improves.

Go deeper

Full documentation.

Optional, for when you want the detail behind any part of Socrates.