Peko Client Workspace Setup (Onboarding)

Peko Client Workspace Setup (Onboarding)

1. 01

   Run the free Peko CLI lint against the client's representative .ipa or .aab before opening any paid tier

   Point the CLI at the build alongside Podfile.lock, Package.resolved, and gradle.lockfile so binary, manifest, and SDK analysis all fire. The 46 mechanical rules are compiled into the binary, so this run costs nothing and tells you whether the build is worth a retainer conversation.

2. 02

   Create a dedicated Peko project for the single client and map their manifest surface

   Load Info.plist, AndroidManifest, entitlements, and privacy manifests into the project. Keep one project per client so findings, blocking status, and remediation history never bleed across accounts.

3. 03

   Complete the project facts form before the first interpretive scan

   Record child-directed status, EU distribution, and any other declared attributes. Peko's interpretive rules read these facts against the code, so a half-filled form produces findings the agency then has to explain away to the client.

4. 04

   Run the initial scan and triage every finding by its blocking, review, or passed status

   Blocking items get fixed before submission. Review items get a written agency judgement call. Passed items get logged as evidence that the build was checked, which is useful when a client asks what the retainer actually covered.

5. 05

   Wire the Peko GitHub Action into the client's pull request pipeline

   Lint runs unlimited on the Free plan, so the Action can gate every PR at no marginal cost. This is the step that turns a one-off audit into an ongoing delivery commitment the client can see in their own repo.

6. 06

   Move the client to a paid tier only when interpretive volume justifies it

   Pro at $20 monthly covers 10 interpretive audits a month against 326 rules plus privacy form answers. Below that cadence, stay on Free and bill the agency's own review time instead.

7. 07

   Hand the client a remediation report mapped to App Store and Google Play policy language

   Pair each finding with the exact file and the fix. This artifact is what justifies the $1,500 App Store Readiness fee and gives the client something to forward internally.