Introduction

About this guide

This guide is for the Affinity team. A PDF guide is available for prospects and clients which also explains our integrations.

Why process is important

We have a process in place to ensure that integration projects are successful and profitable, with clear client expectations, minimal scope creep and compensation for any changes.

Why we offer integrations

  • Efficiency and automation. Many clients need a way to automate the entry, transfer and validation of data across systems.

  • Insight and visibility. Data feeds from Affinity to our clients' BI platforms are often the best way to give them the insights they need.

  • Client and partner retention. The more we offer in this space, the better for everyone.

  • Data quality. Eliminating manual re-keying of information reduces errors.

Documentation is key

Customised integrations in particular are supported by a range of documentation which, when provided at the right time, will:

  • Set pre-sales expectations. Clients know their responsibilities before the contract is signed.

  • Provide structure. Expectations are reinforced through the provision of documentation and checklists at key project stages.

  • Control changes. Everyone is aware when a request is out of scope and how it should be handled.

  • Support ownership: Clients understand ongoing maintenance and support responsibilities post-go live.

This has the following benefits:

  • Sets client expectations from the start, reducing delays.

  • Prevents unofficial or unpaid work.

  • Reduces misunderstandings and blame-shifting.

  • Minimises stress on the team.

  • Improves client satisfaction through transparency.

The risks of poor planning

  • Payroll errors: Inaccurate data can disrupt payroll processing.

  • Compliance issues: Faulty data can lead to non-compliance. 

  • Operational delays: Poor preparation can lead to delays.

  • Data loss: Poor synchronisation can result in data corruption.