01
Product & solution scope
Record the customer journeys, operator tasks, rules, modules, external providers, outputs, exclusions, and acceptance points.
A platform company focused on long-term delivery.
Spolith works with operating companies that need a configurable platform, not a one-off website or a disconnected collection of software tools.
The customer-facing company responsible for the platform scope.
Spolith provides the platform licence and coordinates the agreed product, design, engineering, integration, release, and operating-readiness work under one commercial scope.
The contract defines selected modules, configuration, third-party responsibilities, environments, acceptance evidence, launch support, service levels, exclusions, and the process for later changes.
How we work
A delivery process with named outputs and owners.
The goal is to remove ambiguity before launch: what is included, who provides each dependency, what evidence is required, and who owns operation afterward.
02
Platform configuration
Configure the agreed brand, market, account, content, permission, workflow, and reporting requirements.
03
Integration coordination
Assign provider and interface owners, prepare environments and credentials, test expected and failed flows, and manage dependencies.
04
Operational handover
Prepare access, workflow, release checks, support routes, known limitations, launch ownership, and contracted post-launch change.
Delivery evidence
A technical deployment is not the same as an operating handover.
Launch readiness requires the agreed customer and operator flows, external services, access, exception handling, known limitations, support routes, and ownership to be ready for the target environment.
- DeployedShows that a version reached an environment. It does not by itself prove the agreed workflows are ready.
- ValidatedShows the named acceptance scope was exercised with recorded results and limitations.
- Handed overShows operating access, guidance, issue routes, responsibilities, and post-launch service are in place.
Delivery structure
One customer-facing scope. Coordinated specialist delivery.
Spolith remains responsible for the customer relationship and agreed platform scope while the required product, design, engineering, integration, and operational disciplines work against the same delivery baseline.
Commercial owner
Spolith provides the customer-facing scope, commercials, delivery coordination, and agreed service relationship.
Documented boundaries
Dependencies, provider inputs, environments, acceptance evidence, exclusions, and unresolved decisions stay visible.
Release readiness
A deployment claim is not treated as launch readiness without the agreed functional and operating evidence.
Change after launch
Support, incidents, planned changes, release coordination, and service levels follow the contracted model.
Partnership model
A commercial path from fit review to managed change.
Not every enquiry enters implementation. The initial review confirms whether the operating model and required scope fit the platform before detailed commercials are prepared.
Fit review
Review the operating model, current systems, required channels, providers, roles, and target window.
Scope & contract
Agree modules, outputs, responsibilities, dependencies, environments, acceptance, commercials, and exclusions.
Implementation
Configure the platform, coordinate integrations, validate flows, and track evidence and limitations.
Launch handover
Complete release readiness, access, operating preparation, issue routes, and agreed launch support.
Managed change
Handle contracted support, incidents, planned changes, and later releases through the agreed service model.
Engagement structure
What the commercial model can cover.
The final structure is engagement-specific and recorded in the signed agreement.
Platform licence
The selected platform modules and permitted operating scope, subject to the executed commercial terms.
Implementation services
Product and solution definition, configuration, integration coordination, validation, release preparation, and handover as listed in scope.
Ongoing service
Contracted support hours, incident responsibilities, service levels, monitoring expectations, planned changes, and release coordination.
Contract controls
Customer and third-party dependencies, acceptance, exclusions, data and access responsibilities, environments, and change process.