05 / Make the next client easier

The second client shouldbe easier than the first.

We would start with a mobile-friendly website that works in iPhone and Android browsers. That is the $34,000 Phase 1 scope, not two native apps. Later, separately priced apps can use the same booking system. Each organization keeps its own experience and private information.

Start on the web. Build apps on the same foundation later.

EXAMPLE 05

Phase 1

Mobile web

$34K working estimate

Phase 2

iPhone app

Separately priced

Phase 2

Android app

Separately priced

Native apps are not included in $34,000.

Use the same booking system. Keep access separate.

Each client sees its own records. Keep a history of important changes.

Set up clients
Book flights
Take payments
Help and report
Use the providers, don’t become one

Their records stay private. Updates still get through.

Keep client information private. Retry failed updates safely.

Switch a provider, not the whole product

Travel, payments, customer records and support

Only the access each person needsProtect card detailsTest for busy events

Phase 1 is mobile-friendly web within the $34,000 working estimate. Native iPhone and Android apps are Phase 2, with separate scope, pricing and dates. We would agree this phasing with PIVOT against the RFP's requirement for both apps to launch together.

01

Same product. Their records stay private.

Every organization uses the same foundation. Its records and access stay separate.

02

Add capacity where it's needed

Keep search, bookings and payments separate enough to handle more demand without rebuilding everything.

03

Apps come later, with their own budget

Native iPhone and Android apps are not included in $34,000. We would plan them together in Phase 2, after the web booking proves itself.

Let’s talk through the details

Here’s how we would deliver it.

Our response to your requirements.

We would start with a mobile-friendly website and one shared system for clients, events, flights, bookings, payments and reports. Travelers use it in their iPhone or Android browser, without downloading an app. Native apps can connect to that same system in a separately scoped and priced Phase 2.

Each travel provider gets its own connection, so changing a provider doesn't require rebuilding the traveler experience. We would agree where the system is hosted and any location requirements before building.

We would give each organization access only to its own information, and staff only the access their job needs. We would protect stored and transferred information, keep sensitive keys out of the traveler experience and use the payment provider's secure handling of card details.

Our delivery plan includes records of important changes, tested backups, rules for keeping or deleting traveler data and a response plan for problems. Information about minors needs particular care.

We would build and test these protections before launch, and agree any formal audit or certification requirements as part of scope.

We would add clients to the same product, while keeping their information separate. Behind the scenes, booking updates can be handled without slowing down the traveler's search.

Our engineering plan covers provider limits, safe retries and protection against duplicate bookings. Before opening a busy event, we would test the expected demand and monitor the system.

We would size the first release around agreed event demand, then use real activity to set any future usage limits or fees.

Our $34,000 working estimate does not include native iPhone or Android apps. Phase 1 is a mobile-friendly website, like the traveler experience in the demo. It works in phone browsers without app downloads.

Your RFP asks for iPhone and Android apps to launch together. A mobile website does not satisfy that native-app requirement. Our proposed sequence is to prove the web booking first, then build both apps together in Phase 2. We would agree that change in phasing with PIVOT before signing.

Native apps need their own scope, price, testing, app-store submissions and release dates. No native-app price or delivery date is included in this proposal. They would reuse the booking foundation rather than start again.

We would build on the same foundation as PIVOT adds hotels, experiences, event tools, partner management, money tracking, traveler support and useful recommendations.

Improvements to the shared product can help every client. Optional services can be turned on for the clients who want them. A unique request gets its own agreed scope and price.

Based on: Strategy §§10, 15, 18, 23–24 · RFP technical requirements