GUARANTEE & WORKING TERMS
These are the plain-language principles I use when I take on custom work. A project-specific scope and agreement will control the details of an actual build.
CODE-FAULT GUARANTEE
If an unmodified delivered version fails because of a defect in the implementation I delivered, I will correct that defect without charging additional labor for the fix.
The guarantee does not turn new features, changed requirements, client or third-party code changes, bad data, misuse, or changes to outside services into free development work. If the cause is unclear, I will identify what changed before we decide what kind of work it is.
We agree on what the machine is supposed to do before the main build begins. Quotes cover that agreed scope. New requests or substantial changes may change the price, and I will tell you before I do work that would increase the cost.
The initial $30 covers up to one hour of actual analysis and project work. If the project moves forward, it is applied toward the agreed project price. If you ultimately cancel or do not attend, it is nonrefundable; reasonable good-faith rescheduling is flexible, and I refund it if I cancel.
The session is still useful work, not an audition you lose access to. If we decide not to continue, the concepts, workflow ideas, notes, and other project work produced for you are yours to take forward.
When our primary business is complete, ownership transfers. For a finished build, that normally means when the agreed machine is accepted. I hand over the code, a full instruction manual, and help getting it established on your own systems or accounts. An agreed maintenance period can continue after ownership transfers.
Your data, branding, confidential material, and project-specific content are not reusable material. General-purpose code, components, patterns, and techniques may be reused in other machines unless we agree otherwise. If you need reusable parts to be exclusive to you, we can put that in the agreement; exclusivity will usually affect the price.
Hosting, domains, APIs, payment processors, email services, AI services, and other outside products may have their own fees and terms. I will identify expected dependencies rather than quietly burying them in the machine.
I design and direct the system and use AI as a coding collaborator. I test the resulting implementation against the agreed workflow. I do not represent the code as manually authored line by line.
I can build imports, permissions, backups, and safeguards, but the client is responsible for having the legal right to provide and use the data placed in the system and for following any rules specific to their field.
A build can be handed off, supported for a defined period, or maintained on an ongoing basis. Ongoing availability is not implied forever; the maintenance arrangement is part of the scope.
I keep a reference record of the delivered version and the terms attached to that delivery so there is a concrete baseline for support, warranty questions, and future upgrades.
If you later expand a Machine Part or Skimmed Machine, reusable work carries forward. You pay for the new work, not for me to pretend the old work never happened.
I will not build systems whose purpose is racist, homophobic, transphobic, abusive, exploitative, or otherwise designed to harm people. Different values are not automatically a problem; harm is.
Plain-language summary, not boilerplate theater: exact payment schedule, deliverables, access, maintenance, cancellation, data handling, handoff, ownership, any exclusivity request, and other project-specific requirements will be written down for the individual job. Payment instructions are provided when work is scheduled.