10 / Let's get the first client live

Let's getthe first client live.

We have a clear recommendation and a team to lead the build: prove the mobile-friendly web booking first, then scope and price native apps separately. With PIVOT, we would align on that phasing, the first client, flight provider, payments and traveler support. Those decisions give us the milestones to start delivery.

How we would work, who does it and what we align on at kickoff.

EXAMPLE 10

How we'll work

Kickoff to first live booking ≈ 30 days

One sprint. Thirty days.
A real booking at the end.

Here's the whole month on one page. Steps overlap, so we never sit waiting. You see progress every Friday.

Week 1Week 2Week 3Week 4

Day 1–5

Gather what we need

Flight provider access, Nexion and Concur contacts, event dates, brand files and travel rules.

Us + PIVOT

Tap any step to see what happens. The clock starts once flight provider access is in place. Native apps come after, in Phase 2.

The team doing the work

Patrick Murti

Patrick Murti

Product & frontend

The screens your travelers and team actually use.

Patrick Banjo

Patrick Banjo

Backend & data

The logic, payments and records underneath.

Kevin Hsu

Kevin Hsu

Integrations

Connects the flight provider and the tools you already rely on.

Phase 1 flight log

Seven stops to the first booking.
Here's when we'll need you.

Tap any stop to see what we're building and what we'll ask of PIVOT's team.

Leg 01 · Days 1–5

Get cleared for takeoff

PIVOT picks the first organization and event, and hands us access to the travel and business accounts it already has.

What we do

Set up the project, check every access works and load the first event.

When we need PIVOT

Kickoff call (about 45 min): choose the first client and event, share brand files, and give us access to your flight provider, Nexion and Concur.

Hotels, event tickets and native apps come after Phase 1. PIVOT owns the travel relationships; we build and run the software. Time asks are our estimate.

Our kickoff conversation

01

Choose the first client and event

The organization, travelers and first mobile-friendly web booking

PIVOT

02

Confirm the flight and ticketing partner

Agency relationships, approved booking access and Nexion’s role

Pure Strategy + PIVOT + provider

03

Set the payment and traveler-support plan

Who charges the card, receives the money and handles changes

Pure Strategy + PIVOT + partner

04

Map the booking and customer records

Concur, customer records and the numbers finance needs

Pure Strategy + PIVOT

05

Agree scope and delivery milestones

Phase 1 web scope; separate Phase 2 app pricing and dates; ongoing fees and software rights

Pure Strategy + PIVOT

We would lead the build. These decisions align it with PIVOT’s travel operation.

Our proposed kickoff agenda and participants. We would confirm the named owners, access and launch terms with PIVOT.

01

Which client goes first?

Choose the organization, event and travelers for the web launch. Agree that native apps follow in a separately priced Phase 2.

02

Who owns each step of the booking?

We need names for ticketing, taking payment, checking the money and helping with changes.

03

We're ready for the next conversation

We bring the recommendation, design, demo and working cost model. Next, align on scope, supporting references and delivery milestones.

Let’s talk through the details

Here’s how we would deliver it.

Our response to your requirements.

Which organization and event should we start with? Who is traveling, and where should the booking be made?

We need to understand your existing agency, reservation-system and ticketing relationships, including any industry approvals. Then confirm which flight provider lets us connect, issue tickets and make test bookings.

We also need to agree Nexion's role, how Concur fits and where the main customer record lives.

With PIVOT and the travel partner, we would agree who charges the card, receives the money and commissions, handles changes and refunds, and provides traveler support.

We would also confirm domestic and international service fees, client pricing and reporting responsibility. Before launch, we would test the support handoff using an approved live booking, so the traveler knows where to turn.

This presentation sets out our recommendation, proposed system design, traveler demo and working fee model. We would use the next conversation to agree Phase 1 web scope, costs and delivery milestones. The $34,000 estimate excludes native apps. We would agree the proposed Phase 2 phasing against your RFP's concurrent iPhone and Android requirement, then scope and price the apps separately.

Supporting project examples, references and testimonials remain to be supplied with permission. We would also confirm provider access and validate the booking plan with the chosen travel partner.

Your RFP lists October 23 for submission and November 2 for the decision, without stating a year. We would align the next steps with PIVOT's decision process.

We bring product, design and engineering experience from Google, Meta, Microsoft and Samsung, paired directly with PIVOT's sports travel expertise. Our team would lead the build from the traveler experience through provider connections, testing and launch.

Our recommendation starts with a complete booking, not a broad collection of travel features. One organization proves the foundation; the next uses the same product with its own brand and events.

PIVOT keeps its client relationships, controls pricing and retains its travel-business upside. Our fees separate the build, ongoing technology and outside-provider costs.

The difference is the competition context: we know why people are traveling and design around it. AI supports useful suggestions and reliable answers, without becoming the main attraction. That's the product we want to build with you.

Based on: Strategy §§19–21, 23 · RFP submission & evaluation