U.S. Founding Academy Program · Selecting 3–5 academies
Turn one high-friction academy journey into a measurable operating workflow—in 90 days.
ChatPress connects the minimum signals needed to work on one bottleneck: inquiry to trial, trial to enrollment, attendance to renewal, or member reactivation. Your current booking and payment systems stay in place.
This is a paid, selective design partnership. Applying does not guarantee acceptance.

One bounded engagement
One location. One journey. One primary KPI.
The Founding Academy Pilot is deliberately narrow so both teams can establish a baseline, operate a real workflow, and review the evidence within 90 days.
One U.S. location
A single operating environment with accountable owners.
One customer journey
One bounded handoff where the relationship currently stalls.
One primary KPI
Defined numerator, denominator, source of truth, and observation window.
Up to two integrations
The minimum event connections required for the chosen journey.
Biweekly reviews
Evidence, adoption, exceptions, and next decisions reviewed together.
Human approval
Logging, approval boundaries, and explicit stop conditions remain visible.
Secondary measures may be used for diagnosis, but the Pilot is evaluated against one primary KPI agreed before launch.
Journey selection
Choose the one journey that matters most now.
Identify where qualified inquiries go silent and establish a reviewable follow-up workflow.
Connect completed trials, operator context, follow-up, and the evidence supporting an enrollment decision.
Use attendance, participation, entitlement, and operator review to make renewal risk visible earlier.
Define which inactive members may be appropriate for an approved reactivation conversation.
The 90 days
Map, connect, operate, and decide.
Baseline & Map
Document the current journey, owners, systems, exceptions, source of truth, and comparison baseline.
Connect
Connect the minimum required events from no more than two existing systems after feasibility review.
Operate
Run the bounded workflow with an assigned operator, human review, activity logging, and stop conditions.
Review
Compare observed results with the baseline, document limitations, and decide whether an annual deployment is justified.
Before kickoff, both teams define the evidence that would justify an annual deployment. Conversion requires a separate written agreement; there is no automatic renewal.
Not a rip-and-replace project
Keep the systems that already do their jobs.
Your booking and payment platforms remain the systems of record. ChatPress connects only the events and actions required for the selected journey.
Data migration, booking replacement, and payment replacement are not included. Connector availability, access method, write-back permissions, and security requirements are reviewed during qualification.
Built in real operations, labeled honestly
The workflow foundation is live. Independent U.S. validation is next.
ChatPress is already used inside Ninja Taiwan Academy and YizongTW, revenue-generating businesses operated by the founding team.
These are founder-operated production environments—not independent U.S. customer traction. The Pilot tests whether a bounded package transfers into an independent academy.
Participation requirements
A strong founding partner can commit to the operating work.
- An owner-led U.S. academy with one location available for the Pilot.
- A decision-maker who can approve scope, access, and commercial terms.
- A named operator responsible for day-to-day execution and biweekly reviews.
- Baseline data that is available or can be reconstructed before changes begin.
- A paid Pilot budget that is allocated or can be approved before kickoff.
- A genuine annual deployment path if the Pilot demonstrates sufficient operating fit.
Founding Pilot application
Bring one journey, one accountable operator, and one measurable decision.
We are selecting 3–5 founding academies for the initial U.S. program. The application helps us assess operating fit, baseline readiness, connector feasibility, decision ownership, and budget readiness.
Do not submit customer records, passwords, API keys, payment-card data, health information, or other confidential data.
Not operating in the United States? Start a general deployment inquiry.
Application received.
This does not confirm acceptance into the program. We will review operating fit, baseline readiness, connector feasibility, decision ownership, and budget readiness. If there is a fit, we will contact you about a qualification call.
Please do not send customer data or system credentials at this stage.