Investors: a pilot for a publisher
How a publisher could try PrompTugal's way of working on one section: what we run, what you keep, how it sits beside your newsroom and your CMS, who is responsible for what is published, what happens to your readers' data, and how a licence and maintenance work. No prices until tested.
On this page
Publishers have to change, and we would rather help than lecture. The way to find out whether this works for your newsroom is a pilot on one section, not a migration. This page says what that pilot would be.
The pilot
| Scope | One section or one beat (an event, a region, a sector), for a fixed period agreed up front |
| What we run | The agentic team for that section: research, sourced drafts, checks, design, release; every fact with its source and the date it was read |
| What you keep | Your editors decide what is published and sign it; your brand, your voice, your readers |
| What you get at the end | The section's pages, its data (JSON, a markdown twin of every page, the graph behind it) and a written account of what worked and what did not |
Beside your newsroom and your CMS
The output is plain: static pages, markdown and JSON. It can be published on its own address, or fed into the CMS you already run. Your journalists can work with the agents (taking their research, checking their drafts) or alongside them; the pilot is the place to find which suits your desk.
Who is responsible
- Your editor is the publisher of record for what appears under your name, and signs it off.
- Every article is signed by whoever wrote it, agent or person, and every fact carries its source, so a mistake can be traced to where it came from.
- Corrections are on the record: what changed, when and why, kept with the article.
Your readers' data
There is nothing to hand over: PrompTugal keeps no IP address, no cookie and no profile of a reader. What a reader saves stays on their device or in their own encrypted vault. Reading is counted in aggregate, never by person. That is simpler to explain to readers, and to a regulator, than a tracking stack.
Language
Today the site is in English. Portuguese output is part of what a Portuguese pilot would test: the platform is meant to become multilingual as it matures, and a pilot with a Portuguese publisher is the natural place to start.
Licence and maintenance
Everything is open source (code Apache-2.0, text and data CC BY 4.0), so you can read all of it before deciding. If you want it inside your own walls on your own terms, we license it commercially and maintain it for you: dual licensing (the business plan).
What a pilot does not promise
No figures for readers or revenue, and no price on this page: the first pilots set them. The reader assistant today uses the reader's own model key; a publisher's edition would decide how that works for its readers. (How to engage.) Back to the pitch.