AI engine

The Filo AI Engine.

The technology behind Filo. Every request runs through the Filo AI Engine™, powered by Filo Matrix 1.0™, in eight phases: from understanding what you asked to learning from what you decided.

See the eight phasesHow a team uses Filo

Filo Matrix 1.0

Filo Matrix 1.0™ is the core of the engine.

Filo Matrix 1.0 is the core. It holds what Filo knows about your business, plans the work, carries it out and learns from your team’s decisions.

Around it, four specialist proprietary algorithms do the jobs that have to be exact: reading documents, matching names to records, checking numbers and ranking quotes. The language model is a part we choose for each step. The engine around it is ours.

One request, through all eight phases.

Ana asks Filo to price a customer’s multivitamin at 5,000 and 25,000 bottles.

A diagram of one customer quote moving through the eight phases: understood as a quote for Summit Multivitamin v3, grounded in Ana’s price list, 18 lines matched, a five-step plan, two price requests drafted in her Gmail, Northstar’s PDF read and checked, Ana sends and picks, and the pick is kept with the quote.

The eight phases

Phase 01

Understand the request

Filo works out what kind of job it has been given and which record it belongs to before it does anything.

  1. 1.1Intent and job type: a price request, a customer quote, a record update, a question.
  2. 1.2Safety and scope: what this person may do in this workspace, and what Filo never does.
  3. 1.3Routing to a skill, the playbook for jobs that go best done one set way.
  4. 1.4The record attached: a costing’s chat knows its costing, an RFQ’s chat knows its suppliers.
Phase 02

Ground in your business

Filo Matrix 1.0 pulls in what it knows about your company before it plans.

  1. 2.1Your suppliers, materials, customers and price list, read where they live.
  2. 2.2The project’s documents and the files in the chat.
  3. 2.3Your playbook: your price cutoff, margin, conversion costs and overage.
  4. 2.4A year of supplier email, quotes and attachments, read into a map of your business on day one, and your Baseline report.
Phase 03

Resolve every entity

Every material, supplier and customer named in a document is matched to the record it means.

filo-ops-match
  1. 3.1Matching by your item code, aliases and name.
  2. 3.2Units read and converted: mg, g, kg, IU, per bottle, per serving.
  3. 3.3A score on every match, with the one attribute that would change it.
  4. 3.4Every correction kept as an alias, so the same name never needs fixing twice.
Phase 04

Plan the work

Filo Matrix 1.0 plans the job as steps you can see, and runs them for as long as the job takes.

  1. 4.1A visible plan in the chat, with the step Filo is on.
  2. 4.2Durable runs: every step is saved before it is shown.
  3. 4.3Check-ins: Filo can wait days for a supplier and pick the job back up on its own.
  4. 4.4Messages you send while Filo works are read at its next step.
Phase 05

Act through your systems

Filo works through a typed catalog of functions, the same ones your apps use.

  1. 5.1Records read and written in Google Sheets, Fiddle or Filo.
  2. 5.2Emails drafted in your own mailbox, never sent from ours.
  3. 5.3Every write logged with who asked, from which chat, and the files in it.
  4. 5.4Anything Filo added can be undone.
Phase 06

Verify every number

Prices, MOQs and lead times are read into fields and checked before anyone relies on them.

filo-ops-extractfilo-ops-verify
  1. 6.1Quotes read from the email body, a PDF or a spreadsheet into price, breaks, MOQ, lead time and validity.
  2. 6.2Every quote linked to the email it came from.
  3. 6.3Prices older than your cutoff flagged before they are used.
  4. 6.4A second, independent reading of every number, checked against the arithmetic.
  5. 6.5Each price checked against that supplier’s history, with a confidence score.
Phase 07

Ask before it acts

Anything that leaves the building or changes a record waits for a person.

  1. 7.1Approval cards in the chat, one button each.
  2. 7.2Drafts checked while Filo writes them: a card missing what it needs is redrawn.
  3. 7.3Record changes shown as plain lines before you approve them.
  4. 7.4Thresholds that move with your corrections: fewer corrections, fewer interruptions.
Phase 08

Learn from every decision

Filo gets better at your business from the work your team does with it.

filo-ops-rank
  1. 8.1How each person writes, learned from their sent email.
  2. 8.2What people change in Filo’s drafts, kept as rules for next time.
  3. 8.3Quotes ranked the way your team picks, retrained for your company every night.
  4. 8.4Matches confirmed or corrected, fed back to filo-ops-match.

Four specialist proprietary algorithms.

Each one is Filo’s own code, using a model where it helps. They run around Filo Matrix 1.0 on every job.

filo-ops-extractReads quotes, formulas and documents into fields.In use
filo-ops-matchResolves every material, supplier and customer to its record.In use
filo-ops-verifyChecks every number: units, totals, price breaks, history, confidence.In use
filo-ops-rankRanks quotes the way your team picks, retrained for your company nightly.In use

Always on, under every phase.

Runtime and reliability

Every step is saved before you see it. A restart or a deploy picks the job up where it stopped, and nothing is sent twice.

Model routing

Each step runs on the model that suits it, across five providers. The cost and size of every call is recorded.

Testing against simulated suppliers

Before a release, Filo runs against simulated suppliers who quote, ask questions, decline and go quiet.

Trust & security

Filo runs on Google Cloud in the US. Connection tokens are encrypted, every record belongs to one account, model providers don’t train on your data, and nothing goes out without a person.

Read the security policy →Security at Filo →

See the engine work on one of your products.

Bring a formula, recipe or BOM and your supplier list. We run them through Filo with you in 45 minutes.

Book a demo →How a team uses Filo