Ortem Technologies White-Label Intake and Brand Asset Handoff (Onboarding)

Ortem Technologies White-Label Intake and Brand Asset Handoff (Onboarding)

1. 01

   Open the Ortem intake brief and lock the fixed-scope package before any client call

   Match the client's ask to a published tier: Web Starter from $2,500, Mobile App Starter at $4,000 (1 platform, up to 15 screens), or Mobile App Standard at $8,000 (iOS + Android, up to 30 screens). Write the tier name and screen count into the brief so scope creep has a paper trail.

2. 02

   Collect brand assets in the Ortem white-label bundle format

   Request logo files, color values, typography, icons, and splash screens from the client. These are the only inputs Ortem needs to rebrand a multi-tenant build; no new engineering request is required for a variant.

3. 03

   Set feature flags for the client variant in the multi-tenant configuration

   Select which modules the client's branded app exposes (authentication and onboarding, push notifications, payment gateway, analytics dashboard) based on the tier purchased. Flag anything outside the tier as a change order, not a build request.

4. 04

   Confirm whether AI fine-tuning data is in scope

   Client data is only collected when AI model fine-tuning is part of the engagement. If the package is a standard app or web build, leave the data field empty and note it in the brief.

5. 05

   Hand the completed brief to Ortem and record the delivery path

   Ortem handles development, design, QA, and App Store/Google Play submission under the agency's brand. Log the submission step in the client's retainer record so the agency can report status without chasing the vendor.

6. 06

   Verify source code ownership clause on the signed scope

   Every Ortem tier includes full source code ownership. Confirm the client contract passes that ownership through, or states the agency holds it, before work starts.

7. 07

   Archive the brief and brand bundle against the client account

   Store the tier, feature flags, and asset pack in one folder so the next variant for the same client (or a sibling franchise location) can be stood up from the same inputs.