The boring parts, answered up front.

You can read every term you would be signing before you send a word.

Who you contract with

A limited liability company, named on the agreement and the invoice. You are invoiced like any other vendor, on your terms, in your system.

Before I start

Scope, price, and the delivery date, in writing. Changes to any of the three are a conversation, not an invoice you find out about later.

Capacity

Builds are sequenced rather than run in parallel, which is why a committed date stays committed. Written work is scheduled separately. The earliest date I can start comes back with the reply, before you have committed to anything, so a date you cannot reach costs you one email.

Your code

Instruments run in your environment, on a copy you designate, with the network off. A report quotes the lines it broke, so it contains your source and stays yours. Nothing with a path or a line of your code leaves your infrastructure. I keep aggregate scores and counts only, so a re-measure has a baseline.

Who owns the work

You do. Everything I write for you transfers to you on final payment, source and all. I keep no rights over it and reuse nothing from your codebase anywhere else.

Confidentiality

I will sign your NDA. Client work, client code, and client names stay private by default, including from this page.

If a date is going to slip

You hear it from me the week it becomes likely, not on the due date. A fixed date is worth nothing if the first sign of trouble is silence.

If a build cannot be completed

You get everything built to that point, the documentation for it, and a refund of the balance not yet earned. The answer is money back and working code, not an apology.

If your procurement process needs something not listed here, ask before we go further rather than after. I would rather find out early that I cannot meet a requirement.