Deliver Client Work

Client Work is for a solution delivered to a particular client. It has its own proposal, approval and commitment lifecycle. An application SSO setup is a different workflow and does not replace client approval.

Create the work in the owning workspace#

1. Open Builder and create a Client Work record.
2. Describe the solution and configure the models, surcharge and commercial information requested by the workflow.
3. Review the client-facing proposal before sharing its link.
4. Have the client inspect the proposal, choose the appropriate account and complete the required approval.
5. Check the accepted state and configured production access in Console before deployment.

Make the quote understandable#

Show the authorized models and the Builder surcharge using the terms displayed in the quote. Do not describe a calculator estimate as a guaranteed bill, earning or payout. Keep the client’s approval tied to the actual proposal version.

Production credentials#

Use the credentials created or assigned by the Client Work flow. They follow the accepted payer, model and surcharge restrictions and can include environment-binding rules. Do not reuse a general-purpose key to bypass those restrictions.

Changes after approval#

Use the workflow’s supported revision or regeneration actions and inspect whether new client approval is required. A change made only in your application code does not update the client’s accepted commitment.

Verify before handover#

Check the intended production environment, effective models, accepted terms and a small real request. Keep private credentials out of the client-facing documentation and communicate how access can be retired.