About Relmz·Who we are

We're making business software feel like one thing.

Most operators run on a stack of seven SaaS tools that don't know about each other. Relmz is the answer to "what if they did?"

01/Our story

Started in a back office, paying for six SaaS tools.

Relmz started inside a small business — a multi-location operation paying $2,400/mo across six SaaS tools and still spending half a day every week reconciling them. The bill wasn't the problem. The reconciliation was.

We built Relmz for ourselves first. The platform you see today is the cleaned-up version: one Postgres database per tenant, one customer record across every module, and Sebastien — an assistant for the parts of work that genuinely benefit from one (mostly: writing copy, drafting replies, summarizing what's happened).

We're a small team. We answer support tickets ourselves. We sign real contracts when Enterprise customers need them. Most of all, we ship — and we update the changelog when we do.

fig. 03where it started

02/What we believe

Four principles behind every product decision.

01
One platform, not seven
Most businesses don't need the deepest tool in any single category. They need tools that share a database. We build the shared database.
02
Honest scope
We say what we're not. We're not the cheapest. We're not the deepest specialist anywhere. We're not for everyone. Telling you that builds trust faster than overclaiming.
03
Ship in public
Our changelog is real and updated by the people who write the code. Our roadmap drifts; we update it when it does.
04
Operators first
Relmz is built by people who've run small businesses and have opinions about what 'small business software' should feel like. That bias shows up everywhere.

03/Who builds it

Built by operators, answered by the same people.

Relmz is built by people who've run small businesses — and the same people answer the support tickets and write the changelog. That bias shows up everywhere, on purpose.

Read the changelog

The teamsix facts

01A small team.the people who write the code
02We answer support tickets ourselves.one business day, aimed for
03We've run small businesses.that bias shows everywhere
04We sign real contracts.when Enterprise needs them
05We ship, then update the changelog.in public
06We read every “found a bug” email.all of them

Real humans, real responses

Talk to us.

We aim for one business day on support tickets. We sign real contracts when Enterprise customers need them. We read every “found a bug” email.

Started in a back office, paying for six SaaS tools.

We're a small team. We answer support tickets ourselves. We sign real contracts when Enterprise customers need them. Most of all, we ship — and we update the changelog when we do.

We're making business software feel like one thing.

Started in a back office, paying for six SaaS tools.

Four principles behind every product decision.

One platform, not seven

Honest scope

Ship in public

Operators first

Built by operators, answered by the same people.

Talk to us.

We're making business software feel like one thing.

Started in a back office, paying for six SaaS tools.

Four principles behind every product decision.

One platform, not seven

Honest scope

Ship in public

Operators first

Built by operators, answered by the same people.

Talk to us.