Why we built Rell
Every team bends their CRM until it breaks. We think the tool should bend instead. Here's the thesis behind Rell.
Most CRMs ship someone else's idea of how your business works. You get a Deal, a Contact, a Company — and then you spend months wedging your actual process into those three boxes. Rell starts from the opposite premise: the shape of your business is the product.
Configuration, not customization
Customization is escape hatches bolted onto a fixed core. Configuration is the core. In Rell, objects, fields, views, pipelines, and automations are first-class primitives you compose — the same building blocks our own team uses to build the demos on this site.
- Objects model the things you track — Deals, Patients, Properties, Shipments, anything.
- Fields give those objects shape, with eighteen types from currency to composite address.
- Views are saved lenses — a board for sales, a calendar for ops, a list for finance — over the same records.
- Pipelines move records through stages, with rotting thresholds and entry automations baked in.
- Automations turn 'when this, then that' into a few clicks instead of a Zapier bill.
Cohesive at any scale
The hard part of a no-code platform isn't letting people build — it's keeping a thousand custom workspaces from looking and behaving like a thousand different products. Rell's design system does the heavy lifting: every workspace inherits the same tokens, the same motion, the same density. Flexible underneath, coherent on top.
The tool should bend to the team — not the other way around.
That's the whole idea. The rest of this blog is us showing our work.
Written by the team building Rell — the configurable CRM platform.