The Hub Heartbeat
“How is today going?”
The day's booking curve with the real arrival curve drawn over it. The gap between the two is the no-show problem, visible without a number.
CRM · Insight engine
Your CRM should tell you what changed. Not make you go looking.
Every morning it names the few things that moved in your building and what to do about each one — an upgrade to propose, a member to call, an event worth putting on. And every claim it makes comes with its evidence: the bookings, the payments, the visits behind the number, there to be opened and argued with.
The morning brief
Three things that moved, and what to do about each.
Not a dashboard waiting to be read. A short, dated list of what changed since yesterday, each item written in plain English with the action attached to it.
Tuesday · morning brief
- Four members are consistently using more than their plan.
Their meeting-room hours have run over the included allowance in each of the last three months, and they keep paying the excess.
- A member hasn't been in for nineteen days, and their bookings are down sharply.
Presence, desk bookings and room bookings all fell together — the pattern that usually comes before a cancellation.
- Eleven members share an interest and overlap on Thursdays.
They are in the building on the same afternoons and already sit near one another. There is an event in that.
Illustration of the brief being built. Not a live screen.
Receipts
A score is not a verdict. It is a sum you can go and check.
Every number on every screen opens into the named facts that produced it — the actual bookings, payments, visits and mail items, each with its date. Nothing is handed down from above.
A prediction is only worth what its evidence trail is worth.
An operator who cannot interrogate a score will nod at it and never act on it. So the working is the product: open any claim, read the facts underneath it, and decide for yourself whether you agree. If we cannot show you why, we do not show you the number.
Every line here is a record the system already holds. Open one and you land on the booking, the payment or the item itself.
Receipts
Churn risk is elevated for this member.
Built from 6 facts across the last 60 days.
- 12 MarLast recorded presence in the building19 days ago
- 09 MarMeeting-room booking cancelled2 hours
- 04 MarDesk bookings this month against monthly average2 of 11
- 01 MarInvoice paid, on timeno arrears
- 26 FebMail item collectedcollected
- 18 FebMail item not collectedstill held
What it watches
The behaviour of a building — not the history of a booking calendar.
Presence, bookings, mail, phone calls, events, doors and payments all sit in one system. Nothing is synced in from somewhere else, so nothing is lost in the gap between two tools, and nothing arrives a day late in a shape that no longer matches.
Presence
Who was in, and when.
Bookings
Desks and rooms, booked, changed, cancelled.
Mail
Collected, or not.
Phone calls
Calls answered on the hub's number.
Events
Sign-ups, attendance, who came with whom.
Doors
Access granted, at the hour it happened.
Payments
Invoiced, collected, outstanding.
One record per member, written by the building itself as the day happens.
Six ways to see it
Six views. One question each.
Each one exists to answer a single question an operator actually asks out loud. Nothing here is a report you have to assemble.
The Presence Calendar
“Who is fading?”
A year of squares per member. A member drifting away visibly fades months before they leave.
The Social Graph
“Who holds this place together?”
Members as connected points, sized by presence, linked by shared days. The catalysts sit in the middle; the lonely ones float at the edge.
The Money River
“Where does the money actually go?”
A flow from each product line into collected, outstanding and at-risk.
The Churn Radar
“Who is drifting toward the edge?”
Every member plotted by engagement against value, with a trail showing the last ninety days.
The Demand We Turned Away
“What business did we not do?”
The hours people wanted and couldn't have, by asset kind.
What it never does
Three things we will not build.
No report builder.
We ship answers, not homework. Every number means the same thing in every hub, so hubs stay comparable.
No configurable scoring weights.
One number, computed the same way every time, that you can argue with out loud.
No black box.
If we can't show the working, we don't show the score.
Free and paid
Capture is free. Interpretation is the paid part.
Free, always: capture.
Every lead the building produces is captured and kept — from tours, day passes, check-ins, event sign-ups and enquiries. It is your list, and it keeps growing whether or not you ever pay us for a single insight.
Never paywalled, permanently: your own data stays exportable.
Whatever you decide about the paid side, you can take your records out. That is not a plan feature; it is a standing commitment.
Paid: interpretation.
The scoring, the morning brief, the six visuals and the actions that come attached to them. This is Flentix CRM Growth: the only module we charge separately for, priced per hub, per month, with an annual rate that carries the same one-month-free treatment as every other annual price on the site. Every other module — booking, payments, invoicing, members, community, events, kiosk, white label and the whole virtual-office stack — is included in the platform licence.
CRM Growth, per hub, from
€49/mo
Annual rate: €539/yr
Status
This is in development.
This page describes what the CRM is being built to do, not what you can log in and use this morning. We would rather show you the destination and be straight about where the road currently ends.
Real today
- Lead capture across tours, day passes, check-ins, event sign-ups and enquiries.
- The scoring rules that turn recorded activity into a signal.
- The proposal engine that produces an upgrade offer from a member's usage.
Being built
- The morning brief.
- The receipts drawer.
- The six visuals.
We are not putting a date on it here. When a piece is live, it will be described as live and nowhere else.
Want the CRM as it lands? Start with the platform.
Get set up on the platform and the records the insight engine needs are already being written by your building. CRM Growth is the module that turns those records into interpretation.