# Four sheets, four audiences, one stack — the Lisbon summit handouts

> The September 2026 startup-summit handouts: the same capabilities framed for founders, startups, investors and corporate buyers, each as a page and as the PDF that was handed out — with a 'what exists today' column that is unflattering on purpose.

*Source: <https://sgit.ai/summit/index.html> · site v0.2.80 · this file is generated from the same content as the page, so the two cannot drift. Every page on this site has a `.md` twin; internal links below point at them.*

---

[Home](../index.md) / Summit sheets

# Four sheets, four audiences, one stack

The handouts from the Lisbon startup summit, September 2026. The same capabilities, framed four ways — because a founder, a startup, an investor and a corporate buyer are reading for four different reasons. Each sheet is here as a page *and* as the PDF that was handed out.

**What makes these worth publishing rather than filing.** Every row carries a **what exists today** column, and that column is unflattering on purpose: *“no payment link”*, *“not yet packaged as its own product”*, *“research design; implementation not claimed”*, *“write-only intake built, never sold”*. A capability sheet that cannot say which rows are not finished is a brochure.

|  | Sheet |  | Handout |
|---|---|---|---|
| 01 | **[Founders](founders.md)** Open source technology that works today | 7 rows | [PDF ↓](pdf/sgit-ai__01-founders.pdf) |
| 02 | **[Startups](startups.md)** Let’s build together | 9 rows | [PDF ↓](pdf/sgit-ai__02-startups.pdf) |
| 03 | **[Investors](investors.md)** How does your firm share data with its portfolio? | 6 rows | [PDF ↓](pdf/sgit-ai__03-investors.pdf) |
| 04 | **[Corporate users](corporate.md)** Services available now | 8 rows | [PDF ↓](pdf/sgit-ai__04-corporate.pdf) |

## Why four, and not one

The rows underneath are largely the same. What changes is the question each reader arrives with — *can I build a company on this*, *can I build on top of it*, *how does my firm share data and what are my portfolio's agents doing*, *how do I govern the agents already running*. Splitting at the front door rather than compromising inside one document is the same choice [the interim CISO pack](../demos/vaults/interim-ciso-pack/index.md) makes, and the same one [three surfaces](../docs/surfaces.md) argues for.

## One number in the PDFs is already out of date

The printed sheets say **“26 public vaults”**. At the time of printing that was right; [the table](../demos/vaults/index.md) now lists **29**, because three were published in the week the sheets were being handed out. The pages here do not repeat the number, and link to the live table instead — which is the general fix: **a printed artefact should point at a computed one for anything that moves.**

Proof 02 · 14 September 2026 · fact set: brief v0.33.70. Code: permissive software licence. Documents: CC BY 4.0. [The network](../network/index.md) · [Published vaults](../demos/vaults/index.md)


---

*[Site index for agents](../llms.txt) · [HTML version](https://sgit.ai/summit/index.html)*