Clear scope. Controlled delivery. Work your team can own.

1. Scope of services

Professional services may include discovery, workflow and integration audits, architecture advice, cost-reduction reviews, automation design, n8n deployment or configuration, API and webhook integration, observability, documentation, training, incident support, and maintenance.

The exact services, deliverables, timing, dependencies, exclusions, and acceptance approach will be stated in the relevant proposal or statement of work.

2. Starting an engagement

Work begins after the parties agree the engagement in writing. An engagement document will normally identify:

• the business outcome and scope;
• deliverables and any acceptance criteria;
• fees, payment milestones, or rate structure;
• target dates and dependencies;
• client and Strategy Guide Win responsibilities;
• assumptions, exclusions, risks, and required access; and
• any service-specific security or data-processing requirements.

Estimates depend on the information available at the time. Discovery may identify constraints that require a revised scope, design, schedule, or fee.

3. Delivery standards

Strategy Guide Win will perform services with reasonable care and skill, using a DevOps-first approach suited to the agreed outcome and risk level.

Our standard delivery approach

• prefer the simplest maintainable solution that meets the requirement;
• treat credentials, permissions, logs, backups, and failure handling as design inputs;
• make material assumptions and trade-offs visible;
• avoid unnecessary platform or licence cost;
• test agreed critical paths before handover where the environment permits; and
• provide proportionate documentation for the delivered work.

Delivery dates are targets unless the engagement document states that a date is fixed. Dates may move when access, approvals, information, third-party services, or client dependencies are delayed.

4. Client responsibilities

The client is responsible for providing timely access, accurate information, suitable test data, decisions, approvals, and an authorised contact who can resolve questions.

The client must also:

• hold the rights and permissions needed for systems, data, software, and accounts supplied for the work;
• maintain appropriate backups and business-continuity controls unless backup work is expressly included;
• review deliverables and report material issues within the agreed review period;
• control production deployment decisions unless deployment authority is expressly delegated;
• tell us about relevant legal, regulatory, security, retention, or procurement requirements; and
• avoid sharing live credentials through insecure channels.

5. Scope and change control

A change request is any requested change that materially affects deliverables, assumptions, architecture, schedule, risk, or effort.

Small clarifications may be handled within the existing engagement. Material changes will be documented with the expected impact on cost, timing, and deliverables and must be approved before the changed work begins.

We will not treat urgent messages, meeting comments, or access to a system as approval for materially out-of-scope work unless the parties clearly agree otherwise in writing.

6. Fees, expenses, and taxes

Fees may be fixed, milestone-based, time-based, or recurring, as stated in the engagement document. Unless otherwise stated:

• fees exclude applicable taxes;
• pre-approved third-party costs and reasonable expenses are charged separately;
• unused fixed-scope effort does not automatically become a credit for unrelated work;
• late or missing client dependencies may require rescheduling; and
• work outside scope requires written approval.

Payment terms and any consequences of overdue payment will be set out in the relevant engagement document or invoice.

7. Acceptance and handover

Where acceptance criteria are agreed, the client should assess the deliverable against those criteria during the review period. A material issue should include enough detail for it to be reproduced or understood.

Subject to the engagement scope, handover may include workflow exports, source or configuration files, deployment notes, operating instructions, known limitations, access-transfer steps, and recommended next actions.

Minor defects or improvements that do not prevent the agreed primary use will normally be handled as follow-up items rather than grounds to reject the whole deliverable.

8. Confidentiality

Each party should protect the other party's non-public business, technical, security, and commercial information and use it only for the engagement.

Confidentiality obligations do not apply to information that is already public through no breach, was lawfully known without restriction, is independently developed, or must be disclosed by law. Where legally permitted, the affected party should receive reasonable notice before compelled disclosure.

9. Security and data protection

Security controls will be proportionate to the agreed work, information sensitivity, environment, and risk. The client remains responsible for deciding its legal and regulatory requirements.

Where practical, access should be least-privileged, time-limited, individually attributable, and removed when no longer needed. Secrets should be stored in suitable credential or secret-management facilities rather than embedded in workflow logic or documentation.

If the services require Strategy Guide Win to process personal data on the client's behalf, the parties may need a separate data-processing agreement before that processing begins.

10. Third-party platforms and services

Services may depend on third-party software, cloud services, APIs, licences, plugins, hosting providers, or client-selected systems. Those services are governed by their own terms, availability, pricing, limits, and security controls.

Strategy Guide Win is not responsible for a third party changing or withdrawing a feature, API, price, quota, or service. We will identify material known dependencies and, where in scope, recommend practical mitigation or alternatives.

11. Intellectual property and reusable materials

Ownership and licence terms for engagement deliverables will be stated in the engagement document. Unless otherwise agreed, each party keeps ownership of material it owned or developed independently before the engagement.

Strategy Guide Win may retain and reuse general knowledge, methods, patterns, non-client-specific templates, utilities, and experience, provided this does not disclose client confidential information or transfer client-owned data.

Open-source and third-party components remain subject to their applicable licences.

12. Warranties and limitations

We do not promise that software, integrations, networks, APIs, or third-party services will be uninterrupted or error-free. Automation can reduce work and risk, but it cannot remove every operational, security, or business risk.

Any service levels, warranty periods, remedies, liability limits, or exclusions must be stated in the applicable engagement agreement. Nothing in this policy excludes rights or liabilities that cannot lawfully be excluded.

13. Suspension and termination

Either party may end an engagement as allowed by the applicable agreement. Strategy Guide Win may suspend work where payment is materially overdue, required access or decisions are not provided, an instruction appears unlawful, or continuing would create unreasonable security or operational risk.

On termination, the client remains responsible for fees and approved costs for work performed up to the effective termination date. Subject to payment and the agreed scope, we will provide a reasonable handover of completed work and client materials in our possession.

14. Policy updates

This policy may be updated to reflect changes in services, operating practices, or legal requirements. The effective date at the top of the page will be revised when a material update is published.

An update will not retroactively change a signed engagement unless the parties agree that change in writing.