Partner Lifecycle
Every TruModule integration, regardless of platform, region, or device, goes through the same four phases. Nothing here is optional or skippable: a build that skips straight to development without an agreed scope is the single most common cause of expensive rework later.
The Technical Scope of Work (TSOW) is the agreed document that defines what will be built. It is created during scope agreement, signed off before development is treated as committed scope, and used as the baseline for accreditation.
Timelines vary a lot by integration complexity, but as a rough estimate, the technical build itself typically runs 10-15 days once scope is agreed, and a first-time partner relationship (pre-sales through to a signed scope) can take longer where there's no existing commercial relationship to build on. Treat both as an order of magnitude, not a quote. Your Solutions Architect will give you a real estimate once your integration is scoped.
The four phases
| Phase | What it's for | You'll come away with |
|---|---|---|
| 1. Initial engagement | Understanding the integration requirements and platform architecture: what TruRating needs, and how your platform will talk to ours (including UX). | A shared, high-level picture of what the build will look like. |
| 2. Scope & agreement | Locking down exactly what's being built, in order to build the best customer feedback solution. | A signed Technical Scope of Work (TSOW). |
| 3. Build | You build against the agreed TSOW, with TruRating reviewing along the way. | A working build, informally reviewed ahead of formal testing. |
| 4. Post-build & accreditation | Structured testing against the full agreed scope, then formal sign-off. | An accredited, production-ready integration. |
What matters at each phase
- No build should be treated as production-ready until the relevant TSOW scope has been agreed and accreditation has been completed. A signed TSOW with active Solutions Architect involvement is the baseline for any build; go-live itself depends on passing accreditation in phase 4, not on the TSOW alone. Skipping either step is how expensive rework happens.
- Screen and UX sign-off happens in phase 3, before you finish building, not after. Bring your screen designs and customer flows to TruRating early. A build that reaches phase 4 without this sign-off is typically sent back.
- Phase 4 has three distinct checks, not one: screen design, message-level protocol validation, and full User Acceptance Testing on your real target system. All three need to pass before go-live.
Read next
- Getting Started with a Build: the practical steps: sandbox access, TransportKey, Postman collection, what accreditation involves, and what we need from you.
- Scoping a Partner Integration: what goes into the Technical Scope of Work itself, and what makes a build "non-standard."
- TruModule Specification (partner sign-in required): the requirements your build is scoped and accredited against.