Find the right instruction for the stage you are in.

Choose the route before choosing the technology.

Start by describing the current situation, people involved, repeated problem, desired business result, deadline, existing tools, and any hard constraints. Starlife will place the requirement into one of four commercial paths.

Evaluate what exists before requesting what does not.

1. 1
   Read the product detail

   Confirm available features, supported users, deployment model, current limitations, dependencies, and the actual release state.

2. 2
   Choose the commercial route

   Hosted access, one-time license, managed deployment, customization, white-label, and resale rights are different agreements.

3. 3
   Review infrastructure

   Confirm domain, runtime, database, storage, email, push, third-party accounts, device distribution, and renewal costs.

4. 4
   Plan support

   Separate defects, installation, configuration, training, custom changes, provider failures, and future feature work.

Use milestones to turn uncertainty into decisions.

New requirements, changed assumptions, delayed inputs, additional integrations, or major revisions may require a change request with a revised cost or timeline.

Prepare access without sending secrets through ordinary forms.

Installation may include files, dependencies, environment values, database, storage, routes, SSL, DNS, email, scheduled work, notifications, health checks, workflow tests, and a deployment record. The exact checklist depends on the product.

Follow the public delivery journey with a private code.

1. 1
   Receive the tracking code

   The authorized contact receives a high-entropy code after the project enters delivery.

2. 2
   Open Project Tracking

   Enter the code or use the secure link supplied by Starlife. A code is not an account password.

3. 3
   Read the current state

   Review progress, delivery health, expected completion, current milestone, next action, and public updates.

4. 4
   Contact support with context

   Include the code when asking about a blocked decision or discrepancy. Do not share it publicly.

Separate transaction submission from verified payment.

1. 1
   Submit after transferring

   Use the private estimate page only after initiating the selected bank, Mobile Money, crypto, or hosted payment.

2. 2
   Keep the STP tracking code

   The confirmation screen and printable acknowledgment show a high-entropy payment tracking code.

3. 3
   Track with the sender phone

   Open Payment Tracking and enter the code with the same sender phone. The result excludes transaction IDs and secret credentials.

4. 4
   Follow the published state

   Submitted, verification, action-needed, verified, commencement-ready, cancelled, and refunded states include a timestamp and next action.

From business signup to daily customer support.

Send evidence that helps separate the cause.

A useful support request includes the affected URL or product, account or tracking reference, expected behavior, actual behavior, exact time and timezone, device and browser, steps to reproduce, recent changes, error text, and safe screenshots or logs.

Keep ownership with the client without spreading access.

• Use unique passwords and enable multi-factor authentication where available
• Keep domain, hosting, payment, email, and source ownership in authorized accounts
• Use named users instead of one shared administrator credential
• Remove temporary access and rotate secrets after deployment
• Keep environment files, private keys, database exports, and backups outside public web access
• Document renewals, responsible contacts, backup schedule, recovery route, and provider dependencies
• Review permissions when staff, agents, or suppliers change responsibility