Engagement terms.
How the work is scoped, priced, delivered and owned. Where a signed proposal or statement of work is more specific than this page, that document governs.
01The engagement
The engagement is an embedded systems partnership: I work close to the organisation, first to understand how it actually runs and what is holding it back, then to continuously design, build and deploy the systems that change it. Discovery is part of the engagement rather than a separate purchase.
Every engagement is priced by scope, never by the hour, and the scope is written down and agreed before you pay anything. That written scope — or a signed proposal or statement of work — is the contract for the engagement, and it governs wherever it is more specific than this page.
02Price
An embedded systems partnership runs on a three-month initial term and is quoted per engagement. The figure is set against the responsibility involved and written into your scope before anything begins. Institutional transformation, major custom platforms, external engineering teams and substantial third-party costs are scoped separately.
The figure that binds is the one written into your scope, which is fixed before work starts. You will not receive an invoice for an amount you did not agree to. Work outside the agreed scope is quoted separately and is never assumed.
03Payment
A deposit reserves the slot and starts the work; the balance is due on delivery. Larger scopes may instead be invoiced against agreed milestones. The exact split and dates are set in the written scope and reflected on the invoices. Invoices are payable by the method stated on them. If you abandon the work after it has started, the deposit is retained for time already spent.
An ongoing partnership is scoped based on involvement, invoiced monthly in advance and runs month to month — either side may end it with 30 days’ written notice. Fees already invoiced for a started month are not refundable, and you keep everything delivered.
04Materials and timeline
You provide the access and materials the work needs — accounts, credentials, environments, documents, and whoever has to sign off. The delivery date is set in the written scope, and the clock starts only once the scope is agreed, the payment terms are met, and the materials are in hand. Incomplete or late access delays delivery, and that delay is not a breach on my side.
05Revision round
- you receive the work for review against the written scope
- you submit one written list of feedback within 5 business days
- I apply that list once, then the work is delivered
- drip feedback is batched until the list is complete
- new capabilities, extra surface area, or a change of direction fall outside the agreed scope and are quoted separately
06Ownership and licence
- on final payment — and continuously across an ongoing partnership — you own the deliverables produced for you: the systems, code and documentation as delivered, on infrastructure you control
- there is no lock-in: end the engagement and everything built for you keeps running under your control
- you must hold the rights to all materials, content and credentials you provide
- third-party tools and services — model providers, hosting, payment processing, libraries and the like — remain under their own terms and are billed to you directly unless the scope says otherwise
- I may reference the work in my portfolio unless you ask me not to in writing before delivery
07Your organization’s data
Where an engagement involves your organization’s material or access to systems you run, what can be seen, where it lives, and what happens to it at the end is agreed in writing before anything is connected. Nothing you provide is used to train models. See the privacy policy for how information reaching this site is handled.
08Assessing and improving, not certifying
When the work involves reviewing, connecting or improving a system you already run, I assess it and improve it against known issues and good engineering practice. That is not a certification that the system is bug-free, secure against every possible threat, or compliant with any particular standard or regulation. No such guarantee is given or implied.
Systems that use AI models produce output that is probabilistic, not deterministic. Where judgment matters, the systems I build are designed to put a person in the loop, and the scope will say where that line sits.
09Limitation of liability
I deliver senior engineering and a scope fixed in writing. I do not guarantee revenue, growth, search rankings, uptime targets, model accuracy, or the behaviour of third-party platforms. To the fullest extent the law allows, total liability under any engagement is limited to the fees you actually paid for that engagement.
10Acceptance
Agreeing to a written scope, or paying a deposit or invoice against it, constitutes acceptance of these terms. Where a signed proposal or statement of work differs, that document governs for that engagement. These terms are governed by Astral Studio LLC (US).
Questions: hello@jordiamat.com · Privacy: /privacy/