/DECK 01 · THE AMPLIO WAY OF WORK
IDENTITY · RITUALS · SECOND BRAIN

How Amplio actually works.

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.

+37%Average ROAS lift
100+Teams shipped on
5servicesProductised catalogue
1vaultSingle source of truth
Walter Masseroni Gonzalez · Amplio Data
01 / 10 · next
/01 · IDENTITY
/WHO WE ARE

We embed senior data expertise inside marketing teams.

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. We make sure the numbers are right first.

/OPERATING MODEL
  • Async-first, AI-augmented team
  • Tightly integrated with each client's stack
  • Everything lives in a version-controlled Second Brain
/TAGLINE

Better Data. Smarter Campaigns. Proven ROI.

03-Resources/Brand/ · Walter & Daragh · Barcelona
02 / 10
/02 · WHAT WE DELIVER

Five core services. One outcome: data you can trust.

Every engagement maps to one or more of these. Know them cold.

01 · TRACKING

GA4, GTM & Server-side

Full GA4 + GTM build, server-side via Stape with custom connections to 7 platforms. Recovers 20 to 40% of lost conversions.

02 · ATTRIBUTION

Custom attribution & ROI

Cross-platform attribution. GA4 to ads reconciliation. 34% of sessions are hidden by consent — we measure the gap.

03 · REPORTING

Monthly reporting & reviews

AI powered reporting, anomaly detection, consent impact analysis. Monthly performance report + business review meeting.

04 · CONSENT

Consent Mode v2 & compliance

Cookiebot, Usercentrics, Consent Mode v2. GDPR compliant without sacrificing data quality.

05 · AI INTERFACE

Chat with your data

Custom AI interface on your preferred LLM. Real time insights into your data and tracking setup. Unlimited connections.

+ PROJECTS

One time & ad hoc

Audits, migrations, custom builds, incident triage. Scoped engagements outside the retainer tiers.

03-Resources/Brand/ · service catalogue
03 / 10
/03 · HOW WE PACKAGE

Three tiers. One ladder.

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.

TIER 01 · FOUNDATION

Foundation

€400 to €1,500
One time

Scope: Audits, GTM rebuilds, server side migrations, Consent Mode v2 implementations, attribution wiring. Productised one time engagements with a fixed price.

TIER 02 · MAINTAINED

Maintained

€700 to €1,200/mo
Monthly retainer

Scope: Ongoing tracking maintenance, Consent Mode v2, server side with custom connections to 7 platforms, custom attribution, monthly reporting + business review.

TIER 03 · MANAGED

Managed

From €1,800/mo
Monthly retainer

Scope: 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.

03-Resources/Templates/proposal-template.md
04 / 10
/04 · PROOF POINTS
/VERIFIED — NEVER FABRICATE OTHERS

Only these numbers. Never invent new ones.

These appear in decks, emails, the website. Anything else is unverified and does not ship.

ROAS LIFT
+37%
Average across clients
FULL SETUP
48h
End to end time
DATA BACK-AND-FORTH
–90%
Versus manual reporting
TEAMS SERVED
100+
Across EU + UK
CONSENT-HIDDEN
34%
Sessions we recover visibility on

20 to 40% of lost conversions recovered via server side + enhanced conversions. This is the sixth verified number.

CLAUDE.md · Section 1 identity block
05 / 10
/05 · THE SECOND BRAIN

The Vault is the company.

Everything we know — every client, every SOP, every pattern — lives in a markdown Vault. Version-controlled. AI-readable. It's how Amplio scales.

00 · INBOX

Unsorted capture

Brain-Dump.md is the firehose. raw/ is immutable source material — clip, never edit.

01 · PROJECTS

Has a deadline

Active client deliverables, internal builds, campaigns with a finish line.

02 · AREAS

Ongoing responsibility

Google Ads, Analytics, Sales, Amplio-Internal. Work that never "finishes".

03 · RESOURCES

Reference & SOPs

Brand voice, playbooks, templates, skills, research. The library.

05 · GALAXY

Atomic ideas

One concept per note, max 300 words, ≥1 wikilink. How knowledge compounds.

06 · CLIENTS

Client spaces

One folder per client. Overview, meetings, reports, tracking, correspondence, recommendations.

Amplio-Brain/ · IPARAG structure
06 / 10
/06 · KARPATHY'S THREE LAYERS

Raw → Wiki → Schema.

The Vault is built on a 3-layer architecture inspired by Karpathy's LLM Wiki. Understand this and you understand how the system learns.

LAYER 01

Raw Sources

00-Inbox/raw/

Immutable inputs. Articles, transcripts, PDFs, clippings. Tagged processed: true once compiled.

LAYER 02

The Wiki

05-Galaxy/ + 03-Resources/

Compiled, structured, interlinked. Atomic Galaxy notes + Resources. What Claude reads when answering.

LAYER 03

The Schema

CLAUDE.md + program.md

The rules. How the Vault works, what gets routed where. The brain of the brain.

STEP 01
Capture
STEP 02
Compile
STEP 03
Link
STEP 04
Lint
STEP 05
Enrich
03-Resources/Playbooks/vault-autoresearch-playbook.md
07 / 10
/07 · BIDIRECTIONAL COMMANDS

Talk to the Vault. It talks back.

Say these to Claude and the right thing happens: file created, folder routed, report generated.

SESSION

"Update memory"

Overwrite CURRENT STATE, append to log. Run at 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 full space from template. Updates index. Seeds data-context.

CLIENT

"Client brief: [name]"

Claude reads their _overview + recent notes, returns 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 ICP file. Returns score + tier + rationale.

LEARNING

"Track recommendation"

Adds a row to the client's recommendations-tracker. Closes the loop.

CLAUDE.md · Section 5 bidirectional commands
08 / 10
/08 · DAILY RHYTHM

How a day actually looks.

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.

/MORNING — OPEN THE DAY
  • Walter + Daragh: run "Session brief" in Claude
  • Everyone else: open the Vault Dashboard
  • Check the 09:00 vault-autoresearch run
/THE DASHBOARD · READ ONLY
  • ops.ampliodata.io
  • MRR, client health scores and bands, alerts
  • Open vs actioned recommendations per client
  • Active projects, top 20 pipeline
  • Refreshed 2× daily · 08:15 and 17:15 local
/UPDATES → EMAIL
  • 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 (read only)
/FEEDBACK → THE FORM
  • Wrong number, missing client, stale rec? Teach the Vault
  • forms.gle/Bcs52Zjd7qsyuJuv8 — one atomic signal per submission
  • Correction · Gap · Confusion · Contradiction · Example
/END OF DAY
  • Walter + Daragh: "Update memory" in Claude
  • Everyone else: send the day's update_ emails

Scheduled autoresearch runs in the background: compile, lint, enrich, pattern analysis, health scoring. See scheduled-tasks-reference.md for the full 10 task fleet.

03-Resources/Playbooks/scheduled-tasks-reference.md
09 / 10
/09 · THE RULES & WHAT'S NEXT

Thirteen non-negotiables.

If your work contradicts one of these — stop and ask. These rules are in CLAUDE.md for a reason.

  • 01 Load on demand — read the file, don't recite from memory
  • 02 Vault-first — search before giving advice
  • 03 Verified metrics only — never fabricate proof points
  • 04 Cross-link always — client notes ↔ Galaxy concepts
  • 05 Keep the vault alive — every session leaves it richer
  • 06 Ask before assuming — clarify ambiguous commands
  • 07 No orphans — every note links to a hub
  • 08 update_ emails → vault sync
  • 09 Close the loop — log every recommendation
  • 10 Extract signals — surface requests, objections, churn
  • 11 Test patterns, don't just confirm
  • 12 Every client gets a health score — <70 triggers alert
  • 13 No data-context gaps — API or manual, always present
NEXT — DECK 02: CLIENT LIFECYCLE

Welcome. This is the operating system. Learn it once. Use it every day. Questions → Walter or Daragh. Better questions → Claude.

CLAUDE.md · Section 6 behavior rules
10 / 10