Booko's FAQ says it works with Mindbody, Mariana Tek, Boulevard, Zenoti, TicketingHub and BigQuery, and that "your team changes nothing". But the sitemap has exactly one integration page, /partners/marianatek, and even that page is not linked from the homepage. An owner who searches "Mindbody dynamic pricing", "Boulevard pricing integration" or "Zenoti dynamic pricing" has nothing on booko.com to land on, and Mindbody's own Dynamic Pricing article is what they find instead. The integrations are Booko's main promise ("no switching") and its main distribution, and five of the six are invisible.
First action
Copy the Mariana Tek page into a Mindbody version and list the data each side exchanges.
How to measure it
Integration-page demo requests
- Now
- –
- Target
- 15 a month
- By
- 90 days
Steps
Write the template
Turn the Mariana Tek page into a fixed outline: data in, data out, setup, controls, memberships, verticals, demo CTA.
Founding Growth Lead 1 day
Confirm the facts per system
For each of the five systems, check exactly what the live integration reads and pushes today, and what is still in development.
Founding Engineer 2 days
Write Mindbody first
Include a fair section on how whole-schedule pricing differs from Mindbody's own per-class Dynamic Pricing.
Founding Growth Lead 2 days
Write the other four
Boulevard and Zenoti framed for med spas and salons, TicketingHub for tours and attractions, BigQuery for in-house data teams.
Founding Growth Lead 1 week
Link and index
Add a /partners index, link it from the FAQ answer and footer, add the pages to the sitemap and submit them in Search Console.
Founding Engineer 1 day
Tag the demo requests
Pass the system name into the demo booking so each lead arrives labelled.
Founding Engineer 2 hours
Tell the partners
Send each platform's partner team the page link and ask how they list integration partners.
Founders 1 week
Measure and expand
Track impressions, visits and demos per page monthly; add the next system when a deployment ships.
Founding Growth Lead monthly
Why it works
Publish /partners/mindbody, /partners/boulevard, /partners/zenoti, /partners/ticketinghub and /partners/bigquery using the Mariana Tek page as the template, and add a /partners index linked from the FAQ and footer. Each page answers the same questions: what Booko reads (schedule, bookings, cancellations), what it pushes back (prices, promo codes, credits), how long setup takes, which controls stay with the operator (floor, ceiling, exclusions, pause), how memberships and packs are treated, and which verticals use that system (Boulevard and Zenoti for med spas and salons, TicketingHub for tours and attractions). The Mindbody page also explains plainly how whole-schedule pricing differs from Mindbody's built-in per-class Dynamic Pricing. Every page ends in a demo request tagged with the system, so the founders know which integration each lead needs before the call.
Searches that name a booking system are the highest-intent searches in this category: the searcher already runs the software and wants to add pricing to it. Integration pages also give each platform's partner team, and AI assistants answering "does X work with Mindbody", a page to point to.
Ready to use
ChecklistIntegration page outline
[ ] H1: Dynamic pricing for <System>, with no switching [ ] What Booko reads from <System> (schedule, bookings, cancellations) [ ] What Booko pushes back (prices, promo codes, credits) [ ] Setup: who does the work and how long it takes [ ] Controls: floor, ceiling, excluded dates and services, pause [ ] Members and class packs keep their terms [ ] Who uses it: the verticals on <System> [ ] How it differs from <System>'s own pricing tools (where they exist) [ ] Billing: flat subscription, no per-booking fee [ ] Demo request tagged with <System> [ ] Linked from /partners, the FAQ and the footer; in the sitemap
Risks and how to handle them
Overstating what an integration does today
Have the engineer who built it sign off each page, and mark features in development as such.
Partners object to the comparison with their native feature
Keep the Mindbody section factual and complementary: Booko works inside Mindbody rather than replacing it.
Evidence
- Your websiteHomepage FAQ: "Which systems do you work with?" names Mindbody, Mariana Tek, Boulevard, Zenoti, TicketingHub and BigQuery, and says "We do the integration work, and your team changes nothing." The agents watch booking history plus weather, local events, school calendars, paydays and competitor promotions. Operators set a price floor and ceiling, exclude dates and services, choose customers who always see the standard price, keep member and class-pack terms, and can pause at any time. The page lists SOC 2, HIPAA and enterprise security, and an integration diagram of eight system types, including Ticketing and Tours and Clinic and EMR.Source
- Your websiteSitemap (14 URLs, checked November 9, 2026): the homepage, /mission, five /careers pages, six /legal pages and one integration page, /partners/marianatek. There are no blog, pricing, case-study, use-case or other integration pages, and the homepage does not link to the Mariana Tek page.Source
- Your websiteMariana Tek integration page: a push-model integration that needs "no development work"; incentives are promo codes, complimentary credit grants and adjusted pricing; it supports credits and memberships; Booko is "not a marketplace or aggregator"; billing is a flat SaaS subscription with no revenue share or per-transaction fee. It describes Booko as building tools for fitness and wellness businesses, says branded-app support is in development, and gives the old bookoapp.com domain (which now redirects to booko.com) and a founder's personal email as the contact. No metrics or customer examples.Source
- Competitor researchMindbody's own Dynamic Pricing "automatically adjusts class prices to meet real-time demand" using "past attendance, time of day and day of the week"; Mindbody suggests putting 30% to 75% of the class schedule on it, with a floor up to 50% below the drop-in price and a ceiling 30-35% above.Source
- HiringFounding Growth Lead (San Francisco or New York; $90K-$150K plus 0.50-1.50% equity): "Design, run, and iterate on growth experiments across product, marketing, and distribution channels"; help build the growth playbook; define north-star metrics such as signups, activation, retention and referral loops; run outbound and inbound campaigns; manage content, paid, partnerships, community and SEO; prepare decks and one-pagers for major sales meetings; "Data-obsessed, measuring everything".Source