A Mindpod Technologies Newsletter · Atlanta All issues

The Mindpod Spot Issue No. 04  ·  November 2026

Who Owns It?, in a small organization, every system either has a name on it or it has nobody. Three questions tell you which, in about ten minutes each.

In This Issue

  1. Who Owns It?, why “it came with the last IT person” means nobody, and what nobody costs.
  2. Three Questions, who can change it, who checks it, what happens when it’s wrong.
  3. Field Reports, the ownership check for law firms, clinics, nonprofits, and businesses that hand their IT to an outside provider (an MSP).
  4. From the Editor’s Desk, holding our own AI agents to the same three questions.

Highlights

  • The expensive messes rarely start with a bad decision. They start with no decision.
  • An owner is a named person, not a department, a vendor, an invoice, or “the IT company.”
  • Three questions, asked out loud: who can change it, who checks it, what happens when it’s wrong.
  • The plainest form of ownership is a thing that stops and asks before it acts.
Feature

Who Owns It?

Before you ask whether any piece of your technology is any good, ask the question that comes first: does it have an owner?

The expensive messes in a small organization almost never start with a bad decision. They start with no decision, a system that arrived, stayed, and quietly became something the business can’t run without while nobody was watching. The backup job everyone assumes is running. The shared login nobody remembers creating. The subscription that renews every year because cancelling it would mean working out what it does. None of those were chosen. They accumulated, and in a small firm, accumulation is the default state of technology. So the first question isn’t “is this any good?” It’s “does this have an owner?”

Three Questions

Ask these this week

Pick one system your organization lives with, the backups, the file share, the tool that sends reminders, and ask three things out loud.

  1. Who can change it?

    A name, not a role. If the answer is “the IT company” or “whoever has the admin password,” you’ve found a system that can be changed by people who don’t own it and can’t be changed by the people who do. Write down who may change it, and who has to be asked first.

  2. Who checks it?

    “Working” needs a definition and someone watching. A backup nobody has restored from is a hope, not a backup. An automation nobody has looked at since the day it was set up is a stranger sending mail on your letterhead. Name the person who looks, how often, and what “fine” looks like.

  3. What happens when it’s wrong?

    Not the subscription price, the bad week. If this fails, misfires, or leaks, who finds out, how fast, and what can be undone? Owners can describe the failure. Everyone else describes the feature list. If nobody can describe the bad week, the system is making decisions for your business.

Scoring is blunt on purpose

Three clear answers: that system has an owner, move on. One or two: supervised in name only; tighten the gaps. None: that technology is running part of your business unsupervised until someone takes the pen. A failed check isn’t an indictment of the tool. It’s a vacancy, fill it with one name, one paragraph on what the thing does and what it costs when wrong, and a date for the next check.

Field Reports

The ownership check, sector by sector

Four kinds of organization, the same three questions. Find your row, then start with the system we point at.

Law Firms

Every matter has a partner. Does the calendar?

Every matter has a responsible attorney. The systems it lives on often answer to nobody. Start with the deadline calendar: who can change a deadline rule, who checks that reminders still fire, what happens the day one doesn’t.

Do this week

  • Write one name beside the deadline calendar, and tell that person they own it.
  • Put in writing who may change access to client files, and who must be asked first.

General awareness, not legal advice, confirm specifics with your own counsel and malpractice carrier.

Health Clinics

Clinical decisions have owners. The reminder service doesn’t.

Clinics are clear about who owns the clinical call. The systems around it, the reminder service, the fax-to-email bridge, the scheduling tool with one login shared across the front desk, are where nobody tends to live. Ask the three questions of every tool that can see a patient’s name.

Do this week

  • List every tool that touches patient information and write one name beside each. A blank is a finding.
  • Retire the shared front-desk login, or name the person who owns it.

General guidance, not medical or compliance advice, verify against your own HIPAA and clinical policies.

Nonprofits

The donor list has a champion. Does it have an owner?

Lean teams run on goodwill and inherited tools: the donor database a former development director set up, the email platform a volunteer configured. Start with the donor database, who can export it, who checks the automated receipts, what happens if one goes out wrong.

Do this week

  • Name the owner of donor data and write down who may export it.
  • Open every automated send, receipts, thank-yous, renewals, and check whether anyone has read one since it was set up.
Businesses on an MSP

Your provider runs it. You still own it.

Hiring a managed service provider (MSP) moves the work, not the ownership. Your MSP can change almost everything; the question is who on your side is asked first, who reads their reports, and who decides what happens when something breaks. A good MSP will welcome the questions.

Do this week

  • Name the one person in your business who is the MSP’s counterpart, the human they ask before changing something.
  • Ask the MSP the three questions about backups and admin accounts, and write the answers down.
Who sends you this

A quick word about the people behind the newsletter

Mindpod Technologies is an Atlanta firm with a single mission: give the organizations that hold our communities together, small businesses, firms, clinics, nonprofits, the kind of AI, cloud, and security discipline that used to require an enterprise team and an enterprise budget. It’s led by a technologist with 20+ years in enterprise infrastructure, cloud and security, and this newsletter is part of how we give some of that thinking back, no strings attached.

If you’d like a second set of eyes on your three answers, bring the system you’re least sure about. Thirty minutes, no pitch.

From the Editor’s Desk

Every Agent Has to Ask

I’m building Mindpod with AI agents, and I hold them to the same three questions I just asked you to put to your own systems. Honest status: 35 agents are designed; five are in alpha, which means they may rehearse, read, or propose a change, never make one. Every consequential action, a send, a publish, a change to a setting, stops at a human approval gate. Mine.

What that has taught me is that the bottleneck isn’t the agents. It’s the quality of my approvals. If I rubber-stamp, the gate is theater, so every request has to arrive with the answers attached: what it wants to do, why, what the bad week looks like, and how we’d undo it. An agent that stops and asks beats one that guesses right most of the time. That isn’t an AI invention; it’s plain change control, pointed at a new kind of tool. I’m building the company with them, gated, logged, supervised, and writing down what happens, misses included.

If this reached you by email, hit reply and tell me your role and the one system you suspect has nobody’s name on it. I read every reply. On the web? The address below works the same.

Jaras FunderburgFounder, Mindpod Technologies

Connect

Colophon

  • Editor, Jaras Funderburg
  • Design & Communications, Jarvonnah Funderburg
  • Issue No. 04 · November 2026
  • Insights are general guidance, not legal, medical, or financial advice.

You’re reading Issue No. 04 of The Mindpod Spot. Forward it to someone who keeps the lights on. Subscribe & read past issues →