About - Ygor Fonseca
Founder & Systems Lead at Leanboat.
Ygor is co-founder and Systems Lead at Leanboat. He has been writing production software for fifteen years across the same brand portfolio Luis has been growing — BusBuster (co-founder), TheNextGuide, NextBreakout, and the rest of the Leanboat-operated brands.
For Leanboat, he builds and operates Studio, the AI-native system underneath AI Social Selling: a brand file per account that codifies how each seller actually speaks, agent workflows that run the research, production and publishing, approval gates that keep a human yes on everything that goes out in someone's name, and kill switches that shut a workflow down the moment it starts misbehaving.
The work is engineering, not slideware. Every client engagement runs on top of a system he can rebuild from source.
Articles by Ygor Fonseca
June 29, 2026
Why your marketing keeps starting from zero — and the discipline that makes it compound
Two brands spend the same for years; one’s marketing compounds, the other resets every campaign. The difference is entity propagation — define each thing your brand is known for once, and carry that exact definition across every surface.
June 23, 2026
Your About page isn’t copy anymore. It’s training data.
Type your company into ChatGPT and a model hands your buyer a description you never wrote. An llms.txt won’t fix it — your ordinary pages are the training data. State what you are in checkable terms.
June 18, 2026
What you own when an AI engagement ends — and why it's the one part that can't be rebuilt.
The fourth part of a brand-install is the memory layer — what a firm learns about your brand, kept with the reason. The methods transfer between brands; the memory never does, which is why it’s the one part that’s truly yours when the engagement ends.
June 15, 2026
How an AI content engine actually learns — and when to trust the numbers it shows you
The Learn step of an AI content engine: when to measure (a fast beat for anomalies, a slow beat for decisions, cadenced to your volume), what to measure (signals that survive small samples), and how the loop reallocates toward what won. A number you never act on is a scoreboard, not a feedback loop.
June 14, 2026
One check isn't a gate. What it takes to ship AI content safely at volume.
Adding 'an AI review step' isn't safety — a checker that fails for the same reasons as the writer shares its blind spots. How defense in depth (independent layers) and risk-tiering let an AI content engine ship fast without shipping mistakes.
June 12, 2026
Why an honest AI-native install starts with data archaeology, not agents
An AI-native install can only act on the customer it can see — and on day one that customer is scattered across five tools that disagree. Why the real first phase of the work is data archaeology, not agents.
June 9, 2026
How do you let AI agents act on your accounts and stay accountable for what they do? The kill switch.
The autonomous-agent wave sells the removal of the human. But a brand letting AI act on its accounts is buying outcomes it can stand behind — and that takes an accountability layer on day one: scoped access, an audit log, approval gates, and a kill switch the brand holds.
June 5, 2026
What actually gets a brand cited by AI search — and why the dashboards can’t deliver it
Three unrelated sources settled in eleven days what gets a brand cited by AI search. We sampled nine GEO/AEO vendors to see what they sell instead — receipts included.
June 2, 2026
The instructions library is the agency's growing methodology — not a deck, not a senior person's head
Most agencies keep their method in a senior person's head or a slide deck — neither compounds. The third option is a library of small instructions files that run: capture a task once, generalize it, reuse it across brands. Garry Tan runs his own work this way; here's the same shape moved into a services firm, and why the growing library is the asset.
May 28, 2026
How content actually compounds for a small team — and why most agencies still describe it as a calendar
Two five-layer frames apply to content. Blomfield's loop is how the work gets smarter; Birkett's surface — Strategy, Enablement, Execution, Feedback, Repurposing — is what a small team has to staff. Here's the operating model that compounds, and the layer most teams under-staff.
May 26, 2026
How an AI agency should describe what it builds you — and why most still can’t.
AI-native services delivery has had a stable engineering vocabulary in public for more than a year. Most services firms still describe AI as a capability bolted onto existing services — and the bolt-on framing without that vocabulary underneath is one of the strongest audit signals a buyer has.
May 22, 2026
An AI-native agency ships a brand-install, not a team. Everything else is org chart.
What does an AI-native services firm actually hand a client? Not a team — a brand-install: a folder of plain text the AI reads on every task. Five components (working hypothesis, locked rules, instructions index, memory index, kill switch), one weekly self-improvement loop, and the moat that lives in the catalog. Series B (Codified Engagement), post 1 of 4.
May 21, 2026
From framework to install: wiring a self-improving content loop into your team's files
The companion install guide to the self-improving content engine: Blomfield's five layers as plain-text files in a folder, the week-by-week install order across the first month, the routing that loads the right slice per task, and the four failure modes that break it.
May 14, 2026
A pull-request culture for knowledge. The discipline AI-native marketing teams are converging on.
At Speero Circus 2026, three independent talks landed on the same shape: AI generates knowledge fast, but unreviewed AI output becomes organizational truth. The discipline AI-native marketing teams are converging on is a pull-request culture for knowledge — labeled reviewer, pass/fail signal, back-edit before merge.
May 10, 2026
An AI-native agency installs a nervous system, not a deliverable
Garry Tan calls it the difference between a filing cabinet and a nervous system. The same architecture works at brand scale — and most brands can't install it alone. The real test of an AI-native engagement: what's still running in the brand's repo six months after the agency stops billing.
May 8, 2026
Every AI-native services firm has a name on its method. The naming is the moat.
Three AI-native services firms in three different verticals are publishing the same artifact in 2026 — a named operating method, in writing, on the public site. The naming is not a brand-voice flourish. It shortens the sales cycle, pre-filters operator hires, justifies productized pricing, and makes the firm defensible against agencies that cannot be lined up on a comparison page.
May 7, 2026
If your AI marketing feels like a chat window, the function was never written down.
Most 'AI for marketing' rollouts in 2026 feel like working for a chat window — the operator types, edits, ships, repeats, and the work never compounds. The fix is not a better model. It is writing the function down well enough that an agent can run it. Two installs from inside our own work, plus the same shape applied to B2B SaaS.
May 1, 2026
Hierarchy was never the goal. It was the workaround.
Two thousand years from the Roman contubernium to your current org chart, the constraint hasn't moved. Block just published the first public-company manifesto for what comes after — and the implication for everyone smaller than Block matters more than the headline did.
April 29, 2026
Pick a service. There's already an AI-native version of it.
In one quarter, six AI-native services companies hit valuations totalling north of $20 billion. The architectural pattern underneath all six is the same — and marketing is the lagging vertical.
April 27, 2026
The 15-person AI-native services company. Its name is Every.
Every employs 15 people, ships five products, runs a daily newsletter and a $1M consulting business, and writes 100% of their code with AI. The architecture is documented. Here is what 15 people now ship.