CRM & custom entities

Contacts first. Then whatever you run.

A CRM where the contact sits next to the documents, invoices and bookings it generates — extended by custom fields, related records and tags until it matches the way your business actually works.

01Contacts

The contact is the spine.

Every document, invoice, booking and form submission hangs off a contact. Extend it until it fits.

01 / Custom fields

Fields with real types

Add fields to contacts or any entity type — required or optional, reordered by drag, options with separate stored values and labels. One field per entity is the primary: it names the record everywhere.

02 / Tags & groups

Labels with rules

18 colors, 300+ icons, and groups that carry policy: restrict a group to certain models, or make it exclusive so an entity holds exactly one of its tags. Tag a document in a workflow and the whole chain carries it — and adding or removing a tag is an automation trigger.

03 / Advanced filters

Segments without a query language

Twelve operators over built-in and custom fields, plus tag set logic — any, all, none — stacked into one AND-combined filter. The same engine drives the list views and the REST API, and typed storage keeps it fast.

04 / Day-to-day speed

Built for volume

Edit contacts inline from the list, create them from a dialog wherever you are, and move whole books of business with CSV import and export. Your data arrives in bulk and leaves the same way.

02One record of everything

The relationship, accumulated.

05 / Connected by default

Nothing floats loose

Documents are addressed to contacts, bookings attach the contact they create, form submissions stamp the contact they opened. The record accumulates the whole relationship on its own — no “log this in the CRM” step, ever.

06 / Portal, per contact

Invite from the contact card

Invite, resend or revoke portal access right on the contact — with invitation status, activation date, login count and last-seen tracked on the record. Tokens are hashed; revoking is one click.

07 / CRM triggers

Data changes are events

Four contact triggers and four record triggers feed the automation canvas — created, updated, tagged, untagged — filterable to a specific tag. Moving a label can move a workflow.

03Custom entities

Invent the nouns.

Projects, campaigns, properties, assets — define an entity type once and its records get the full CRM treatment.

08 / Entity types

A schema in a minute

Name it, pick an icon and color, add fields. Records list, search, filter and tag exactly like contacts, and the primary field gives every record its name — in lists, relationships and search alike.

09 / Records

No empty columns

A record is nothing but your fields — there's no generic schema underneath to fight. The primary field names it everywhere, search reaches every value, filters run on the typed columns, and each entity type gets its own view/create/edit/delete permissions for roles.

10 / Relationships

Both sides stay true

Relationship fields link contacts and records in four cardinalities. Make one bidirectional and the inverse field appears on the target automatically — link a contact to a company and the company lists the contact, with every add and removal synced both ways.

11 / Wired into everything

First-class, not a sidecar

Forms create records and link them to contacts, automations read and write record fields and fire on record changes, and templates pull record data into documents. A custom entity behaves like it shipped with the product.

One email, one contact

Email is unique per subaccount — imports and integrations dedupe instead of multiplying.

Typed at the bottom

Numbers, dates and booleans live in indexed, typed columns — not stringly-typed JSON.

Scoped by construction

Every query carries the tenant — cross-client reads are impossible, not just discouraged.

Portal tokens hashed

Portal invitations use 64-character tokens stored as SHA-256 hashes, revocable any time.

“We made Campaigns an entity type on a Tuesday. By Thursday the intake form was filling it.”
ICIvy ChenHead of operations, Parallel North

Your data, your shape.

Contacts, custom entities, relationships and tags on every plan — next to the documents and payments they produce.

Flat price. No usage charges. Ever.