Axe Throwing Booking Software

Axe throwing software for lanes, waivers, and leagues in one place.

Your venue books lanes in one tool, collects waivers on paper, and scores league night on a chalkboard. We turn that into one system: lanes booked by group size, no thrower on a lane without a signed waiver, and scoring that happens in the lane as the axes land.

See our work

Bring one busy Friday night. Leave with a build, buy, repair, or wait recommendation.

Trusted by

Perceptional logoMusgrave GroupUrShipper logoBrux Dental SolutionsBella Skin Institute LogoEnergia RewardsDraftly logoTuneClub LogoSekou LMS logoLogo of food order management app gulaSnelwegDealsGrubly logoPSi logoInstantor Rewards logologo of Mobile app for events, membership clubs, and communitiesAldiFest retail campaign logoVidmattic logoEMS Connect logoWorx Squad logologo of Online Web App For Making Intrologo of Referral and Viral Marketing PlatformConcurrences logoGE logoTicketstop logo

The brief

Start with what is not working.

Good software decisions begin with the constraint, not a list of features or a preferred technology.

01

A party of fourteen books online, then staff have to work out the lane math by hand at the door.

02

One person in the group has not signed a waiver, and nobody can tell until they are already at the lane.

03

League scores live on a chalkboard and a spreadsheet, so one wrong total turns into an argument.

Plain answer

Axe throwing booking software helps a venue sell lane time by group size, collect a signed waiver from every thrower before they play, score games in the lane, and run league nights under WATL, IATF, or house rules. RaftLabs builds it around your lanes, your session lengths, and your league format.

What to remember

  • Use this when bookings, waivers, and scoring live in separate tools and staff join them up by hand.
  • One booking record should carry the group, the lanes, the waivers, and the payment.
  • No waiver, no throwing. The check should happen in the system, not in a coach's memory.
  • The first release should cover one complete night, from online booking to the last league score.
  • The code, cloud accounts, data, and operating notes should stay usable by another capable team.

The first decision is not what to build.

It is whether software is the right answer at all. We use four possible recommendations before discussing a development scope.

  • 01

    Buy

    Choose a maintained product when it already books lanes by group size, gates every thrower on a signed waiver, and scores your league format. Paying for software you do not have to maintain is often the better trade.

    Run the build-vs-buy numbers

  • 02

    Repair

    Keep the existing product when throwers and staff still get value from it and the code can be understood safely. Start with evidence: where the code lives, how the data is organized, what is tested, which outside services it depends on, who can access what, and how updates go live.

  • 03

    Build

    Own the system when your lane rules, waiver check, and league format are the way your venue runs, and the general tools keep bending them out of shape. Start with one complete night and the connections that night cannot work without.

  • 04

    Wait

    Do not turn a changing league format or unsettled session policy into permanent software. Settle the rules, name the owner, and measure what the current mix of tools costs on a busy night first.

Not sure which path is yours? Bring it to a 30-minute call. Leave with the answer in writing.

Fit

Custom software should earn its maintenance burden.

A feature request is not enough. The case is real when the same problem shows up on busy nights, in waiver gaps, or in league arguments.

A fit

Bookings, waivers, and scoring live in separate tools, and staff join them up by hand every night.

Your league runs a format the general booking tools cannot score without a side spreadsheet.

The venue can name an owner and what 'done' looks like for the first release.

Not a fit

A maintained product already handles your lanes, waivers, and league format with reasonable setup.

The venue wants software to settle an unresolved safety or league policy.

The brief is a feature list with no night, session, or league result attached.

Not sure which side you are on? Use the first call to make that decision. A useful answer may be to buy, connect, repair, or wait.

Start with the night, not the software.

An axe throwing problem usually starts as a Friday night problem. A corporate group books for fourteen and arrives with sixteen. Three waivers are missing and the line is backing up. One lane sits empty for forty minutes because the bookings either side of it left a gap too short to sell. League night has the same shape in a different form: a chalkboard total is wrong, nobody kept the throws, and the standings take an evening to rebuild.

None of those problems is a missing screen. Each one is a rule applied by hand under pressure: how many lanes a group of this size needs, who is allowed to throw, how a clutch call scores in your format, and what happens when the headcount changes. When staff carry those rules in their heads, the venue runs on memory. Memory fails exactly when the room is full.

A second product hides inside the first. Throwers see a booking page and a target. Your team lives in the other half: lane assignment, waiver checks, walk-in sales, score corrections, refunds, and a record of who changed what. Quotes that squeeze all of that into one admin line are where budgets break, so we quote your team's screens as their own job from the start.

Custom software makes sense when one owned system can hold those rules better than a booking tool, a waiver app, and a spreadsheet stitched together. The first release should run one complete night, from the first online booking to the last league score. It should not try to replace every tool in the building at once.

We start where it hurts.

The booking page is only one part of the job. The real scope includes lane capacity, the waiver check, scoring rules, what happens when things change, who can see and change what, and who runs it after release.

Lane booking by group size

A group books once and the system does the lane math: how many lanes the group needs, side by side, for the full session with briefing and changeover included. Bookings sit back to back, so prime hours are not cut into short gaps no one can buy.

A waiver for every thrower

Every thrower signs before they play, on their own phone, and the waiver sits on the booking against their name. A parent signs for minors and age limits are checked per product. At check-in the screen says cleared or not cleared, and a lane does not start for someone who is not cleared.

Scoring in the lane, not on a chalkboard

Throwers tap where the axe landed on the target shown on the lane tablet. The system adds the score, keeps the turn order, and shows the total where the room can see it. A wrong tap is undone or corrected by a coach, and the correction stays on the record.

League nights under your format

League signups, payments, matches, and standings live with the bookings. WATL, IATF, and house formats each carry their own ring values and clutch rules. Standings come from match scores, so a corrected score rebuilds the table and the playoff picture on its own.

Walk-ins, parties, and the counter

Walk-ins join the same lane picture as online bookings, so a lane is never sold twice. Party packages, deposits, and balance payments sit on one order. Food, drinks, and merch sell in the booking flow and at the counter from the same stock count, so the last item cannot be sold twice.

Which one is yours?

Bring it to a 30-minute call. Leave with a build, buy, repair, or wait recommendation in writing. Free, whether or not we ever work together.

One night

One night, end to end.

A venue night is one chain. If one link is handled on paper, staff end up carrying the whole chain by hand.

Book

Groups book by size and pay a deposit. Lanes are held side by side, confirmations and reminders go out, and every thrower gets the waiver link with the booking.

Arrive and clear

Check-in shows the group, the lanes, and the waiver state of every thrower. Missing waivers are signed on the spot, on the thrower's own phone, before anyone picks up an axe.

Throw and score

Coaches run the safety briefing, then play starts on the lane tablet. Scores, turn order, timers, and party games all sit in the lane, with the running total visible to the room.

Close the night

Counter sales, deposits, and balances agree on one record. League results from the night are already in the standings, and the lane picture for tomorrow is clean.

Proof

The fifth attempt became a product customers could keep using.

UrShipper had already worked with four development vendors. Its founder describes the communication and decisions during the recovery.

The case study documents a 14-week recovery, five carrier connections, a Shopify fulfilment workflow, and client-reported results. It is one comparable project, not a promise that every inherited codebase can follow the same plan.

Read the UrShipper case study

Which part of the night costs you the most right now?

Bring it to a 30-minute call. Leave with a build, buy, repair, or wait recommendation in writing. Free, whether or not we ever work together.

Let the work pick the shape.

The way people work should decide the form of custom software. Start with where the user works, which device they have, whether the signal drops, what data they need, and how fast the system must respond. Those facts tell us what belongs in the first release.

One product may need several surfaces. Each one should support the same complete workflow, not start another feature list.

How it works

Close one expensive risk before opening the next.

Each stage answers a buyer question and leaves behind a decision you can inspect. The next stage only opens when the expensive uncertainty in the current one is small enough to accept.

  1. 01
    Understand

    Trace one busy night

    Where do lanes, waivers, and scores actually break down?

    Follow one group from online booking to the last throw, and one league match from signup to standings. Include the workarounds, the paper, the side spreadsheets, and the arguments that a tidy process diagram usually misses.

    Decision produced

    A map of one full night: bookings, lane assignment, check-in, scoring, counter sales, exceptions, and the cost of each failure worth changing.

    Risk closed

    Paying to automate the visible symptom while the expensive constraint remains.
  2. 02
    Shape

    Choose the first useful release

    What needs to exist together for one complete night to work?

    Choose the shape from the way the night runs, not from a preferred technology. Name the lanes, the session types, the staff roles, who can access what, the exceptions, and the result the first release must complete.

    Decision produced

    The first-release boundary: lane booking, waiver gating, in-lane scoring, and the league format, with a clear definition of done for each part.

    Risk closed

    A small-looking feature list that quietly depends on several interfaces, systems, and owners.
  3. 03
    Prove

    Review working software

    Will it hold up on a real Friday night?

    Review the product against the agreed night, not a tour of finished screens. Record changed assumptions and test what happens when a headcount grows, a waiver is missing, or a tablet fails mid-session.

    Decision produced

    Working checkpoints tested with a full group booking, a missing waiver, a corrected score, and a league table rebuilt from play.

    Risk closed

    Discovering the important gaps during migration or after customers depend on the release.
  4. 04
    Transfer

    Release, measure, and hand over

    Did the night improve, and can another capable team operate it?

    Run one weekend on the new system while the old way stays as backup. Compare check-in time, empty lane gaps, and scoring disputes before the next part of the venue moves over.

    Decision produced

    A controlled release, comparison with the starting point, operating notes, account ownership map, and a recommendation for what should happen next.

    Risk closed

    Measuring development activity instead of the business result, or depending on the original vendor to keep the system running.

What stays out of the black box

These are operating conditions to put in the engagement, not claims to take on faith.

The scope names one complete night

The lanes, the session types, the waiver rule, the scoring format, the exceptions, and what 'done' looks like. A screen list is not enough.

Progress is visible in working software

Reviews against the product at agreed checkpoints, while there is still time to act.

A scope change has a price before it has code

A new workflow or system connection shows its effect on cost and timing before anyone approves it.

Ownership exists throughout, not only at handover

Code, cloud, data, and provider access stay visible and under your control from day one.

The work is checkable without being technical

Checkpoints are working software you use yourself, reported in plain language.

Custom software by industry.

Start from your domain. Each area below is a working practice with shipped products behind it.

What it costs

Every project starts at $10K.

The first phase turns the costliest patched workflow into a scoped build with written acceptance criteria.

Starting investment

Starts at $10K

Workflow complexity, systems to connect, data migration, and user roles set the scope. After a 30-minute call, you get a written build, buy, repair, or wait recommendation plus first-phase direction. Free, whether or not you build with us.

Build or buy

Buy an existing productBuild custom software
Best fitBooks lanes by group size, gates waivers per thrower, and scores your league formatYour lane rules, session shapes, and league format are the way your venue runs
Manual workSetup and process changes can remove the paperworkStaff rebuild lane plans, waiver lists, and standings by hand every week
ConnectionsExisting connections work with reasonable setupA critical connection to your other systems cannot be done cleanly any other way
Neighbouring workUse multi-attraction software when axes are one activity among many, and room software when timed rooms are the productOwn custom software when axe lanes, waiver gating, and league scoring are the product

Work with us

Bring one busy Friday night. Leave with a decision.

In a 30-minute call, we will help you decide whether to buy, connect, repair, build, or wait. If custom software is not the sensible next move, that is still a useful answer.

  • One named workflow owner and one complete path for the first phase.
  • Scope, price, what 'done' looks like, and exclusions agreed before paid work starts.
  • Code, cloud, data, and provider access remain under your control.
  • Post-launch warranty cover for defects in the agreed scope.

Frequently asked questions

Straight answers to what buyers ask before they scope. Still stuck? .

It is software built around one axe throwing venue. A booking holds the right number of lanes for the group size and session length. Every thrower on that booking needs a signed waiver before they can be checked in to a lane. Once play starts, scores are entered in the lane and added up by the system. League nights use the same records, so signups, matches, and standings come from play itself, not from a second spreadsheet.

A focused first release covers online booking by group size with deposits, lane assignment that keeps a group on lanes side by side, a waiver for every thrower linked to the booking, a check-in screen that shows who is cleared and who is not, walk-in sales at the counter, in-lane scoring on a tablet, league signups with matches and standings, and food, drink, and merch sales on the same ticket. Your venue rules decide session lengths, age limits, and league format. The software applies those rules the same way every night.

The group books once, in one order, and states how many people are throwing. The system works out how many lanes that group needs and holds lanes next to each other for the full session, including the safety briefing and the changeover time your venue allows. The organizer pays the deposit on that one order. Staff do not split the party across separate bookings or move lanes around by hand when the group arrives.

Each thrower signs on their own phone, from the booking confirmation or a code at the door, and the signed waiver sits on that booking against that person's name. A parent or guardian signs for a minor, and the age limit you set for each product is checked at the same time. At check-in, staff see a simple list: cleared, or not cleared. A lane session cannot be started for a thrower who is not cleared, so the rule does not depend on a busy coach remembering to ask.

Staff add the walk-in group at the counter in the same system that holds the online bookings, so a walk-in can never be given a lane that is already sold. Waivers are signed on the group's own phones while the lane is prepared. Payment, including a split bill, sits on the same record as the booking. On a busy night there is one queue and one lane picture, not a walk-in list on paper next to a booking screen.

A tablet at the lane shows the target. The thrower or coach taps where the axe landed, and the system adds the score, handles the turn order, and shows the running total on the lane screen and, if you use one, the overhead screen. A wrong tap is fixed with an undo or a coach correction, and the correction stays on the record. That ends the two common chalkboard problems: mental maths under pressure, and a total nobody can trace back to a throw.

Yes, if the scoring rules are set up as a named format rather than fixed in the screens. A WATL format, an IATF format, and your own house format can each carry their ring values, clutch or killshot calls, and the throws those calls are allowed on. A league is tied to one format for its season, and casual party games can use simpler formats on the same lanes. Your league decides which format it sanctions. The software keeps the scoring honest to the format you picked.

Standings are worked out from the match scores, not typed in. When a coach corrects a score, the match result, the standings, and any playoff seeding that depends on it are worked out again from the corrected record. Player history keeps both the throws and the correction, so a dispute a week later can be settled from the record instead of from memory.

The system places bookings back to back on the same lanes instead of scattering them across the room. A session that ends leaves the next full session length open, rather than a short gap that is too small to sell and too large to ignore. Staff see the whole room on one screen and can hold lanes for a large group or a league night while the remaining lanes keep selling.

The booking is updated in one place. If the new group size needs another lane, the system checks the lanes next to the group first and shows staff the options before anything is confirmed to the organizer. The deposit and the balance due change with the booking, and the waiver list grows with the group, so the extra throwers are asked to sign before they arrive rather than at the door.

A multi-attraction venue sells different activities side by side, such as bowling, karting, and axe throwing, and needs one checkout across all of them. That broader problem sits on our leisure venue page. This page covers a venue where axe lanes are the main event: lane capacity by group size, a waiver for every thrower, in-lane scoring, and league play. If axes are one attraction among many, start with the broader page.

An escape room sells a timed room to one group, with clues and a reset between games. An axe venue sells lane time that turns over all night, scores every throw, and runs leagues over a season. The booking shapes look similar from a distance and behave very differently on the floor. If your rooms are the product, our escape room page is the closer fit. This page is lanes, waivers, and league scoring only.

In most venues, standard tablets at the lanes and a normal screen above them are enough, because the system runs in a browser rather than on special terminals. The scope should name the devices you already own, how each tablet is paired to its lane, and what staff see if a device fails mid-session. Scores already entered stay on the record, so a dead tablet delays a lane, it does not lose the match.

The first paid phase may cover a bounded audit of your current booking and league process, a small proof, or a first release that runs one complete night. The final price depends on how many lanes and session types you run, whether league scoring and counter sales are included, what it needs to connect to, and how many staff roles use it. The agreed phase is priced in writing before it starts.

You judge what you can see, not the code. Run one real night through each checkpoint yourself: book a group of fourteen, leave one waiver unsigned and try to start the lane, score a match and correct one throw, then read the league standings it produces. Progress is reported in plain language: what changed, what is next, and what it costs. Because you own the code, the accounts, and the operating notes throughout, nothing about the work is locked inside our heads.

You own the code built for you and control where it lives, the cloud accounts, the data, analytics, and third-party subscriptions. Outside services and open-source pieces keep their own licence terms. The operating notes and handover material stay current so another capable team can take over.

Yes. Takeover starts with an audit: where the code lives, how your data is organized, what is tested, which outside services it depends on, who can access what, and how updates go live. Code that is sound stays. Only the parts blocking reliable Friday nights and league nights get replaced.