Multiple systems.
Built together.

It comes down to whether the systems need to share infrastructure. Building a new website while also adding loyalty and outings benefits from one set of foundational decisions: shared data sources, shared email infrastructure, shared analytics. Doing them as separate Reads means three discoveries, three foundational decisions, three handoffs. The Yardage Book makes those decisions once.

We don't advise that because mid-engagement scope changes break the coordinated sequencing that makes the Yardage Book work in the first place. If you realize during the engagement that you need an additional system, the cleanest path is to scope it as a Read after the Yardage Book delivers or fold it into a Loop afterward.

The eight-to-twelve-week range covers the vast majority of Yardage Books. If your specific build is going to take longer because of scope complexity or integration depth, we'll know during scoping and price accordingly. If something unexpected stretches the timeline mid-build, we'll work through it together. We don't bill extra for our own scoping mistakes.

It depends on the systems. Some share infrastructure and need to be built in a specific order (the website usually comes first because email and analytics depend on it). Others can run in parallel. We map the sequence during the discovery phase and keep weekly check-ins running across each track.

We don't promise specific revenue numbers, because too much sits outside the systems themselves for any honest guarantee to be possible. What we do guarantee is that the systems get built to scope, on time, with before-and-after metrics measured so you can see what actually changed.

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.