Elementary Interactive

What we sign, not what we claim

We don't publish client names. Our clients are entitled to their privacy, and a logo has never been a contractual guarantee of anything. What we publish instead are the commitments we're prepared to sign.

The question behind the question

Every procurement review asks the same thing first: what happens if this supplier stops existing?

It is a fair question, and the usual answer — a wall of client logos — does not address it. A large client list tells you that a supplier was chosen before. It tells you nothing about what you are left holding if they go.

Our answer is that continuity should not depend on our goodwill, or on our continued existence.

01 · Documented handover

Your system is documented as it is built, not reconstructed afterwards: source code, infrastructure definitions, deployment procedure, and an administrator's manual written for the people who use the system rather than the people who wrote it.

It is delivered with the system, not held back as leverage.

02 · Escrow, where it's required

Where vendor continuity is a formal procurement requirement, we provide the technical side of an escrow arrangement at no cost: automated deposit of source code, build environment and documentation to the escrow agent of your choosing, from the same pipeline that builds your system.

The escrow contract itself is between you and the agent, and the arrangement is yours to fund. We don't hold a standing deposit with a firm of our own choosing, because an escrow that isn't tied to a specific client contract protects nobody.

03 · Direct access, defined response times

Support is not a queue. The people who answer are the people who built the system — no first-line triage, no ticket routed to someone opening your codebase for the first time.

Response times are published, not negotiated: the same figures appear in the contract, on the SLA and Support page, and in the tracker that measures them.

04 · Upgrade record

Two major platform versions to date, across two generations of the underlying interface framework.

The second replaced the entire front-end layer. That was our decision, driven by our technology rather than by any client requirement — so we carried out the migration at our cost. No client has been asked to fund a platform-driven migration, and none has had to rebuild content, permissions or configuration: the data layer was unchanged.

When the platform needs to move, the platform pays for it.

Who this isn't for

If that's the situation, we would rather say so now than find out together in month four.

A single campaign site

A self-service tool your team configures without us

An organisation where nobody owns the web platform internally

A budget that treats a website as a one-off purchase

What transfers to you and what doesn't is a separate question.

What you own