Registrations arrive by DM and email, and we chase payments by hand
We build a registration form with payment on the site. After paying, the guest gets a ticket with a QR code, and the record lands in a spreadsheet or CRM (customer database).
We build websites for conferences, festivals, meetups and paid workshops: schedule, speakers, registration, payment and a ticket in the buyer's inbox. Attendees pay on their own, and you see sales in one place.
Quote and schedule after your brief

We build a registration form with payment on the site. After paying, the guest gets a ticket with a QR code, and the record lands in a spreadsheet or CRM (customer database).
Each ticket type has its own cap. We agree on the schedule after clarifying scope and dependencies. If payment fails, the ticket goes back on sale.
You edit sessions, speakers and rooms yourself in a simple admin panel. Changes appear on the site at once, and you can email registered attendees about them.
We add a scan page that works from a phone. It marks each ticket as used and rejects a second scan of the same code.
Use a package to describe what you need. We agree on the quote and schedule after reviewing your brief and requirements.
A meetup, workshop or course for 50–200 people
An event for 200–1,000 guests with several rooms
A large event with several languages and international guests
You describe the task and current workflow. We clarify requirements, choose a first stage and prepare a quote.
We agree the page map, ticket types and layout. Changes are made before development starts, so nothing built gets redone.
We build the site and connect the payment provider and email. First test purchases run on test cards.
Together we walk the full path: purchase, email, QR code, scan, refund. We fix problems before sales open.
We open sales and hand over the domain, hosting, payment account and email. Every account is registered to you under the agreed terms.
We prepare a quote after reviewing your brief and requirements. A first stage can cover: one-page site with schedule and speakers; One or two ticket types with online payment. Scope, payment and schedule are agreed before work starts.
For a one-off event of 30 people, that can be enough. The trade-offs are a fee on every ticket, a shared design and a guest list that lives on someone else's account. Your own site gives you your data and your own page to run ads to.
Payment terms are agreed with the quote before work starts. For a staged project, we describe the result and acceptance criteria for each stage. Support and third-party services are listed separately.
You set the refund policy, and we put it on the site. Refunds are issued from the payment dashboard, and the ticket stops working afterwards. More complex rules, such as partial refunds by date, need a separate agreement.
Event name, date and venue, a draft programme, ticket types with prices, a logo and speaker photos. We also need your company details to connect payments. The project brief helps collect the rest.
We agree on the handover of code, materials and account access before work starts. Third-party licences and services are listed separately when needed.
Describe your business, the outcome you need and your current workflow. We will clarify the requirements and prepare a quote after your brief.