How We Engage

The terms are the first deliverable.

Morillo Hudson engagements follow a standard model: a bounded pilot, a scope agreed in writing, and commercial terms structured so that a new client's commitment is staged rather than taken on trust. The model is set out below so that prospective clients can see how we work before any engagement begins. The terms of any specific engagement are those recorded in its engagement letter.

01 — The Pilot

Bounded, and Defined in Writing

First engagements are typically fixed-scope pilots of around thirty days, defined by a written scope document agreed before work begins.

Written Scope

Agreed before work begins

The scope document records what is to be delivered, what it does, and the acceptance criteria against which the work is assessed. The capabilities of an engagement are those recorded in its scope document.

Staged Payment

Commitment in stages

Pilots are typically paid in stages - a portion on signature and the balance on acceptance - so that a new client's commitment tracks demonstrated progress. Payment terms for each engagement are recorded in its engagement letter.

Warranty

After handover

Engagements typically include a defect-warranty period following handover. Its duration, the remediation process, and any ongoing support terms are recorded in the engagement letter, so that post-handover obligations are defined before signature rather than negotiated after delivery.

02 — Ownership

Built for You. Transferred to You.

We build inside your perimeter and transfer the deliverable to you. The engagement model is transfer, not tenancy.

Your Perimeter

Data stays home

Systems are designed as isolated, single-tenant infrastructure under your control, so that client material is processed inside your perimeter, and so that client data is not used to train external models.

Transfer

IP, source, documentation

On acceptance, you receive the deliverable, its source, and its documentation, with assignment of the deliverable IP created for the engagement as recorded in the engagement letter. Third-party and open-source components remain subject to their own licenses.

Deliverables are built on standard, documented technology and are intended to be operated and extended without dependence on us. Handover typically includes a working session with your team.

Access at Handover

Independence by design

Access credentials are returned or revoked at handover unless ongoing support is engaged. Deliverables are designed so that you are not dependent on any single vendor - including us.

How we work is stated before we are engaged.

Begin With an Inquiry

This page describes Morillo Hudson's standard engagement model. It is provided for information, does not constitute an offer, and does not form part of any contract. The terms of each engagement are exclusively those set out in its signed engagement letter.