lexisOS
Setting things up…
Compose · CRM
One CRM record, not four copies of it.
Leads, Contacts, Companies, Deals, and Vendors are full record types with their own custom fields, tags, and saved views.
The data model
Five record types, one thread between them
A scraped LinkedIn profile is a Person — deduplicated per organization, not re-created on every re-scrape. Convert it to a Lead, manually or automatically on a score threshold, a stage change, or a tag being added. Qualify the Lead and convert it again, into a Contact or a Deal — the conversion is one action and locks the source record so it can’t drift. Vendors runs as a full parallel object with its own notes, tasks, tags, deals, and timeline, switched on separately as its own feature.
CRM
Person → Lead
Lead → Contact
Lead → Deal
Vendor (separate object)
How a record moves
From scraped profile to closed deal
Scraped from LinkedIn
A profile becomes a Person record, deduplicated per organization.
Converted to a Lead
By hand, or automatically on a score threshold, stage change, or tag added.
Converted to a Contact or Deal
One action promotes a qualified Lead and locks its source record.
Scored the whole way through
An admin-defined points table applies deltas as events fire — not a machine-learning model.
The shared record shell
Every channel, one record
Lead, Contact, Deal, and Vendor detail pages share one record shell with four tabs, so activity from any channel lands in the same place instead of a separate screen per feature.
Overview
Recent activity, inline-editable fields, and this record’s custom fields.
Communications
Email, SMS, calls, and meetings — in one panel, not four inboxes.
Files
Documents from WorkDrive, uploaded or embedded directly on the record.
Automations
The workflow runs and signals that touched this specific record.
What you get
Built to shape around your process
The parts that make the CRM yours, not a fixed template.
Custom fields
Text, number, date, boolean, select, multi-select, URL, email, phone, and currency fields, defined per entity type.
Configurable pipelines
Custom stages per organization, with win/loss flags, probability, and color — full CRUD and drag-reorder.
Saved views
Filter and sort with 20+ operators, reusable across list screens and Lists.
Dynamic Lists
A saved filter that recomputes its own membership on a schedule you set, or a static list you manage by hand.
Rule-based scoring
An admin-defined points table per event type — a stage change, a tag added, a reply — not a black-box model.
Spreadsheet import
CSV or Excel import with explicit column-to-field mapping you control, up to 50,000 rows per import.
Tags, notes, and tasks
Shared primitives across Leads, Contacts, Deals, and Vendors.
Bulk operations
Bulk edit fields, bulk status change, and bulk add-to-list across Leads, Contacts, and Deals.
Sync, don’t replace
Two CRMs you can run alongside LexisOS
Zoho CRM and HubSpot both sync two-way, but not identically. Zoho pushes people, companies, and leads, pulls whole modules back in, and gets a live webhook for near-real-time inbound updates. HubSpot pushes leads only today and pulls hourly — there’s no HubSpot webhook yet. Both are genuine two-way sync with field mapping and a conflict log, not a one-way export.
LexisOS CRM
Zoho CRM
HubSpot
Keep exploring the platform
See your pipeline as one record, not four.
Start free and bring in Leads, Contacts, and Deals first. Custom fields, pipelines, and scoring are there from day one.