Product
Five parts, working off the same connected books — available on every client you carry, at once.
A short product walkthrough: the All Companies view of a firm’s clients, then one client’s workspace where a user opens chat, asks “Why did net income drop last month?” and CentSight answers with the figures and the ledger entry behind them. Switching to a second client starts a fresh chat with nothing carried over.
Illustrative walkthrough · example clients and sample figures
Chat
Questions in the register you'd use with a colleague — why margin moved, what's driving a variance, whether a client can afford a hire. Figures are computed against the ledger and come back with the transactions behind them attached.
Why did net income drop last month?
Net income fell $4,120 against last month, but the business didn’t get worse. An annual software renewal was expensed in full in June; only one month of it belongs there.
Source: 1 bill entry · Jun 4 · QuickBooks Online
Signals
Continuous monitoring on each client's connected books. Cost jumps, aging receivables, contracts running out, runway shifts and miscategorized entries surface on their own, so you walk into the call already knowing.
Contracts running out
Pulse HQ
Invoices to chase
HW E-Commerce
Getting paid
Marketing Agency
This year against last year
Restaurant Group
Rent collected on time
Coastal Property Group
Widgets
Live views of cash position, revenue mix, operating cash flow against net income, spend by vendor and category. Arranged per client, because a contractor and a SaaS business don't watch the same numbers.
Arranged per client company
Cash position
HW E-Commerce
Revenue mix
Marketing Agency
Operating cash flow against net income
Pulse HQ
Spend by vendor and category
Restaurant Group
Financial model
Projections and scenarios built off the client's own actuals rather than a template. Change an assumption and see it flow through — then take it into the conversation where your judgment does the rest.
Pulse HQ
The client's own actuals
Read from the connected ledger rather than a template.
Assumptions you set
Headcount, pricing, collection timing.
Scenarios side by side
Each one showing what the change moved.
Knowledge
How each client bills, what's seasonal, which vendors matter, what counts as non-recurring. The things a good analyst learns over months, held per client so answers arrive with the nuance already applied.
Restaurant Group
Seasonality
Q4 is the seasonal peak. December is not a trend.
Billing
Catering invoices on net terms; the dine-in side settles same day.
Non-recurring
Equipment purchases are one-off — keep them out of the run rate.
Vendors
Two suppliers cover most of food cost, so a price change from either moves margin.
Kept apart
Separate connections, separate data, separate history. Your team moves between clients without holding the boundary in their head.
HW E-Commerce
Connected to QuickBooks, Chase, Stripe
Marketing Agency
Connected to QuickBooks, BofA, HubSpot
Pulse HQ
Connected to QuickBooks, Mercury, Stripe
Restaurant Group
Connected to QuickBooks, Wells Fargo, Slack
Separate data, separate history, separate connections. Nothing crosses between columns.
Connects with
Read-only throughout. CentSight holds the connections, so credentials never pass to a model provider.
Where firms point it
Assemble the numbers and the narrative for a board pack, with every figure traceable when someone asks where it came from.
Get a defensible starting model off a client's actuals in minutes, then spend your time on the assumptions that matter.
Catch miscategorized entries, duplicates and unusual vendor activity before the package goes out the door.
Find what moved and why without opening QuickBooks, the CRM and three bank tabs to reconstruct it by hand.
See where a client's cash is heading and what changes it, across every company on the roster at once.
Answer the Tuesday question on Tuesday, with something you're willing to put your name on.
Common questions
From the client's connected ledger. The arithmetic is done in code against the entries, not written by a language model, and each figure comes back with the transactions behind it so you can check the trail before you sign your name to it.
No. Every connection is read-only. Nothing is posted, reclassified or migrated — the client keeps working in the system they already use, and CentSight reads from it.
No. They read from the same connections, so using one costs you nothing on the others. Most of the value shows up once chat and signals are both running on the same client, but neither depends on the rest.
That's your call. It is built as a first draft off the client's actuals — a starting point for your team to interrogate and refine, not a finished deliverable. What leaves your firm is still what your firm decided to send.
Connect the client's QuickBooks, and their bank feeds through Plaid where it helps. Both are read-only, and CentSight holds the connections itself, so credentials never pass to a model provider.
Yes — signals run per client, against that client's own books and the knowledge held in that workspace, so what surfaces for a contractor isn't what surfaces for a SaaS business.