Legal
Terms
Last updated 12 September 2026
We wrote this page ourselves, in plain English, and it has not been reviewed by an attorney. It is an accurate description of how we work and of what we will and will not do. The review is on the list, and this page will change when it happens.
These cover work bought from Daniel Avila, who operates as Day Ten Consulting. What each piece of work costs is on the services page; the terms below are the same whichever one you buy.
What you are buying
Teaching, building, or both. A session is ninety minutes of live teaching plus the recording and the materials. A build is one working workflow, running in your own accounts, delivered with a one-page explanation of every choice in it, a recorded walkthrough, a written failure plan, and thirty days of bug fixes. An intensive is a half day for a team. A tune-up is one scheduled block and one change to something we already built.
The scope of a build is written down before you pay anything, in a short scope document we send you after the call. That document and this page describe how we work. The agreement you sign is a separate document sent with the scope document.
The scope fence
Every build is one trigger, up to three integrations, one output, and no custom code beyond an off-the-shelf automation layer. That fence is what makes a fixed price and a fixed date honest. Work outside it is a separate piece of work at a separate price, and we will say so rather than absorb it quietly and miss the date.
Paying
- Builds and intensives are half up front and half on delivery. Session seats and tune-ups are paid in full before the date is held.
- We send you a payment link directly. Nothing is charged from this website and no card details ever reach it.
- The delivery clock starts when the deposit clears — not when you send it, and not on the day we spoke. A build is seven calendar days from that moment.
- An organization that pays against an invoice rather than a card is invoiced on its own purchase-order process, normally on thirty-day terms.
Refunds
- Deposit paid, work not started
- Refunded in full, on request, no questions.
- Deposit paid, work started
- Not refunded. The deposit buys the calendar slot and the slot is gone.
- Build delivered and you are unhappy with it
- We fix it inside the agreed scope, free, within the thirty-day window, and the balance is still owed. A build that cannot be made to work as it was specified is refunded in full, deposit included.
- The job turned out to be bigger than the scope
- Not a refund question. Widening the fence is a new engagement at a new price, and you can decline it.
- Session seat, cancelled more than 24 hours ahead
- Refunded in full, or moved to a later date, whichever you prefer.
- Session seat, cancelled inside 24 hours
- Not refunded. You get access to the recording instead.
- A recording bought on its own
- Not refundable. It is delivered the moment it is bought.
No refund is ever conditional on giving us a review, a testimonial or a reference.
Your accounts, your data
You buy your own AI subscription and your own tool accounts. We work inside them and hand them back. Everything we build runs on your side, so nothing switches off because you stopped working with us, and you can change any part of it without asking us.
You own the workflow, the configuration and the written materials produced for you. We keep the right to reuse the general methods and the framework itself, neither of which is specific to you.
Confidentiality, both directions
What you tell us about your business stays with us. We will not name you, show your workflow, quote you, or describe your business recognizably anywhere — in a talk, a post, a case study or a conversation — without your written permission, asked for in advance. That applies to anonymized versions too.
The same goes the other way: material from a session or a build is for you and your team, not for redistribution.
What we do not take on
- Anything touching patient records or health information.
- Anything that moves money or handles payment details.
- Personal data about other people at any scale.
- Anything that would require a formal security review to approve.
- Acting for you in front of any government agency.
- Work for a government department, a defense contractor, or a company pursuing that kind of business.
When we decline something we give you a specific referral rather than a vague no. If work turns out mid-engagement to be one of these, we stop, tell you why, and refund what has not been earned.
What AI systems do and do not do
These systems make mistakes, including confident ones. Everything we build has a verification step — a check before anything leaves — and a written plan for what to do when it goes wrong, and we will show you both. What goes out under your name is still yours to stand behind, and a person belongs in the loop anywhere a mistake would be expensive.
Limits
If something we did goes wrong, what we owe you is capped at what you paid us for that piece of work. We are not responsible for the behavior, pricing, availability or terms of the third-party tools a workflow runs on, and we are not responsible for indirect or consequential business losses. Nothing here limits anything that cannot lawfully be limited.
Ending it
Either of us can stop before a build begins, and the refund rules above say what happens to the money. There is no retainer, no subscription and nothing that renews on its own, so there is nothing to cancel once a piece of work is finished.
If these terms change
The date at the top changes with them. The terms that apply to your work are the ones in force on the day you paid, and the scope document names that version.
Questions
Ask before you buy rather than after: daytenconsulting@gmail.com.