|

Introducing Cosly: an AI staff team for small nonprofits

Most executive directors I know in the Canadian nonprofit sector are a one-person army. They’re the CEO, the fundraiser, the marketer and their own executive assistant. It’s a recipe for burnout, and it puts a hard ceiling on how much good the organization can do.

I’ve been building something to help with that, and today I’m ready to share it. It’s called Cosly.

What Cosly is

Cosly is an AI staff team built for small nonprofits. It’s a set of AI agents that take on the work that piles up on a small team, starting with donor communications and social content.

I built it for this sector on purpose. A general AI tool doesn’t know what moves management looks like or how lapsed donor recapture works. It has no idea why the weeks before your fiscal year-end feel like a sprint. Cosly starts from that knowledge, so you aren’t explaining how a nonprofit works every time you ask for help.

While you’re in meetings, Cosly’s agents can be working in the background:

  • Scanning your donor pipeline for people who are due for a touch.
  • Drafting personalized outreach for you to review.
  • Learning from each correction you make, so the drafts sound more like you over time.

Nothing goes out without your approval

The worry I hear most about AI goes something like this: “I can’t risk it making something up and sending it to a major donor.”

I agree, and that worry shaped the whole design. Cosly keeps a person in the loop. Every draft waits for you, and no donor email, social post or research brief goes anywhere until someone on your team has approved it.

That approval step matters more as the tools get more capable. Cosly’s agents can work through several steps on their own, which a chatbot can’t, and that’s exactly why the final say has to stay with a person.

Who it’s for

I’m building Cosly for small registered charities, the ones with one to five staff where the ED is doing the work of five people. These are the organizations that feel the admin load the most and have the least room to hire for it.

My goal is to save teams like that 5 to 10 hours a week on donor communications and social content. Those hours go back to the work that needs a person, like a call with a long-time donor or a conversation with a program participant.

I also want it to cost less than the problem it solves. Plenty of nonprofit tech ends up eating more staff time than it saves, and I don’t want to add to that pile.

Why I built it

I’ve spent years working with nonprofits on their systems, and the pattern I see over and over is a strong mission held back by manual admin. The people are good at their jobs, but there aren’t enough of them for all the copying, pasting and follow-up in front of them.

AI can take a lot of that work on now. I wanted a version a three-person charity could use without an IT department, one that knows how the sector works and keeps people in charge of anything that goes out.

I’m starting here in Calgary. Our local sector is resilient, but we’re dealing with the same staffing gaps as everyone else, and I’d rather build this alongside local EDs than guess at what they need.

I’m working with a small group of Calgary charities as design partners to shape Cosly, and if you’d like to be one of them, the details are at cosly.ca.

Similar Posts