Skip to content
Basecomp logo
02 / SaaS · Competitions

Basecomp: a platform to run prize competitions end to end.

I was the lead developer for the backend and administrative dashboard. The engagement was purely backend-focused, covering the systems and workflows behind the competition platform.

My role
Lead Developer · Backend & Dashboard
Stack
Laravel · Livewire · Tailwind · MySQL · AWS · Stripe
Live site
basecomp.io
End-to-end
competition operations
Peak-ready
spiky traffic patterns
Auditable
draw & winner logic
Administrative dashboard
Basecomp administrative dashboard showing revenue, visitor and order metrics with trend charts
The operational view: revenue, visitors, orders and the competitions driving sales.

The challenge

Replace the patchwork.

Competition businesses often juggle ticket sales, payments, entrants and draws across tools that do not talk to each other. Basecomp set out to put the whole operation into one platform.

Launch competitions

Create competitions and ticket tiers.

Sell securely

Handle entries and payments reliably.

Run fair draws

Transparent and auditable winner selection.

Inside the project

Commerce logic under pressure.

  1. Multi-tenant platform

    One system serving several competition businesses at once.

  2. Competition management

    Competitions, ticket tiers and the rules that govern them.

  3. Tickets & entries

    Entry handling from purchase through to the closing draw.

  4. Payments

    Card payments through Stripe, at the moment demand peaks.

  5. Entrants & orders

    Centralised views for customers, entries and orders.

  6. Draw workflows

    Winner selection that has to stay transparent and auditable.

  7. Administrative dashboard

    The screens the whole operation is run from day to day.

  8. Peak-load traffic

    Thousands of buyers arriving in the final minutes before a draw closes.

What I built

The backend and dashboard, end to end.

I was the lead backend developer responsible for the platform's backend and dashboard. The work stayed on that side of the product.

  1. Backend architecture

    Designed and built the multi-tenant backend the platform runs on.

  2. Dashboard implementation

    Built the dashboard used to create competitions and run the operation day to day.

  3. Competition & ticketing logic

    Implemented competition creation, ticket tiers, entries and the workflows around them.

  4. Payment backend

    Built the payment paths and the backend logic that keeps them reliable when demand peaks.

  5. Draw & entrant workflows

    Implemented winner selection and the operational views for customers, entries and orders.

01 / Competition operations
Basecomp competitions calendar showing scheduled draws, revenue metrics and competition status across the month
The calendar operators use to schedule draws, track revenue and manage competition status day to day.
02 / Live analytics
Basecomp live analytics showing real-time visitor map, active sessions and checkout activity
Real-time visitor activity when demand spikes in the final minutes before a draw closes.

For draw integrity and peak-load payment engineering, read Auditable draw logic and peak-load payments in competition SaaS . Basecomp also publishes operator guides on publicly verifiable draws and competition operations.

Under the hood

Architecture for spiky traffic.

Popular competitions can create thousands of buyers in the final minutes before a draw closes. The platform uses a multi-tenant Laravel architecture, a payment path designed for reliability under load and AWS infrastructure that can scale for peaks.

LaravelLivewireTailwind CSSMySQLAWSStripe

Building a backend-heavy business platform?

Let's talk about the architecture, workflows and engineering needed to make it reliable.

Let's talk →