Home / Articles / A presentation for every project: how the agentic workflow behind a talk built in a day can turn each project from a build day into a visual, dynamic presentation, and a service

A presentation for every project: how the agentic workflow behind a talk built in a day can turn each project from a build day into a visual, dynamic presentation, and a service

By Dinis Cruz · 2026-10-31 · article v1.0.0 · newsroom v0.14.27 · presentationsagentic-workflowseventsinfographicsvillagersalgarvearticle

Abstract: After the Vibathon in Faro, someone in the event's group chat suggested that it would be nice to have a quick pitch deck or presentation for each project people worked on during the day. I agree, and we already have every piece needed to do it. Two days earlier I gave a talk at hack::soho whose presentation was built in a day by a team of agents and one editor, from an empty repository at sixteen minutes past midnight to the stage at seven that evening, with its own site and dynamic infographics. The same workflow can take what a team built on a build day, the app, its notes, a voice memo of the pitch, and turn it into a presentation of its own: a site that tells the project's story, explains it with infographics, embeds the app, and sources every number. This afternoon, ChatGPT made two infographics for me from the six articles we wrote today about Algarve Evolution, and they show how far even one prompt goes. With an agent team, a repository and a review step, every project from a build day could leave with a presentation by the show and tell, or by the next morning. It is a good way to show the power of agentic workflows, because the presentation is itself one, and it is also a service: one that providers in a region could offer, priced per project, finite, as the villager services we have described. The book we are writing about the talk already explains much of how it works, and this connects to how we recommend running these days: every participant ships something someone else can use, and a presentation is how they show it.

In short

• A participant asked for a quick presentation for each project from the build day. I agree.
• We already have every piece. A talk of mine was built in a day by an agent team, with its own site.
• The same workflow can present each project: its story, dynamic infographics, the app itself, every number sourced.
• Even one prompt goes far. ChatGPT's two infographics of today's articles show it.
• It shows the power of agentic workflows, because the presentation is one.
• It is a service that providers can offer per project, finite and handed over.
• It fits how we recommend running build days: ship something, then show it.

The suggestion

After the Vibathon Algarve 2026, someone in the event's group chat suggested that it would be nice to have a quick pitch deck, or presentation, for each of the projects people worked on during the day. I agreed, and replied with a link to the presentation of my own talk: "we could do one of those presentations (with dynamic infographics) for each of those projects and MVPs delivered during the event".

We already have every piece

Two days earlier, on 29 October, I gave the ultimate insider at hack::soho. Its presentation was built in a day: from an empty repository at 00:16 to the stage at 19:00, by nine agents and one editor, with its own site, its own navigation and infographics that move. Overnight, two more agent teams worked on the book of the talk, with a companion for reviewers, and that book, which we are still writing, already explains much of how the workflow runs.

Everything a project presentation needs is there: a repository to hold the material, a team of agents with roles, a researcher that checks every claim, a designer that draws infographics, a writer, a review step, and a site per presentation.

What one prompt already does

This afternoon I asked ChatGPT for infographics of the six articles we wrote today about Algarve Evolution, and it made the two in this article: one shows the six as a connected ecosystem, the other is a reading map with each article's address. They are not perfect, a word is misspelt in the small print and the people are illustrations, but they are a good picture of what even one prompt can do with good material. A project from a build day is good material.

A presentation for every project

The workflow, applied to a build day:

1. The project: what a team built on the day, the app, its notes, and a short voice memo of the pitch.
2. A repository that holds the app and its record together, public, with the team's permission.
3. An agent team: a researcher that checks what the project claims, a designer that draws the infographics, a writer that drafts the story, and a review before anything is shown.
4. The presentation: a site of its own that tells the story, explains it with dynamic infographics, embeds the app, and sources every number.
5. Shared: a link for the show and tell, an article for the newsroom, an infographic to print.

Done during the afternoon, every project can be presented at the show and tell; done overnight, every team wakes up to a presentation of its own.

It shows the power of agentic workflows

A good demonstration of agentic workflows is not a talk about them. It is a presentation, made by agents, of what the participants themselves built that day. The participants see their own work explained back to them, and they see, in the result, how the workflow did it.

And it is a service

There is a business here too. Making a presentation of someone's project, a site, infographics, a short article, is a service that providers in a region can offer, priced per project, finite and handed over, like the villager services we have described. Founders need to explain what they built to customers, investors and partners, and most never have the time to.

How we recommend running build days

It fits how we recommend running these days, which I wrote up in running an AI build event: everyone ships something someone else can use. A presentation is how they show it, and how it reaches the people who were not in the room.

What this does not claim

• It is a proposal. No project from the day has a presentation yet.
• The infographics were made by ChatGPT, at my request, from our articles; they are illustrations, not photographs, and have small errors.
• The talk's timing is from its own records, as the case study sets out.
• The participant who suggested this is not named; the group chat is private.
• My interest: I would like to offer this, and I build the tools it uses.

Where this comes from

• My voice memo of 31 October 2026, word for word in admin/notes/2026-10-31__project-presentations/memo-01.md in this site's repository, with my message in the group chat quoted from it.
• The two infographics, made by ChatGPT for me on 31 October 2026 from this newsroom's articles.
• Related: a talk built in a day, the book of the talk and its companion, running an AI build event, villager services for explorer coders, Vibathon Algarve 2026.

Peer review Not reviewed yet. Review it

Want the next issue by email. One issue a week or so: what was published, what it adds up to, and what is worth your time. Subscribe to the SGit Newsroom →

← All articles