Know · GrowthOps, the one record, included
One record.
Every dollar traced.
Every module writes to the same customer record: one CRM, one pipeline, one forecast. Each paid invoice is followed back to the touch that started it, and each month you see what the agents did and what it was worth.
Included in every plan.
One record
Northline Grocers northline.example
- Oct 14Be foundVisit from an AI assistant’s answer
- Oct 14WinHue chat: asked for a quote
- Oct 16DeliverQuote Q-2026-0142 signed online
- Oct 28DeliverJob done, invoice INV-1038
- Nov 6Paid$4,800 received
Traced · First touch: Be found. Last touch: Win.
The problem
Five tools.
Five versions of the customer.
The record is split.
The ads account, the inbox, the quote sheet and the accounting app each hold a piece of the customer. None holds the whole.
Nobody can say what paid.
An invoice gets paid. Which ad, answer or email started it is a guess, so the budget follows opinions.
The work is invisible.
Hundreds of small tasks a month, done by agents and people. At renewal, nobody can show what they were worth.
How it works
01Agent
Connect
Your HubSpot, or the simple CRM in your workspace, filled from your invoices or a spreadsheet. One record per customer.
One CRM
02Agent
Write
Every module writes to it: the ad click, the AI-answer visit, the Hue chat, the reply, the quote, the job, the invoice, the review. Each step is on your ledger.
Every touch on the record
03Agent
Trace
Each payment is followed back through the invoice, the job or the quote, to the lead and the touches before it. A link the records don’t make is never guessed.
Invoice ↔ first touch
04Agent
Report
On the 1st, a draft Head of Digital report in your workspace: what moved, what it earned, what is next, what needs your yes.
A report on the 1st
01
Revenue, traced to the paid invoice.
Only payments received in the month count, at the amount paid. Each one is credited to the module that touched the customer first, or last before the sale. Last touch is the default, so no dollar counts twice.
An invoice typed by hand has no origin. A customer with no recorded touch is “source unknown”, and the chain says which link is missing.
Paid in October
$18,400 on 9 paid invoices · 7 traced to a touch
| Module | First touch | Last touch |
|---|---|---|
| Be found | $9,700 | $3,400 |
| Win | $4,300 | $10,500 |
| Keep | $2,300 | $2,400 |
| Source unknown | $2,100 | $2,100 |
INV-1043 · $2,100Typed by hand: no quote or job behind it.
02
What the agents did. What it was worth.
Per module: the tasks, the things made, the person-hours they replace, the cost per task and the multiple of its price. The method sits under every figure, and a low multiple is shown as it is.
Person-hours replaced are an estimate: tasks × the standard minutes for each kind of task, valued at your hourly cost ($45 until you set yours). Multiple = (value of that time + revenue credited) ÷ the module’s share of Head of Digital (the monthly price ÷ 4).
October
| Module | Tasks | Hours (est.) | Cost per task | Multiple |
|---|---|---|---|---|
| Win | 508 | 75 | $0.98 | 27.8x |
| Keep | 230 | 31 | $2.17 | 7.6x |
| Deliver | 60 | 9 | $8.33 | 0.8x |
| Know | 140 | 7 | — | Included |
Know is in every paid plan: its hours are counted, with no multiple.
03
The Head of Digital report, every month.
On the 1st, the month in four parts, with numbers: what moved, what it earned, what is next, and what waits for your yes. It is a draft in your workspace, printable, rebuilt from today’s records when you ask.
Nothing is emailed unless you turn it on. Revenue lines show only to people whose role includes invoices.
Head of Digital report, October 2026
- What moved
- Win: 240 inquiries captured and routed and 172 customer questions answered from your records (+38 tasks vs last month).
- What it earned
- $18,400 came in on 9 paid invoices; 78% of them traced back to a touch. $2,100 is “source unknown”.
- What is next
- Deliver is at 0.8x: we will look at what it should do more of next month, or whether it belongs on your plan.
- Your yes
- Keep: 6 waiting for your yes.
04
Each module feeds the next.
What one module learns goes to the module that can act on it, as a suggestion with where it came from. A question the AI assistant answered without you becomes a content brief; an answer you approved becomes your FAQ page.
Every hand-off waits for a person’s yes. A reply to the Outbound or Grow module stops that contact’s steps in every department.
Suggestions · waiting for your yes
From AttractCreate
Content brief: a buyer question where the AI assistant doesn’t name you, with the sources it cited.
From InboundAttract
FAQ page brief: an answer you approved in the Inbox, with FAQPage markup.
From ExpandAttract
Reviews: 14 new this quarter, 4.8 on average, as an action for your AI-answers score.
From OutboundInbound
Interested reply from Hôtel Cartier: in the Inbox, with what was sent. Its steps stopped.
Know · GrowthOps · in the app
Open it the way a client does.
The Humonix app with sample data, opened on this page’s pane. Switch modules in the sidebar, open a draft, approve or decline it: everything works here and nothing is sent or saved.
05
Headless. The same record, in your tools.
Every view on this page is also a tool. Hue uses them, and so can your AI assistant, your scripts and your other systems: the same names, the same answers, the same approvals.
Your AI assistant
MCP
Claude, ChatGPT or Cursor, with the scopes you grant: ask Hue, read the record and the value, propose drafts into your queues. Nothing approves or sends from there.
Your scripts and ERP
REST API
Keys an owner makes, each with scopes, a rate and an optional IP allowlist. An invoice created through the API is a draft.
Your other systems
Webhooks
The events you pick, signed (HMAC-SHA256 with a timestamp) and retried from 1 minute to 24 hours.
# MCP · your AI assistant
tools/call revenue_by_module {"month":"2026-10","model":"first"}
# REST · your scripts
GET /api/v1/company/invoices
POST /api/v1/tools/value_summary
# Webhooks · pushed to you
invoice.overdue · job.late · ledger.approval
Your CRM: the one in your workspace, or your HubSpot, read directly. With GrowthOps, approved fixes go back to HubSpot once you turn write access on. Any other CRM or ERP reads the record through the API and gets the webhooks.
Where it sits in the loop
Know is not a step in the loop. It is the record under all six departments: each department reads the customer from it and writes back what it did, so the next one starts where the last one stopped.
UnderAll twelve modules
Price
No price of its own.
Know, the one record, comes with every paid plan: Hue Pro, One module, Head of Digital and Enterprise. It is not a module, and the record is yours on every plan.
Available
Included
In every paid plan.
- One record per customer: the CRM, the pipeline and the revenue forecast in your workspace
- Revenue traced to the paid invoice, first and last touch
- The Value view, per module and in total
- The Head of Digital report, a draft on the 1st of every month
- MCP, the REST API and webhooks
With Head of Digital, the record is also cleaned every week (duplicates, owners, stale deals) and the forecast is kept by stage.
Your data is hosted in North America, close to you: Toronto by default, with your own US instance on request.
Hire the seat, or run it as a department? Do the math →
What would the loop return on your numbers? See it by department →
Compared with HubSpot · GoHighLevel
Book 30 minutes
Tell us where your customers live today: a CRM, a spreadsheet, your invoices. In 30 minutes we look at how one record would work for you and what your first month of the Value view would show.
A person replies in business hours with a time. When a calendar is open, you can pick one right away.
On the phone: calls answered, missed calls recovered, bookings from calls and minutes, on the Value view, with minutes at cost.
Problems this solves
In the words we hear
Questions
What does “included” mean?
Know comes with every paid plan: Hue Pro, One module, Head of Digital and Enterprise. It is not a module and has no price of its own. With Head of Digital, the record is also cleaned every week.
How is revenue traced?
Each payment received in the month is followed back through its invoice, the job or the quote, to the customer and the touches before the sale: an ad click, an AI-answer or search visit, a Hue chat, a reply, a nurture or lifecycle message. First touch and last touch; last by default, so no dollar counts twice. When a link is missing, it says “source unknown” and which link.
Are the person-hours measured?
No. They are an estimate: tasks × the standard minutes for each kind of task, with where each standard comes from. The time is valued at your hourly cost; until you set yours, ours is $45.
We already have a CRM.
HubSpot is read directly. With GrowthOps, approved fixes go back to it once you turn write access on. Any other CRM or ERP reads the record through the REST API and webhooks, or sends us an export.
Can our own AI assistant use it?
Yes, over MCP, with the scopes you grant on a consent page. It can ask Hue, read the record and the value, and propose drafts into the queues you already approve. It can’t approve, send or write to a CRM. Every call is in your access log.
Is it in French? Where is our data?
The app, the Value view and the report work in English and Québec French. Your data is hosted in North America, close to you: Toronto by default, with your own US instance on request.
One record.
The whole loop.
Thirty minutes: where your customer record lives today, and what one record would show you by the end of the first month.