Packages and pricing

Three packages. Named prices.

The morning arc does not change across the packages; the basket does. Shared, private, or two-basket charter. Pricing is per seat and published below; the booking form is one click away.

RampStack

Built by the RampStack trinity

How Drift & Dawn Balloon Co. was built

The four-stage workup behind this hospitality + experience demo, summarized. Generalized and pattern-level; no named competitors. The full Format A spec and the verification log live in the operated-side run record.

Stage 01

Basano · competitor review

  • Hospitality-experience balloon operator homepages split the field. The long-running heritage operators run aerial-photography piles above the fold without naming the experience arc or the safety posture explicitly; the newer operators surface pricing and booking but bury both behind a regional selector that disorients a first-time visitor. The position the field leaves open is an experience-led homepage that also names price and safety on first scroll.
  • Pricing is rarely above the fold. The field treats price as a secondary callout reached through a 'See pricing' button or a regional dropdown, even though a hospitality experience priced at $200 to $500 per seat is exactly the kind of commitment a first-time visitor wants to qualify before scrolling further. The pattern that converts (price visible early, packages named) shows up at small-operator scale; the larger operators that could afford the polish leave it off.
  • Trust and safety signals are present but unevenly surfaced. FAA certification, lead pilot hours, weather posture, and refund posture are the four signals a first-time experience buyer needs; the audited homepages carry at most two of the four above the fold, and the missing signals are frequently the load-bearing ones (weather-cancellation policy and pilot hours).
  • Booking path is uneven across the field. Some homepages drop the visitor into a multi-step regional selector before the first form field; others run a phone-only conversion model. The shape that produces above-field conversion (a single named booking page with a clear demo-or-live form) is rare.
  • Photography is the field's universal strength. Every audited homepage carries strong aerial photography; the convention is solid and stable. A new entrant should not invert this convention; the work is to wrap the photography in narrative arc copy that names the dawn-launch sequence rather than letting the images carry the page alone.
  • On-page SEO and structured data are uneven across the field. LocalBusiness with geo and openingHours is common; TouristTrip schema (the more specific subtype for a hot-air-balloon ride as an offered experience) is rare and is the cheapest standout for a new entrant.

Stage 02

Krine · positioning

Position
Experience-and-trust-led hospitality balloon operator. The hero declares the dawn-launch arc and one trust signal together; an immediately-visible packages strip surfaces named packages with named prices; an above-the-fold safety callout names FAA certification, lead pilot hours, and the weather-or-refund posture; the booking flow is a single page with a clear demo-only confirmation. The position the field's audited homepages split around: aerial-photo-pile without arc on one side, and price-and-booking-buried on the other.
Archetype
lantern-hotel
Voice
Atmospheric, place-literate, second-person, present-tense, sensory-forward. Names the time of day, the temperature, the sound of the burner.

Stage 03

Tholo · build plan

home

  • competitor-experience-audit
  • vertical-site-conventions
  • landing-page-copy
  • information-architecture
  • frontend-component-build
  • seo-onpage

experience

  • landing-page-copy
  • frontend-component-build

packages

  • landing-page-copy
  • information-architecture
  • frontend-component-build

about and safety

  • landing-page-copy
  • frontend-component-build

book (demo)

  • frontend-component-build
  • landing-page-copy

workup

  • landing-page-copy
  • frontend-component-build

Stage 04

Basano · verification

Holds(8)

  • Heading hierarchy holds across all six pages: exactly one H1 per page, H2 / H3 sequence with no skipped levels.
  • Language declaration, semantic landmark structure (header, main with id=main-content, footer, nav with aria-label), and the skip-navigation link via ShowcaseMetaLayer are all present and correctly wired across the microsite.
  • JSON-LD LocalBusiness on the layout (with the boutique-balloon-operator geo and opening-hours block) and TouristTrip schema on the packages page; BreadcrumbList on all non-home pages.
  • Hero zone carries the load-bearing hospitality-experience conventions: the dawn-launch arc one-liner, a named trust signal, and an immediately-visible package strip with named prices, all above the fold. Inverts the field default of aerial-photo-pile-without-arc and buried-price.
  • About-and-safety page surfaces the four signals (FAA certification, lead pilot hours, weather-or-refund posture, insurance) the audited homepages frequently leave off.
  • Booking flow validates name, email, date, and seats (1 to 16); demo-only confirmation state is clearly labeled; the form does not submit to any backend.
  • Lantern boutique-hotel register held: warm cream and dawn-amber palette, serif lockup, sensory-forward voice, place-literate copy, present-tense second-person where appropriate.
  • Demo-only labeling on the booking surface is consistent and visible: amber 'Demo only' chip on the form heading, footer disclaimer site-wide.

Fails(5)

  • Intentional noindex and nofollow on the demo build (correct for a demo, flagged by the verifier across pages against a production-ready standard). Same not-a-defect-in-context the prior demos carry.
  • Canonical URL declares the production rampstack.co host while the build is served from localhost during the audit; cross-origin canonical mismatch is the localhost-vs-production artefact, not a real defect. Recurring across all pages.
  • Title tags and H1s on inner pages lean structural (The experience, Packages, About and safety, Book) rather than search-keyword-aligned. Judgment item for the showcase context; a live balloon-operator build would target topical keywords explicitly.
  • Demo placeholder address and demo placeholder lead pilot hours in the structured data and the safety page; intentional for the fictitious-org showcase build, flagged against a production-ready standard.
  • Logo-less type lockup; the SVG hero is the type-led placeholder this batch ships with. The logo pass is a separate per-brand later dispatch.

Not assessable(5)

  • Core Web Vitals and page experience (no field data in a static-fetch audit).
  • robots.txt and XML sitemap content (single-page audit does not crawl).
  • Booking backend integration (none in this build by design; demo-only validation flow).
  • Real FAA certification and pilot records (intentionally absent; demo-only fictitious operator).
  • Mobile responsiveness past basic reflow at the audit viewport (separate device captures required).