Should we show prices on our website?

Yes. Hidden pricing doesn't create calls — it creates abandoned visits. A visible from-price with the deposit split ('$50 today, the rest at the DZ') filters nobody who was actually going to book and reassures everyone who was on the fence.

Won't posting our weight limit scare people away?

The opposite. The person over your limit finds out at the DZ, gets turned away after driving an hour, and writes the one-star review your next hundred customers read. Eligibility upfront protects them and you.

Is 'call to book' good enough?

It's a business-hours filter on a decision most people make at night. Every evening and weekend your phone doesn't answer, the booking either waits — or goes to whoever answers online. Keep the phone as the fallback, not the only door.

Do we need to replace our booking software?

Usually not. Most booking systems can show pricing earlier, cut fields, and state policies — they're just configured with defaults. The fix is usually settings and page design around the widget, not a new vendor.

Field guide

Why First-Timers Bail at Your Deposit Page

2026-07-22 · 3 min read · Rick Taylor

The straight answer

Nervous first-timers abandon tandem bookings for five fixable reasons: surprise fees that appear at payment, weight and age limits they discover too late, no weather policy before they commit, forced account creation, and booking that only works during office hours. Every one of these is a website decision, not a customer problem. State eligibility and total price before the calendar, promise free weather rebooking before the deposit, cut the form to five fields, and keep online booking live at 11pm — when most of them are deciding.

It's 11pm. Someone just watched a tandem video for the fourth time, opened your site, and hovered over Book Now. They're excited and terrified in roughly equal parts — and the terrified part is looking for any excuse to close the tab.

Most DZ websites hand them five.

We audit drop zone sites for a living, and the same booking-page failures show up again and again. None of them are exotic. All of them are fixable — most by your current web person, this week.

1. The surprise fee at the end

Industry-wide, about seven of ten started checkouts get abandoned, and the number one trigger is a cost that appears late. Fuel surcharge, gear fee, booking fee, "prices don't include" fine print — if the number at payment doesn't match the number that got them into the flow, the terrified part wins.

The fix: the total price — with the deposit split spelled out — appears the first time a price appears. "$XXX all-in. $50 holds your spot, the rest at the DZ." No asterisks at the finish line.

2. Eligibility they find out about too late

Weight limits and age minimums buried in an FAQ accordion are how someone books, drives an hour, and gets turned away at manifest. That's a refund, a ruined birthday, and a one-star review your website caused.

The fix: eligibility before the calendar, stated plainly and kindly. "Under [X] lbs? 18+? You're good — pick a date." The people it filters were never jumping; the people it reassures book with more confidence.

3. No answer to the weather question

Every first-timer knows skydiving depends on weather, and every first-timer quietly wonders: what happens to my money if it rains? If your site doesn't answer before the deposit, the doubt rides along to the payment screen — and often wins there.

The fix: the weather promise, in plain words, next to the booking button. "Weather hold? Free rebooking, no questions." One sentence removes the single biggest hesitation in the entire flow.

4. Friction that reads as risk

Forced account creation. Eleven form fields. A date picker that fights thumbs. Wrong mobile keyboards. To a confident buyer these are annoyances; to a nervous one, every extra step is another moment for the doubt to catch up.

The fix: date, party size, name, email, phone. Everything else can be collected after they've committed. And test the whole thing on an actual phone — that's where your customers are.

5. A booking door that closes at 5pm

"Call to book" means your booking system keeps office hours while your customers decide at night. The 11pm googler doesn't leave a voicemail — they either book somewhere that's open, or the excitement fades by morning.

The fix: real online booking, live around the clock, with the phone as a warm fallback for people who prefer it. You're not choosing between the two — you're refusing to lose the after-hours majority.

The pattern

Notice what every one of these has in common: the customer was ready, and the website introduced the doubt. Tandem demand mostly finds you on its own — the site's whole job is not fumbling it in the last hundred feet.

If you want to know which of the five your site is doing right now, send it through the free roast. We'll walk your booking flow like a nervous first-timer on a phone and send back exactly where they bail — with the fix attached to every finding.

Fix it properly

Where this gets handled.

Questions

Asked frequently.

Should we show prices on our website?: Yes. Hidden pricing doesn't create calls — it creates abandoned visits. A visible from-price with the deposit split ('$50 today, the rest at the DZ') filters nobody who was actually going to book and reassures everyone who was on the fence.
Won't posting our weight limit scare people away?: The opposite. The person over your limit finds out at the DZ, gets turned away after driving an hour, and writes the one-star review your next hundred customers read. Eligibility upfront protects them and you.
Is 'call to book' good enough?: It's a business-hours filter on a decision most people make at night. Every evening and weekend your phone doesn't answer, the booking either waits — or goes to whoever answers online. Keep the phone as the fallback, not the only door.
Do we need to replace our booking software?: Usually not. Most booking systems can show pricing earlier, cut fields, and state policies — they're just configured with defaults. The fix is usually settings and page design around the widget, not a new vendor.