Skip to content

Platform / Knowledge Hub

Institutional memory, queryable.

Every quote, every contract clause, every supplier conversation gets indexed. Your agents can recall what worked, what didn't, and why. So can your team.

Book a demoSee the agents

10y of history ingestible · semantic + structured search · runs on your data

The shape of what you know

A real map, drawn from a real customer's data.

Every blue node is a supplier, a contract, a quote cycle, or a clause. The amber nodes are decisions your team made and the agents remember. The lines are the relationships an answer can travel along when someone asks a question.

Spaceflow Knowledge Hub map view showing hundreds of interconnected nodes representing suppliers, contracts, quote cycles, and decisions, organized as a graph.
Indexed across email, contracts, ERP records, and supplier portals. Every node carries the sources it was built from.

scroll →

From map to answer

Ask in plain English. Get the sourced answer.

The graph is what an agent walks when you (or another agent) asks a question. The answer comes back with every source it touched, so your team can check the work before acting on it.

knowledge.recall

What did we pay steelcore last December and did we get terms?

1.2s

answer · sourced

You paid €3.38/kg on PO-2381. The win came with a one-cycle term concession (Net 30 → Net 45) traded for a 5% volume commit. Steelcore's OTIF in that quarter was 96.1%.

sources · 4 of 28

  • email / 2025-12-08Quote response from steelcore for SKU STL-87410.94
  • po / PO-2381Past PO at €3.38/kg · Net 45 · won0.91
  • note / H. KayaInternal note: concession traded for volume0.83
  • scorecard / 2025 Q4Steelcore OTIF 96.1% · returns 0.4%0.71

28 sources searched · indexed back 10 years

expand →

What this replaces

The thing your senior buyer knows isn't written down anywhere.

Procurement runs on people who remember the last six cycles. When they leave, you start over.

Tribal knowledge walks out the door

Every senior hire

Who quoted you well last time. Which clause in the master agreement covers this scenario. Why you dropped a supplier in 2022. None of it is in the system. All of it is in someone's head, and that head eventually changes jobs.

Same questions, answered from scratch

Time tax

What did we pay for this last quarter. What was the standard payment term we negotiated. Did this supplier ever miss a delivery. People spend a measurable share of their week answering questions they already answered six months ago.

Decisions have no paper trail

Audit pain

When an auditor asks why you chose vendor A over vendor B, the answer is usually a slack thread or a meeting nobody remembers. The Knowledge Hub records the inputs and the reasoning, automatically.

How it ingests, indexes, and recalls.

  1. INGEST

    Pulls from where work happens

    Email, contracts, ERP, ticketing, your shared drives. Read-only. We pull in what's relevant and skip what isn't.

  2. STRUCTURE

    Builds a typed graph

    Every supplier, every SKU, every clause, every event becomes a node. Relationships make the graph queryable in ways search can't reach.

  3. INDEX

    Semantic + structured

    Vector embeddings for fuzzy questions ('have we ever had a quality issue with this material'), structured queries for hard ones ('show last 8 quarters of pricing').

  4. RECALL

    Sub-second answers

    Your agents and your team query the same hub. The answer includes citations to the original sources so you can verify.

Works with

Pulls from where your knowledge already lives.

OutlookGmailSharePointGoogle DriveConfluenceNotionSAPOracleSalesforceSlack