Implementation and support
Distinguish the source licence, standard assistance and a separately scoped implementation engagement.
Choose your starting pointLink to section
Source licence
- Your order and supplied terms define update access, support period and service commitments.
Scoped implementation
- Implementation is quoted after scope review and is separate from the source-only checkout.
Optional implementation servicesLink to section
Guided setup
- A discovery brief and setup checklist for one agreed environment
- Branding and configuration of your email, sign-in and billing providers
- Validation of an agreed account, workspace and project journey
- Readiness checks and operating notes for your team
- A handover session with follow-up defined in the quote
- A configured environment, validation checklist and handover notes.
- Business-specific development, existing customer-data migrations, hosting and ongoing operation are quoted separately.
Business adaptation
- Discovery and written acceptance criteria for a prioritized workflow
- Agreed interface, API, data model and integration changes
- Permission checks and regressions for the new workflow
- Validation in an agreed environment with recorded results
- A documented handover and explicitly scoped follow-up
- An implemented workflow, validation results and handover notes.
- The quote defines the workflow and integration boundaries. Larger engagements can exceed 10,000 €; hosting and ongoing operation are separate.
These are starting service fees. The source licence and third-party provider costs are itemized separately in your quote. Confirm the deliverables, target environment, acceptance checks, total price and included follow-up in writing before work begins. A quote can exceed the displayed starting price.
Request a written proposalLink to section
Use the project brief form to describe the workflow, choose setup or business adaptation, and share an indicative budget. Company and desired timeline are optional. Keep credentials and customer data out of the brief.
The confirmation provides a request reference after the email provider accepts the transmission to PyColors. It does not certify inbox delivery or confirm a price, booking or delivery date. We review the request before agreeing on a written scope. Use the displayed reference when following up with PyColors.
Standard starter supportLink to section
Installation guidance and reproducible defects in the supplied starter belong to the support scope of your purchased offer. Purchase access and recovery use purchase support. Share your version, minimal steps, diagnostic code and a redacted screenshot; keep secrets, session cookies and customer data out of support messages.
Your purchased terms remain authoritative
This guide does not replace the terms supplied with your order or reduce rights granted with an existing purchase. Business-specific features, hosting, ongoing operation and upgrades of customized code require an agreed scope. No default SLA, response deadline or 24/7 coverage is promised by this page.
Define the engagementLink to section
A written engagement can define the following steps with PyColors:
Licence and baselineLink to section
Identify the source release and the licensed entity involved.
Initial configurationLink to section
Agree on the database, authentication, email and billing setup for your target environment.
Targeted adaptationLink to section
Name the workflow, integration or design change and its acceptance criteria.
Validation and handoverLink to section
Agree on checks, operating notes and ownership of credentials, backups and alerts.
Bounded follow-upLink to section
Record the support period, included assistance and escalation route for that engagement.
Adapt one shared foundationLink to section
Use the included workspaces, projects, assigned tasks, due dates and discussions as the first reusable business example. Keep branding and product settings in their documented entry points, and build domain-specific workflows on that baseline. A specialized workflow or integration belongs in the agreed scope and acceptance criteria. Review included capabilities before defining your adaptation.
Inspect an example deliveryLink to section
The implementation example turns the two engagements into concrete briefs: one configured preview environment, or one internal client-delivery workflow. It shows the scope, environment record, acceptance evidence and team handover contents.
Download the editable example handover to review the format. It is an illustrative document: its result fields are marked NOT RUN, with spaces for the actual revision, environment, tester, outcome and evidence. Complete these at acceptance for the agreed scope. Keep credentials in your credential manager and record only their ownership and location.
Prepare for handoverLink to section
Confirm who operates the application, manages provider accounts and can restore the database. Record the delivered revision, acceptance results and outstanding operator setup.