Why we built Mercleo

Every small organization we have worked with runs on some version of the same stack: a CRM chosen years ago, an email tool bolted to it, a ticketing vendor, a course platform, a spreadsheet that quietly outranks all of them — and one administrator holding the whole thing together by hand.

That person is the real integration layer. They re-key the same human being into four systems. They reconcile the donation report against the email list against the membership roll, and they are the only one who knows which of the three Margarets is the same Margaret. When they take a week off, data entry waits for them. The tools were each, individually, a reasonable choice. The sum of them is a job nobody was hired to do.

The wedge

The industry’s standard answer is integration: keep the five tools, add plumbing. We spent enough time on the receiving end of that answer to distrust it. Syncs drift. Fields map imperfectly. Every connected pair of systems is another thing that silently breaks on a Tuesday, and the administrator is still the one who notices.

So we made the opposite bet. Not five tools, integrated — one person record, shared. The member who buys a ticket, takes the course, and makes a gift is one row, not three reconciled ones. Products sit on top of that record and stay deliberately focused — relationships and giving, people and hiring, events and learning — but none of them owns a private copy of a human being. The integration problem is not solved. It is removed.

That decision is what makes everything else about Mercleo possible: one account, one bill, one place your audience signs in, and an administrator who does their actual job instead of being middleware.

Who it’s for

Nonprofits, associations, and small businesses — organizations big enough to run real programs and far too small to have an operations team mopping up after their software. The ones where the office administrator, the volunteer coordinator, and the database manager are one person, part-time.

They are underserved for a structural reason: each of them individually is a small customer, so the industry either sells them enterprise software scaled down until it is merely confusing, or consumer tools scaled up until they buckle. We think they deserve software built for their actual shape.

The commitment

Three things we hold ourselves to, stated publicly so they cost us something to walk back:

• Plain pricing. You pay for the products you use and the seats doing the work. No tiers engineered to be outgrown, no call-us column.
• Your audience is never billed. Contacts, members, donors, learners — the community you serve will never be a line item. We wrote about why.
• A Canadian company. Built here, priced in dollars that don’t fluctuate with someone else’s economy, and taking Canadian compliance — CRA receipting included — as a first-class requirement rather than a localization afterthought.

The longer story — the about page has the short version — is that we kept watching capable, over-stretched people do robotic work between systems that refused to talk. The platform is our answer. We built Mercleo so the administrator can stop being the software.