Skip to content

Suggested

Language: English. French, Portuguese and Arabic are in preparation.

Discuss your project

A platform you can plan around.

Understand what is recurring, what is implementation work and how Platform releases are governed before you commit to architecture or budget.
Current production release:Platform 17.4

What you are buying.

Your proposal will state the production scope, licence basis, environments, included capabilities, implementation work, optional managed operations and any programme-variable services.

  • Platform licence

    Recurring

    Recurring right to use the agreed Platform deployment and capabilities for the production scope.

    Recurring licence under the commercial agreement.

  • Implementation services

    One-off or milestone

    Discovery, configuration, workflow engineering, integrations, data work, testing, deployment and training.

    Fixed, milestone, outcome-based or T&M depending on scope.

  • Managed operations

    Optional, recurring

    Agreed support, monitoring, DevOps, databases, incident management and continuous improvement.

    Optional recurring managed service.

  • Programme-variable services

    Variable, disclosed

    Approved third-party, cloud, messaging, verification or similar variable services where applicable.

    Disclosed in the proposal and contract rather than hidden.

The licence structure follows the agreed production scope, scale and deployment model. Exact pricing is agreed through scoping.

Assess → Implement → Platform licence → Optional operate

  1. Assess

    Focused, fixed scope

    One-off

    You may stop here. The recommendation is yours to use with any supplier.

  2. Implement

    Fixed, milestone, outcome-based or T&M

    One-off or milestone

  3. Platform licence

    Agreed production scope

    Recurring

  4. Operate

    Managed operations

    Optional, recurring

Programme-variable services — third-party verification, messaging or cloud — are disclosed in the proposal and contract rather than hidden inside the licence.

Product core, client configuration, programme integrations.

The release number applies to the maintained Seamfix Platform core. Client-specific configuration, workflows and integrations sit around that core and are governed through the programme's deployment and change process.

This separation is what allows the common platform to keep evolving without treating every client as a forked product.

Platform core17.4
Client configurationProgramme integrations
  1. Platform coreThe maintained Seamfix Platform. The release number — currently 17.4 — applies here.
  2. Client configurationWorkflows, forms, rules, roles and branding that sit around the core.
  3. Programme integrationsConnections to the programme's sources and systems, governed through its deployment and change process.

Release lifecycle.

Current production release

Platform 17.4

  1. 01Plan
  2. 02Build & test
  3. 03Release
  4. 04Programme validation
  5. 05Deploy / upgrade
  6. 06Support & monitor

The cycle repeats.

Exact support windows, release cadence and upgrade obligations are defined by the applicable product and service terms.

Questions procurement should ask us.

  1. 01What is included in the recurring Platform licence for this programme?
  2. 02What creates additional implementation cost?
  3. 03What is the approved hosting and residency model?
  4. 04Which integrations or external services have variable cost?
  5. 05Which Platform release will the programme run?
  6. 06How are upgrades, security fixes and change control handled?
  7. 07What support and managed-service commitments are included?
  8. 08What happens to programme-specific configuration when the Platform changes?

Get these answers for your programme.