How do you turn a monthly investor letter into AI-friendly content?
Break it into one HTML page per theme. Each thesis gets its own page: a title phrased as a question, a complete answer in the opening paragraph, figures in sourced tables, an FAQ, and structured data — signed by the portfolio manager, with visible dates. The PDF still goes to clients; the HTML version exists for AI crawlers. It adds no writing work, because the content already exists.
What are the five steps in the conversion?
| STEP | ACTION | OUTCOME |
|---|---|---|
| 1 · Take inventory | List the theses, data, and views in the letter | A map of the questions the letter answers |
| 2 · Break it up | One page per thesis, H1 as a question, answer in 40 to 80 words | Self-contained, citable pages |
| 3 · Structure it | H2 and H3, HTML tables with sources, FAQ, JSON-LD | Machine-readable content |
| 4 · Sign and date it | Named author with credentials, publication and update dates, internal links | E-E-A-T signals |
| 5 · Publish and index | Sitemap, llms.txt, IndexNow, Bing, and Google | AI crawlers reach the pages within days |
Source: steps 2 and 3 of the ReBo method, 2026.
Step 1: the inventory decides everything else
Before writing a line, read the letter looking for three things: the theses it argues, the data it presents with a figure and a source, and the implicit question each passage answers. That map sets how many pages the letter yields, not the other way around. A letter covering rates, currency, and equities yields three pages. One that goes deep on a single theme yields one denser page.
Step 2: why break it up rather than publish it whole
This step draws the most pushback and delivers the most results. A letter covers several subjects because it is written to be read start to finish by someone who is already a client. AI cites pages that answer one specific question. A page covering three subjects answers three questions partially. Three thematic pages each answer one in full.
You also build an index page for each edition. It preserves the full read for the human and works as an internal hub pointing to the thematic pages.
Steps 3 and 4: what gets added and what gets preserved
Nothing in the original gets rewritten in substance. You add structure around it: a heading hierarchy, an executive summary up top, tables with headers and units where loose figures sat before, an FAQ block at the end, and JSON-LD markup. You preserve exactly the numbers, the dates, the named entities, and the primary sources — those are what make a passage citable.
Signing the page is the cheapest step and the one teams skip most often. A named author with a title and a bio page, plus visible publication and update dates, turns anonymous text into a verifiable source — one of the E-E-A-T signals that weigh on selection.
What are the most common mistakes in the conversion?
Four mistakes keep coming up: publishing the letter as one page, posting a summary that links to the PDF, leaving charts as images, and republishing every month at the same URL. Each one wipes out most of the effort.
| MISTAKE | WHY IT UNDOES THE WORK |
|---|---|
| Publishing the whole letter as a single page | Answers several questions partially instead of one in full |
| Publishing only a summary and linking to the PDF | A summary lacks the factual density needed to earn a citation |
| Leaving charts as images, with no underlying table | The core data of the analysis stays invisible to machines |
| Republishing every month at the same URL | Erases the history and each edition's canonical URL, the address a citation points to |
Source: ReBo conversion diagnostics, 2026.
What about sensitive or regulated content?
It stays out, and drawing that line is easier than it sounds, because what builds authority with AI is analysis, not advice. The public version carries the market theses, the macro view, the scenarios, and the firm's methodology. It leaves out recommendations on specific securities, performance figures without the required disclaimers, investor data, and return projections.
Build the workflow around review. Every page clears internal sign-off before it goes live, inside a window agreed at the start of the project, instead of going over to compliance piece by piece after the fact.
What changes for the asset manager's team?
Almost nothing, and that is the point. The team writes the letter the way it always has, in the same format and on the same schedule. ReBo handles the splitting, the structuring, and the publishing inside the four-stage pipeline, and the portfolio manager signs off before anything goes live.
The back catalog usually pays back fastest, because past editions already exist and already cleared review. Converting them in one pass builds a library of interlinked pages covering the same themes over time — the signal of consistent coverage that retrieval systems reward. Month by month, the citation rate shows what it returns. To get started, book a call.
Keep reading
The problem this conversion solves is laid out in the pillar article on why AI can't read PDFs. For what a page needs in order to win selection, see how ChatGPT chooses the sources it cites. For the industry view, see AI Visibility for asset managers. For the concepts, see what AI Visibility is and what GEO is.
Frequently asked questions
Should the whole letter become a single page?
No, and that is the most common mistake. A letter covers several themes, and AI cites pages that answer one specific question. Publish one self-contained page per thesis, plus an index page for the edition that preserves the letter as a continuous read.
Does publishing the letter in HTML cannibalize the PDF we send clients?
No. The PDF stays the formal delivery to the client and the compliance record. The HTML pages exist for AI crawlers and search engines. Different audiences, and the public version extends the reach of work you have already paid for.
What about sensitive or regulated content in the letter?
It stays out. The public version carries the market analysis and the broad theses, which is what builds authority, and leaves out specific recommendations, performance figures without the required disclaimers, investor data, and anything restricted under CVM or ANBIMA rules.
How much work is this every month?
For the asset manager's team, almost none: the letter already exists. Splitting, structuring, and publishing are steps 2 and 3 of the ReBo method, and the portfolio manager only signs off on the pages before they go live.
Is it worth converting the old letters?
Yes, and it usually pays back fastest of anything in the project, because the archive is already written and already approved. Converting past editions in one pass builds a library of interlinked pages covering the same themes over time, which is exactly the signal of consistent coverage that retrieval systems reward.
Can I always publish at the same URL and just update the content?
Not for monthly editions. Each edition needs its own permanent URL, because that address is what a citation points to. Republishing at the same URL erases the history and dismantles the archive you are trying to build.