The Read

One system.
Built end to end.

The Read is a focused four-to-six-week build of one named system. The scope is defined, the deliverables are clear, and the end date is on the calendar before we start. Most engagements start here.

Get a Free Audit → See Pricing →
How It Runs

Three phases. Four to six weeks.

1
Week 1
Discovery and Baseline
We dig into the current state of the system we're building, capture baseline numbers from your tee sheet, POS, or whatever's running, and lock scope before any build work starts.
2
Weeks 2-5
Build
The named system gets built end to end. That includes the tools, the sequences, and the integrations needed to make it work. Weekly check-ins keep the build on track and the surprises small.
3
Week 6
Launch and Handoff
We launch the system, train the team on it, and hand off documentation so the work lives on without us in the room.
What's Included

What you get with every Read.

Every Read includes the same engagement-level scope, no matter which named system you're building.

✓ Kickoff and discovery session
✓ Baseline metrics captured before we start
✓ Weekly progress check-ins
✓ One named system, built end to end
✓ Documentation and handoff materials
✓ Light team training on the new system
✓ 14-day post-launch Q&A window
✓ Optional transition into a Loop engagement
Pricing & Terms

What it costs.

$5,000 to $8,000
Billed 50% upfront, 50% on delivery
The format
The engagement is priced upfront. There's no hourly billing and no scope creep surprises. You'll know what you're paying before we start.
The terms
You pay half on signing and half on delivery. The first half locks the calendar and starts the work. The second half closes the engagement out.
What moves the price
Three things move the price. The first is which named system is being built, since some require more setup than others. The second is the state of your current infrastructure, since a clean foundation builds faster than a messy one. The third is the number of integrations needed with existing tools like POS, tee sheet, or email.
What Gets Built

Systems we typically build as a Read.

Outings & Events System
The outings line leaks at most courses. We build the inquiry-to-booked funnel that catches the revenue you're losing.
Learn more →
Loyalty & Retention System
Most courses treat their customer base like a transaction log. We turn it into a relationship system that earns repeat play.
Learn more →
Lessons & Programs System
Lessons fill by referral. Juniors fill if the pro sent the email. We build a real funnel underneath both.
Learn more →
If you're looking for Online Presence or Indoor Golf Marketing OS, those typically anchor the Yardage Book.
Who It's For

Is a Read the right call?

A Read fits when:
  • ✓ You've got a hunch about which revenue line needs the work first.
  • ✓ You want a defined start, defined scope, and a defined end.
  • ✓ You'd rather build one thing well than three things at once.
  • ✓ You want pricing locked before the work starts, not billed by the hour.
A Read isn't the right call when:
  • − You need foundational work across multiple systems built together. Consider the Yardage Book.
  • − You want ongoing month-to-month support, not a project. Consider the Loop.
  • − You're pre-launch or sub-12 months in operation and don't have baseline numbers yet.
FAQs

Questions we hear a lot.

How do I know which system to build first?
We work it out together on the free audit call. The answer typically comes from where the revenue is leaking hardest, which line you've been putting off, or which one you've already half-started and never finished. We'll point you in a direction. You decide.
What if my situation doesn't match one of the five named systems?
Email us anyway. The five systems cover the majority of what independent courses and sim facilities actually need, but golf has real edges and yours might be one of them. Sometimes the right move is to scope something custom inside a Read. Sometimes it's to wait until the Yardage Book makes more sense.
What happens after the 6 weeks?
You own the system. You run it. If you want help running it past the build, we can continue the partnership with a Loop engagement. Either way, we leave you with documentation, training, and a 14-day Q&A window in case something needs a quick fix or you have a question.
How is the Read different from the Yardage Book?
Scope. The Read is one named system, built end to end, in four to six weeks. The Yardage Book is two or three systems built together, in eight to twelve weeks, when the foundational decisions need to be made once instead of three separate times. If you're not sure which fits, we'll figure it out on the audit call.
Do you offer guarantees?
We don't promise specific revenue numbers because too much sits outside the system itself for any honest guarantee to be possible. What we do guarantee is that the system gets built to scope, on time, with before-and-after metrics measured so you can see what actually changed.
Can I pay in monthly installments instead of 50/50?
The standard is half on signing and half on delivery. If your accounting cycle makes installments easier, let us know on the audit call and we'll talk through it. We're not too strict about the exact structure as long as the engagement is real and the work is funded.
Let's Talk

Ready to read your line?

Get a free audit. We'll walk your setup, tell you where the revenue's leaking, and point you at the system most likely to plug the gap. We don't pitch and we don't pressure.

Get a Free Audit →