This article is general educational information, not legal advice. Disclosure obligations depend on your specific employment agreement, policies, and state. When in doubt, have your documents reviewed by an employment attorney.
Should you tell your employer about AI side business is really three questions wearing one question’s clothes, and untangling them is the entire answer. Question one: does your employer’s policy require disclosure? — a factual question with a factual answer, and if that answer is yes, the decision is over: you disclose, properly, full stop, because a required disclosure skipped is the single risk in this whole library that has no upside and no repair. Question two: if disclosure is optional, is it wise for you? — a judgment call with real factors on both sides, which this post maps honestly rather than pretending one answer fits everyone. Question three: if and when you tell, how? — a craft question with a learnable script. Most anxiety about this topic comes from mashing the three together; most good outcomes come from answering them in order.
One framing note before the framework, because this library has said it before and it governs everything here: discretion and concealment are different things. Choosing not to volunteer optional information is discretion — normal, professional, and practiced by every employee about most of their personal life. Withholding information your contract or policy requires you to provide is concealment — and concealment converts a compliant side business into a terminable offense regardless of how innocent the business itself is. The quiet-build posts in this series are quiet within the rules; this post is about finding exactly where your rules draw the line.
The stakes context is the standing one. According to Crunchbase News’ layoffs tracker, roughly 127,000 U.S. tech workers were laid off in 2025, and per Wall Street Journal reporting throughout 2025–2026, reductions remain policy — which is both why parallel income (against a W-2 that is the most withheld and least deductible income there is) is worth building, and why the employment relationship funding the build deserves careful handling. The business itself is the least of anyone’s worries: local AI implementation for service businesses — by the U.S. Small Business Administration’s figures, a market of roughly 36.2 million small businesses with meaningful AI installed at fewer than 4% by most adoption surveys — is about as far from most corporate employers’ interests as commerce gets, which is precisely what makes both the disclosure conversation and the discretion option easier than people fear.
This guide walks through the disclosure decision in 2026: the required-disclosure check that comes first, the honest map of when voluntary disclosure helps and when discretion serves better, the conversation script, and the honest realities — including the twin failure modes on either side of the line.
Question One: Is Disclosure Required?
The factual check, done before any judgment call:
Read three documents: your employment agreement, the employee handbook’s outside-activity / moonlighting section, and the conflict-of-interest policy (plus, at larger companies, any code-of-conduct disclosure process). You are looking for language like “employees must disclose outside business activities,” “written approval is required for outside employment,” or a conflict-questionnaire process that asks the question directly.
If any of them require it: disclose, through the stated channel, accurately. Describe the business precisely — implementation services for local small businesses, no overlap with employer products, customers, or markets, conducted entirely on personal time with personal resources — and get the acknowledgment or approval in writing. This is the FAANG-post rule generalized: a filed, approved outside activity is bulletproof; an unfiled required one is a landmine that gets more dangerous the better the business does.
If the documents are silent or ambiguous: ambiguity goes to an employment attorney, not to a guess — one consult, your actual paper, your state. (Annual conflict-of-interest attestations deserve special attention: signing one inaccurately converts quiet discretion into active misrepresentation, which is the line no builder should ever cross.)
Only when the answer to question one is a clean “not required” does question two exist.
Question Two: If Optional — The Honest Map
Where disclosure is genuinely voluntary, the decision has real weight on both sides:
The case for telling:
It converts a secret into a non-event. Carried secrets leak energy (the balance post’s most expensive line item), and a disclosed side business ends the ambient worry about being “found out” via a client’s LinkedIn post or a mutual acquaintance.
It banks trust with the manager relationship. Volunteered transparency, offered before it was asked for, reads as integrity — and managers who hear it from you respond very differently than managers who hear it from the rumor mill.
It future-proofs the transition. The eventual resignation (per the roadmap posts) lands gently on ground that was prepared; some builders have even converted disclosure into flexibility — a four-day arrangement, a clean part-time bridge — that discretion could never have negotiated.
The case for discretion:
Workplace dynamics around side income are genuinely unpredictable. A secure, reasonable manager hears “well-managed professional with initiative”; an insecure one hears “one foot out the door” — and you get exactly one read on which manager you have. Promotion decisions, stretch assignments, and layoff lists are influenced by perceived commitment, fairly or not.
Information travels beyond its audience. The manager you trust tells their manager in a calibration meeting; the disclosure you made to one person becomes context you don’t control in rooms you’re not in.
Timing may simply be early. A month-two build with zero clients is a hypothesis, not a fact; many builders reasonably wait until the practice is real (and their performance record is visibly untouched) before volunteering anything.
The honest synthesis: discretion is the sensible default for optional disclosure in the early build — provided the compliance layer is immaculate — with voluntary disclosure becoming increasingly attractive as (a) the practice stabilizes, (b) the manager relationship is strong and secure, and (c) the transition horizon approaches. The decision is also revisitable: discretion now does not foreclose disclosure later, while disclosure now cannot be undone. Asymmetries like that deserve respect.
Question Three: The Conversation, If and When
The craft of telling well, for the required filing and the voluntary conversation alike:
Lead with reassurance, not confession. The opening frame: “I want to be transparent about something that doesn’t affect my work here.” Then the three facts that answer every unasked question: what it is (implementation services for local small businesses — dental offices, HVAC companies), what it isn’t (no overlap with our products, customers, or market; no use of company time or resources), and what hasn’t changed (my commitment and performance here — which the record shows).
Choose the channel deliberately. Required disclosures go through the stated process (HR portal, conflict questionnaire, legal review) — precisely, in writing. Voluntary conversations usually belong with the direct manager first, in person, brief and matter-of-fact; a five-minute non-event framing produces a five-minute non-event.
Bring the paper trail, not the pitch. If asked for detail, the LLC name and the market description suffice; nobody needs revenue figures, client names, or the dream. Enthusiasm about the side business, in this room, is miscalibrated — the message is boring and managed, and boring is the goal.
And never negotiate the wall. Whatever the reaction, the standing rules are non-negotiable in both directions: the employer gets full professional performance and zero side-business presence on their time and tools; the side business stays in its evening-and-weekend lane. The conversation announces the wall; it doesn’t open it.
Why the Order of Questions Is the Whole Framework
The structural recommendation: answer required-first, wise-second, how-third — because each question only exists if the previous one resolved, and most disclosure disasters come from answering them out of order.
The reasoning is structural:
- Builders who start with question two (“would telling be smart?”) while question one was answerable (“telling was mandatory”) have made a judgment call about something that was never theirs to judge — the concealment trap in its most common form.
- Builders who agonize over question three’s script before resolving question two burn energy on a conversation they may rightly never have.
- The ordered framework also localizes the anxiety: question one is a reading assignment, question two is a bounded judgment with named factors, question three is a rehearsable script. Nothing in the stack is the formless dread it impersonates.
- And the order protects the relationship either way: the employer who eventually learns of a compliant, walled, optional-disclosure business has nothing to object to; the employer who learns of a concealed required-disclosure one has everything. The framework’s first question is where the entire risk lives — which is why it goes first.
I graduated from Vanderbilt. Almost went straight into investment banking. I spent years at Vanderbilt University reading the same labor reports and McKinsey decks that documented the trends now defining 2026 — and I came away with one inescapable conclusion: a salary has a ceiling. Inflation doesn’t.
I decided not to try and outrun inflation with a salary. I replaced my corporate salary by implementing pre-built AI tools we leverage — Intercom AI, Helios AI, and n8n at the core, plus the broader implementation stack — for service businesses with operational gaps they can’t fix on their own.
What Most Articles Won’t Tell You About the Disclosure Decision
A few honest realities:
The twin failure modes are the Undershare and the Overshare. The Undershare is the grave one: skipping a required disclosure, or shading an annual conflict attestation, on the theory that the business is too small or too unrelated to matter — a theory that fails precisely when the business succeeds enough to be noticed. The Overshare is the common one: narrating the side venture to colleagues, posting the launch on LinkedIn, letting enthusiasm broadcast what discretion should have held — and discovering that information, once released, routes itself. The framework’s line between them is bright: everything the policy requires, disclosed precisely; everything else, released deliberately or not at all.
Colleagues are not a disclosure channel. The framework governs employer disclosure; workplace chatter is a separate and simpler rule — the quiet-build posts’ standing advice: tell almost no one at work, because you control the first telling and nothing after it.
A hostile reaction to a voluntary disclosure is information, not catastrophe. If a compliant, walled, performance-clean side business draws managerial hostility, you’ve learned something real about the relationship funding your build — and the wall you announced is also the boundary that protects you while you decide what to do with the learning.
The strongest disclosure is a performance record. Whenever and however the telling happens, an unimpeachable day job is the exhibit that settles it. The builder whose work never dipped has a five-minute conversation; the builder whose work visibly funded the side project has a different one, deservedly.
Document everything on the required path. Filed forms, written approvals, dated acknowledgments — the boring folder that answers any future question before it’s asked. You learn a skill instead of buying into a business model, and the skill includes running the employment relationship like the professional you are. (This post is educational, not legal advice; your documents and your attorney govern your specifics.)
According to McKinsey’s Superagency in the Workplace report (2025), 92% of companies plan to increase their AI investments over the next three years, yet only 1% describe their AI deployment as mature. The builders who handle this decision well in 2026 are not the boldest or the most secretive. They’re the ones who recognized that the question decomposes into three answerable ones — and executed methodically through them, in order.
Read the Three Documents This Week
The action sequence for should you tell your employer about AI side business:
This week: Read the employment agreement, the outside-activity policy, and the conflict-of-interest process. Answer question one factually.
If required: File the disclosure through the stated channel, accurately, in writing — this week, not eventually.
If optional: Run the question-two map against your manager, your timeline, and your temperament; default to disciplined discretion in the early build; calendar a revisit at each roadmap gate.
If and when telling: The three-fact script — what it is, what it isn’t, what hasn’t changed — brief, boring, and documented.
Always: The wall, both directions, immaculate — and the performance record that makes every version of this conversation a non-event. (Educational sequence; your paper and your counsel set your specifics.)
The builders deciding this well in 2026 are not the ones who guessed. They’re the ones who recognized that the answer was in three documents and three questions — and executed methodically through the framework.
Read the policy first. Disclose what’s required, always. Choose the rest deliberately. Keep the wall immaculate. Let the record speak.
Reminder: this article is educational information, not legal advice. Your agreement, your policies, your attorney.
Pick the industry. Take the first step. If you want to see the playbook fully in action – tap here to start.
