elkaMY AI helps nonprofits, human service organizations, and foundations move from AI curiosity to working systems — responsibly. Governance first. Nothing built that your team can't sustain.
elkaMY.AI
Sound familiar?
You're not behind. You're being careful — with good reason.
01
Your board is asking for an AI plan.
Funders and board members are starting to ask what your organization is doing about AI. You need an answer that's honest and defensible — not a slide with a robot on it.
02
Your staff are already experimenting.
People on your team are using AI tools right now, with good intentions and no rules. That's not a discipline problem. It's a sign they need guidance you haven't had time to build.
03
You can't afford to get this wrong.
Every dollar is spoken for, and the trust of the people you serve took years to earn. Wasting money on tools that don't stick — or compromising client trust — isn't an option.
The front door
Every engagement starts the same way.
We don't build anything before groundwork. That's not caution for its own sake — it's how we make sure what gets built actually fits your organization and your obligations.
The AI Groundwork Sprint
Know where AI can help, where it should wait, and how to adopt it safely — in about four weeks.
You typically come away with:
A readiness assessment
A use case map
A starter AI use policy
A data risk snapshot
A six-month roadmap
A board-ready summary
Fixed fee — we'll share exact pricing in a thirty-minute call, and it won't be a mystery or a negotiation.
Sometimes the honest finding is "not yet" — and we'll tell you exactly what readiness would take.
After groundwork
What comes after groundwork.
Once the groundwork is done, we build — one workflow at a time. Each pilot takes a piece of work that's eating your staff's hours and turns it into a governed workflow built from your organization's own approved materials, with staff trained and hours saved measured.
When a system we build can't answer from your approved materials, it flags the gap for a person instead of inventing something — we think that's what trustworthy AI looks like.
And many organizations keep us on afterward for ongoing senior advice.
What we won't do
Some commitments don't bend.
elkaMY AI does not recommend AI tools that score, rank, triage, or make eligibility decisions about individual clients.
Client-identifying information should never be entered into general-purpose AI tools.
The most trustworthy AI system sometimes says "I don't know" — or flags a gap for a human instead of inventing an answer.
And when the honest answer is "you're not ready yet," that's what we'll tell you.
Get started
Let's talk about where AI fits in your work.
Thirty minutes, no slides, no pressure. We'll listen to what you're trying to figure out and tell you honestly whether we can help.
We also work with funders on building AI readiness across grantees —
Services
Groundwork first. Then one workflow at a time.
Our work follows one sequence: understand your organization's readiness, build one governed workflow at a time, and stay available for senior advice when you want it. No catalog to navigate — just a method that starts the same way for everyone.
First
Start with groundwork
The AI Groundwork Sprint
How every engagement begins.
Know where AI can help, where it should wait, and how to adopt it safely — in about four weeks. The Sprint is a fixed-scope readiness engagement that gives your leadership an honest, board-ready picture of where AI fits your organization and what safeguards need to exist before anything gets built.
You typically come away with
A readiness assessment — where your organization stands today, in plain language
A use case map — where AI can save staff time, and where it should wait
A starter AI use policy — rules your staff can actually follow
A data risk snapshot — what data you hold and what protection it needs
A six-month roadmap — sequenced next steps, sized to your capacity
A board-ready summary — the honest answer your board is asking for
The Sprint asks roughly eight hours of your team's time across the four weeks — interviews, a short survey, and two working sessions. We do the rest.
Fixed fee — we'll share exact pricing in a thirty-minute call, and it won't be a mystery or a negotiation.
Who this is for: Organizations — typically with budgets between $1.5M and $15M — getting AI questions from boards, funders, or staff. It's not for organizations that want a chatbot by Friday, or a consultant to validate a decision that's already been made. Sometimes the honest finding is "not yet" — and we'll tell you exactly what readiness would take.
Then
Build one workflow at a time
Workflow pilots
For organizations that have done readiness work and are ready to build.
After groundwork, we build — one workflow at a time. Each pilot takes a specific piece of work that's consuming your staff's hours and turns it into a governed, AI-assisted workflow. The system is built from your organization's own approved materials, your staff are trained on it, and the hours saved are measured — so you know whether it worked, not just whether it shipped.
A common example: turning an organization's own approved proposals and reports into a governed drafting workflow — one that never invents content and flags gaps for human review instead. When a system we build can't answer from your approved materials, it says so and hands the question to a person. We think that's what trustworthy AI looks like.
Pilots are scoped after readiness work — ask about a demonstration in your discovery call.
Ongoing
Keep senior help on call
Ongoing advisory support
Available to organizations we've done readiness or pilot work with.
Some organizations want senior help on call after a Sprint or pilot — someone who already knows their work, their data, and their constraints, and can weigh in as new AI questions come up. That's what ongoing advisory support is: a standing relationship, not a new project every time you have a question.
Resources
Not ready for a conversation? Start with our free prompt toolkit — ten AI prompts for mission-driven teams, with data-safety rules built in.
Where to start
Not sure where to start? That's the most common place to start.
Every engagement begins with the same conversation. We'll listen, ask questions, and give you an honest read.
Approach
Groundwork before building. Adoption as the measure.
We work in five phases. They're sequential, but they're also a loop — most engagements revisit earlier phases as new questions surface. The point isn't to follow a process for its own sake. The point is to make sure no critical question gets skipped — and that nothing gets built before the groundwork says it should be.
01Assess
Where does AI actually fit in your work — and where doesn't it?
We start by listening — to leadership, staff, and where appropriate, the people you serve.
What we do together
Interview leadership and staff about the work that eats their hours
Map your current workflows, data, and decision points
Inventory tools you're already paying for
Identify high-value use cases and rule out low-value ones
What you get: A clear-eyed assessment of where you are, what you're ready for, and what's worth doing first.
02Align
What do we agree to do, in what order, with what guardrails?
Translate findings into decisions your whole organization can stand behind.
What we do together
Translate findings into a phased roadmap
Align board, leadership, and staff on priorities
Surface tradeoffs and decision points before they become problems
Define what "responsible" means for your specific context
What you get: A shared plan your board can approve and your staff can execute.
03Build
What workflow do we actually improve — and with what tools?
One workflow at a time, with tools your organization owns and can afford.
What we do together
Build from your organization's own approved materials
Use business-grade tools at a modest monthly cost — no custom software
Integrate with the systems you already have
Keep the design simple, maintainable, and reversible
What you get: A working workflow your team owns — no vendor commissions, no software sales, no system you can't afford to keep running.
04Govern
How do we make sure this stays responsible as it scales?
Build the oversight before it's needed, not after something goes wrong.
What we do together
Establish oversight roles and review cadence
Document policies, acceptable use, and escalation paths
Build privacy, bias, and accuracy checks into the workflow
Brief the board on what we built and how it's governed
What you get: Governance your auditors, funders, and community can trust.
05Adopt
Will your team actually use what we built?
Adoption — not documents — is the measure of success.
What we do together
Train staff in plain language, tied to their actual work
Support change management — the human side, not just the tool
Set up feedback loops to catch problems early
Hand off ownership so the work continues without us
What you get: A team that owns the change, not a deliverable that collects dust.
The gap principle
Why our systems say "I don't know."
The most trustworthy AI system sometimes says "I don't know" — or flags a gap for a human instead of inventing an answer.
Most AI failures in mission-driven work don't come from systems that refuse to answer — they come from systems that answer confidently when they shouldn't. Every workflow we build treats a flagged gap as a success, not a failure, because it means a person gets to make the call the machine wasn't qualified to make.
elkaMY AI is a young practice built on old experience — we're deliberate about taking on work we can deliver exceptionally, which means we'll tell you quickly if we're not the right fit.
Talk it through
Curious how this would apply to your work?
The first conversation is the most important one. Let's start there.
Responsible AI
Responsibility isn't a phase. It's the frame.
Most consultants treat responsible AI as a section in the appendix. We treat it as the starting question. Before we talk about what to build, we talk about who could be harmed, what oversight is needed, and what we won't do.
Here are the commitments we work from. They show up in every engagement — not as a checklist, but as a frame for the decisions we make together.
Our commitments
Five commitments. And what we won't do.
AI should save staff time without compromising client trust.
elkaMY AI does not recommend AI tools that score, rank, triage, or make eligibility decisions about individual clients.
Client-identifying information should never be entered into general-purpose AI tools.
Human review is required before AI-assisted work leaves the organization or enters an official record.
The most trustworthy AI system sometimes says "I don't know" — or flags a gap for a human instead of inventing an answer.
And what we won't do
No software sales or vendor commissions — we recommend tools because they fit, not because we profit.
No recommendations an organization can't sustain after we leave.
Where the honest finding is "this organization isn't ready to build anything yet," that is what the report will say.
How we think about your data
Not all data carries the same risk.
In every engagement, we sort an organization's information into four tiers — because the rules that make sense for a public annual report would be reckless for a client file.
Public
Information already published or intended for the public — annual reports, website copy, published research. The lowest-risk tier, with the most flexibility.
Internal
Day-to-day operational material — drafts, meeting notes, internal templates. Useful with AI tools, with basic guardrails in place.
Sensitive
Information that could harm the organization or individuals if exposed — financials, personnel matters, strategy documents. Handled with stricter rules and tighter tool choices.
Client-identifying
Information that identifies the people you serve. The rule for this tier is absolute: client-identifying information should never be entered into general-purpose AI tools. No exceptions, no workarounds.
How the tiers get applied — which tools, which workflows, which safeguards — is part of the groundwork we do with each organization.
Your context
Want to talk through responsible AI for your specific work?
Every organization's risk surface is different. The first conversation usually surfaces things you hadn't named yet.
About
Built around clarity, mission, and the work people actually do.
[Founder photo placeholder]
The Founder
[Founder Name]
[PLACEHOLDER — Approved founder bio, 200–300 words. Angle: strategic-and-credentialed / story-and-mission / hybrid. Include: current and prior roles, formal training, sector depth, civic and board experience, and the lived perspective that shapes how elkaMY AI sees problems. Do not name specific organizations the founder leads or has led. Do not invent.]
[Continue bio if needed.]
Why we exist
The third option, made real.
Most organizations we talk to are stuck between two bad options: ignore AI and fall behind on capacity and decisions, or chase AI and risk wasting money, eroding trust, or harming the people they serve.
elkaMY AI exists to make the third option real: practical, responsible AI adoption that fits how your organization actually works. We translate. We build. We govern. We make sure your team owns what we leave behind.
What we believe
Five positions we don't soften.
Adoption is the deliverable.
A tool nobody uses is a failed engagement, no matter how clever it is.
Mission comes before margin.
We work with organizations whose values we share. We turn down work that doesn't fit.
Plain language is a moral position.
Jargon protects the people using it from being held accountable. We don't hide behind it.
Responsibility doesn't slow you down.
Done well, governance is the thing that lets you move faster — because nobody has to undo work that should never have shipped.
Small and focused beats big and generic.
We're built to do a few things well for a few organizations at a time. That's the firm we want to be.
Where we work
elkaMY AI is based in [PLACEHOLDER — location line], and we work remotely with mission-driven organizations across the U.S. We travel for kickoffs, board sessions, and key workshops when it serves the work.
Start a conversation
Let's see if we're the right partner for your work.
The first call is for fit, not selling. If we're not right, we'll tell you — and where possible, point you to someone who is.
Insights
Notes from the work.
Short, useful writing on responsible AI adoption — written for leaders making decisions, not for engineers building systems.
Free Resource
Ten AI Prompts for Mission-Driven Teams — Free
Ten ready-to-use prompts for the work nonprofit teams do every week, each with data-safety rules built in. Every prompt tells you what information is safe to include — and what should never go into a general-purpose AI tool. [PLACEHOLDER — toolkit link]
Get the toolkit
Cornerstone POV
[PLACEHOLDER — cornerstone title 1]
The first of two launch pieces establishing the elkaMY AI point of view on practical, governed AI adoption. [Founder to write]
Read post
Cornerstone POV
[PLACEHOLDER — cornerstone title 2]
The second launch piece — a practical guide for leaders evaluating AI decisions. [Founder to write or co-write]
Read post
Your context
Want to talk through any of this for your organization?
Reading is one thing. Applying it to a specific decision is harder. That's what the discovery call is for.
Book a Call
Let's talk about where AI fits in your work.
Thirty minutes, no pitch deck. If elkaMY AI isn't the right fit, we'll tell you that too.
We'll listen to what you're trying to figure out, ask a few questions, and give you an honest read — including, where possible, pointing you to someone else if we're not the right partner.
Pick a time
Choose a 30-minute discovery slot that works for you. We'll send a confirmation with a video link.
[PLACEHOLDER — calendar tool embed]
Calendar tool to be selected. 30-min slots, 3–5 per week to start.
Prefer email?
Tell us a bit about what you're working on. We reply within two business days.
We reply within two business days. No follow-up sequences, no automated nurture campaigns — just a reply from a person.
What to expect
A simple 30 minutes.
You talk for the first 15 minutes.What you're working on, what you've tried, what you're worried about.
We ask questions for the next 10.To understand the work, the team, and the constraints.
We tell you what we'd do next.Whether that's an engagement with us, a different kind of help, or "you're closer to ready than you think — here's how to start."