How to build yourself a speaker page like this one

Eight steps

1. 1

   Realise you do not have to write anything from scratch

   This is the most important step and it costs nothing. It is also where I stalled longest — I assumed I had to sit down and formulate my positioning.

   You do not. You already formulated it. It is just scattered across posts, calls and decks from the past few years.

   AI is not the writer here. It is the archaeologist.

2. 2

   Collect the raw material into one folder

   Everything you have already written or said: social posts, old decks, your CV, recordings of talks, call and webinar transcripts, email threads with organisers.

   Do not sort it and do not clean it up. Sorting is the model's job, not yours.

   My input was: 151 Facebook posts (official export: Settings → Your information → Download your information), transcripts of 429 hours of streams and sessions, an old deck, and a CV.

   Do not start with "I should organise all of this first." That is the same excuse that is why the page still does not exist.

3. 3

   Mine your positioning instead of inventing it

   The difference between "write about me" and "extract it from my material" is the difference between generic copy and yours.

   The first gives you "a dynamic leader with extensive experience." The second gives you what you actually repeat year after year — and what you repeat year after year is your positioning.

   Prompt for this stepCopy prompt

   Here is my material from the past few years: posts, transcripts, decks. Do not write anything new and do not add your own ideas. Extract exactly three things:
   1) the claims I repeat most often;
   2) where my position diverges from the conventional view in my field;
   3) the specific numbers and examples I reach for when I explain my work.
   For every item, quote the source passage you took it from.

   Insist on a source quote for every claim. Without that the model will invent an elegant position you have never held, and you will discover this on stage.

4. 4

   Extract your voice as a separate file

   This is the step people skip, and it is exactly why the pages all come out identical.

   I built a profile of my own written voice from 151 posts: median paragraph length (128 characters), how I break thoughts across lines, how many emoji I use (0.4 per post — effectively none).

   That file then goes into every subsequent request. Without it the model writes in press-release register and the page ends up looking like a thousand others.

   Prompt for this stepCopy prompt

   Analyse my writing and build a profile of my written voice. Compute it over the corpus rather than estimating: median paragraph and sentence length, typical openings, what I use to separate sections, average emoji per piece, words I use constantly and words I never use. Separately, list 10 real example phrases. Save this as a file I can attach to future requests.

5. 5

   Decide what the page must make someone do

   One action. Not three.

   Mine is "Request a talk" — a form with exactly three required fields: name, email, organisation. Everything else is optional.

   The logic is simple: an organiser still working through a shortlist of ten does not know the date, the budget or the city yet. Eight required fields is a closed tab. Better to get the enquiry on three fields and ask for the rest by email.

   Making "event date" and "budget" required filters out precisely the people who are still deciding — the ones you could still win.

6. 6

   Assemble the page

   Here you either hand this whole instruction to a tool, or you learn to do it yourself. See the block below.

   Either way the build order is the same: structure first (what follows what, and why), then the copy for each block, and only at the end how it looks.

   Build a page, not a PDF. A link can be updated after every talk; a file sitting in someone's inbox since March can never be updated.

   Step 6 forks in two

   If you already know your way around Claude Code, you do not need the rest of this.

   Open it, give it the link to this page and say: "build me the same thing, following these instructions." It will. That is genuinely how this works — the page is written so it can be handed to a machine.

   ---

   If you would rather understand it yourself, including how to get the whole thing deployed on a host.

   That is the course "AI agents for company founders": 6 lessons on taking an AI product to production instead of leaving it as a demo on your laptop. A speaker page is the simplest possible example of it.

   See the course9 999 ₴ · One course, lifetime access.

   «Робота з АІ-агентами для засновників компаній»

7. 7

   Put up evidence, not adjectives

   "Experienced speaker" carries zero information. A recording of a talk is evidence.

   The minimum: recordings (even if you only have three), topics with a concrete promise, testimonials with names, and — above all — pricing in the open.

   On pricing specifically. Most people write "fee available on request." That costs you enquiries: an organiser with a 30k budget simply will not write, to avoid embarrassment, and you will never learn he existed. A range, with an explanation of what moves you from one end to the other, beats any amount of mystery.

8. 8

   Do the organiser's job for them

   A separate page with materials: bios at three lengths (50, 100, 200 words), high-resolution photos, technical requirements, topics with descriptions.

   This is not politeness. It saves one email round-trip per invitation: the organiser needs a 50-word bio for the programme, and if it is not there he writes to you, you answer a day later, and the event slips.