v0.8 · Live · Built with touring crews

Every show starts with an advance.
Stop doing it by email.

RiderFlow replaces the 40-page PDF, the seven-thread Gmail conversation, and the venue hospitality spreadsheet with one live document — built by artists, filled by venues, signed off at doors.

Free forever for artists. No credit card. No demo call. Your first rider in under ten minutes.

Currently advancing shows for

Touring artists, booking agents, artist managers, venue general managers, festival production offices, tour managers, promoters, stage managers, backline techs, theatre producers, comedy agents, corporate AV, and the occasional cruise ship entertainment director.

The problem

Every show has the same Monday morning.

Two sides of the same broken process. Both sides think the other side has it figured out. Neither does.

If you build riders

Riders named by hope.
`tech_rider_v4_FINAL_clean_use_THIS.pdf`. Twelve versions deep, and the venue will still email asking whether they have the latest one.
Responses buried in reply-all.
Five venues confirmed catering. Four sent the console list. Two said "working on it" in October. Which is which? You find out at load-in.
One line, seven replies.
"Do you have an ADM2?" — "No but we have X." — "Will X work?" — "Ask the monitor eng." — "He’s on tour." — "Can we rent?" — "Who’s paying?"

If you receive them

PDFs in inbox hell.
Four tours this week, four PDFs, four different layouts, four different vocabularies. You reply to three. The fourth surfaces Thursday afternoon.
The vegetarian line gets lost.
The third act on the bill asked for plant-based catering six weeks ago. It’s on page 31. Catering read the first page.
"We don’t have that. What do you have?"
The rider asks for KSM9s. You have Beta 58As. The reply takes nine emails. By then the artist is already on the plane.

How it works

Advance a show in three steps.

01

Write it, or import it.

Structured sections — tech, hospitality, travel, catering, schedule. Drag, type, done. Or drop your old PDF and we digitise it: instruments, mic list, hospitality lines and all.

02

Send one link.

The venue opens it, sees your rider, responds item-by-item — confirm, propose alternative, flag. You get notified per item. Nobody types "reply-all" again.

03

Sign off when it’s right.

Every change is versioned. Restore any version with one click. Export a clean PDF on doors day, keep the live version for accounting and the next tour.

The AI loop

When the rider and the venue finally talk to each other.

Most riders get read once by a production manager and misread twice by everyone else. RiderFlow puts AI on both sides of the handshake so the details stay understood, not just transmitted.

Artist side

  1. 01
    Artist

    Sends the rider.

    Structured, live, versioned. Not a PDF.

  2. 02
    Artist · AI

    Reads the response.

    Compares what came back against what was asked. Flags deal-breakers. Highlights the swaps worth negotiating.

  3. 03
    Artist

    Accepts, counters, or escalates.

    Sign off when you’re ready. Everything stays in one document.

Venue side

  1. 01
    Venue · AI

    Fits rider against inventory.

    Maps the request to what’s on hand in under a minute. Green, amber, red.

  2. 02
    Venue

    Proposes alternatives.

    AI drafts substitution replies for the red items. Crew reviews, approves, sends back.

  3. 03

    Loop until signed.

    Zero email threads. Every round captured in version history.

For artists, managers & agents

Write less. Tour more.

The rider you write for the first support slot is the same rider you'll need for the headline tour, with edits. RiderFlow keeps the edits.

Available today, free forever: the rider builder, versioning, response collection, PDF export, and tech / hospitality / travel / catering sections that actually talk to each other.

Rider Importer

Pro · Live

Drop your existing PDF. We read it, structure it, and hand it back as a living RiderFlow document. Last tour’s rider becomes next tour’s starting point.

Rider Assistant

Pro · Live

Describe the show in a line — "indie rock quartet, 80-cap club, support slot." We draft the rider. You edit. It already knows the mic list you always ask for.

Response Analyzer

Pro · Live

Seven venue responses, one dashboard. Flags the deal-breakers ("no monitors at FOH"), spots the easy yeses, shows the swaps worth negotiating.

For venues & events

Say what you have. Say it once.

Every rider walks in asking the same questions. Your answers don't change much between Tuesday and Saturday. Write them down once — let the incoming riders fit themselves.

Available today: receive riders by link, respond per item (confirm, alternative, flag), versioning so nothing gets overwritten, and clean PDF exports for your records.

Inventory Library

Team · Q4

Your console. Your mic list. Your stage dimensions. Your catering options. Stored once, reused for every incoming rider. Finally, somewhere that isn’t a shared spreadsheet from 2019.

Fit Analysis

Team · Q4

Each rider comes in, we map it against your inventory in under a minute. Green = you have it. Amber = close substitute. Red = rent or flag. No more "going to check and get back to you".

Alternative Proposer

Team · Q4

Rider asks for KSM9s, you have Beta 58As. Draft the substitution reply, push it for review, send when approved. Your FOH engineer edits, doesn’t author.

For festivals & promoters · Roadmap 2026

Forty artists. Six stages. One audit trail.

Built for the people who found out at 3 PM on Saturday that two bands had asked for the same keyboard rig. Not shipped yet — the direction we're heading after the venue tier lands.

One dashboard, every stage, every artist.
See every rider for every stage of your festival in one view. Sort by day, stage, load-in, deal-breaker status, open questions.
Conflict detection before the production meeting.
AI flags conflicts on sight: "three headliners asked for the same mic package on the same day", "two bands need the same piano at 16:00 across stages". Fix it on paper, not on site.
Delegate per-item to the right crew.
Lighting questions go to the LD. Catering lines go to hospitality. Load-in timing goes to the stage manager. No more single-inbox choking.
One audit trail, the whole festival.
Every confirmation, every alternative, every signed-off rider — in one export. When accounting asks about last summer, you have an answer.

Pricing

Free for the people writing riders. Pay when AI does the heavy lifting.

You don't pay for the pen. You pay for the assistant who reads forty pages and tells you what matters.

Free

Forever, for artists. The rider writing part should not cost you money.

$0/ month
  • Up to 3 active riders
  • Unlimited response collection
  • PDF export
  • Version history — 90 days
  • Share by link, no recipient account
  • For artists, managers, tour managers, agents
Start free
Coming soon

Pro

For artists & managers advancing more than a handful of shows.

$19/ month per artist account
  • Everything in Free
  • Unlimited riders and tours
  • Unlimited version history
  • Rider Importer — PDF to digital
  • Rider Assistant — draft from a brief
  • Response Analyzer — compare side-by-side
  • Priority email support

AI features live. Free trial credits on signup; top-ups coming soon.

Try Pro

Team

For venues, festivals and production offices.

From $99/ month
  • Multi-user, role-based permissions
  • Venue / festival inventory library
  • Fit Analysis — rider vs inventory
  • Alternative Proposer — draft replies
  • Multi-stage scoping
  • Audit log and data export
  • SSO on request

AI features shipping Q4. Talk to us about onboarding.

Book a call

Running riders across a roster as a booking agent or management company? Talk to us — we have something for you.

Questions we keep getting

The honest answers.

Is it really free for artists?

Yes. Rider writing, response collection, version history (90 days), and PDF export stay free for artists forever. The scope of a headline artist's rider vs a club band's rider is the same from our side — you shouldn't pay for it. If you want unlimited history and the AI features, that's Pro.

I already have a rider PDF. Can I use that?

Yes — the Rider Importer ingests your PDF and hands it back as a structured RiderFlow document. Upload, preview the extracted sections, edit, commit. Or copy it in manually if you prefer.

How does the AI work — is it going to invent a mic that doesn't exist?

The AI is scoped to your inputs: your rider on the artist side, your inventory library on the venue side. It doesn't invent gear. If it doesn't know the answer, it flags the line for human review. No fake Shures.

Is my data used to train models?

No. Your rider, your inventory, your responses are yours. We don't train on customer data. Details in the Privacy page.

Do venues need an account to respond?

No. You send a link. They open it, respond item-by-item, done. No account, no password, no app to install. They can make an account if they want to reuse their inventory across riders — that's the Team tier.

What if I want to go back to a previous version?

One-click restore. Every save is a version. Nothing is overwritten, and every version shows who changed what and when.

Can I export to PDF?

Yes. Because the rest of the world still lives there. The PDF is clean and stamped with the current version number, so nobody can argue they were reading v6 when you had already sent v8.

What happens when I cancel?

Your data stays available for 60 days in read-only mode, then is deleted. Export everything to PDF any time, no questions asked.

Is this just another SaaS pretending to be an industry tool?

We've run riders through it on real tours. Our first FOH engineer test-user swore at v0.3; things got better in v0.4. We're now on v0.8. It's getting closer to what you actually need — and you can tell us what's missing directly.

Still something missing? Tell us directly — that's the short road to v0.9.

Start here

Stop emailing PDFs to people you've never met.

Your first rider takes ten minutes. Your fifth takes two. Your hundredth takes the time it takes to say “same as last month but add one guest.”