TL;DR
Do not use AI as a fake customer, unsupervised agent on money/security/legal issues, inventor of metrics, or anywhere review cost exceeds creation savings. Accelerate drafts; keep humans on trust, truth, and irreversible calls.
Introduction
Unbounded AI advocacy creates fragile companies. This is the stop list — with alternatives — so you use leverage without avoiding the human work that builds businesses.
Ten Hard Stops
- Personas instead of interviews. Scripts yes; synthetic buyers no.
- Autonomous high-stakes support. Drafts OK; unsupervised refunds/security no.
- Invented fundraising/marketing numbers. If you did not measure it, do not publish it.
- Legal conclusions from chat. Prep questions; hire counsel for decisions.
- Tasks where review > work. Tiny edits, simple sheets — just do them.
- Spam at scale. Narrow lists beat AI-personalized sludge.
- Skipping founder sales too early. You need objection scar tissue.
- Secrets and full exports into random tools. Privacy basics apply.
- Unbounded repo rewrites. Spec + small diffs + verify.
- Automated people decisions. Biased, indefensible, culturally toxic.
Decision Tree
Is an error cheap/reversible? Is ground truth in your context? Will a human review before external impact? Would you put your name on a public version? Two or more "no" → slow down or skip.
Alternatives Map
Fake interviews → 5 real calls. Autobot refunds → macro + approval. AI TAM → bottom-up math. Entity choice via chatbot → advisor checklist. Mass cold email → warm intros. Agent repo rewrite → vertical slice + PR.
Culture
Praise deliberate non-use. Ban "ChatGPT said so" as a rationale. Ask weekly: where did we skip AI on purpose?
Where AI Remains Excellent
Outlines, editing, test-idea generation, summaries you still skim, boilerplate under review, option brainstorming you filter.
Personal Avoidance Signals
No customer talks in 14 days but dozens of strategy chats; AI feature spam nobody asked for; busy anxiety without shipping; pricing logic that only exists in a transcript.
Team Policy Snippet
"AI is allowed for drafts and coding assist. AI is not allowed to send customer-facing commitments, invent metrics, or replace scheduled customer conversations. When unsure, ask before pasting customer data."
Field Notes From Operators
The difference between AI tourism and AI leverage is usually process. Operators who win write the decision criteria down, keep prompts in a shared library, and schedule a weekly review of what the tools got wrong. They treat model output like an intern draft: useful, sometimes impressive, never automatically trusted with customers, cash, or compliance.
When something works, they turn it into a checklist. When something fails, they add a ban rule. Over a quarter, that creates a private playbook no generic Twitter thread can replace. Your advantage is not access to the same models everyone else has — it is the taste and constraints you encode around them.
Use the rest of this guide as a living document. Revisit after each quarter's tooling changes. Delete advice that no longer matches how you work. Add examples from your own tickets, deploys, and sales calls so the next hire inherits judgment, not just subscriptions.
If you only remember one practice, make it this: every AI-assisted external action needs a named human owner. Ownership is what converts speed into responsibility. Without it, you get probabilistic chaos with a friendly chatbot UI.
Practical Exercises
Exercise A — Constraint writing. Take a vague prompt you used last week. Rewrite it with stakes, options, criteria, and a required disconfirming paragraph. Compare outputs. Keep the better template in your library.
Exercise B — Data minimization. Redo a support or research prompt with redaction. Note whether quality dropped. If not, make redaction the default.
Exercise C — Cost model. Pick one AI SaaS tool. Estimate monthly cost at 10x usage. Decide in writing whether that curve is acceptable.
Exercise D — Stop list. Add three company-specific "do not use AI for X" rules based on your product risk. Share them with anyone who has a seat.
Exercise E — Postmortem. Find one bad AI output that reached a customer or commit. Document cause, blast radius, and the process change that prevents repeats.
These exercises take a few hours total and prevent months of quiet drift.
Worked Walkthrough
Imagine a solo founder considering an AI support add-on at $400/month. They run a 21-day pilot on 60 tickets, measure edit distance and CSAT, discover the bot mishandles plan-change requests, and keep draft-only mode while rewriting three KB articles. They revisit autonomy next quarter. That sequence — hypothesis, timebox, metric, decision — is the entire craft. Apply it to vendors, content systems, coding agents, and prompting for strategy. The tools change; the discipline does not.
Another walkthrough: a founder wants "thought leadership" via AI. They brief one distinctive thesis from a real customer failure, draft with AI, rewrite the opening by hand, add a checklist artifact, publish, and pitch a single niche newsletter. One earned mention follows. That beats twenty interchangeable posts with zero distribution. Systems create that behavior on purpose.
Extended Playbook
Operators who get durable value from AI treat it like infrastructure with runbooks. They keep a shared prompt library, a stop list, and a weekly 30-minute review of failures. They measure outcomes (tickets resolved well, features shipped safely, pages that earn citations) instead of chat volume. They assign a human owner to every customer-facing automation. They budget for business-tier privacy settings the moment real customer data appears. They refuse multi-year vendor contracts before a pilot proves fit on their own messy inputs.
They also write. Short specs before coding agents. Decision memos before strategy chats. Briefs before content drafts. The writing is the control surface; the model is the accelerator. Without writing, you get confident entropy.
Another durable habit: version your rules. When a bad output ships, add a ban. When a good pattern repeats, add a template. After a quarter you have a private operating system that competitors cannot copy by buying the same subscriptions. That is the real stack advantage — taste encoded as process.
Finally, schedule deletion. Old chats, unused seats, stale connectors, and zombie pilots accumulate risk and cost. A monthly cleanup is as important as a new tool trial. Speed without subtraction is how startups drown in dashboards.
Scenarios and Responses
Scenario: investor asks for AI strategy. Answer with jobs-to-be-done, current tools, data boundaries, and what you will not automate. Do not perform science fiction.
Scenario: customer asks if a human will help. Promise a human path and keep it. Autonomy theater destroys NPS.
Scenario: contractor pastes a client list into a consumer model. Revoke access, delete where possible, review legal duties, update acceptable use training immediately.
Scenario: coding agent "fixes" auth broadly. Revert, re-spec, implement in a thin slice, add a regression checklist.
Scenario: content calendar demands five AI posts/week. Cut to one deep piece with distribution. Volume without voice trains readers to ignore you.
Scenario: vendor demo looks perfect. Demand a pilot on your samples with kill criteria and 10x pricing before you celebrate.
Checklists You Can Run Tomorrow
- Approved AI tools list exists and is shared
- Training opt-out enabled on business accounts
- One-page acceptable use for data
- Prompt library with at least five templates
- Stop list with at least five bans
- Pilot template for any new AI vendor
- Content brief template with voice kit link
- Support escalation matrix if AI drafts exist
- Weekly failure review on the calendar
- Monthly seat and connector cleanup
If fewer than six boxes are checked, fix basics before buying another tool.
Extended Playbook
Operators who get durable value from AI treat it like infrastructure with runbooks. They keep a shared prompt library, a stop list, and a weekly 30-minute review of failures. They measure outcomes (tickets resolved well, features shipped safely, pages that earn citations) instead of chat volume. They assign a human owner to every customer-facing automation. They budget for business-tier privacy settings the moment real customer data appears. They refuse multi-year vendor contracts before a pilot proves fit on their own messy inputs.
They also write. Short specs before coding agents. Decision memos before strategy chats. Briefs before content drafts. The writing is the control surface; the model is the accelerator. Without writing, you get confident entropy.
Another durable habit: version your rules. When a bad output ships, add a ban. When a good pattern repeats, add a template. After a quarter you have a private operating system that competitors cannot copy by buying the same subscriptions. That is the real stack advantage — taste encoded as process.
Finally, schedule deletion. Old chats, unused seats, stale connectors, and zombie pilots accumulate risk and cost. A monthly cleanup is as important as a new tool trial. Speed without subtraction is how startups drown in dashboards.
Scenarios and Responses
Scenario: investor asks for AI strategy. Answer with jobs-to-be-done, current tools, data boundaries, and what you will not automate. Do not perform science fiction.
Scenario: customer asks if a human will help. Promise a human path and keep it. Autonomy theater destroys NPS.
Scenario: contractor pastes a client list into a consumer model. Revoke access, delete where possible, review legal duties, update acceptable use training immediately.
Scenario: coding agent "fixes" auth broadly. Revert, re-spec, implement in a thin slice, add a regression checklist.
Scenario: content calendar demands five AI posts/week. Cut to one deep piece with distribution. Volume without voice trains readers to ignore you.
Scenario: vendor demo looks perfect. Demand a pilot on your samples with kill criteria and 10x pricing before you celebrate.
Closing Perspective
The founders who look "anti-AI" in 2026 are often the ones using it most effectively — just not everywhere. They refuse fake productivity. They protect customer trust. They keep learning loops human where it counts. Use AI heavily where errors are cheap; refuse it where errors are expensive. That single distinction is worth more than any prompt pack.
Refusal is a skill. Practice it in public with your team so speed never outruns judgment.
Key Takeaways
- Ban fake customers, unsupervised trust moments, and fabricated facts.
- Skip AI when review erases the savings.
- Protect secrets, legal calls, and early sales learning.
- Use reversibility as your filter.
- Make human judgment culturally safe.
FAQ
When avoid AI?
When it replaces reality, unsupervised trust, invents facts, or slows you after review.
Customer discovery?
Not as a replacement for humans.
Investor updates?
Draft only from real bullets.
Slowdown modes?
Unread drafts, agent thrash, AI-review meetings.
Outreach?
No spam factories.
Rule of thumb?
Reversible cheap errors → assist. Trust/legal → human-first.