1. Acceptance of these terms
These Terms of Service ("Terms") govern your use of walkeraisystems.com and any services provided by Walker AI Systems LLC, a Texas limited liability company operated by Byron Walker in Lindale, Texas ("Walker AI Systems," "we," "us," or "I").
By using this website, contacting us about an engagement, or engaging us for work, you agree to these Terms. If you don't agree, don't use the site and don't hire me. No hard feelings.
These Terms are read together with our Privacy Policy.
2. What we provide
Walker AI Systems designs, builds, deploys, and operates AI and automation systems for mid-market companies. That currently includes AI assessments, agent systems, document and data pipelines, back-office workflow automation, custom software, operations dashboards, and operations retainers on systems we have built.
Prices published on this website are indicative starting points, not offers. The binding scope and price for any engagement is the one in your signed Statement of Work.
Every engagement starts with a paid AI Assessment: fixed scope, fixed price, with a written findings and roadmap report delivered on a named date. The report is yours whether or not you build anything with me afterward, and it may well conclude that you shouldn't build anything yet. There is no free consultation; a diagnosis that costs nothing tends to produce a proposal shaped like whatever the consultant already wanted to sell.
3. Engagements & Statements of Work
Every paid engagement is governed by a written Statement of Work (SOW) signed by both parties. The SOW defines:
- What is being built, in specific terms.
- What is explicitly out of scope.
- What it costs and when it's payable.
- The timeline and what "done" means.
- What you need to provide and by when.
If it isn't in the SOW, it isn't in the project. That protects you from me quietly reducing scope, and it protects me from unbounded work. New requests mid-project get a written change order with a price attached before any work happens on them.
Where an SOW conflicts with these Terms, the SOW wins for that engagement.
How an SOW gets signed
Electronically. An SOW, change order, or acceptance certificate signed through an electronic signature service is as binding as ink on paper, and each party's electronic signature satisfies any requirement for a writing or an original, under the federal E-SIGN Act, the Texas Uniform Electronic Transactions Act, or any similar law. A document may be signed in counterparts, and a scanned or emailed copy of a signed page has the same effect as the original.
You sign first and I countersign; the agreement takes effect on the later signature. You'll always receive the fully executed copy along with the signature certificate showing when each party signed. If your organization requires its own signature platform, that's fine. Say so and we'll use it.
4. Ownership & intellectual property
What you own
On full payment for an engagement, you own the deliverables built specifically for you: configurations, prompts, workflows, custom code, documentation, and the data flowing through the system. Accounts with third-party providers are created in your name from day one and the credentials are yours.
You can take the system in-house, hand it to another vendor, or throw it away. There are no hostage situations here.
What I keep
I retain ownership of my pre-existing and general-purpose materials: my methods, internal tooling, reusable patterns, templates, and the accumulated know-how of doing this work. You get a perpetual, irrevocable, royalty-free license to use any of it that is embedded in your deliverables, for as long as you like.
Put simply: you own your system. I don't have to forget how to build systems.
Your materials
Anything you give me, including your data, your logos, your customer lists and your documents, stays yours. I get a limited license to use it only to do the work you hired me for.
Publicity
I may reference the fact that we worked together, and describe the work in general terms, in a case study or on this website. I will not publish your name, your logo, your data, or specific results without your written permission. Ask me not to mention you at all and I won't.
5. Third-party services & costs
Systems I build run on third-party infrastructure: telephony carriers, AI model providers, hosting, databases, scheduling tools. These are billed directly to accounts in your name, not marked up and passed through me.
You see every dollar those vendors charge. I don't take a cut of them and I have no incentive to pick an expensive one. Third-party running costs vary widely by system. A document pipeline processing thousands of pages a month costs materially more to run than a scheduled internal agent. I'll give you a written estimate before you commit, and the assessment report includes it.
The flip side: these vendors have their own terms, their own outages, and their own pricing changes. I don't control them, and I'm not liable for what they do. What I am responsible for is noticing when they break and telling you.
Some services, notably SMS messaging in the United States, require carrier registration and approval that is outside my control and can take days or weeks. I'll tell you honestly what the lead time looks like, but I can't promise a carrier will approve anything.
6. Payment
If you're having a cash-flow problem, tell me before the invoice goes past due. I'm a one-person business and I'd rather work something out than send a collections letter.
7. Cancellation
Monthly services
Month to month. Cancel any time with 30 days' written notice. No termination fee, no clawback, no minimum term. You keep everything built for you, the accounts, and the documentation. I'll do a handover call at no charge.
Fees already paid for the current period are not refunded, but the service runs through the end of that period.
Build engagements
You may cancel a build in progress at any time with written notice. You pay for work completed to that point, and you receive everything produced so far. I will not hold partial work hostage over a cancellation.
If I cancel
I may end an engagement with 30 days' notice if the work turns out to be outside my competence, if the relationship isn't working, or if you use the system for something in section 11. If I terminate for any reason other than your breach, I refund unearned fees and hand over everything built to date.
8. The guarantee
Nothing I build fails silently.
Systems I build are instrumented to detect and report their own failures. If a system I built and monitor fails without alerting you or me, I fix that gap at no charge: both the failure and the reason it went unreported.
To be precise about what this is and isn't:
- It covers silent failure: the system broke and nobody was told.
- It does not mean the system will never make a mistake. AI systems get things wrong. The promise is that you will find out.
- It applies to systems I actively monitor under a current monthly agreement.
- It does not apply after you modify the system yourself, or after monitoring lapses.
- It is a commitment to fix the gap, not a money-back guarantee or a cash remedy.
This is the entire reason the business exists. If it ever stops being true, hold me to it.
9. Your responsibilities
Projects fail on inputs more often than on engineering. To hold up your end:
- Give me accurate information about how your business actually works, including the parts that are messy.
- Respond within a reasonable time when I'm blocked on you. Timelines in an SOW assume you do.
- Provide access to the systems the automation needs to touch.
- Review what I deliver and tell me when it's wrong.
- Comply with the law in how you use the system, including consent, recording, and messaging rules covered in section 11.
Delays caused on your side move the timeline. I'll tell you when that's happening rather than quietly missing a date.
10. What AI systems can and cannot do
This section matters. Read it.
- AI systems make mistakes. They mishear, misinterpret, and occasionally produce confident nonsense. Anyone selling you a system that never errs is lying to you.
- They are not a substitute for professional judgment. A system I build does not give legal, medical, or financial advice, and should not be configured to.
- They are not for life safety. Do not deploy a system I build as the sole path for emergency response, medical triage, or anything where a missed message means someone gets hurt. Emergencies need a human path and a fallback number.
- Third-party outages happen. Carriers go down, model providers rate-limit, APIs change without warning. I build for it and monitor for it; I cannot prevent it.
My commitment is not that the system will be perfect. It's that it will be monitored, measured, and honest about its own error rate: and that you'll get a report showing you where it got things wrong, rather than a dashboard full of green checkmarks.
11. Acceptable use
You agree not to use anything I build to:
- Break the law, including the TCPA, CAN-SPAM, state recording-consent laws, or carrier messaging rules.
- Send unsolicited marketing calls or texts to people who did not consent to receive them.
- Deceive people about whether they are speaking to a machine. Systems I build disclose that they are AI when asked, and I will not remove that.
- Harass, defraud, or discriminate against anyone.
- Handle regulated data such as protected health information, cardholder data, or similar, unless the SOW explicitly scopes for it and the appropriate agreements are in place.
- Replace a human in a life-safety or emergency-response path.
This isn't boilerplate. Violate it and I will terminate the engagement, and I'd rather lose the revenue than build something that hurts people.
12. Confidentiality
Each of us will protect the other's confidential information, use it only for the engagement, and not disclose it to anyone who doesn't need it. This survives the end of the engagement.
It doesn't cover information that's already public, that you or I already knew, that we independently developed, or that a court orders us to hand over. If I'm legally compelled to disclose something of yours and I'm permitted to tell you, I will.
Signed a mutual NDA with me? That governs instead of this section.
13. Warranty disclaimer
EXCEPT AS EXPRESSLY STATED IN THESE TERMS OR A SIGNED STATEMENT OF WORK, THE WEBSITE AND SERVICES ARE PROVIDED "AS IS" AND "AS AVAILABLE," WITHOUT WARRANTIES OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE, OR NON-INFRINGEMENT.
WALKER AI SYSTEMS DOES NOT WARRANT THAT ANY AI SYSTEM WILL BE ERROR-FREE, UNINTERRUPTED, OR THAT IT WILL PRODUCE ANY PARTICULAR BUSINESS RESULT. ESTIMATES OF REVENUE RECOVERED, CALLS CAPTURED, OR TIME SAVED ARE ILLUSTRATIVE AND ARE NOT GUARANTEES.
In plain English: I will do good work and I stand behind it, but I'm not promising your revenue will go up by a specific amount, and nobody honest would.
14. Limitation of liability
TO THE MAXIMUM EXTENT PERMITTED BY LAW, WALKER AI SYSTEMS SHALL NOT BE LIABLE FOR ANY INDIRECT, INCIDENTAL, CONSEQUENTIAL, SPECIAL, EXEMPLARY, OR PUNITIVE DAMAGES, OR FOR LOST PROFITS, LOST REVENUE, LOST BUSINESS OPPORTUNITIES, OR LOSS OF DATA, ARISING OUT OF OR RELATING TO THE SERVICES, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
WALKER AI SYSTEMS' TOTAL AGGREGATE LIABILITY ARISING OUT OF OR RELATING TO THESE TERMS OR ANY ENGAGEMENT SHALL NOT EXCEED THE TOTAL FEES YOU PAID TO WALKER AI SYSTEMS IN THE TWELVE (12) MONTHS IMMEDIATELY PRECEDING THE EVENT GIVING RISE TO THE CLAIM.
These limits do not apply to gross negligence, willful misconduct, or anything a court says can't be limited.
I'm being straight with you about why this is here: I'm one person. If an automation I built contributes to a bad outcome in your business, I can't absorb unlimited liability for it, and no solo consultant can. The cap is what makes it possible for me to do this work at all.
15. Indemnification
You agree to indemnify and hold harmless Walker AI Systems from claims arising out of: your use of a system in violation of section 11, content or data you provided, your failure to obtain required consents from your own customers, or your breach of these Terms.
I'll indemnify you against claims that my original work product infringes someone else's intellectual property.
16. Governing law & disputes
These Terms are governed by the laws of the State of Texas, without regard to conflict-of-law rules. Venue for any dispute lies in the state or federal courts located in Smith County, Texas.
Before either of us files anything, we agree to talk about it first: a good-faith conversation within 30 days of written notice of the dispute. Most problems that end up in court were a phone call that didn't happen.
If any provision of these Terms is found unenforceable, the rest stays in effect.
17. Changes to these terms
I may update these Terms. The "last updated" date at the top will change. Continuing to use the website after an update means you accept it.
Changes to these Terms do not alter a signed Statement of Work. Your SOW is your SOW; I can't amend your contract by editing a web page, and I wouldn't try.