The whole first pass fits inside an afternoon. You spend eight minutes on it; the rest is ours.
Ten fields and a paragraph about the event. Attach a logo, a speaker list, a deck — whatever you already have.
Copy written, pages built, registration and payments wired, analytics installed and checked.
The site lands in your portal as a real page. Approve it, or write what to change and we rebuild.
Your domain mapped, certificate issued, served from a CDN. Nothing goes live until you say so.
Not a template you finish yourself — copy written, pages built, payments live, analytics firing.
Every version lands in the portal as a real page with browser chrome and version history. Approve it, or write what to change and we rebuild.
Six things have to be true before an event site is worth publishing. Each one below is ours to build, wire and prove — not a setting you configure after handover.
You fill in ten fields — event name, host, dates, venue, expected size, ticketing model — and describe the event in a paragraph. That is the whole of your input.
From it we draft every page in your voice, pull brand colours and type from your logo, and build the agenda and speaker list from whatever you already have: a spreadsheet, a deck, or an email thread.
Not a one-pager with anchors. Home, agenda, speakers, sponsors, venue and travel, FAQ, press, code of conduct — as many pages as the brief calls for, each with real content on it.
Pages respond properly from phone to desktop, images are compressed and sized, and the copy is proofread before it reaches you. Change requests come back as a new version, never a patched file.
Paid, free, invite-only or all three on the same site. Tiers, caps, promo codes, group rates, waitlists and manual approval are configured before launch, from what you described in the brief.
After launch it stays yours to run: the portal holds the attendee list, per-tier numbers, badge export and check-in list, and you can open or close a tier without coming back to us.
Connect the processor you already use and registration fees settle straight into your account, in your currency, on your existing payout schedule. We never hold funds and take nothing per ticket.
Local payment methods matter more than card logos: we enable bank transfer, USSD, mobile money, Apple Pay and Google Pay where your audience expects them, and test a live transaction before the site goes public.
Tell us which tools to fire and on which pages. We install the tags, wire the registration funnel as events, configure the consent banner for your regions, and verify each one reports before launch.
Tracking is set per page rather than blanket site-wide, so a gated investor site stays quiet while a public summit tracks the full path from ad click to confirmation page.
Nothing goes live until you approve it. When you do, we map your domain or subdomain, issue the certificate, and serve the site from a CDN so it loads in under a second wherever your audience is.
After launch the portal is your control room: version history on every page, one-click rollback, registration numbers, and a change request box that comes back to the same team that built the site.
Name them in the brief. We connect them before the site goes live, so nothing needs setting up after launch.
Priced per event site, not per seat or per month. Page count, how much content we write and whether the event runs in several cities move the number.
One event, up to five pages, one registration flow.
The whole site — agenda, speakers, sponsors, travel — plus launch support.
A repeatable site pattern across your calendar, with one team who knows it.