Where the conversation stands.
On June 23, Genesis and Brian Teichmann met for a two-hour discovery session to review the initial $10K proposal for Book My Grand. The conversation went deeper than expected. Brian surfaced three concerns that reframed the scope: platform capacity beyond the MVP tier, calendar integration with Airbnb, Vrbo, Outdoorsy and other channels, and the affiliate versus direct booking model for vendor economics.
On June 25, Genesis held an internal technical review with the engineering lead, Denderson. The purpose of that review was to translate Brian's questions into what is actually buildable, at what cost, on what timeline. The output of that session is what you are reading now: three viable paths, priced honestly, with the technical reality of what plugs into Book My Grand and what does not.
The purpose of this proposal is not to close a deal. It is to align on the right scope before either side commits. Genesis will not sell a promise the engineering team cannot deliver at the price quoted. The recommendation stands at Plan A, and the reasoning is laid out in full below.
Why this proposal exists.
The vision is bigger than the MVP tier.
Brian is not asking for a booking site with an AI concierge on top. Brian is asking for a Grand Lake equivalent of Booking.com, an aggregator that pulls together vacation rentals, boat tours, fishing guides, restaurants and lodging into one clean experience. That is a platform, not a landing page.
The original $10K scope still makes sense as a starting point. It does not make sense as the full answer. Selling it as the full answer would be dishonest.
Three tiers, three price points, three risk profiles.
Engineering broke the problem into three levels of ambition. Level one puts Book My Grand in the water this quarter for $10K. Level two builds a real API-integrated platform for $40K–$50K over 8–14 weeks. Level three builds the full Booking-class platform for $400K+ over 6–12 months.
Genesis stands behind Plan A as the recommendation for this stage. Plans B and C are on the table with full transparency about what they cost and what they require from Brian on the vendor and capital side.
Site plus AI Agents.
A professional Book My Grand website with an admin panel where Brian manually curates up to 10 vacation packages, backed by the same 15 AI agent team demonstrated live in the June 23 meeting.
- → 15 specialized AI agents (concierge, ops, marketing, SDR, admin)
- → Professional Book My Grand website with custom domain and SSL
- → Admin panel to publish up to 10 curated vacation packages
- → Marketing landing page featuring Brian's ready-made vacation packages for direct-to-traveler sales
- → Inline chat concierge trained on Book My Grand voice and inventory
- → Stripe checkout with lead handoff to Brian for booking confirmation
The purpose of Plan A is validation. Brian tests the concept in-market, learns which packages actually sell, builds cash flow, and earns the right to invest in Plan B with real data behind the decision.
Site plus real API integration.
A custom platform with live API integration into one B2B supplier that Brian contracts directly. This is the tier where the site actually reserves inventory in real time on the visitor's behalf.
Plan B is not the recommendation today because it commits capital before demand is validated. When Plan A produces real bookings and a clear supplier fit is identified, Plan B becomes the next contract.
Full platform build.
A Booking.com class platform built from the ground up by a dedicated team of 5 to 10 engineers. This is what Brian described as the long-term vision in the June 23 meeting. Genesis is transparent about what it costs to actually deliver that.
Plan C is not framed as a commercial proposal. If Brian is interested in exploring it, Genesis will arrange a separate exploratory session between Brian, Denderson and Anna (as translator) to walk through what a build of this scale actually looks like, on staffing, architecture, capital and time. That call is discovery, not sales.
The three paths, compared honestly.
| Plan A · Recommended | Plan B · Phase 2 | Plan C · Exploratory | |
|---|---|---|---|
| Investment | $10K one-time | $40–50K Estimated · scope-dependent · supplier separate | $400K+ realistic $600K–$1.2M |
| Timeline | 3–5 weeks | 8–14 weeks | 6–12 months to MVP |
| Brian's role | Curates packages, closes bookings manually with local vendors | Finds and signs the B2B supplier contract independently | Brings investor capital, or proves traction in Plans A and B first |
| Ideal for | Starting now, validating market demand, building cash flow | Scaling with a supplier already contracted, real API bookings | Owning the platform end-to-end, targeting M&A or licensing exits |
| Risk profile | Low | Medium | High |
| Genesis recommendation | Start today | Phase 2 after validation | Exploratory call only |
What plugs into Book My Grand, and what does not.
Brian's biggest question in the June 23 meeting was: can Book My Grand actually reserve inventory across every category the visitor might want? Below is the technical reality, verified in the June 25 review. Roughly 80% of the mix is achievable via three B2B APIs, at the Plan B tier.
Coverage confirmed for Grand Lake boat operators and Branson tour providers. Documented REST API, no volume minimums, 25% API partner commission.
650K+ Vrbo properties plus 800K hotels in one integration. Vrbo covers the Grand Lake market. Partner Collect model keeps Brian as merchant of record.
80K+ hotels across the Americas including major brands in Branson and Tulsa. REST API with a free sandbox tier for prototyping.
Three overlapping options for tours and activities. Viator is the largest, GetYourGuide has the cleanest API, Bokun connects directly to the TripAdvisor marketplace.
Adds international reach for foreign visitors coming to the lake. Commission model, 4–8 weeks approval window.
Not direct inventory sources for Brian, but the tools property managers use. Genesis can encourage Grand Lake PMs to publish via these channels to feed the Vrbo pipeline.
Airbnb does not offer a bookable API to third parties. Only workaround is iCal read-only synchronization with 15-minute to 4-hour latency, which introduces overbooking risk.
No single API covers restaurant reservations at Grand Lake. Each vendor would need OpenTable, Resy or Tock integration individually, and coverage in the region is thin.
Outdoorsy and RVshare operate as closed marketplaces without partner APIs. Coverage of this category on Book My Grand would require manual curation and lead handoff.
Building proprietary channel management, PMS, direct vendor contracts and a global-class reservation engine is a 6–12 month build. Genesis will not price this into Plan A or B because it is not honest to do so.
Genesis recommends Plan A.
Plan A puts Book My Grand in the water this quarter for a defensible ten thousand dollars. It gives Brian a professional site, a full AI agent team, and a working admin panel to test ten curated packages against actual demand. It generates the market signal every subsequent decision should rest on.
Plan B is the natural next contract, but only after Plan A produces real bookings and a supplier fit is identified with data. Committing $40K to $50K before that signal exists would be investing on a hypothesis, not a result.
Plan C stays on the table as an exploratory conversation with Denderson and Anna directly, whenever Brian is ready to think about the platform build at that scale. It is not on the table as a commercial proposal for this stage.
This sequence, Plan A now, Plan B after validation, Plan C as a strategic decision later, protects Brian's capital, protects Genesis's ability to deliver, and keeps every stage of Book My Grand aligned with real evidence from the market.