WW·AVIATION

The Roadmap

Five phases.
Mostly configuration.

Because the platform already runs, the path to a soft launch at DXR/HPN is short. Each phase is additive — nothing here is a rebuild.

PHASE 1

Jet products + Worker catalog

Create the jet products in Aryeo; add jet keys to SERVICE_MAP with prices, durations, and product IDs; implement size-class → sqft/duration/tier mapping; route aircraft metadata into order notes. Test a booking end-to-end against a real Aryeo sandbox order. No front-end yet.

PHASE 2

Jet brand front-end

New Astro project on its own domain. Reuse the booking components — service grid becomes a size-class selector, address becomes an airport picker, plus calendar and review steps. Point it at the Worker that's already in production and wire the jet IRIS persona. (This showpiece is the design preview of that site.)

PHASE 3

Aviation portfolio + IRIS jet knowledge

Add an aviation portfolio section to waynewilsonphotography.com — purely brand lift and SEO, not a booking funnel. Jet clients come through Eric's dealer and charter network into the jet site, not Wayne's. Load iris:jet:* knowledge into KV — size-class guidance, FBO access notes, prep checklists, turnaround, aerial permissions.

PHASE 4

Multi-photographer ops

Add Eric and Matt as Aryeo team members for scheduling and assignment; territory routing in IRIS; a payout reconciliation report (revenue, direct costs, each side's 50%). Add Stripe Connect only if split-at-source becomes wanted — it's additive, not a rebuild.

PHASE 5

Polish

Editing-pipeline hooks (AI auto → QC → Vietnam overflow tracking), the on-ramp logistics checklist, and jet galleries delivered through the existing customer portal.

Bottom line Building from scratch would buy automatic payment splits and clean aircraft metadata — and cost months. Not worth it for v1. Ship jet on Aryeo behind the existing Worker, repurpose square footage as cabin size class, drop the airport address into the address fields, and stand up a jet-branded front-end on the same backend. Revisit a native payment layer only if split-at-source becomes real friction.

Open Questions

What we settle before we fly.

Payout model

v1 collect-then-pay-out, or Stripe Connect split-at-source from day one? Changes only the payment layer.

Brand name + domain

Drives the second Astro project, the theme, and the IRIS persona.

Size-class pricing

Confirm the tier table and per-class prices with Eric — he knows the market.

Aerial at DXR / HPN

What's permitted on the ramp and in the airspace? Gate the drone add-on so IRIS doesn't over-promise.

Aircraft metadata

Does the Aryeo spec expose a custom field on orders? If not, lock the notes-prefix format.

One Aryeo group or two?

Running jet products inside the existing group is simplest — one calendar, one Stripe. Confirm no reason to split.

That's the whole job.

Back to the partnership Start over