White-Label Reseller Readiness Audit (Onboarding)

White-Label Reseller Readiness Audit (Onboarding)

1. 01

   Confirm the client's app scope fits a template-driven build before signing the reseller agreement

   Map every requested screen and integration against the platform's extension library. GoodBarber ships over 190 extensions and BuildFire lists more than 150 plugins, so anything outside that surface is a custom-development conversation, not a reseller margin.

2. 02

   Verify the white-label tier actually removes vendor branding from the client-facing surface

   Full white-label programs exist on BuildFire, Shoutem, and AppInstitute, but the reseller contract must state who owns the App Store developer account and the bundle identifier.

3. 03

   Price the retainer against store fees, plugin subscriptions, and per-app hosting, not just build hours

   A single app carries Apple's annual developer fee plus the platform's per-app charge. Model 12 months of recurring cost before quoting a fixed retainer, or the account turns unprofitable in month four.

4. 04

   Test the publish path end to end with a throwaway app under the client's own developer account

   Submit a dummy build through review, confirm push notification certificates attach correctly, and record the actual approval turnaround. Store rejection reasons surface here, not in the client's launch week.

5. 05

   Document the customization ceiling in writing and get the client to acknowledge it

   State plainly which features require native code and cannot be delivered on the platform. This is the single clause that prevents a scope dispute when the client asks for offline mode or a custom payment flow.

6. 06

   Assign one named owner for platform account access and credential rotation

   Agencies that let credentials live in a shared inbox lose days when the account holder leaves. Store reseller and store credentials in the agency password manager with a documented rotation date.

7. 07

   Set a quarterly review of the client's feature requests against platform release notes

   Track which requested capabilities the vendor ships versus which stay blocked. This gives the agency a factual basis for either expanding the retainer or recommending a rebuild.