Make the service clear before configuring it.

A service needs an output, a boundary and an acceptance rule before it needs a checkout page.

Use a retainer for recurring access or capacity; use a project when a defined output and endpoint are the real promise.

Credits express a service unit; hours express time. Neither removes the need to define what the client receives.

Budget deliverable time after existing work and administration—not from every paid working hour.

Include setup, retained tools and recurring administration alongside the license bill.

A paid invoice, a service entitlement and an accepted deliverable are three different records.

Recording a payment is different from processing it; know which system confirms the money moved.

Ask for the objective, output, source material, constraints and approver—then define when the brief is complete.

Use branching to remove irrelevant questions, not to hide information required for a safe handoff.

A completed onboarding checklist means you are ready to work—not that the purchased work is complete.

A familiar domain and clear instructions help navigation; they do not replace authentication or permission checks.

Give clients one first task, one source of truth and one clear way to ask for help.

Test each role against a specific client job; administrator access cannot prove the client’s experience.

Use fictional material to verify the whole handoff, then pilot with a willing client before migrating everyone.