Custom Registration Integration
Brooklyn Basketball

The custom integration is $5,000 as a one-time fee, covering 75 total hours of development. The first 25 hours — subdomain configuration, header and footer suppression, dark mode compatibility, and Next.js QA — are included at no charge as part of Playbook's integration partnership model. The remaining 50 billable hours are priced at $100/hour, and the $5,000 figure covers them in full with no surprises. There are no recurring fees tied to the custom dev work itself; it is a flat, one-time project cost that sits separately from the Playbook platform subscription. Program configuration items — session minimums, stacking bulk discounts, early bird pricing tiers — are also included within the 75-hour budget, so the $5,000 is the all-in number for everything described in this scope. Schedule a demo to discuss platform subscription plans alongside the custom dev cost.

Phase 1 — subdomain setup, header suppression, dark mode compatibility, and Next.js QA — can typically be completed in one to two weeks from kickoff, depending on DNS propagation timing and client-side review cycles. Phase 2 iFrame embeds are more QA-intensive: the calendar view alone carries an estimated 2–3 week testing window because live schedule data needs validation across day, week, and month views on both desktop and mobile. Phase 3 full API mode is a future-phase project whose timeline depends on Brooklyn Basketball's engineering team availability and their own frontend build schedule, and is best planned after Phase 2 has run stably in production. For a club moving through Phase 1 and Phase 2 sequentially, the typical total range is four to six weeks from kickoff to live embedded checkout. Any scope confirmed under the additional requests section is delivered within the same 75-hour budget and does not extend the timeline unless it materially adds to the build surface.

Yes. Session minimums are enforced at the cart level, not surfaced as instructional text — ages 6–8 are blocked from selecting more than one day per week, and older age groups cannot complete checkout without selecting a two-day minimum, enforced in the registration flow itself. Multi-tier bulk discounts for after-school programs stack automatically: 2 days triggers 5% off, 3 days triggers 10% off, and 4 days triggers 15% off, each applied the moment the cart hits the threshold without any manual override by staff. These discount rules are scoped specifically to the after-school category — they do not apply to summer camps, skills academy sessions, leagues, or other program types, so pricing stays clean across Brooklyn Basketball's full program mix. Early bird pricing is handled via a secondary pricing tier rather than a late fee label, so deadline-based price increases appear as a natural price update rather than a penalty, which avoids the friction that late fee language creates for families still deciding. All of these configurations are included within the 75-hour project budget and are treated as prerequisites before Brooklyn Basketball's first season goes live on the platform.

The iFrame embed wraps Playbook's existing registration UI inside a frame that sits natively within your site — it inherits your page's navigation and chrome while the actual registration interface is rendered by Playbook's servers. This is the fastest path to a seamless registration experience, requires zero frontend development on Brooklyn Basketball's side, and is exactly what Phase 2 delivers. The full API mode, by contrast, exposes all program data, registration submissions, payment processing, and calendar endpoints as raw API calls — Brooklyn Basketball's engineering team builds the complete frontend in Next.js or any other stack, and Playbook handles only the backend data layer and payment transaction logic. API mode gives Brooklyn Basketball total control over every interaction design decision: animations, typography, accessibility patterns, and edge-case UI states in the registration flow. The tradeoff is build time and engineering resource cost: iFrame is weeks, full API mode is typically months of dedicated frontend development. Phase 3 adds $3,000 to the project and is recommended only after Phase 2 has run stably in production long enough to confirm the data flows before committing to a full frontend rebuild on top of them.