Demo guide — of1

"We make websites that rewrite themselves — for every visitor, in real time, based on what they actually came to find."

What is of1?

The 30-second brief for demoers

Key URLs

Setup checklist

Complete before the booth opens

Download the extension zip from the shared folder and decompress it to your Desktop

Open chrome://extensions — enable Developer mode (top-right toggle)

Click Load unpacked → select the unzipped extension folder → confirm of1 appears in the toolbar

Test the extension on wknd.site before the demo — open the site, click Activate in the extension, wait ~1 minute for indexing, browse several adventure pages, then return to the homepage and press Personalise

Keep wknd.site as your fallback audience website — it works reliably with the extension

Demo script

Full flow — approximately 8–12 minutes

1. Ask the audience for a website — ~1 min

Ask someone in the audience to name any website they know — ideally a brand or company site. wknd.site is a reliable fallback if nothing comes up. Navigate to it and open the of1 side panel.

Say: "Give me any website — a brand you know, a company site. We're going to run of1 on it, live, right now."

Tip: Avoid sites with aggressive bot protection (banks, government). Content-rich sites like retail, media, or B2B SaaS work best.

2. Activate the extension on their site — ~1 min indexing

Open the of1 side panel, click Activate on the domain. The extension starts crawling — reading the site's structure, indexing pages, building a content model. Watch the page count climb. This takes 1–2 minutes.

Say: "I just activated of1 on this site. Right now it's indexing most important pages — understanding the structure, the content, the blocks. It's building a model of what this site knows. Give it a minute."

3. Pivot to arco.coffee — ~3–4 min

While their site indexes, navigate to arco.coffee. This is your showcase — a site built from scratch as a generative website. Walk through it: show the homepage, a product page, the story. Then click Personalize and show the transformation.

Say: "This is arco.coffee — a coffee brand we built as a generative website. Every element is designed to be personalized. Watch what happens when I click Personalize."

Tip: Point to specific mutations in the widget: "This headline was rewritten. This product was swapped. This CTA changed. And here's the reason the AI gave for each one." The reasoning is the reveal.

4. Tease — back to their site — ~30 sec

End the arco demo by teasing that you're about to do the same on the site they gave you. Build anticipation before switching tabs.

Say: "That was a site we built for this. Now let's try the same thing on the site you gave me — one we've never touched."

5. Browse the audience's site — ~2–3 min

Navigate back to the audience's site. Browse deliberately — look at a product, read a page, click into a category. You're building intent signals. Take your time. The extension is reading every click, every scroll, every page you land on.

Say: "I'm just browsing — the extension is watching. Every page I visit, every product I look at, it's building a picture of what I'm here for. It doesn't track me. It just pays attention."

Tip: Browse 3–5 pages with a consistent theme (e.g. all outdoor gear, or all enterprise pricing). The more consistent your browsing, the stronger the intent signal and the more dramatic the personalization.

6. Return to homepage — click Personalize — ~1 min

Navigate back to the homepage. Open the side panel and click Personalize. The page rewrites in real time — headlines shift, content reorders, CTAs change. Use the widget to walk through each mutation.

Say: "Based on what I browsed, here's what of1 decided to change — and here's why it changed each one."

Warning: if nothing changes, the site may not have enough indexable content, or the intent signal was too weak. Refresh, browse 2–3 more pages with a clear theme, then try again. wknd.site is your safe fallback.

7. Navigate the widget — before/after — ~1 min

Use the mutation widget to walk through each change. Toggle between the original and personalized versions. Show the reasoning for each mutation. Let the audience ask questions here — this is the most engaging moment.

Say: "This is the original. This is what of1 changed it to. And this is the AI's reasoning. It's not guessing — it's explaining itself."

8. Capture and share the demo — ~30 sec

Click the Share button in the widget. A QR code appears. The audience can scan it to get their own copy of the demo — a permanent before/after page showing exactly what changed on a real website, live at the event.

Say: "Scan this. You'll get a page showing exactly what changed, with the AI's reasoning for each mutation. Something to take away from today."

FAQ

Questions you'll get at the booth

Is this tracking me?

How is this different from A/B testing?

How long does it take to implement?

Does it work on any website?

What AI model does it use?

What does "co-innovate" mean?

The close

How to end every demo conversation

Finish strong

"arco.coffee is what a generative website looks like when it's built right. We could build the same thing for you — or co-innovate with your team to get there. That's the conversation we want to have."