CorSports
01/About

Built by people who've actually run the events.

CorSports is the platform we wanted while we were on the other side of the spreadsheet. Two co-founders, two decades of running events between us, one shared frustration with how the operations side has been taped together.

Founders

Two operators. Twenty years between us.

[TODO: bio] Story to follow — the short version: we've been the host union, the team manager, the match commissioner, the venue operator and the vendor. Different sides of the same spreadsheet.

Coris Zietsman and Josh Kruyt on the field at DHL Stadium
Coris (right) & Josh (left) · DHL Stadium · Springbok test
Coris Zietsman
Co-founder · CEO

[TODO: bio] Personal bio to be written by Coris. Keep operator-to-operator voice, specific tournaments and venues, no marketing slop.

Josh Kruyt
Co-founder · CTO

[TODO: bio] Personal bio to be written by Josh. Keep operator-to-operator voice, specific tournaments and venues, no marketing slop.

What we believe

The principles we won't break.

These aren't marketing language — they're the operating principles for the build.

  1. 01

    Operator-first, always.

    Every feature ships with a question: would you actually use this on the day? If the answer's 'maybe in v2' it gets cut. Operators have spent years working around bad tools — they don't need a new one to work around.

  2. 02

    Freemium by design.

    Every product has a Free tier that's genuinely useful — not a 14-day trial, not a feature-stripped demo. A small club paying nothing should still get real value. Sophistication is monetised; the basics aren't.

  3. 03

    Sport- and event-agnostic.

    We started in rugby. The platform doesn't know that. Conferences, ceremonies, broadcast, athletics, hockey, festivals — same primitives. The world doesn't need rugby-shaped event software.

  4. 04

    Configurable without dev gatekeeping.

    If a sensible operator could reasonably need to change a setting without a code release, that setting lives in the UI. We don't make customers raise tickets for things they should own themselves.

  5. 05

    Engineering blueprint, not marketing veneer.

    The platform is built like a serious operator's tool. Multi-tenant from day one. Audit log on every state change. Tenant-isolated queries. We make architectural decisions like the platform's going to outlive us — because it should.

Origin

Why this exists.

[TODO: origin story] The longer story — when, where, why we decided to build this — is being written by Josh and Coris personally.

Until then: we've been the operators on the other side of every spreadsheet, every WhatsApp group, every PDF briefing pack mailed out the night before kick-off. The platform is what we wanted while we were doing that work.

Want to talk to the people who build this?