# PyColors · example implementation handover

Illustrative delivery. The scope, environment, acceptance checks and follow-up for your engagement are confirmed in the written quote.

SAMPLE ONLY — no customer delivery or completed acceptance is asserted. All result fields below are NOT RUN and must be completed for the agreed environment.

Project: Product studio · internal delivery workspace
Delivery date: [record the agreed delivery date]
Delivered revision: [record the exact release/commit]
Target environment: [record the agreed preview URL]
Delivery owner: [record the responsible role]
Receiving owner: [record your team's responsible role]

## 1. Agreed scope

### Guided setup · From 3,000 €
A first workspace your team can take over

- One agreed preview environment, configured in accounts owned by your team.
- Your brand, sign-in providers, transactional email and Stripe sandbox settings.
- A first account → workspace → invitation → project journey, with recorded checks.

This example configures the existing starter. A new business feature or a production data migration needs its own agreed scope.

### Business adaptation · From 7,500 €
An internal client-delivery workflow

- A client-delivery view built on workspace projects, assigned tasks and discussions.
- An agreed summary of pending work, owners and due dates, with the interface and data changes it requires.
- Role and workspace-access checks, regression results and developer notes for the adapted flow.

The delivery view is an example adaptation to scope. Customer-facing access, a full CRM, external integrations and formal approvals are separate requirements to define.

These are alternative example scopes. Starting service fees, the source licence and provider costs are itemized separately in the written quote. Final deliverables, price, acceptance and follow-up are agreed before work begins.
Scope selected: [record the agreed service and scope reference]
Changes and exclusions: [record agreed changes and exclusions]

## 2. Environment configuration record

Record configuration locations and ownership. Keep secret values, session cookies and customer data out of this document.

### Source & runtime
Configuration: Delivered revision, runtime versions and reproducible startup commands.
Evidence expected: Revision reference and installation/build output.
Environment / owner / evidence location: [complete at handover]
Status: NOT RUN — complete at acceptance

### Database & access
Configuration: Preview PostgreSQL connection, migrations and workspace membership rules.
Evidence expected: Migration record and access-check results.
Environment / owner / evidence location: [complete at handover]
Status: NOT RUN — complete at acceptance

### Sign-in & email
Configuration: Agreed providers, callback URLs, verified sender and recovery flow.
Evidence expected: Redacted provider configuration and delivery references.
Environment / owner / evidence location: [complete at handover]
Status: NOT RUN — complete at acceptance

### Billing sandbox
Configuration: Your test catalog, webhook endpoint and expected plan changes.
Evidence expected: Sandbox checkout and webhook references; saved subscription state.
Environment / owner / evidence location: [complete at handover]
Status: NOT RUN — complete at acceptance

### Operations
Configuration: Diagnostic checks, operator contacts and the agreed backup/restore procedure.
Evidence expected: Operating notes, responsible owners and outstanding launch actions.
Environment / owner / evidence location: [complete at handover]
Status: NOT RUN — complete at acceptance

## 3. Acceptance record

Keep the expected and observed outcome together. Record blockers and retest results rather than marking an unverified journey complete.

### Account access
Expected: Sign in, recover access and return to the intended workspace.
Evidence to attach: Test identity, environment, date and redacted recovery evidence.
Environment / date / tester: [complete]
Actual result: [complete]
Result: NOT RUN
Evidence reference / remaining action / owner: [complete]

### Workspace onboarding
Expected: Create a workspace, invite a teammate and retain onboarding progress.
Evidence to attach: Invitation delivery/acceptance reference and saved progress.
Environment / date / tester: [complete]
Actual result: [complete]
Result: NOT RUN
Evidence reference / remaining action / owner: [complete]

### Project delivery
Expected: Create a project and task, assign an owner, set a date and save a discussion.
Evidence to attach: Resource references and persistence after reload.
Environment / date / tester: [complete]
Actual result: [complete]
Result: NOT RUN
Evidence reference / remaining action / owner: [complete]

### Permissions
Expected: Reject access from another workspace and respect the agreed member roles.
Evidence to attach: Allowed/denied role checks and regression output.
Environment / date / tester: [complete]
Actual result: [complete]
Result: NOT RUN
Evidence reference / remaining action / owner: [complete]

### Billing sandbox
Expected: Apply the agreed test subscription changes and verify the saved result.
Evidence to attach: Sandbox event references, expected state and observed state.
Environment / date / tester: [complete]
Actual result: [complete]
Result: NOT RUN
Evidence reference / remaining action / owner: [complete]

## 4. Team handover

### What was delivered
Scope, delivered revision, affected screens and the acceptance criteria agreed for the engagement.
Record / owner / location: [complete]

### How to run it
Install, build and migration commands; environment names and where your team manages credentials.
Record / owner / location: [complete]

### What was verified
For each agreed journey: environment, date, expected outcome, actual result and evidence reference.
Record / owner / location: [complete]

### How to operate it
Health checks, logs, monitoring destination, backup/restore instructions and responsible owners, as scoped.
Record / owner / location: [complete]

### What remains
Known limitations, open launch actions, their owners and the follow-up window written into your quote.
Record / owner / location: [complete]

Receiving-team review: [record reviewer, date and remaining actions]
Agreed follow-up: [copy the period, included assistance and contact route from the signed quote]

## Continue with PyColors

- Example and scope: https://pycolors.io/starters/pro/implementation-example
- Project brief: https://pycolors.io/request-a-quote
- Support boundaries: https://pycolors.io/docs/starter-pro/implementation-support