I’ll help you turn the current mix of spreadsheets and SaaS tools into a setup you can run again next month, with agreed definitions, documented decisions, and working pipelines and reporting.
These terms apply to the work you approve in writing (including any proposal you accept) and to any ongoing retainer work I carry out for you. If something isn’t written down, I treat it as not agreed yet and I’ll confirm it before I build it.
What I will deliver
Data and AI consulting covers the work needed to define your KPIs, map and obtain data access, build or improve your warehouse or lakehouse and pipelines, and produce dashboards and a model or RAG prototype you can re-run with the same inputs and definitions.
Your deliverables are listed below. I will build and hand over what’s listed, plus the code, configuration, and notes needed to operate it next month. You will assign one day-to-day point of contact for KPI definitions and sign-off, and one person who can approve access to the data sources and internal documents I need. If access is delayed or revoked, timelines move with it.
* KPI definition sheet * Data access map * Warehouse or lakehouse setup * Scheduled pipelines with checks * Dashboards and KPI reporting * Model or RAG prototype package
Payment
For setup work, I invoice 25% to start and the remaining 75% when I hand over the setup deliverables. For ongoing retainer work, I invoice at the start of each month for that month’s work. Every invoice is payable within 7 days of its date.
If a payment is late, I will pause work and pause any agreed timelines until the account is back up to date. If a handover depends on a final payment, I will hold the handover until that invoice is paid. If you have a billing admin process I need to follow (PO number, vendor form, routing), tell me before I start so invoices don’t get stuck.
Revisions and changes
Revisions are for tightening what we already agreed, not for changing the target. For dashboards and KPI reporting, a revision round means one consolidated set of changes to layout, labels, calculations, filters, and wording based on your feedback. For a model or RAG prototype package, a revision round means one consolidated pass on prompt or feature choices, evaluation setup, and packaging.
I include 2 revision rounds. If you want more rounds, or you change definitions, data sources, or success criteria after I’ve started, I’ll describe the change in writing before I do it. That note will cover what changes, what stays the same, and any pricing or timeline impact.
Who owns what
Once invoices are paid, you own the finished deliverables I hand over for this engagement, including the KPI definition sheet, dashboards and KPI reporting, and the model or RAG prototype package. You can use them internally and with your vendors as needed to run your operations.
I keep ownership of my underlying tools, templates, reusable code patterns, and methods that I bring to the work, even if I use them to build your deliverables. If I include any third-party tools or libraries, they stay under their own licenses and rules. If you want to reuse my reusable components outside your business or resell them, tell me and I’ll confirm what’s allowed in writing.
Portfolio use
I may show parts of the finished work as an example of what I do, such as anonymised screenshots of dashboards, a high-level architecture diagram, or a short description of outcomes. I do this to show my approach to definitions, repeatability, and handover, not to share your sensitive information.
If you want this work to stay private, tell me in writing and I won’t use it in my portfolio. If you are fine with portfolio use but want limits (for example, no company name, no numbers, or no screenshots), tell me what those limits are and I’ll follow them. I will not share raw data, credentials, or internal documents.
Retainer rhythm
This engagement is bought as a retainer. Each month, I plan work with you based on the current backlog, the state of data access, and what is most likely to hold up reporting or an AI feature if it breaks. I invoice at the start of each month, and work continues month to month unless either of us ends it.
Either of us can end the retainer by giving notice in writing. I will confirm the notice period with you in writing when the retainer starts, since some clients need time to transition access or reporting ownership. When notice is given, I’ll prioritise handover, documentation, and stabilisation work so you are not left with something fragile in the final weeks.
Limits and assumptions
I’m responsible for doing the work with reasonable care and for documenting what I built, what data it uses, and what needs to be true for it to keep running. I’m not responsible for outages, changes, or restrictions in third-party systems you use (SaaS tools, data sources, cloud services), or for decisions made from reports when the underlying inputs are incomplete, delayed, or changed without notice.
Data work can only be checked against tests that exist. I will set up checks and monitoring alerts for agreed failure modes, but I can’t catch a change that wasn’t defined as a test yet. If a source system changes, you agree that some rework may be needed to restore pipelines, definitions, or model inputs, and I’ll explain the options before I proceed.
Ending the work
Either of us can end the work by giving notice in writing. I will confirm the notice period with you in writing at the time we start, so it matches how you need to manage access, security, and internal ownership.
If the engagement ends, you’ll pay for work completed up to the end date, plus any non-cancellable costs you approved in advance. After the final payment is received, I will hand over what has been completed so far, along with the latest code, configuration, and operating notes that exist at that point. If access is removed before handover is complete, I’ll hand over what I can from what I already have, and I’ll note any gaps caused by the access change.
Signature
