Two ways in

We'll fit how you already run the place. Or we'll run it for you.

There are two versions of this and the difference is where your data lives. Which one you get is a discovery answer, not a sales answer, and we would rather find out than guess.

1

Connect what you already run

If your tee sheet, your POS and your range system expose an API - and if your agreements allow us access to it - the app sits on top of what you already have. Nothing gets ripped out. Your tee sheet stays the tee sheet, your POS stays the POS, and the golfer gets one place to do all of it.

Whether this door is open depends on your contracts and on what those systems actually expose. We don't know yet, and anyone who tells you they do hasn't read them either.

2

Or we build it and host it

If the systems won't open, or you'd rather not keep paying for them, we build the pieces ourselves and host them, shaped to exactly how you run the property. Not a configuration of somebody else's product. Yours.

This is the bigger project and we would say so before you signed anything, not after.

Either way, the thing we're building is the same: one record of your golfer. Not five integrations - one record. Whether your existing tee sheet feeds that record through an API, or this becomes the sheet of record itself, changes the build. It doesn't change the product, and it doesn't change who owns the customer at the end of it. You do.

The first thing to look at is your tee sheet contract.

You book through TeeItUp, operated by GolfNow. Those agreements often carry inventory commitments and exclusivity terms, and they decide whether we can be a booking channel into your existing sheet, or whether booking has to work differently. We don't know your terms. Nobody should quote you a scope or a timeline before that question is answered, and we're not going to. We'd rather raise that with you now than discover it after you've signed something.

Four phases, and the first one ships nothing.

Phase 1

Discovery

Answer the questions that change the shape of the project. Contracts, APIs, the Inrange conversation, alcohol policy, and four hours watching a Saturday morning and a Thursday range night. Nothing golfer-facing ships in this phase, and that's correct.

Phase 2

MVP

A golfer can do their whole visit in the app, and your staff can run the day from the console. This is the phase that has to be genuinely good - a mediocre first version poisons adoption and there's no second launch.

Phase 3

Depth

The features that make golfers stay and stop your staff using spreadsheets entirely.

Phase 4

Platform

Wearables, cart screens, coaching and fittings. Only once the core is proven.

1.1 Book & BelongBooking, check-in, membership, the staff Today view
G-12G-51C-01
1.2 Feed & RangeOrdering, kitchen display, runner app, bay booking
G-33C-06R-01G-37
1.3 PlayGPS hole view, scorecard, offline round
G-22G-24
1.4 CompeteEvents, registration, live leaderboards, season standings
G-43G-46
1.5 Prove ItAnalytics, weekly digest, attach-rate reporting
C-22

GPS is third on purpose. It's the most exciting piece and the most expensive, so booking and ordering are already earning while the hard mapping work is in flight. If it slips, the product still works.

What actually exists

Every screen in the product, on one page.

The ones that are built are rendered. The ones that aren't are ghosted, with the same ID and the same one-line purpose as the rest. Nothing is hidden and nothing is padded - a wall showing only what exists would misrepresent this in both directions, because it hides the plan and flatters the progress.

Counts are read off the cells on that page, not typed into a caption. Tap a flow there to see which screens it touches, and in what order. They're the same three you tapped in the prototype.

Open the wall

Who's asking

[CK] Phase Zero Labs, in one paragraph.Three or four sentences. Concrete, not puffed: no history, no bios, no logos, no mission statement. The prototype is the credential; this only has to establish that a real outfit is behind it.

We'd like to build this with you, not sell it to you.

Palm Beach National would be the first course on this platform and our design partner. That means favourable terms, and it means real access - time with your staff, a Saturday morning, a Thursday range night, and your actual numbers instead of our placeholders. What we want back is a reference and a written case study once it works.

As a design partner you also get to decide which of the two doors we go through - fit what you already run, or let us build and host it. That call comes out of discovery with you, not out of a proposal written before we've seen your contracts.

If you run more than one course.

This was built as a platform, not as one course's app. Everything you've tapped through is driven by tokens - the brand, the mascot, the programme names, the daypart labels. A second course is a value swap, not a rebuild. If you're looking at this for a portfolio rather than a property, that changes the conversation in your favour and we should have a different one.

The same three screens under a different brand, as proof.

Thirty minutes, and a look at your tee sheet contract.

That's the whole ask. Not a project, not a budget, not a decision. Thirty minutes to walk you through this properly and hear where we've got your property wrong - and a look at the tee sheet agreement, because it's the one thing that could change the shape of all of it and neither of us should guess at it.

[CK] Contact details.Calendar link, email and phone go on the three buttons above.

Concept proposal - not an official Palm Beach National product.

Back to

The idea, in ninety seconds.

Start over

Concept proposal - not an official Palm Beach National product. Screen content is illustrative. Built by Phase Zero Labs on the Nineteen design system.