The event you opened it from: the programme, the roster, the tiers, the money, the messages. It cannot see your other events or any other organiser’s, and attendees never get to talk to it.

Can it do anything I cannot do myself?

No, by design. Every change goes through the same code as the button in the dashboard, with the same permissions. A co-host’s assistant can do what a co-host can do, and no more. Refunds and deleting an event are not on its list at all.

What does the draft from a link need?

A link to a page about the event, last year’s website will do, or a written brief. It fills in what it can read, the title, dates, venue, tiers, programme and speakers, and leaves the rest blank rather than guessing. You check the draft before anything is published.

Can we switch it off?

Yes. The assistant is a line on your plan, so if you would rather not have it, we switch it off for your organisation. It only ever answers people who can already edit the event, and it changes nothing without an approval.

Does it put attendee data into the chat?

Never. Ask for an export and you get a download link to a file, the same governed export the dashboard makes, recorded the same way. Names appear in an answer; emails and phone numbers do not.

Support

AI assistant

An event assistant that acts on your event. Nothing changes until you approve it.

Paste last year’s website and get a draft event. Then ask it to move a session, email the people who have not checked in, or export the roster. Every change is a card you approve first, run through the same code as the dashboard.

From a link to a live event ↓

An assistant with the keys, and one rule about using them.

Questions it answers

The programme, the roster, the tiers, the money, the delivery log. On the spot.

Changes it proposes

Each one a card that does nothing until you approve it.

Event at a time

The one you opened it from. Not your other events, never anyone else’s.

Changes without you

Approve or decline. Both are recorded, with who and when.

From a link to a live event

Draft the event from last year’s website, then run it by asking.

A draft you check. A cover you choose. A change you approve. The same event, from the first minute to the day.

From a link to a live event

Draft the event from last year’s website, then run it by asking.

A draft you check. A cover you choose. A change you approve. The same event, from the first minute to the day.

Step 1 of 4

Paste last year’s website and get a draft event.

A link or a written brief. It reads the title, the dates, the venue, the tiers, the programme and the speakers, and lays them into a draft for you to check. What the page did not say stays blank rather than guessed.

Draft from a link

founderssummit.nl/2025

Read from the page. Blank where the page said nothing.

TitleAmsterdam Founders Summit
Dates22 to 23 April
VenueBeurs van Berlage
TiersEarly bird, Standard, VIP
Programme18 sessions, 2 rooms
Speakers12 names, 9 photos

Left blankCapacity, prices

Check the draft

Start blank

Things you can ask

Ask in plain words. It answers from your programme, your roster and your tiers.

Say it the way you would say it to a colleague. A question gets an answer. A change gets a card. An export gets a file. The right-hand line is what actually happens.

“Who is speaking on day two?”

Answer

Answers from the programme

“How many VIP tickets are left?”

Answer

Reads the live count

“Did jane@ get the doors-open email?”

Answer

Reads the delivery log

“Who from this list has not registered?”

Answer

Reconciles it against the roster

“Move the keynote to 10:00”

Approval card

A card, waits for your yes

“Add a coffee break after the panel”

Approval card

A new session, for approval

“Invite these forty people”

Approval card

A batch you can edit first

“Export the roster”

File

A file, never data in the chat

The rule

Every change is a card: what will happen, then Approve or Decline.

A broadcast, a moved session, a new tier, a cancelled ticket. The card names the people, the times, the money, before anything runs. Type something else instead and the card is dropped, not sent. Both answers are written to the event’s log.

Needs your approval

Email 38 people who have not checked in

ToTicket holders, not checked in
ChannelsEmail and push
SubjectDoors are open until 10:30
SendsOnly after Approve

Approve

Decline

Type something else instead and the card is dropped, not sent.

What it sees

It sees the event you opened it from, and nothing else.

The event is bound on the server, not in the prompt, so it cannot be talked into another one. A co-host’s assistant can do what a co-host can do. Attendees never get to talk to it.

Scope

Amsterdam Founders Summit

Opened from this event. Bound to it on the server, not by the prompt.

This event’s programme, roster, tiers, money, messages
Your other events
Any other organiser’s event
Attendees, asking it anything

A co-host’s assistantWhat a co-host can do, no more

Exports

Exports leave as a file. Personal data never appears in the chat.

Ask for the roster and you get a link and a row count. The file is the same governed export the Attendees tab makes, filtered the way you asked, recorded the same way.

Export everyone on the VIP tier

CSV

attendees-vip.csv

27 rows · name, email, tier, checked in

Download

In the chatA link and a count
In the fileThe rows, the same export as the tab
RecordedWho, when, which filter

The usual way

What changes when the assistant can act, not just answer.

Setting upRetyping last year’s website into a formA draft from the link, checked by you

The coverA designer, a week, a licenceMade from the brief, or your own upload

A question on the dayOpen three tabs and countAsk it. It reads the live event

A change on the dayEdit, then remember to tell everyoneA card, a yes, the notice goes out

A chat box that actsTrust it, or do not use itEvery write waits for your approval

Who did that?Nobody knowsThe log says who approved it, and when

The left column is your own experience of a form, a designer and three open tabs. Nobody else’s product is named, on purpose.

On the day

The same assistant on your phone, standing in the room.

Organiser mode carries the conversation. Which session is next in the Shaffyzaal? Who from Atlas has arrived? Push the panel back fifteen minutes: proposed, approved, done, and the schedule-change notice goes out.

The numbers

Fifty-five things it can do, and a record of every one it did.

Twenty-four answers on the spot. Thirty-one changes that wait for a yes. Every approval and every decline is a row in the event’s log.

What it answers, and what it asks first.

A question is answered. A change is a card. The registry decides which, not the model.

things it can do, every one through the same code as the dashboard

Questions it answers on the spot24
Changes it proposes and waits for31

Approved, declined, recorded.

One sample week, one event.

declined, and recorded the same way

Nothing ran without one of the two.

What one event asked it in a week.

Questions by what they were about.

The programme

The roster

Messages

The money

The log, row by row.

Every change it made, with who said yes. The same audit log the dashboard writes.

Mon 09:14Delay 2 sessions by 15 minapproved · you
Mon 09:20Broadcast to 38 not checked inapproved · you
Tue 16:02Create tier ‘Late’ at €690approved · Lena
Wed 11:40Cancel Marc Deleon’s ticketdeclined · you

The shortcut is real. The keys are still yours.

An assistant that can act on a live event needs one rule more than it needs another feature. Ours is that every write is proposed first, run through the same code as the dashboard, and recorded with who approved it.

Straight answers

Switching it off, attendee data, what it can see, and what it does not do yet.

No. Anything that writes to your event, a schedule change, an email, an invitation, a removal, arrives as a card describing exactly what will happen, and happens only when you approve it. Questions it answers immediately.

Also in the product

Check-in, the event page and the app run on the same ticket list.

Schedule

The programme, current, in every pocket in the room.

See schedule

Communications

Every message to the room, from the list the door checks.

See communications

Ticketing & payments

You are the merchant. The money goes to you as you sell.

See ticketing & payments

Get started

An event assistant that acts on your event. Nothing changes until you approve it.

An assistant with the keys, and one rule about using them.

Draft the event from last year’s website, then run it by asking.

Draft the event from last year’s website, then run it by asking.

Paste last year’s website and get a draft event.

Ask in plain words. It answers from your programme, your roster and your tiers.

Every change is a card: what will happen, then Approve or Decline.

It sees the event you opened it from, and nothing else.

Exports leave as a file. Personal data never appears in the chat.

What changes when the assistant can act, not just answer.

The same assistant on your phone, standing in the room.

Fifty-five things it can do, and a record of every one it did.

What it answers, and what it asks first.

Approved, declined, recorded.

What one event asked it in a week.

The log, row by row.

The shortcut is real. The keys are still yours.

Switching it off, attendee data, what it can see, and what it does not do yet.

Check-in, the event page and the app run on the same ticket list.

The programme, current, in every pocket in the room.

Every message to the room, from the list the door checks.

You are the merchant. The money goes to you as you sell.

Ask for the change. Approve it. Done.