One deck. Everything about the company: what we do, what we believe, the Second Brain, the commands, the rituals. Read it before your first real task.
/ Amplio internal onboarding · use → to advance
/ 01 — Identity
Not a consultancy that advises from the outside. Not a freelancer that disappears. We sit inside the team — fixing tracking, proving ROI, automating reporting. Powered by AI.
The rule of Amplio: we don't just show numbers. If the data is wrong, nothing built on it ships.
The operating model: an async first, AI augmented team, tightly integrated with each client's stack. Everything lives in a version controlled Second Brain.
The Amplio tagline. It travels with everything we ship.
/ 02 — What we deliver
Every engagement maps to one or more of these. Know them cold.
Full GA4 + GTM build, server side via Stape with custom connections to 7 platforms. Recovers 20 to 40% of lost conversions.
Cross platform attribution. GA4 to ads reconciliation. 34% of sessions are hidden by consent — we measure the gap.
AI powered reporting, anomaly detection, consent impact analysis. Monthly performance report + business review meeting.
Cookiebot, Usercentrics, Consent Mode v2. GDPR compliant without sacrificing data quality.
Custom AI interface on your preferred LLM. Real time insights into your data and tracking setup. Unlimited connections.
Audits, migrations, custom builds, incident triage. Scoped engagements outside the retainer tiers.
/ 03 — How we package
Foundation is the productised one time fix. Maintained is the recurring retainer. Managed stacks a custom AI interface and unlimited connections on top. Every new deal lands in one of the three.
Audits, GTM rebuilds, server side migrations, Consent Mode v2 implementations, attribution wiring. Productised one time engagements with a fixed price.
Ongoing tracking maintenance, Consent Mode v2, server side with custom connections to 7 platforms, custom attribution, monthly reporting + business review.
Everything in Maintained + custom AI interface on your preferred LLM for real time insights into your data and tracking setup. Unlimited connections.
Every new deal maps to Foundation, Maintained, or Managed · upgrades from Maintained to Managed are celebrated · downgrades trigger a client health review
/ 04 — Proof points · verified, never fabricate others
These appear in decks, emails, the website. Anything else is unverified and does not ship.
34% of sessions are hidden by consent — we measure the gap.
20 to 40% of lost conversions recovered via server side + enhanced conversions.
/ 05 — The Second Brain
Everything we know — every client, every SOP, every pattern — lives in a markdown Vault. Version controlled. AI readable. It's how Amplio scales.
Brain-Dump.md is the firehose. raw/ is immutable source material — clip, never edit.
Active client deliverables, internal builds, campaigns with a finish line.
Google Ads, Analytics, Sales, Amplio-Internal. Work that never "finishes".
Brand voice, playbooks, templates, skills, research. The library.
One concept per note, max 300 words, ≥1 wikilink. How knowledge compounds.
One folder per client. Overview, meetings, reports, tracking, correspondence, recommendations.
/ 06 — Karpathy's three layers
The Vault is built on a 3 layer architecture inspired by Karpathy's LLM Wiki. Understand this and you understand how the system learns.
00-Inbox/raw/ — immutable inputs. Articles, transcripts, PDFs, clippings. Tagged processed: true once compiled.
05-Galaxy/ + 03-Resources/ — compiled, structured, interlinked. Atomic Galaxy notes + Resources. What Claude reads when answering.
CLAUDE.md + program.md — the rules. How the Vault works, what gets routed where. The brain of the brain.
The loop: 01 Capture → 02 Compile → 03 Link → 04 Lint → 05 Enrich
/ 07 — Bidirectional commands
Say these to Claude and the right thing happens: file created, folder routed, report generated.
| Group | Command | What happens |
|---|---|---|
| Session | "Update memory" | Overwrite Current State, append to the log. Run at the end of every session. |
| Session | "Process inbox" | Reads Brain-Dump.md, routes items, clears processed. |
| Session | "Compile / Lint the vault" | Full pass over raw sources. Lint checks broken links + stale content. |
| Client | "New client: [name]" | Creates the full space from template. Updates the index. Seeds data-context. |
| Client | "Client brief: [name]" | Claude reads their _overview + recent notes, returns a status summary. |
| Client | "Pipeline review" | Reads all prospects, summarizes scores, stages, next actions. |
| Content | "Draft outreach for [persona]" | Reads persona + outreach templates. Personalizes. |
| Content | "Score this lead: [company]" | Reads the ICP file. Returns score + tier + rationale. |
| Learning | "Track recommendation" | Adds a row to the client's recommendations-tracker. Closes the loop. |
/ 08 — Daily rhythm
Only Walter and Daragh have direct access to the Vault. Everyone else reads it through the Vault Dashboard and writes to it through update_ emails. The Vault stays alive because every session leaves it richer than it started.
Walter + Daragh run "Session brief" in Claude. Everyone else opens the Vault Dashboard. Check the 08:00 daily-intelligence run.
ops.ampliodata.io — MRR, client health scores and bands, alerts, open vs actioned recommendations per client, active projects, top 20 pipeline. Refreshed every 4 hours by deploy-cycle.
Send to the Amplio Updates label, subject update_[you]: [client] — [what changed]. The sync task routes and writes to the Vault. Never write to the Vault from the dashboard.
Wrong number, missing client, stale rec? Teach the Vault: forms.gle/Bcs52Zjd7qsyuJuv8 — one atomic signal per submission. Correction · Gap · Confusion · Contradiction · Example.
Walter + Daragh: "Update memory" in Claude. Everyone else: send the day's update_ emails.
Compile, lint, enrich, pattern analysis, health scoring — Phase I of the 08:00 daily-intelligence run. See scheduled-tasks-reference.md for the four cycle fleet.
/ 09 — The rules
If your work contradicts one of these — stop and ask. These rules are in CLAUDE.md for a reason. Two per row here; the full text lives in Section 6.
/ Next step
Questions → Walter or Daragh. Better questions → Claude. Next up: Deck 02 — Client lifecycle.