Terms of service

Effective July 2026. These mirror the delivery boundaries printed on the pricing page.

Engagements

Every engagement is defined by a written scope with a fixed USD price, agreed before work starts. The written scope is the contract of record for what "done" means. Changes to scope are new written orders with their own price; they never silently extend an existing one.

Payment

Fixed-price work is invoiced before the build starts. Retainers bill monthly in advance and cancel with written notice, effective at the end of the paid month. Client infrastructure costs (hosting, API usage, SaaS) are billed by those providers to the client directly; we add no markup.

Delivery and communication

Delivery is async and written, with a one-business-day reply SLA. We do not attend meetings or calls. Weekly written briefs are the reporting mechanism during active engagements.

Ownership and handover

Work is delivered to the client's own accounts (code repositories, database, hosting). On acceptance and payment, the client owns the delivered code, data, and documentation entirely. We retain the right to reuse general methods, patterns, and non-client-specific tooling.

Guarantees

The AI Operations Audit carries a specific guarantee: if we find nothing worth building, the fee is refunded in full. Other engagements are accepted against their written scope. We fix what does not match the scope at no charge.

Confidentiality

We publish no client names, numbers, or case studies without written permission. The case studies on this site describe our own companies, which is why they carry real figures.

Liability

Liability is capped at the fees paid for the engagement in question. We build carefully and hand over documented systems, but the client operates their own infrastructure after handover.