About
CoreCNX exists because three good products in the same suite didn't share a single contact record. So we built one. Every door knock, every text reply, every chatbot lead, every email open: one timeline, one contact, in chronological order.
The origin
For two years we shipped the CNX Suite as three separate products: Beacon for the doors, CampaignCNX+ for the texts, Alma for the chatbot replies. Each product was good at its own job. None of them shared a contact record with the others.
A campaign manager would walk into the Monday meeting holding three tabs. Beacon showed who'd been knocked. CampaignCNX+ showed who'd replied to the SMS blast. Alma showed who'd booked an appointment off the website chatbot. The same person (Maria Santos, lives on Fourth Street, voted in the primary) would appear in all three, with a different contact ID in each, and no one tool would tell you the full story of what she'd actually done.
That's the specific gap CoreCNX was built to close. Not "another CRM." A contact spine. A place where the door knock, the SMS reply, and the chatbot booking all land on one timeline, in the order they happened, tagged with which product wrote them.
Beacon, CampaignCNX+, and Alma are channel products. They each do one job well: walk doors, send texts, triage replies. They write activity. They don't try to be the source of truth for who a contact is.
CoreCNX is the source of truth. It's the contact record, the pipeline, the unified timeline, and the email-marketing workspace built around them. The other three products POST events to it via signed webhook the moment something happens at the door, on a phone, or in a chatbot widget. CoreCNX resolves the contact (phone first, email second, create-if-no-match third), checks the event hasn't already been recorded, and writes it to the timeline.
The unified timeline is not a tab. It's the central feature. Everything else in the product (pipeline, email, reports, tasks) is built on top of it.
Most CRMs treat the contact record as a folder of notes. You open Maria's record and you see her name, her email, a list of tags, a custom field for her ZIP code, and somewhere near the bottom a tab labeled "Activity" that almost nobody clicks.
We inverted that. The activity feed is the contact record. When you open Maria's page in CoreCNX, the first thing you see is a chronological scroll of every real-world event your suite produced: the door knock from April, the SMS reply from May, the chatbot booking from June, the donation last Tuesday. Each event is tagged with a colored dot showing which product wrote it. You can filter by source, by time range, by disposition, by tag.
The pinned facts at the top (lead score, last touch, lifetime value, custom fields) are still there. But the spine of the page is the feed. That's the decision that drives everything else: how the schema is shaped, how the ingestion pipeline is shaped, how the reports are shaped, how the dashboard is shaped.
CoreCNX Beacon CampaignCNX+ Alma
We are HCM, a small studio of operators and engineers building software for campaigns and small businesses that have run out of patience with Salesforce. The CNX Suite is four products and not a fifth. CoreCNX is the spine. Beacon walks doors. CampaignCNX+ sends texts. Alma is the website chatbot on the website. Same login, same billing, contact records flow between all four.
The intentionally small product family means we can write the tools to talk to each other in our sleep, instead of negotiating with a partner team at a different company that might decide tomorrow to change their API. That's the reason the suite exists in this shape. It's also the reason CoreCNX exists, because once you're committed to building four products, you have to commit to building the place they all meet.
About a third of CoreCNX accounts will probably never wire in another suite product. They run a law firm, a regional services business, a small nonprofit. They use it as a regular CRM with a clean pipeline, decent email marketing, a contact list that imports from CSV, and reports that don't require a certification to read. That's by design.
Pricing scales with contact volume (same shape as Beacon and CampaignCNX+) and starts at $49 a month. There's no per-user fee. No "integrations tier." No sales call required to see the product. A 14-day free trial with no card. We'd rather have ten thousand small accounts running the product happily than a hundred enterprise contracts that nobody enjoys signing.
We won't build a marketing-automation suite with sixty triggers, twelve form builders, and a workflow canvas that requires a consultant to deploy. We won't build a "platform" with an app store and a partner certification program. We won't build the things that turn a CRM into a procurement event. There are excellent companies who already build those products and we are not them.
What we will keep building: a contact spine that handles every event your program produces, a pipeline that fits how a real campaign or sales team thinks, an email tool that joins the same timeline as everything else, and a set of integrations narrow enough that we can keep them all working without adding a customer-success org chart to the company.
Brian Hunter, founder · HCM · Edwardsville, IL
Try it
Sign up, import a contact list, fire a test webhook from your terminal. Watch the event land on the contact's timeline in seconds. The product we built for ourselves is the product you get.