Effective October 28, 2026 · Founding cohort, January 19 to February 9, 2027
These terms cover Executive AI Build, a paid program from Moving Average, Inc. ("we"), a Texas corporation. "You" means the leader who reserves a seat and the company they reserve it for. By paying for a seat, you agree to these terms. The Executive AI Build page describes the program, and these terms add the rules that go with it. The site's Terms of Use and privacy policy also apply. Where they conflict with these terms, these terms win for the program.
What you get
A seat for you and one process owner: four live sessions on Zoom on Tuesdays from January 19 to February 9, 2027, a follow-up session about six weeks later, the preparation materials, written feedback from John Knox on your project, and the program's Slack channels.
We'll do our best to hold every session at the published time. If we have to move one, we'll give you as much notice as we can.
Price and refunds
The founding price is $2,500, paid in full when you reserve a seat. Payment is processed by Stripe.
- Before the first session (January 19, 2027): a full refund, for any reason. Ask through the contact form or by replying to any program email.
- After the first session: no refund. If you can't continue, your seat moves to the next cohort.
- If the cohort doesn't run, or we decide it isn't a good fit for you: a full refund.
Confidentiality
What's said in Build stays in Build:
- Lessons are shared under the Chatham House Rule. A lesson is a method or pattern that would apply to any company doing similar work, told without anything that shows whose it was. For example: "support replies improved once the team gave the AI its 20 most common questions with approved answers, and sent refund requests to a person." Anyone may use lessons, but no one may say who said it or where they work. John may write about lessons without names.
- Business details stay in the group. A detail is anything specific to one company: its customers, product plans, numbers (including results), how its systems are set up, its own prompts, documents and data, and any combination of facts that would show whose it was. Details are confidential by default, whether or not anyone marks them. John will ask before using any detail, including a result with a number.
- When you're not sure which one something is, treat it as a detail.
- Keep the most sensitive material out. Don't bring customers' personal data, health or financial records, passwords or keys, or anything a contract forbids you to share, to the sessions, the channels or your check-ins. If you must discuss something like that, describe it without the details, or mark it confidential and ask before you share it.
- These rules bind everyone in the program, including your process owner. You're responsible for making sure your process owner knows and follows them.
Transcripts and channels
We transcribe the sessions. We don't record video, and if that ever changes, we'll ask everyone in the session first. We make reasonable efforts to remove confidential details from each transcript before we share it. You can ask us to remove anything else. Transcripts go only to the leaders in the group, and we delete them 30 days after the follow-up session. Please don't bring AI note-taking bots.
The Slack channels are for members during the program and for a limited time afterward. We'll tell you before a channel closes. Slack keeps its own copy of what's posted, under Slack's terms.
Your work and ours
Your work is yours. The process you build, the guide to running it, your prompts, your data, and everything you create for your project belong to you.
Our materials are for your company's use. The handbook, templates, checklists, videos and other program materials stay ours. You and your process owner may use them, and adapt them, inside your company. Please don't resell them, publish them, or run your own program from them.
We'll ask before we use your name, your company's name, or a quote from you in anything public.
Your responsibilities
You decide what runs in your business. Before you put a process into use, you and your team check its results and make sure it complies with the law, your contracts, and the terms of the AI tools and other services you use. You're responsible for your accounts, your data and your systems, and for any costs of the tools you choose.
Advice and results
Build is tailored to your project, and the feedback you get is John's honest judgment. It is not legal, investment, financial, tax, accounting or other professional advice. John Knox is not a lawyer or a registered investment adviser. For those questions, talk with a qualified professional.
What you get out of Build depends on your process, your systems, and the time you and your process owner put in. We can't guarantee a particular result.
Limit of liability
We provide the program with care, but otherwise "as is," without warranties of any kind, express or implied, to the fullest extent the law allows. We are not liable for any indirect, incidental, special, consequential or punitive damages, or for lost profits, data or goodwill, arising from the program or from anything you build or decide during it. Our total liability for any claim about the program is limited to the amount you paid for it.
Some places don't allow these limits, so they may not all apply to you.
Changes, law and contact
We may update these terms for future cohorts at any time. For a cohort that has already paid, a change applies only in two ways: we tell you before your cohort starts, and you can take a full refund instead; or, once the program has started, you agree to it in writing (an email or a Slack message is enough). Otherwise the terms you paid under stay in force for your cohort. These terms are governed by the laws of the State of Texas, without regard to its conflict-of-law rules. If a court finds part of them unenforceable, the rest still applies.
Questions? Use the contact form.