Client Agreement

How engagements are documented

Every engagement is documented before work begins. Smaller pieces of work are covered by a single proposal that acts as the agreement. Ongoing or multi-phase relationships use a Master Services Agreement with individual Statements of Work underneath it.

Nothing starts on a handshake. You should always know the scope, the fee, the timeline, and what you own before the first invoice.

What a proposal defines

Scope and deliverables in specific terms, not general categories. Milestones and their fees. Timeline and dependencies. What we need from you and by when. Which third-party platforms are involved and who pays for them. What support looks like after handover.

Ownership of what we build

On final payment, you own the deliverables built for you: workflows, code, dashboards, documentation, and configurations. They are yours to run, modify, or hand to another provider.

We retain ownership of our general methods, internal tooling, templates, and know-how developed independently of your engagement. This lets us work efficiently for everyone without taking anything specific to your business.

Accounts and subscriptions are set up in your name wherever possible, so access does not depend on our continued involvement.

Your data

We access client systems and data only to the extent needed to deliver the agreed work, using the narrowest permissions that make the job possible. Access is revoked at the end of an engagement unless ongoing support is in place.

We do not sell client data, and we do not use identifiable client business data to train models. Where an engagement touches regulated or sensitive data, handling terms are addressed explicitly in the agreement.

Confidentiality

Business information shared during an engagement — operations, financials, processes, customer data, strategy — is treated as confidential and used only for the engagement. Mutual confidentiality terms are standard in our agreements and can be signed separately before scoping if you prefer.

What we need from you

Projects stall on access and decisions more often than on engineering. Agreements set expectations for both: a named point of contact, timely responses to questions, access to relevant systems, and decisions at defined checkpoints.

Where a delay on your side moves the schedule, we adjust the timeline rather than quietly absorbing it.

Human oversight and responsible use

Systems that involve AI are built with defined guardrails: human approval gates where judgment matters, logging, escalation paths, and validation on outputs that affect customers or money.

You remain responsible for how the system is operated after handover, including compliance in your regulatory environment. We document intended use and known limitations so those decisions are informed.

Changes to scope

Scope changes are normal. They are handled through a written change order describing the addition, its cost, and its effect on the timeline — not absorbed silently or discovered on a final invoice.

Ending an engagement

Either side can end an engagement with written notice as defined in the agreement. On exit you receive documentation, credentials, and the work product as it stands. Fees are settled for work performed.