What we built · SaaS
Orkestriq: the platform we built for events and operations.
International conferences, summits and forums run on spreadsheets, email and a team holding it together by hand. We applied our SaaS process to that problem and built the whole platform ourselves. Orkestriq is focused on events in Africa and the UK.
The organiser’s dashboard and the delegate’s portal, from the same record. Demonstration data.
The operation behind the event
Built for everyone involved, and what each of them needs.
Organisers
One delegate record from registration to the report, instead of a list rebuilt by hand.
Delegates
Their schedule, badge and messages in one place, in their own language, with no password to remember.
Sponsors
Each sponsor’s package, deliverables and deadlines tracked in one place, and numbers to show them afterwards.
Speakers
Linked to their sessions, so the programme delegates see is the one the team edits.
Registration and on-site teams
QR check-in and badges, so arrivals are counted, not estimated.
Communications
Email and push to the whole list or any part of it, and an assistant for the questions delegates ask all day.
What it does
Before, on the day, and after.
Before
Registration, invitations and delegate data
A public registration page, invitations and reminders, and one clean record per person.
On the day
Check-in, badges and live messages
QR check-in at the door, badges, room changes sent in seconds, and delegate questions answered.
After
Reporting for organisers and sponsors
Who registered, who came, which sessions drew people, and the report a sponsor asks for.
Africa and the UK
Two markets, chosen on purpose.
Orkestriq is built for events in Africa and the UK. That shows in the product: every delegate gets the portal, the emails and the assistant in English or French, whichever they chose.
The same delegate portal, in English and French.
How it’s built
The parts you can’t see are the ones that matter in your system too.
Each client’s data is separated in the database itself.
The rule that one organiser can never read another’s delegates is enforced where the data lives, and tested against the same rules that run in production.
Delegates get in without an account.
No password to set or forget. Access is tied to the event and switches off after it ends.
A mailing to thousands finishes, even when something fails.
Bulk sends run as jobs that pick up where they stopped, with a record of what went to whom.
Limits are enforced by the system, not the screen.
What a plan allows is checked in the database, so it holds however the data arrives.
The assistant answers only from approved content.
And says so when it doesn’t know.
Two languages, chosen per person.
The portal, the emails and the assistant all follow the delegate’s language.
A platform we build for you gets the same care, whatever it does. Our SaaS service
Running an event?
Run it on Orkestriq, which has its own site and its own prices. If you need something built for your own workflow, talk to Automyx.