trailmark

Roadmap

Six phases to a platform that runs the whole race.

Each phase ships something an organization uses for real. Effort is relative size, never a date.

Este prototipo esboza la funcionalidad; las pantallas, los flujos y los datos son ilustrativos, no el producto terminado. Ilustra la dirección y no incluye el plan completo de la aplicación ni todas sus funciones.

What you get at each phase

Phase 0

Cimientos

Done

The production foundation is built — every later phase adds to it, none rebuilds it.

  • Tenant isolation and authorization, enforced by the build
  • Real-time and background work in place
  • An automated quality gate on every change
Details
Scope
Tenancy, identity, admin, real-time plumbing, Signal design system
Goal
Build the production foundation once, so every later phase is additive, not a rewrite.
What the partner org gets
Nothing to see yet — this is the platform underneath everything that follows.

Phase 1

Lanzamiento para organizadores

Effort · XL

One organization runs a whole season on Trailmark — entries, lottery, messages, race day and results.

  • Registration, lottery and checkout for real events
  • Race day: pickup, aid-station check-in, safety desk
  • Past seasons migrated and reconciled
First live registration Historical data migrated and reconciled First lottery run First race day on Trailmark Organizer dashboard → Event-year setup →
Details
Scope
Event catalog, commerce core, registration & lottery, results, communication, race day, volunteers (vision specs 2–9)
Goal
Take one organization live end to end — publish an event, sell entries, run a lottery, communicate, run race day, post results.
What the partner org gets
Everything a race director touches on race weekend, for real events and real registrations — with your past seasons migrated and reconciled first.

Phase 2

Primera temporada real

Effort · L

Real money and real messages, at scale — payouts in the bank, texts that land, support that answers itself.

  • Payouts to your own bank account
  • SMS and email that reliably arrive
  • Automated support inbox and a status page
First payout to an organizer Platform revenue → Announcements & delivery log →
Details
Scope
Live Stripe Connect and payouts, deliverability, SMS compliance, production ops
Goal
Turn the working product into a business that can safely take money and text people at scale.
What the partner org gets
Real payouts landing in your bank account, and messages that reliably reach runners' phones.

Phase 3

El día de carrera, en todas partes

Effort · L

Every runner followed live, and Trailmark on every phone's home screen.

  • Timing mats and GPS feeding the board
  • Native iOS and Android apps with push
  • Offline-first aid-station mode
Native apps in stores Race-day board → Spectator tracking →
Details
Scope
Timing/RFID integration, GPS live tracking, native iOS/Android via Hotwire Native, push
Goal
Replace fixture splits with live timing and give every crew member a phone to follow from.
What the partner org gets
Real-time tracking on course, and a native app icon on the home screen — same screens, no rebuild.

Phase 4

Comercio y comunidad

Effort · L

New revenue beyond entries — merch, sponsors, fundraising — and a reason to open the app between races.

  • Shop and iPad POS at the venue
  • Sponsor portal and fundraising pages
  • Social feed and photo gallery
Details
Scope
Shop and inventory, iPad POS, social feed and share cards, photos, Strava/Garmin
Goal
Give runners a reason to open Trailmark between races.
What the partner org gets
A merch table that runs itself, and a social feed that keeps the season alive after the finish line.

Phase 5

Inteligencia

Effort · M

AI where it removes real toil, paid for with credits by the organization that uses it.

  • An assistant that answers the race team
  • Photos matched to runners automatically
  • Benchmarks against peer events
Assistant answering race teams Event finder (AI search) → Organizer AI assistant →
Details
Scope
AI event finder, organizer AI assistant with credits, bib recognition, campaigns and newsletters
Goal
Use AI where it removes real toil, paid for by the org that uses it.
What the partner org gets
An assistant that answers "how's registration pacing" instantly, and photos that find themselves.

Milestones

What "done" looks like along the way — each mapped to the phase that delivers it.

  1. Phase 1

    First live registration

  2. Phase 1

    Historical data migrated and reconciled

  3. Phase 1

    First lottery run

  4. Phase 1

    First race day on Trailmark

  5. Phase 2

    First payout to an organizer

  6. Phase 3

    Native apps in stores

  7. Phase 4

    Shop live

  8. Phase 5

    Assistant answering race teams

Partnership

The first organization shapes the product as much as it uses it. A founding partnership is a working relationship, not a sales contract.

What the partner contributes

  • Real event data

    Past seasons, rosters and results to migrate and test against.

  • A pilot race

    One event run end to end on Trailmark in Phase 1.

  • A champion on staff

    One person who owns the rollout and speaks for the team.

  • A feedback cadence

    A standing check-in through every phase, and honest notes after race day.

What the partner gets

  • Early access

    Every phase first, on your own events, before general release.

  • Input on priorities

    A real say in what gets built next and in what order.

  • Founding-partner terms

    Terms that recognise being first — agreed together, not a price list.

  • Migration handled for you

    Your history moved, reconciled and signed off, with nothing lost.

NV

Who I am

Nick Verges

I'm Nick — an ultrarunner and software developer building the platform the sport deserves. I'd work alongside your team, from first season to the one after.

How Trailmark makes money

A platform fee on every purchase — registrations, lottery entries, add-ons, merch, AI credits, sponsor placements — plus a subscription per organization.

The revenue model →

Relative effort by phase

Bar height is relative size, not time — Phase 1 is the biggest lift because it is the whole organizer launch.

XL

Phase 1

L

Phase 2

L

Phase 3

L

Phase 4

M

Phase 5

Size · S

A focused slice — one small piece, start to finish.

Size · M

A solid chunk — a few connected pieces.

Size · L

A major build — most of a sub-project.

Size · XL

The foundation itself — everything downstream depends on it.

Built for production

Phase 0 is already in place — tenant isolation, authorization, real-time and a quality gate on every change — and the platform is designed for the noon rush when registration opens.

Built like infrastructure →