07 / The booking is half the job

The booking isonly half the job.

We would lead the mobile-friendly web build in small, visible steps, with PIVOT reviewing progress each week. Our launch standard is clear: a real booking works, the money matches and the traveler can get help. Native apps come later, with their own scope and budget.

Here's how we take the web booking from design to launch.

EXAMPLE 07

Prove the booking. Launch with confidence.

01

Agree

Know who does what

  • First client and mobile web scope
  • Provider access and agreements
  • Who takes payment and helps travelers

We move on when

We have access and everyone knows their job

02

Build

Make the booking work

  • Find and book a flight
  • Pay and receive confirmation
  • PIVOT can see the booking

We move on when

A test booking works from start to finish

03

Prove

Validate the full journey

  • Help travelers and check payments
  • Test failures and private client access
  • Test desktop, iPhone and Android browsers

We move on when

An approved real booking works, including support

04

Grow

Make the next client easier

  • Open to the first travelers
  • Learn from real bookings
  • Set up the next organization

We move on when

PIVOT signs off before we expand

Pure Strategy / Lead the build and software support

PIVOT + travel partner / Set the traveler-servicing plan

Native apps follow in Phase 2, with separate scope, pricing and dates.

This sequence covers Phase 1: mobile-friendly web. We would set dates once provider access and launch scope are confirmed. Native iPhone and Android apps are a separately scoped and priced Phase 2, with their own delivery schedule.

01

Know who does what before we build

Choose the first organization. Confirm who provides flights, takes payment, issues tickets and helps travelers.

02

What if the payment fails?

Prices change. Payments fail. People request refunds. We need to test those, not just the happy path.

03

Prove it works before adding people

The booking and payment must match. The traveler must be able to get help. PIVOT signs off before we expand.

Let’s talk through the details

Here’s how we would deliver it.

Our response to your requirements.

Pure Strategy would lead delivery, covering design, engineering, provider connections and testing. We would agree priorities, build in short steps and show PIVOT progress each week. Every step has a clear completion check.

At kickoff, we would name the people responsible for each part of the build and agree their assignments. PIVOT's decision-maker would work directly with our team on product and operating choices.

We would plan the Phase 1 web launch around provider access and the first client's needs. First confirm the operation, then build the booking, test it with the team and launch with that client. Native apps are not part of this first launch or the $34,000 working estimate.

The earlier one-month concept was a starting point for a small pilot, not a commitment for the full RFP. We would agree the web milestones separately from the Phase 2 app schedule. Moving the RFP's concurrent native-app delivery into Phase 2 needs PIVOT's agreement.

Your RFP lists October 23 for submission and November 2 for the decision, without stating a year or launch date. We would turn the agreed scope and dependencies into delivery milestones with PIVOT.

Pure Strategy would look after the software: monitor it, fix problems, maintain it and keep provider connections working.

PIVOT and its travel partner would handle flight changes, cancellations and disrupted trips. We would make the traveler contact and handoff clear in the product. The specific servicing owner remains to be agreed.

Before launch, we would agree support hours, escalation, response times and out-of-hours costs. Any 24/7 coverage would need to be explicitly scoped and agreed.

A traveler must be able to find a flight, confirm its current price, pay and receive the ticket and confirmation. PIVOT must see the booking, check the money and get changes handled by the right person.

We would test this with the provider's test system, then with approved live bookings. We would also check failed payments, duplicate requests, separate client access and the website in desktop, iPhone and Android browsers. Native-app testing belongs to the separately agreed Phase 2.

PIVOT should approve the complete process before we open it to more travelers.

Keep the shared product secure, reliable and working well for every client. Then add services PIVOT can choose to sell. Unique requests get their own agreed scope.

We also need a clear way to test updates, release them safely and undo a change if it causes a problem. Those responsibilities should be agreed, not left until something breaks.

Based on: Strategy §§6, 10, 12–14, 20–21 · RFP project approach & timeline