Clear on what AI can do, and what it shouldn't

Responsible AI use means being specific and accountable for its output.

Policy last reviewed · October 2026

AI handles the volume,
your team makes the decisions

Every workflow I build follows the same rule: AI handles the first pass, I read it, adjust it, and approve it before anything goes out. No deliverable I produce sends output directly from an AI to a funder, a donor, a board, or a client before I read and give it my personal approval. That's not an optional add-on. Once the workflows are running inside your organization, the same rule applies with your staff in my place: someone on your team reads and approves anything that goes out under your name.

The reason is practical as much as it's ethical. When AI produces the draft and someone who understands the work reviews it, the output stays accurate, the organizational voice stays intact, and your team keeps the understanding of what was built and why. Cut the human out of that process and you get faster outputs that gradually drift from what makes your organization sound like itself. That's not what I'm here for.

I've watched this play out in workshops and in conversations with organizations. The organizations that do best with AI are the ones where at least one person genuinely understands the tool well enough to explain to a colleague what it produced and why. Building that understanding into every engagement from the start is how I work, and it's why I don't hand off a finished tool and disappear.

If all the work is handled by AI, there's no personality left. Speed isn't worth much if what gets delivered doesn't sound like you anymore.

Connor Jarvis · Founder

The short version: your data is yours

What does Connor actually see during an engagement?

Whatever is necessary to do the work: workflow documents, internal processes, communications templates, and any content we're building together. I don't ask for access to systems I don't need.

Does Connor use AI tools on my organization's data?

Yes. I use Claude, and the work runs in your organization's own Claude Team or Enterprise account, under Anthropic's commercial terms, which don't use your content to train models. I only use my own account for work that involves none of your data. If your organization wants to look at other AI platforms, we scope that out together before any of your data goes near them. Either way, you know exactly which tools touch your data before we start. Only what the task needs goes in. Details about your clients or staff go in only if your organization is comfortable with that, and donor information only with the donor's consent, since donors are a third party who never agreed to share it with me. You can keep any document or task out of AI tools entirely. AI-assisted work is the core of what I do, but what goes into it is your call.

Is there information you won't take at all?

Yes. Identifiable information about anyone's physical or mental health or health care, and about anyone under 18, stays out of the work. Statistics that don't identify anyone are fine. And no one but me sees your data unless you agree in writing first.

What happens to our data when the engagement ends?

Anything built inside your own tools and accounts is yours and stays there. On my side, I keep an archive of the working files so we can pick up where we left off if you come back, but within 30 days after the engagement ends I remove personal details about your clients, staff and donors. The archive stays on my encrypted laptop, never in cloud storage, and I delete it after two years. If you'd rather I delete everything, tell me and I will, with written confirmation if you want it. Nothing from your work goes into a portfolio or case study without your explicit permission.

Before any engagement begins, both parties sign a Service Agreement and a Data Processing Agreement. The Service Agreement covers scope, deliverables, and a confidentiality clause that protects everything shared during our work together. The Data Processing Agreement is specific to how AI tools are used on your data: what gets processed, which tools touch it, and how it's archived or deleted afterward. These documents exist because accountability shouldn't be a verbal promise.

Places I won't take AI

Not because AI can't produce output in these areas. It can. But there are parts of nonprofit work where the judgment, the relationship, and the community trust at stake aren't mine to run through a tool.

  • Crisis communications

    Messages to clients, community members, or the public during an active crisis require decisions that belong to your leadership. I won't draft those.

  • Case management decisions

    Anything that affects a client's access to services, resources, or support stays with a qualified person at your organization. No exceptions.

  • Therapeutic and relational work

    Documentation, follow-up notes, and communications in therapeutic or relational contexts shouldn't go through an AI workflow.

  • Final funding decisions

    I can help draft the application. Who gets funded is not an AI call.

  • High-stakes donor stewardship

    A personal note after a difficult conversation, or a follow-up after a loss, should come from a person.

If it's not the right move, I'll say that

This comes up more than you'd expect. An org arrives with a use case that involves sensitive client data, or a workflow that depends on relationships I wouldn't take near a tool, or a request that's more about looking like the org is using AI than actually getting something done with it. I'll say on the first call that it's not the right move. And I won't take the engagement.

If someone else is better suited to what you need, I'll say that too. The Honest Hour is supposed to give you a straight read.

A mission's authenticity is
the soul of the organization

I grew up handing out food and clothes to people who needed them. The organizations doing meaningful work, understaffed and running on grant cycles, are the ones I built this practice for. It's why I'm focused on nonprofits instead of tech companies or enterprise clients.

The human-in-the-loop principle isn't something I picked up from a framework. It comes from watching consultants hand organizations AI tools they don't understand, built during an engagement that ended when the invoice was paid. I want your team to understand what we built, ensure it will continue working, and have your team developing their own tools and workflows when I'm not around.

Everything above, laid out in one place

I use AI as a tool for your team, not a replacement for it. What you share is used for your work and nothing else, and you decide what goes into an AI tool. I'll tell you honestly when AI isn't the right call, and there are parts of nonprofit work I won't run through an AI workflow under any circumstances. If that's the kind of consultant you're looking for, the first call is free.

Book The Honest Hour Not ready to talk? Start with the writing.