Before buying a branded coaching app, verify who controls the store accounts, domain, content, payment account and student exports. Demonstrate the complete learner journey and obtain the package limits in writing. A logo on an app does not by itself establish ownership, portability or the right commercial fit.
What does “your own app” mean?
It can mean a dedicated listing, a configurable application or access through a shared platform. Ask which arrangement is proposed and what it permits. Keep ownership, operational access and branding separate: being able to edit a logo is different from controlling a developer account or transferring an app. Do not assume one vendor’s arrangement applies to another.
Download the branded-app buyer checklist. This is an editable, ungated worksheet from ThePrepLab. Examples are illustrative, not customer results. Use anonymous IDs instead of student personal information.
| Area | Ask the provider | Evidence to request |
|---|---|---|
| Store accounts | Who owns the listing and handles review or renewal? | Named responsibilities and proposed account arrangement |
| Domain and brand | Who registers the domain and controls changes? | Written ownership and access scope |
| Content | What can we export, in which format? | A sample export with media and answer keys |
| Payments | Who receives funds and handles refunds or disputes? | Commercial terms and a supported demonstration |
| Student data | What records can authorised staff obtain? | Field list, access controls and sample with fake data |
| Exit | What assistance, charges and deadlines apply? | Documented process and limitations |
Test the journey, not just the home screen
Give a test learner the actual onboarding instructions. Ask them to find the course, start a practice activity, submit an answer and locate feedback. Ask an educator to correct a draft question and preview it. Check the supported devices your students use. Record observed behaviour and unresolved questions instead of approving from screenshots alone.
Compare the same commercial scope
Use one scenario for every proposal: the same students, courses, storage, test volume and support needs. Ask which charges are recurring, usage-based, one-time or third-party. “No platform revenue share” does not automatically mean no payment processing charges. This checklist does not state that any particular charge or feature is included in PrepLab’s current package; confirm the written offer.
A worked decision example
Imagine two fictional offers. Offer A has a lower subscription but no demonstrated question export. Offer B costs more and successfully exports the pilot questions with keys and figures. If portability is mandatory, A remains unproven regardless of its attractive price. If B fails your required student workflow, it also remains unproven. A scored checklist supports judgment; it should not hide a non-negotiable failure inside an average.
What should be a launch blocker?
- Unclear responsibility for account ownership or ongoing access.
- An essential student or educator task fails during the pilot.
- No agreed way to address content corrections or access failures.
- Undocumented limits that materially affect your planned volume.
- An exit or export requirement remains promised but untested.
Keep the evidence date beside each answer. Platform policies and commercial offerings can change, so review the relevant official store and provider requirements during procurement. This is a buyer’s operating checklist, not legal advice or a guarantee of app-store approval.
How should I evaluate ThePrepLab?
Bring your requirements and a permitted sample paper to a demonstration. Ask the team to show branded student delivery, question preparation and the specific export or access needs you have. Mark anything not demonstrated as “not tested,” not “included.” Use current pricing and the migration pilot to complete the evaluation.