Engagement
From First Call to Handover

How Synapse Technologies runs a piece of client work: discovery, scoping, build, handover, and the support that follows.

01
Discovery
Discovery

Discovery Call

Understanding the work you want to change, the systems it runs on, and the constraints any solution has to respect.

Progress20%
A call with the people who own the process
The workflows and decisions in scope
Systems and data sources involved, and who owns each
Constraints on data, access, and compliance
02
Scoping
Scoping

Scope & Written Proposal

A written proposal setting out what gets built, which service it runs under, and what it costs.

Progress40%
Use cases prioritised by value and feasibility
Consulting, implementation, or a capability retainer
Architecture direction and integration points
Deliverables, milestones, and commercial terms in writing
03
Approval
Approval

Plan Review & Prerequisites

Reviewing the proposal with your team, agreeing the scope, and confirming what has to be in place before work starts.

Progress60%
Review call with business, IT, and compliance owners
Revisions where the scope needs to change
Agreed deliverables and success criteria
Access, environments, and data prerequisites confirmed
Written approval to begin
04
Build
Build

Build, Integrate & Validate

Building against the agreed scope and integrating the result with the systems your team already works in.

Progress80%
Data pipelines built against your real sources
Models and services developed and evaluated
Integration with the systems the work runs on
Regular working sessions with your team
Validation on cases your team already knows the answer to
05
Handover
Handover

Handover & Capability Transfer

Moving the system into everyday use, training the people who will run it, and handing over what they need to keep it running.

Progress100%
Move into live use with the teams who will use it
Training for administrators and day-to-day users
Documentation and runbooks handed over
Source, configuration, and architecture notes transferred
A review once the system has been in real use

Roles and
Responsibilities

An engagement runs on both sides. These are the things we depend on from your team, and the things you can hold us to.

Need From You

What We Need From You

A named owner for the process, and a named owner for IT

Access to the systems and data the work depends on

Feedback inside the review windows agreed at kickoff

Real examples your team can already judge the answers to

Authority to decide scope, access rules, and priorities

Expect From Us

What You Can Expect From Us

Scope, deliverables, and costs written down before work starts

Regular working sessions and written progress updates

The reasoning behind each technical tradeoff, in plain terms

Code, configuration, and architecture documented and handed over

A named point of contact for the whole engagement

Support After Handover

Work does not stop at handover. We stay reachable for questions and fixes, and we keep adjusting the system as real use shows what needs to change.

SupportIterationCapability TransferAdvisory
01

Post Handover Support

We stay reachable for questions and fixes while your team settles into running the system.

02

Iteration

Changes to the system once real usage shows where it needs adjusting.

03

Capability Transfer

Walkthroughs, documentation, and paired work so your own team can maintain and extend what was built.

04

Ongoing Retainer

Where you want a team on hand for the long term, AI as a Capability continues the work on a retainer.

Discovery Starts Here.

Tell us which process you want to change and we will walk through it on a call. No obligation.

Book a Discovery Call