Scope a build

Case studyRevenue-share

Verified deployment

Reliant Sentinel Training Solutions

Airsoft retail & milsim events · reliantftx.com

A shop and an events business running on one system — and we're paid a share of what it earns, not a fee.

Scope a build like this Visit reliantftx.com (opens in a new tab)

The Reliant Sentinel site — the next operation, its countdown, and tickets on sale
Plate № 01reliantftx.com, live

The brief

Two businesses, one customer.

Reliant Sentinel sells airsoft gear in Utah and runs weekend events.

It's the same people doing both — buying kit and booking a place. Running that as two separate businesses meant two sets of records for one customer.

What we built

A shop, a season, and a community.

One customer record behind all three. Buy a rifle and book a weekend and it's the same account.

  • The shop Gear, loyalty points, event photos, and rental kit that only becomes available once someone has booked a place.
  • The events One list that follows a player from buying a ticket to walking through the gate — place booked, waiver signed, pass scanned.
  • The community Each event gets its own private space for briefings, questions and files, so the organising doesn't sprawl across group chats.
The staff console's event list — every operation with tickets sold against capacity and its published state
Plate № 02The console behind it

How it works on the day

The jobs it does so staff don't.

Rules the system won't let anyone break. That's the point of it.

What it handles

Selling a ticket
An event can't oversell. When the last place goes, it stops selling — nobody has to watch it.
Buying for a group
Buy four places and four separate passes come back, one per person.
Getting people in
Staff scan a phone at the gate. It keeps working if the signal drops in a field.
Signing the waiver
Signed on a phone before arrival, filed against the right person, chased automatically if it's missing.
Gear and tickets together
One account. Rental gear unlocks only once someone actually holds a place.
Sales tax
Worked out per state at checkout, so nobody is reconciling it by hand later.
How we're paid
A share of what the platform earns. No invoice, no monthly fee.

What that prevents

  • Turning people away at the gate because an event sold more places than it has.
  • Someone playing without a signed waiver on file.
  • A queue at check-in because the phone signal died in a field.
The technical detail

For anyone who wants the parts list: a Django core on PostgreSQL with Redis and Celery for background work, and two React single-page apps — the public shop and the staff console. Sign-in is Authentik single sign-on: Google for customers, roles for staff.

Payments and tax run through Stripe Checkout and Stripe Tax with a per-state engine. Ticket capacity is enforced in the database, not the app, which is why an event cannot oversell under load; multi-packs issue a QR code per seat, and check-in tolerates being offline. Waivers are versioned and e-signed with a generated PDF.

Every merge passes quality and security gates — static analysis plus dependency, secret, container and infrastructure scanning. A partner application reads a read-only feed over a private network.

The commercial model

We get paid when they do.

No upfront invoice. Stagg built the platform and runs it for a percentage of net revenue.

reliantftx.com Revenue-share

Skin in the game

If the platform does not sell gear and tickets, we do not get paid.

Built · run · maintained

How it settles

Recorded, not invoiced

Our share comes out automatically when a sale settles, and every split is written to a record neither side can quietly edit.

Both sides can audit it, any time

What they own

The customer, and the record of them.

A revenue-share is a partnership, not a lease.

  • One record per customer Their points, their waivers, what they're allowed to rent and what they've earned as an affiliate — all in one place, not four.
  • The numbers behind the business Sales, tickets, waivers, who turned up and what it earned — one place to look, and it's theirs.
  • The money and the ledger A share both sides can audit, not a month-end line item.

In the line

The products behind it.

The whole line, in one platform.

Next step

Tell us what you run.

Three steps in the scope builder, or one line by email.

Base
Utah — Mountain Time · replies within 24 hours