Connect messy company knowledge into one source-backed brain for decisions, customers, projects, and execution. Find the answer and the source — then assign the next action.
Simulated ingestion only — no live connectors in this MVP. For corpus-style experiments, use advanced ingest.
Command query
What did we decide about enterprise pricing?
Enterprise pricing is anchored on list with controlled exceptions. The latest operating decision is a VP Sales + CEO dual approval for any discount that breaks the list-price guardrail, with finance enforcing net-30 exceptions only above $120k ARR.
Source trail
Newest corroboration firstSlack
#exec-decisions · thread 1
List price holds in enterprise unless VP Sales + CEO both approve in writing — posted in #exec-decisions.
Docs
Notion · PRD / policy · v2
Notion policy page v3.2: pilot discount ladder and case study quid pro quo.
CRM
Salesforce · opportunity notes · 3
CRM opportunity ACME: AE notes request 18% — flagged as above current threshold.
Decision history
Pilot discount approved
CEO15% pilot discount for logos with public case study commitment.
Annual prepay motion
CFOFinance asked for net-30 exception only when ARR > $120k.
Enterprise list price guardrail
VP SalesList price holds unless VP Sales + CEO both approve in writing.
Contradictions found
Discount authority
Signal A
Sales playbook: AE can approve 10% without exec.
Signal B
Exec thread: discounts >8% require CEO in enterprise segment.
Next step: Reconcile in CRM policy doc and post the final rule in #pricing.
Owners
Recommended next actions
Stage calibration: Series B — multiple owners, more CRM + support corroboration. Department lens: leadership — prioritizing operating cadence, capital allocation, and org risk.
Knowledge debt
Every fast team generates context faster than it records it. CortexHQ exists to stop losing decisions in Slack — and to turn scattered context into operating memory.
Slack threads disappear under velocity — decisions never become records.
Docs go stale the week after they ship — teams still cite them in customer calls.
The same debates repeat because nobody can find the last resolution.
Customer feedback is scattered across tickets, calls, and CRM notes.
New hires ask questions a tenured operator already answered — somewhere.
Leaders lose operating context when work spans tools and time zones.
How it works
CortexHQ is not a chat app. It is the layer that connects evidence to decisions — so teams stop repeating the same questions with different answers.
Ingest
Pull signals from Slack, docs, meetings, code, CRM, and support — normalized into memory objects.
Organize
Cluster by customer, decision, project, and owner — not by whichever channel was loudest.
Ask
Ask in plain language. CortexHQ returns the answer, the source trail, and what changed over time.
Verify sources
Every claim links to evidence. Stale docs get flagged when they disagree with newer threads.
Assign next actions
Owners and follow-ups are extracted so execution does not die in chat.
Remember decisions
Decision timelines become durable operating memory — not a one-off summary.
Live preview
This is local mock logic with realistic demo data — tuned to show sources, confidence, contradictions, and actions the way a production brain should behave.
Answer
Unresolved product and delivery risks cluster around release reliability and activation. Engineering is tracking intermittent CI failures on the release branch, while product is watching onboarding abandonment — both are open with owners, but timelines are not yet aligned in one decision record.
GitHub
org/core · issue #1200
GitHub issue #1204: release workflow flaky on cache step — intermittent failures.
Slack
#exec-decisions · thread 2
Slack #engineering: hotfix SLA at risk if branch stays red through Thursday.
Decision history
Flaky CI on release branch
Eng ManagerRelease branch failing intermittently — blocks hotfix SLA.
Onboarding drop-off
PMStep 3 abandonment up 18% week over week.
Contradictions found
Pilot readiness
Signal A
GTM: pilot can start with manual provisioning.
Signal B
Eng: automated provisioning required for SLA.
Next step: Define a temporary runbook and exit criteria for manual mode.
Owners
Recommended next actions
Use cases
From founders to chiefs of staff to engineering and GTM leaders — CortexHQ is for people who need the truth with receipts.
Founder operating memory
Hold the company’s decision graph in one place — what changed, who approved it, and what still conflicts.
Product decision retrieval
Recover the rationale behind scope calls, pricing experiments, and roadmap bets with linked evidence.
Customer feedback synthesis
See repeating objections and signals across support, CRM, and calls — with confidence and freshness.
Onboarding new hires
Give every hire the context of a tenured operator: decisions, owners, and where truth lives today.
Investor update prep
Assemble metrics, milestones, and risks with sources so the narrative matches reality under questions.
Engineering context recovery
Reconnect promises in tickets and Slack to what shipped in GitHub — before dates drift externally.
Source trust
Chat wrappers hide uncertainty. CortexHQ is designed to make uncertainty visible: conflicts, staleness, owners, and timelines.
Every answer has sources
No anonymous summaries — evidence cards show where the claim came from.
Stale info gets flagged
When a doc disagrees with newer Slack or CRM truth, CortexHQ surfaces the gap.
Decisions have timelines
See how a decision evolved across meetings, threads, and revisions — not just the last line.
Owners are extracted
DRIs and approvers are attached to memory objects so accountability stays visible.
Contradictions are surfaced
Conflicting signals are shown for resolution instead of being averaged away.
Pricing
These tiers describe how teams adopt CortexHQ — from a solo founder brain to enterprise governance.
Starter
$149/mo
Solo founder company brain demo: one operator, curated sources, weekly decision digest export.
Compare on pricing pageTeam
$699/mo
Connected team memory: shared graph, department lenses, owner queues, and contradiction alerts.
Compare on pricing pageScale
$2,400/mo
Multi-source company graph: higher sync cadence, risk radar modules, and CS/Sales leadership views.
Compare on pricing pageEnterprise
Custom
Security review support, SSO, audit logs, retention controls, and custom connector development.
Compare on pricing pageFAQ
Straight answers for how CortexHQ is meant to behave when the stakes are real.
Where does my data live in this demo?
This build runs locally with simulated connectors. Nothing here reaches Slack, email, or your CRM. Advanced ingest lets you paste sample notes into the workspace simulator.
How do you reduce wrong answers?
CortexHQ is designed around source trails, confidence, and contradiction detection. When evidence is thin, the UI should say so — this demo encodes that posture in mock outputs.
Which integrations ship first?
The product direction assumes Slack, docs, meetings, GitHub, CRM, and support are the backbone. This MVP visualizes that stack without requiring paid APIs.
How does team onboarding work?
Start with department lenses and source filters, then expand connectors as trust grows. The dashboard is built to train the org on operating memory habits.
What about hallucinations?
Treat any freeform model output as guilty until tied to sources. CortexHQ’s model is: show sources first, then narrative — and flag conflicts instead of smoothing them.
Turn scattered context into operating memory — with sources, owners, and timelines your team can trust under pressure.