One build, four moments
Every event has a date, and everything else counts backwards from it. The invitations need a link. The link needs a page. The page needs a form that works, a programme that updates, and a place for the photos on the day after. We build it as your production arm, the same one that works for PR agencies, branding studios and consultants and communities; the shared terms are on the partners page.
The event page is one Launch Page 72h, planned so that it carries the whole life of the event without a rebuild.
| Moment | What the page does | When it changes |
|---|---|---|
| Before | Registration form, programme, speakers, venue, the reason to come. Copy in Spanish and English. Confirmation email to the guest, the registration routed to the client's CRM or inbox | Live before the invitations go out |
| Door | The registration list is the door list: exported from the client's CRM or the form back-end, filtered by status | The morning of the event |
| Live | The live moment: the stream link, the running order, the hashtag, the thing happening now | Swapped in on the day |
| After | Photos, the recording, the talks, a form for the next edition. The page assistants and search engines find when someone asks about the event later | The day after |
One page, one domain, one set of analytics. Two rounds of revisions before launch, and small text and image changes in the first two weeks after it are on us, which is where the day-after update usually lands.
Registration and check-in mechanics
What is inside the fixed fee: the form with the fields the event needs, a confirmation email, routing to the client's CRM or inbox, a thank-you page, and analytics events so you can tell the client how many people registered from which invitation. The door list is the same data, exported and filtered.
What moves the event to a Campaign Microsite, 1 to 2 weeks: anything the guest does beyond registering. A QR ticket in the confirmation email that the door scans. A capacity limit with a waiting list. Session selection. A quiz or a personal-result generator that runs on the night and captures data. A promo game for the audience. Those are mechanics, wired to the client's CRM and email, and they need the extra week to be designed and tested.
We tell you which format the event needs on the day-0 call, before you promise a date to anyone.
Timeline backwards from the event date
Count from the day the invitations go out, not from the event itself.
| When | What | Who |
|---|---|---|
| Invitations minus 6 working days | Day 0, 30 min: you tell us the event, the date and the format. We confirm the model and the partner price | You and us |
| Invitations minus 5 working days | Day 1, 45 min: brief with the client, one checklist. Programme, speakers, venue, visual identity, the form fields. Materials in, clock starts | You lead, we ask the technical questions |
| Invitations minus 4 to 2 days | The page direction on day one, build and forms on day two, revisions and QA on day three | Us; you approve |
| Invitations minus 1 day | Live on the client's domain. The link exists before anyone needs it | Us |
| Event day | Live moment swapped in | Us, on your cue |
| Event plus 1 day | Post-event update with photos and recording | Us |
If the invitations are going out sooner than that, tell us anyway; the clock runs from when the materials are in, and a producer who has the programme and the identity ready can start on day 1.
Models that fit an event agency
| Model | How the brand sees it | Money | When it fits |
|---|---|---|---|
| White-label (our pick for events) | Your service, your producer, your invoice. We are the invisible digital team behind the event | Your 20–30% margin on our partner price | Most events. The client already has one supplier for the event; they do not need a second one for the page |
| Referral | You introduce us. The contract is between lobod.rocks and the brand; you stay in the loop as much as you want | 15% of the first contract, 10% of renewals | Corporate clients with procurement, or when the page is the client's project and the event is yours |
| Co-branded | One proposal, two suppliers, one team | Each invoices its part; the brand gets 10% off the joint package | A launch event with a campaign around it, where the microsite and the event share one story |
Partner prices are fixed per package. EU invoicing, ex-VAT. No exclusivity, and never two agencies for the same brand: the first one that brings it keeps it. In white-label yours is the only name on the work, and we ask only to publish the results anonymously.
Who talks to the brand, who owns the code
Who talks to the brand: in white-label, only you; we work through your producer and join client calls as your digital team if you introduce us that way. In referral and co-branded, both of us, with you leading. The referral fee, 15% of the first contract and 10% of renewals whether the brand buys through you or directly, is in a one-page partner agreement, so a client who liked the page cannot become our client around you.
Who owns the code, the content and the data: the brand. The page lives on the client's domain, the registrations go to the client's CRM or account, and repositories and access are handed over at delivery. GDPR applies by default, which for an event means consent on the form and a privacy page in both languages. No personal data goes anywhere near model training.
What else an event agency can sell with it
Events produce coverage, and more than 84% of what AI assistants cite comes from earned and third-party sources, journalism alone 22% (Muck Rack, October 2026). In the May 2026 edition, press releases were cited 3.5 times more often in industry-trend answers than in best-of answers. Coverage adds the brand to what assistants read; whether ChatGPT and Gemini then name it is something to measure, not assume. The AI Visibility Audit, five days, shows the client where they stand in four AI models against five competitors. Offer it as the line after the event: the first one is on us.
First step
One contact, Dmytro Lobod, replies the same working day in English or Spanish. Behind that contact, a core of two or three, and the 50+ people of LOBODS brought in per project.