ConnectIQ: A CRM Built Around the Client Workspace, Not the Contact Record

Every CRM we ever used in our PEO was built around the same object: the contact. A person with a name, a title, an email, a phone number, and a log of the times someone from sales reached out. Companies were a grouping of contacts. Deals were a stage and a dollar amount attached to a company. Everything else, which is to say everything that actually mattered for closing a PEO deal, lived somewhere else.

The loss runs lived in email. The mod analysis lived in a spreadsheet. The proposal lived in a shared drive. The carrier submission lived in another email thread. The CRM knew that we had called the CFO twice and that the deal was "in proposal," and it knew nothing about why the deal was stuck or what the proposal said.

ConnectIQ is the CRM inside HALO IQ, and we built it around a different object. Not the contact, but the client workspace: the account with everything attached to it that a PEO needs to underwrite, propose, and close.

PEO sales is about the account, not the person

A contact-centric CRM makes sense for businesses where the sale is a conversation. Software sales, recruiting, real estate: you are selling to a person, and the history of your interactions with that person is the deal.

PEO sales is not that. The person matters, but the deal is made or lost on the account's data: its class codes and payroll, its loss history and mod, its benefits situation, its state footprint, its compliance exposure. A rep who knows the CFO well but does not know the account has a 1.3 mod driven by eleven small claims at the second location is not going to win. A rep who knows the mod and has a proposal that explains it can win without ever having met the CFO.

So the natural unit of a PEO CRM is the account, and the natural contents of an account record are the documents and analyses that describe it. That is what a client workspace is: one place where the submission, the parsed data, the mod projection, the carrier rates, the proposal, and the people all live together.

What a workspace contains

Open a client workspace in ConnectIQ and the first thing you see is not a contact list. It is the state of the deal: what has arrived, what has been analyzed, what is outstanding, and what the next step is.

Underneath that are the documents. The loss runs, ACORD 130, census, X-Mod worksheet, and dec page that came in through InboxIQ, each classified and parsed, with the structured data they produced sitting alongside them. The underwriter who wants to see the claims that drove the mod does not have to leave the workspace to find the loss run.

Next to the documents are the analyses. The ModIQ projection and loss pick. The CarrierIQ manual rates for the account's class codes. The PricingIQ output. The proposal in its current state in the wizard, and the published version in CanvasIQ when there is one.

And then the people: the broker who sent the submission, the contacts at the prospect, the PEO's own team members assigned to the deal. Contacts are still there. They are just not the center.

The most visible consequence of building around the workspace is that deals in ConnectIQ do not have to be created by a rep. When a submission arrives through InboxIQ and is matched to a company, the deal is created automatically with the documents attached and the parsing already done.

This changes the first hour of a deal's life. In a contact-centric CRM, a rep gets a submission by email, creates a company, creates a deal, uploads the attachments, and then starts the actual work. In ConnectIQ the rep opens a deal that already exists, already has the documents, and already has the loss data aggregated by policy year. The work starts with review rather than setup.

It also changes what the pipeline means. Every submission that lands becomes a deal with a timestamp, whether or not a rep was paying attention that day. The pipeline reflects what brokers are sending, not what reps remembered to log, and a submission that sat unworked for three days is visible as such.

Territories, quotas, and forecasting that mean something

ConnectIQ carries the standard sales management features: territories, quotas, and forecasting. What makes them different in a workspace-centric CRM is what they are computed from.

A forecast in a contact-centric CRM is a sum of deal amounts weighted by stage, where both the amount and the stage are whatever the rep typed. In a workspace-centric CRM the underlying data is in the same record: the account's payroll and headcount from the census, the pricing from PricingIQ, the proposal and whether it has been published. A deal with a published proposal is in a different state than a deal without one, and a forecast built next to that evidence is harder to inflate than one built from a stage dropdown.

Territories and quotas benefit the same way. An account's state footprint and size come from the parsed documents rather than from a rep's memory, which makes territory assignment and quota tracking rest on the account as it actually is.

Working alongside HubSpot, Salesforce, and the broker's view

Plenty of PEOs and brokers have years invested in HubSpot or Salesforce, and we did not build ConnectIQ to force anyone to abandon that. HALO IQ integrates with both, so a team's existing reporting, marketing automation, and executive dashboards keep working.

The division of labor we expect is that HubSpot or Salesforce remains the system of record for the relationship, with marketing touches, sequences, and the broader book of business, while ConnectIQ is the system of record for the deal's substance: the documents, the underwriting, the proposal. A rep can live in Salesforce and still have the deal's workspace one click away, and a sales leader can forecast in either.

We are candid that this is a compromise. A workspace-centric CRM is most useful when it is the primary tool. But a CRM migration is a project nobody wants, and a sync that lets a team adopt the workspace gradually is better than a rip-and-replace nobody will approve.

Because HALO IQ is multi-tenant and brokers are tenants alongside PEOs, the client workspace is also the mechanism for the shared view of a deal we wrote about in January. The broker who sent the submission sees the workspace from the broker's side: the documents they sent, the status, what is missing, the proposal when it is published. The PEO sees everything underneath. Neither is the other's customer, and the workspace is where both of them work on the same deal without emailing each other for status.

What we gave up

Building around the workspace meant giving up some things a contact-centric CRM does well. ConnectIQ is not a marketing automation platform. It does not try to be the place where a PEO runs its nurture sequences or scores website visitors; LeadIQ handles scoring, and the HubSpot and Salesforce syncs handle the rest. It is not a general-purpose CRM for a business that sells something other than PEO, MGA, or brokerage services.

Those are deliberate limits. A CRM that tries to be everything for everyone ends up being a contact list with custom fields, which is exactly what we were trying to get away from.

Why this is the center of HALO IQ

Every other module in HALO IQ produces something that attaches to a client workspace. InboxIQ produces the documents and the deal. ModIQ produces the mod and the pick. CarrierIQ produces the rates. PricingIQ produces the price. The wizard and CanvasIQ produce the proposal. IQ Agent produces the underwriting read. ConnectIQ is where all of it lands, and it is the thing a rep, an underwriter, an operator, and a broker all open to see where a deal stands.

We built it this way because in twenty years of selling PEO, the deal was never really about the contact. It was about the account, and the account was always scattered across six systems. ConnectIQ is the attempt to put it in one.