# Konyx Knowledge Catalog

> The structured, versioned facts about Konyx — industrial procurement software for MRO and indirect spend — that konyxai.com and AI assistants answer from. Every record names its source and the date it was last checked against the product; a capability says whether it is live, planned or not offered.

Owner: Konyx Industrial Intelligence · Contact: ceo@konyxai.com · Version 1.0, updated 2026-10-02. The same records are served as JSON at https://konyxai.com/api/knowledge. Record ids (for example capabilities.rfq) are stable and are what Related lists point at.

## Company

What Konyx is, the problem it exists for, who it is for and how it differs from the systems a plant already has.

### What Konyx is

Konyx is industrial procurement software for MRO (maintenance, repair and operations) and indirect spend. It takes a request from the plant floor to a purchase order in the vendor's inbox: it reads the request, matches it against the company's own catalog and purchase history, ranks vendors, sends the RFQ, compares the quotes and issues the order — and a person reviews every step.

Konyx is a web application used from a browser on a desk or a phone. It is not an ERP and does not replace one: the ERP stays the system of record for the order and the money, and Konyx owns the work that happens before the order exists — the request, the sourcing, the RFQ, the quotes and the decision.

The company is Konyx Industrial Intelligence. The product is at an early stage: complete for pilots, with no published customer results yet.

- Legal name: Konyx Industrial Intelligence
- Website: https://konyxai.com
- Product type: Web application, browser-based, phone-first
- Category: Procurement software — MRO and indirect spend
- Stage: Pilot-ready; first design-partner pilots
- Contact: ceo@konyxai.com

_Source: konyxai.com — home page · Verified: 2026-09-26 · Version: 1 · URL: https://konyxai.com/knowledge/company#what-konyx-is · Related: company.problem, company.who-konyx-is-for, company.how-konyx-differs, how-it-works.overview_

### The problem Konyx exists for

In most plants the request-for-quotation cycle for MRO and indirect parts takes days: a technician describes a part without its number, a buyer chases vendors by phone and email, quotes come back as PDFs, and nobody sees what was paid last time. Konyx collapses that cycle to minutes.

The cost is not only the buyer's day. A rush part bought from whoever answers first costs more than the contract price; a quote compared against nothing is accepted as it is; a request that sits in an inbox delays maintenance. Konyx puts the company's own data — catalog, vendors, purchase history, contracts — beside every line, so the decision is informed and quick.

_Source: Engineering Action Plan — Purpose · Verified: 2026-09-26 · Version: 1 · URL: https://konyxai.com/knowledge/company#problem · Related: company.what-konyx-is, use-cases.last-paid-price, use-cases.no-part-number_

### Who Konyx is for

Konyx is built for asset-heavy plants — refining, chemicals, LNG, aerospace, mills — and for four kinds of people in them: maintenance and operations, procurement, plant and finance leadership, and IT and security.

Maintenance and operations raise requests without leaving the job and see where each one is. Procurement receives structured requests, ranked vendors and comparable quotes instead of chasing. Leadership sees what was asked, what it cost last time, what it cost now and how long each step took. IT and security get one backend, isolation between companies, permissions on every call and an append-only log.

_Source: konyxai.com — Who it's for · Verified: 2026-09-26 · Version: 1 · URL: https://konyxai.com/knowledge/company#who-konyx-is-for · Related: industries.refining, industries.general-manufacturing, company.what-konyx-is_

### How Konyx differs from an ERP, a portal or a marketplace

Konyx is not an ERP, not a vendor portal for technicians to learn, and not a marketplace. It is the front door that understands a request in plain words and the back office that finishes it — with the company's own vendors, its own prices and its own rules.

Against an ERP: the ERP records orders and money; it does not read a photo of a nameplate, find a vendor for a niche part, or send an RFQ to six suppliers at once. Konyx does that work and hands the ERP a purchase order.

Against an e-procurement portal: a portal asks the requester to know the catalog. Konyx asks what they need, in their words, and does the lookup itself.

Against a marketplace: Konyx does not sit between the buyer and the vendor. The company's own vendors quote directly to the company through a link; Konyx supplies the structure, the comparison and the record.

_Source: konyxai.com — What Konyx does · Verified: 2026-09-26 · Version: 1 · URL: https://konyxai.com/knowledge/company#how-konyx-differs · Related: faq.replace-erp, faq.marketplace, capabilities.ask-konyx_

### Principles Konyx is built on

Five rules govern the product: the AI is never the system of record; a person presses Send; the database is the source of truth and the model interprets it; every state change is recorded in the same transaction as the change; and each company is isolated below the application, in the database.

These are not policies layered on afterwards. Drafting an RFQ and sending it are separate permissions; the model's confidence is computed in code from what it could and could not confirm, never taken from the model's own estimate; the audit log cannot drift from reality because the same function that changes a status is the only thing that writes the audit event.

_Source: Engineering Action Plan — §1, §3.7, §3.8 · Verified: 2026-09-26 · Version: 1 · URL: https://konyxai.com/knowledge/company#principles · Related: control.person-presses-send, control.append-only-audit, control.tenant-isolation, how-it-works.what-the-ai-does_

### How to reach Konyx

Email ceo@konyxai.com, or book a demo through the form on konyxai.com. Customers sign in at app.konyxai.com.

A demo is about thirty minutes and walks the request-to-purchase-order flow with the prospect's own part numbers and vendors. No account is created by the demo form; the details are only used to reply.

- Email: ceo@konyxai.com
- Book a demo: https://konyxai.com/#demo
- Customer sign-in: https://app.konyxai.com

_Source: konyxai.com — footer · Verified: 2026-10-02 · Version: 3 · URL: https://konyxai.com/knowledge/company#contact · Related: pilot.shape_

## Product capabilities

Every capability as a record: what goes in, what comes out, and whether it is live, planned or deliberately not offered.

### Ask Konyx — request intake (Live)

The first screen is a question: what do you need? A person says it, types it, photographs the nameplate or drops in a spreadsheet, and Konyx turns it into a structured request — items, quantities, part numbers, manufacturer, urgency — then asks one or two specific questions with the usual answers ready to tap.

Every extracted field carries a state — confirmed, inferred or unknown — and the request's confidence is computed from those states in code, not reported by the model. The person sees the draft, corrects anything, answers the open questions and confirms; nothing is created until they do. A short answer such as a size is enough on its own, and follow-ups re-send the original photos so the model still sees the item.

It works on a phone browser on the plant floor: the composer is pinned at the bottom, the draft opens as a sheet, and voice is transcribed on the server when the browser cannot do it.

- Inputs: typed text; voice; photos (nameplates, labels, the part itself); spreadsheets and CSV files
- Outputs: a structured request with one line per item; per-field confirmed / inferred / unknown state; clarifying questions with tappable answers; catalog matches and purchase history per line; vendors ranked with reasons
- Not in v1: barcode scanning; email-to-request; a native mobile app

_Source: konyx-erp — the Ask Konyx screen; prompt request-extract v4 · Verified: 2026-09-26 · Version: 1 · URL: https://konyxai.com/knowledge/capabilities#ask-konyx · Related: capabilities.catalog-matching, capabilities.vendor-ranking, how-it-works.ask, use-cases.no-part-number_

### Matching against the company's own catalog (Live)

Every request line is matched against what the company already buys — its item master and its vendors' catalogs — by part number and normalised description. It is a lookup in the database, not a model's guess: nothing a model invents, a record found in the company's own data.

Matching is identifier similarity: a request for a Lovejoy L190 finds the catalog's Lovejoy L-190. Each match carries the vendor that sells it, the contract or catalog price, and the vendor's own part number. A stated manufacturer must agree on both sides; when two catalog rows disagree Konyx leaves the match blank rather than guess, because a wrong part number on a document a vendor ships against is worse than none.

A row only counts as the item when it is the item: the size (2", 2 in and 2-inch are the same), the material and grade, the end connection, the pressure rating, the maker and any code written into the description must agree, and a 3-way valve or a repair kit is not the valve. A vendor that only has other sizes or materials is shown as having similar items — never pre-selected as carrying it.

- Method: Trigram and word similarity in Postgres on normalised names and part numbers, scoped to the company, then a same-item check on size, material, ends, rating, maker and codes — in code, not a model
- Outputs: matched item; vendor and price; the vendor's own part number; contract price when one exists

_Source: konyx-api — core/item-match.ts · Verified: 2026-09-28 · Version: 2 · URL: https://konyxai.com/knowledge/capabilities#catalog-matching · Related: capabilities.bought-before, capabilities.vendor-ranking, faq.ai-models_

### Purchase history beside every line (Live)

Under each line of a draft, Konyx shows whether the company bought this before — from its imported purchase history, earlier quotes and earlier requests — and what it paid. The same last-paid price sits beside every quote later.

This is a query over the company's own rows, so it costs nothing and cannot hallucinate. It is what makes a quote comparison credible: you paid this in August; this quote is that.

- Sources: imported purchase history; quotes received in Konyx; earlier requests
- Shown: on the intake draft; on the request page; beside every quoted line

_Source: konyx-api — core/purchase-context.ts · Verified: 2026-09-26 · Version: 1 · URL: https://konyxai.com/knowledge/capabilities#bought-before · Related: capabilities.quote-comparison, use-cases.last-paid-price, integrations.spreadsheets_

### Vendors ranked with reasons (Live)

For every request, the company's own approved vendors are ranked best-first with the reasons on the card: how many lines they carry, exact part-number hits, the lowest price on a line, volume pricing, and whether there is someone to email. Then the Konyx network, then vendors found on the open web.

The buyer picks from one list. Ranking is explainable arithmetic over the company's data, so two buyers see the same order and can say why a vendor is first.

- Order: the company's own vendors; the Konyx network; vendors found on the web
- Reasons: lines covered; exact part numbers; lowest price on a line; volume pricing; contactable

_Source: konyx-api — core/vendor-rank.ts · Verified: 2026-09-26 · Version: 1 · URL: https://konyxai.com/knowledge/capabilities#vendor-ranking · Related: capabilities.konyx-network, capabilities.vendor-discovery, capabilities.rfq_

### The Konyx network (Live)

The Konyx network is a set of vendors and catalogs maintained by Konyx, suggested beneath a company's own vendors only when a catalog line actually matches the request. Choosing one copies it into the company's own list.

Network vendors are platform data, not any customer's. A company never sees another company's vendors; it sees Konyx's, and only where they carry the part.

_Source: konyx-api — platform vendors and catalogs · Verified: 2026-09-26 · Version: 1 · URL: https://konyxai.com/knowledge/capabilities#konyx-network · Related: capabilities.vendor-ranking, faq.konyx-network_

### Vendor discovery on the open web (Live)

For niche parts nobody in the company's list carries, Konyx searches the web, filters the results cheapest-first, reads the survivors' contact pages, scores each candidate with the score's parts kept, and shows a Found on the web section — with contacts and reasons. Nothing is emailed until a person picks the vendor and checks the address.

Search returns links and snippets without fetching pages; a denylist, free heuristics and one cheap model call remove retailers and noise before any page is read. Each find is kept as platform data with its product pages crawled afterwards, so the next request from any company benefits.

The page the search found is read for the product on it before the answer comes back — the vendor's SKU, the maker's part number and the maker, from the data shops publish for search engines, from labelled text, or from a short model read of that one page. The card says how the vendor lists the item, and that vendor's RFQ carries their number.

Discovered vendors are gated behind buyer review by design: it is the quality gate, the deliverability gate and the legal gate in one.

- Outputs: candidate vendors with domain, contact and reasons; the product on the page each was found on, with its part number and maker; an explainable confidence score; their catalog, crawled in the background
- Never does: email a discovered vendor automatically; scrape a search engine directly

_Source: konyx-api — core/discovery · Verified: 2026-09-28 · Version: 2 · URL: https://konyxai.com/knowledge/capabilities#vendor-discovery · Related: control.discovered-vendors-reviewed, use-cases.rush-part-no-supplier_

### One RFQ to all the vendors (Live)

A buyer drafts one request for quotation, sees the exact email each vendor will receive — subject, opening, note, deadline, the vendor's own quote link and their own part numbers — and presses Send. RFQs are never sent automatically: sending is a separate permission from drafting.

Each recipient's copy is rendered on its own, so the greeting, the reply address and the item numbers differ per vendor. Replies can come back into Konyx or go straight to the team's own inbox, by company setting. A draft can be deleted while nothing has gone to a vendor.

A request has one draft at a time: choosing other vendors changes that draft rather than starting another. The request stays with the buyer while the RFQ is a draft and reads RFQ sent once it has gone out.

Every item table reads: item number (that vendor's own code), item, description, manufacturer, quantity — the way a vendor identifies a part. When the request names no maker, each vendor sees the one they list the item under.

- Send from: Konyx; the buyer's own mailbox, via their mail app
- Replies to: Konyx; the team's own inbox
- Permission: rfq.send, separate from rfq.create

_Source: konyx-erp — RFQ page and send screen · Verified: 2026-09-28 · Version: 2 · URL: https://konyxai.com/knowledge/capabilities#rfq · Related: capabilities.own-email-sending, capabilities.vendor-quote-portal, control.person-presses-send, use-cases.supplier-part-numbers_

### Sending from the buyer's own email (Live)

An RFQ or a purchase order can go out from the buyer's own mailbox instead of a Konyx address. Konyx prepares each vendor's message and the buyer sends it from their own mail app, then ticks the recipients they sent; quotes still come back through the vendor's link.

Some plants must send from their own domain by policy, and a message from procurement at the customer's own domain lands better than one from a platform. A per-company default chooses the mode; the send screen can switch it.

_Source: konyx-erp — send screen, mailto mode · Verified: 2026-09-26 · Version: 1 · URL: https://konyxai.com/knowledge/capabilities#own-email-sending · Related: capabilities.rfq, integrations.email, use-cases.send-from-own-domain_

### The vendor's quote link (Live)

Vendors answer an RFQ through a link in the email — no account, no login. They price each line, state lead time and terms, and can revise; every revision is kept, never overwritten.

The link is unique to the vendor and the RFQ and is rate-limited. Quotes land in Konyx as comparable lines the moment they are submitted.

_Source: konyx-erp — portal pages; konyx-api — portal · Verified: 2026-09-26 · Version: 1 · URL: https://konyxai.com/knowledge/capabilities#vendor-quote-portal · Related: capabilities.quote-comparison, faq.vendor-account_

### Quotes side by side (Live)

Quotes come back into one grid: every vendor's price per line, the lowest highlighted, beside what the company last paid. The buyer picks the winning lines and issues the purchase order from them.

Lines are compared as lines, not as documents, so a partial quote and a full one sit in the same table. On a phone the grid stacks into labelled cards.

_Source: konyx-erp — quote comparison grid · Verified: 2026-09-26 · Version: 1 · URL: https://konyxai.com/knowledge/capabilities#quote-comparison · Related: capabilities.bought-before, capabilities.purchase-orders_

### Purchase orders from a quote (Live)

Anyone holding the po.issue permission can turn chosen quote lines into a purchase order at the quoted prices, numbered with the company's own prefix and carrying its ship-to address, terms and standard conditions. The order reaches the vendor one of three ways and always says which.

Konyx can email the order with the PDF attached; the buyer can send it from their own mailbox and mark it sent; or Konyx emails the buyer a copy to forward. Order lines snapshot the vendor's part number and the specification at issue time, so a later catalog import can never change a document a vendor already filed.

Issuing the order walks the request to Ordered; the RFQ closes when every line is ordered. Approval rules are planned; until then the issuer's permission stands in.

- Permission: po.issue
- Company settings: PO number prefix; ship-to; payment terms; standard conditions
- Output: a PDF and an email, or the plain text for the buyer's own mail app

_Source: konyx-api — core/purchase-order.ts, core/po-pdf.ts · Verified: 2026-09-26 · Version: 1 · URL: https://konyxai.com/knowledge/capabilities#purchase-orders · Related: capabilities.quote-comparison, capabilities.approval-rules, faq.who-can-issue-a-po_

### Routing, escalation, notes and notifications (Live)

A request moves through an eleven-state lifecycle behind one guarded transition function. Someone who cannot source it themselves sends it up the supervisor chain to the first person who holds the needed permission; notes travel with the request; a bell announces anything that happens to yours.

Escalation is mechanical: the first person up the chain with the permission, then any holder, the owner last — so a request cannot dead-end because a direct manager lacks the right. The requester can amend a request from Ask Konyx while nothing has gone to a vendor.

Notifications are written in the same transaction as the thing they announce — a request sent to you, a note, a change, a quote back, an order issued.

- States: eleven, with an explicit allowed-transition map
- Notes: plain messages between the requester and whoever the request is with
- Bell: polled every 45 seconds and on focus; no sockets

_Source: konyx-api — core/request-state.ts, core/approver.ts, core/notify.ts · Verified: 2026-09-26 · Version: 1 · URL: https://konyxai.com/knowledge/capabilities#request-routing · Related: capabilities.roles-and-permissions, use-cases.employee-cannot-send, use-cases.tracking-a-request_

### Roles and permissions (Live)

Each company defines its own roles from 26 hard-coded permission toggles. A person holds the union of their roles; the owner holds everything. Requesting, drafting an RFQ, sending it and issuing a purchase order are separate permissions.

That matches how procurement delegates: an administrator grants one maintenance lead the right to send RFQs without promoting them. Default roles come with every company, including Procurement and a built-in Super user, and can be cloned and changed.

- Permissions: 26, as a closed list checked on every API call
- Examples: request.create; rfq.create; rfq.send; po.issue; request.assign

_Source: konyx-api — authz; 26 permissions · Verified: 2026-09-26 · Version: 1 · URL: https://konyxai.com/knowledge/capabilities#roles-and-permissions · Related: control.permissions-on-every-call, capabilities.request-routing_

### The activity log (Live)

Every action — who, what, when — is written to an append-only log in the same transaction as the change, and shown in plain sentences on the request, the person and the company.

The log is append-only at the database level, not by convention. Changes made by Konyx staff through the console are written as done by Konyx, so a company can always see what its vendor did.

_Source: konyx-api — core/audit.ts · Verified: 2026-09-26 · Version: 1 · URL: https://konyxai.com/knowledge/capabilities#activity-log · Related: control.append-only-audit_

### The savings audit (Live)

From one export of a company's purchasing history, Konyx computes what it would have saved: price gaps against the company's own best price and the Konyx network, cycle time, late deliveries, quote competition, rush and card spend, and buyer hours — then writes the findings up as a five-page report.

Every figure is computed in code from the file; the model only writes the narrative from those figures. The audit runs before any contract and is how a pilot's baseline is set. It is prepared by Konyx staff from the company's file, not self-served.

- Input: one CSV of purchase orders or lines, any column names — mapping is confirmed on screen
- Outputs: money: price gaps and where they are; buyer hours and calendar days, manual process versus Konyx; findings, price gaps, vendors, method; a PDF report

_Source: konyx-admin — Audit page; konyx-api — core/savings-analysis.ts · Verified: 2026-09-26 · Version: 1 · URL: https://konyxai.com/knowledge/capabilities#savings-audit · Related: pilot.baseline, proof.savings-audit-method_

### Time saved, RFQ by RFQ (Live)

For every RFQ that goes out, Konyx sets what it would have taken a buyer by hand against the time it actually took in Konyx — per RFQ, per company and across the platform. By hand is estimated step by step from the RFQ's own items, vendors, new vendors and quoted lines; in Konyx is measured from the recorded steps, with idle time capped.

In Konyx runs from the first thing the person asked Konyx for the request to the moment the RFQ went out, adding the time between each recorded step — model calls and every logged action. A pause longer than ten minutes counts as ten, so a draft left overnight is not counted as a night's work. The clock time from first question to sent is shown beside it.

By hand counts only the steps that applied: going back to the requester for details, checking stock and past prices per item, finding each vendor (a vendor new to the company takes longer than one on file), writing the RFQ and typing each item, emailing each vendor, retyping each quoted line that came back through the vendor's link, and laying two or more quotes side by side. The minutes per step are set by Konyx for every company and listed on the page; nothing is estimated by a model.

A company's people with the analytics permission see the Time saved page and a line on their overview; anyone who can read RFQs sees the figure on each sent RFQ. Konyx staff see every company and the platform total, and set the minutes.

- Measured: time in Konyx, first question to sent, idle capped at 10 minutes; clock time, first question to sent
- Estimated per RFQ (built-in minutes): clarify the request: 10 per request; stock and past prices: 4 per item; vendor on file: 5 each; new vendor: 30 each; write the RFQ: 10, plus 3 per item; email each vendor: 4; retype a quoted line: 2; compare two or more quotes: 10
- Also shown: value of the time at a buyer's hourly cost, $45 by default; medians per RFQ, both ways; where the by-hand minutes would have gone

_Source: konyx-api — core/time-saved.ts; konyx-erp — Time saved page; konyx-admin — Time saved · Verified: 2026-10-01 · Version: 1 · URL: https://konyxai.com/knowledge/capabilities#time-saved · Related: proof.savings-audit-method, capabilities.rfq, proof.customer-results_

### Bringing vendors, catalogs and people in (Live)

Vendors and their catalogs come in from one spreadsheet, with contacts; columns are mapped with the model's help and confirmed on screen; every problem row is shown before anything is committed, per vendor; an import can be undone as a unit. The team comes in from a five-column CSV with invitation links.

Each row is judged after it is chosen, by its content rather than its file label, so a phone can pick the file and an Excel workbook gets a clear ask to save as CSV. A test set of 20 vendors and 6,600 catalog rows lands in about six seconds.

- Vendor file: one CSV: vendor, contacts, item, part number, price ladder
- Team file: ID, Name, Email, Role, Manager
- Purchase history: any export, mapped on screen — used by the savings audit and for last-paid prices
- Planned: inventory; open purchase orders; contracts

_Source: konyx-erp — vendor import, team import · Verified: 2026-09-26 · Version: 1 · URL: https://konyxai.com/knowledge/capabilities#data-import · Related: integrations.spreadsheets, pilot.adoption_

### Plan limits per company (Live)

Each company has limits set by Konyx: how many people, how many RFQs a month, how many items on one RFQ. They are enforced in the API and shown to the company under Settings.

- Defaults: 5 people; 250 RFQs a month; 30 items per RFQ
- Set by: Konyx, from the console; every change is written to the company's log

_Source: konyx-api — core/limits.ts · Verified: 2026-09-26 · Version: 1 · URL: https://konyxai.com/knowledge/capabilities#plan-limits · Related: faq.pricing_

### Approval rules and the simulator (Planned)

Policy-based approval routing — by amount, category or exception — with a simulator that shows who would approve a given order before the rule goes live. Not shipped yet; today the issuer's po.issue permission stands in.

_Source: Engineering Action Plan — §3.7, Next · Verified: 2026-09-26 · Version: 1 · URL: https://konyxai.com/knowledge/capabilities#approval-rules · Related: capabilities.purchase-orders_

### Quotes arriving by email (Planned)

Reading a quote out of a vendor's emailed PDF or spreadsheet as a fallback to the quote link. Not shipped: vendor replies by email currently go to the team's inbox, and quotes come back through the link.

_Source: Engineering Action Plan — §3.6 · Verified: 2026-09-26 · Version: 1 · URL: https://konyxai.com/knowledge/capabilities#email-quote-capture · Related: capabilities.vendor-quote-portal, integrations.email_

### Sending through Microsoft 365 or Gmail (Planned)

Sending RFQs and orders through the buyer's mailbox by API, so they appear in Sent without the buyer's mail app being involved. Not shipped; own-email sending works today through the buyer's mail app.

_Source: Engineering Action Plan — Next · Verified: 2026-09-26 · Version: 1 · URL: https://konyxai.com/knowledge/capabilities#mailbox-connectors · Related: capabilities.own-email-sending, integrations.mailbox-connectors_

### A native mobile app (Not offered)

There is no iOS or Android app. The web application is built phone-first — voice, photos and the request draft all work in a phone browser — and nothing in the product requires an installed app.

_Source: Engineering Action Plan — Scope decisions · Verified: 2026-09-26 · Version: 1 · URL: https://konyxai.com/knowledge/capabilities#native-mobile-app · Related: capabilities.ask-konyx, faq.phones_

### Autonomous purchasing (Not offered)

Konyx never sends an RFQ, awards a quote or issues an order on its own. The AI interprets and prepares; a named person with the permission releases every send and every order. This is a design decision, not a missing feature.

_Source: Engineering Action Plan — §3.7, decision log · Verified: 2026-09-26 · Version: 1 · URL: https://konyxai.com/knowledge/capabilities#autonomous-purchasing · Related: control.person-presses-send, company.principles_

## How it works

The four steps from a request on the floor to a purchase order, and exactly what the AI does and does not do at each one.

### Four steps, a person at each one

Ask: a technician says what is needed and Konyx drafts the request from the catalog and history. Route: it goes to whoever may act on it. Send the RFQ: the buyer reviews every line and the email itself, then sends. Compare and order: quotes come back into one grid, the buyer picks the winner and issues the purchase order.

The AI interprets and prepares; people decide. That is what makes the product usable in a plant and defensible in a security review.

_Source: konyxai.com — How it works · Verified: 2026-09-26 · Version: 1 · URL: https://konyxai.com/knowledge/how-it-works#overview · Related: how-it-works.ask, how-it-works.route, how-it-works.send-the-rfq, how-it-works.compare-and-order, how-it-works.what-the-ai-does_

### Step 1 — Ask

A technician says what is needed, from the floor — a sentence, a voice note, a photo of the nameplate or a spreadsheet. Konyx reads it, checks the company's catalog and purchase history, and drafts the request with any open questions.

The person confirms the draft. Each field shows whether it was confirmed, inferred or unknown; the person can change any of it. Only then does a request exist.

_Source: konyx-erp — Ask Konyx · Verified: 2026-09-26 · Version: 1 · URL: https://konyxai.com/knowledge/how-it-works#ask · Related: capabilities.ask-konyx, capabilities.catalog-matching_

### Step 2 — Route

The request goes to whoever may act on it. A buyer sources it directly; a requester who cannot sends it to a supervisor — the first person up the chain with the permission. Notes go back and forth on the request, and it can be corrected before anything is sent.

_Source: konyx-api — request lifecycle · Verified: 2026-09-26 · Version: 1 · URL: https://konyxai.com/knowledge/how-it-works#route · Related: capabilities.request-routing, capabilities.roles-and-permissions_

### Step 3 — Send the RFQ

Vendors are ranked with reasons: the company's own first, then the Konyx network, then vendors found on the web. The buyer picks, reviews every line and the exact email each vendor will receive, ticks the review box, and sends — from Konyx or from their own mailbox.

_Source: konyx-erp — RFQ send screen · Verified: 2026-09-26 · Version: 1 · URL: https://konyxai.com/knowledge/how-it-works#send-the-rfq · Related: capabilities.vendor-ranking, capabilities.rfq, control.person-presses-send_

### Step 4 — Compare and order

Vendors quote through their link. Quotes land as comparable lines in one grid, the lowest per line highlighted beside the last price paid. The buyer picks the winning lines and issues the purchase order; every step is on the request's timeline.

_Source: konyx-erp — comparison grid and purchase order · Verified: 2026-09-26 · Version: 1 · URL: https://konyxai.com/knowledge/how-it-works#compare-and-order · Related: capabilities.quote-comparison, capabilities.purchase-orders_

### What the AI does, and what it never does

The AI reads a request into structure, asks the clarifying question, helps map spreadsheet columns, classifies web search results and writes the savings-audit narrative from figures computed in code. It never sends anything, never awards, never issues an order, and is never the system of record.

Confidence is not the model's opinion: it is computed from which fields were confirmed, inferred or unknown. Every model call is recorded — who asked, which prompt version, what it cost — and shown per company in the console. Prompts are versioned files; a change is a new version, never an edit.

Matching a request to the catalog, finding what was paid last time and ranking vendors are database queries, not model calls. They cost nothing, run in milliseconds and cannot invent a part.

- Model calls: request extraction; clarifying questions; column mapping for imports; filtering web search results; reading product pages of vendors found on the web; the audit narrative
- Never a model call: catalog matching; purchase history lookup; vendor ranking; sending; state changes

_Source: Engineering Action Plan — §3.8 · Verified: 2026-09-28 · Version: 2 · URL: https://konyxai.com/knowledge/how-it-works#what-the-ai-does · Related: faq.ai-models, control.ai-provenance, company.principles_

## Problems and solutions

Concrete situations in a plant's purchasing, and what Konyx does about each.

### The technician does not know the part number

Problem: a coupling has failed and the technician knows the machine, not the part. Konyx: they photograph the nameplate or the part and say what it is for; Konyx drafts the line, asks the one question that matters (size, material, seal type — with answers to tap), matches it against the catalog and purchase history, and ranks the vendors who carry it.

What the buyer receives is a structured request with the catalog match, the last price paid and the candidate vendors — not a phone call to decode.

_Source: konyx-erp — Ask Konyx with photos · Verified: 2026-09-26 · Version: 1 · URL: https://konyxai.com/knowledge/use-cases#no-part-number · Related: capabilities.ask-konyx, capabilities.catalog-matching_

### The same gasket has a different number at every supplier

Problem: one gasket is 101-100-234 at one distributor and LSV-BV-200 at the next; a document with the wrong code gets the wrong part shipped. Konyx: each vendor's copy of the RFQ and the purchase order carries that vendor's own item number, resolved from the item master, a lead list, that vendor's catalog or — for a vendor found on the web — their own product page, and left blank when there is no confident match.

The manufacturer's part number sits under the manufacturer on every document, so nothing is lost. Purchase-order lines snapshot the supplier code at issue, so a reimported catalog can never change a filed PDF.

_Source: konyx-api — core/supplier-part.ts · Verified: 2026-09-28 · Version: 2 · URL: https://konyxai.com/knowledge/use-cases#supplier-part-numbers · Related: capabilities.rfq, capabilities.purchase-orders_

### A rush part with no known supplier

Problem: a niche part nobody on the vendor list carries, and the line is down. Konyx: after the company's own vendors and the Konyx network have answered, it searches the web, reads the candidates' contact pages, and shows a Found on the web section with contacts, reasons and a score. The buyer picks who to ask; nothing is emailed until they do.

_Source: konyx-api — core/discovery · Verified: 2026-09-26 · Version: 1 · URL: https://konyxai.com/knowledge/use-cases#rush-part-no-supplier · Related: capabilities.vendor-discovery, control.discovered-vendors-reviewed_

### What did we pay last time?

Problem: a quote arrives and nobody has the last invoice to hand, so it is accepted as it is. Konyx: the price paid last time — from imported history, earlier quotes and earlier requests — sits under the request line and beside every quoted line, and the contract price appears where a contract exists.

_Source: konyx-api — core/purchase-context.ts · Verified: 2026-09-26 · Version: 1 · URL: https://konyxai.com/knowledge/use-cases#last-paid-price · Related: capabilities.bought-before, capabilities.quote-comparison_

### Quotes come back as PDFs and email threads

Problem: six vendors answer in six formats and the buyer retypes them into a spreadsheet to compare. Konyx: vendors price each line through a no-login link, quotes land as comparable lines in one grid with the lowest highlighted, and revisions are kept rather than overwritten.

_Source: konyx-erp — vendor portal and comparison grid · Verified: 2026-09-26 · Version: 1 · URL: https://konyxai.com/knowledge/use-cases#quotes-in-pdfs · Related: capabilities.vendor-quote-portal, capabilities.quote-comparison_

### An employee who may raise a request but not send an RFQ

Problem: the plant wants anyone to be able to ask for a part, but only procurement to talk to vendors. Konyx: request.create and rfq.send are separate permissions. An employee's request routes to the first person up their supervisor chain who can act; an employee calling the RFQ endpoint directly gets a refusal, not a hidden button.

_Source: konyx-api — permissions and escalation · Verified: 2026-09-26 · Version: 1 · URL: https://konyxai.com/knowledge/use-cases#employee-cannot-send · Related: capabilities.roles-and-permissions, capabilities.request-routing_

### Vendors must hear from the plant's own domain

Problem: policy or vendor relationships require RFQs to come from procurement at the company's own address. Konyx: the buyer switches the send screen to their own email; Konyx prepares each vendor's message, the buyer sends it from their mail app and ticks who they sent; the record shows it and the quotes still come back through the link.

_Source: konyx-erp — own-email sending · Verified: 2026-09-26 · Version: 1 · URL: https://konyxai.com/knowledge/use-cases#send-from-own-domain · Related: capabilities.own-email-sending, integrations.email_

### Proving the case before signing anything

Problem: finance wants a number before a pilot, and vendor claims are not evidence. Konyx: the company sends one export of its purchasing history; Konyx computes the price gaps, cycle times and buyer hours from that file and writes the findings up. The baseline is the company's own data, before any contract.

_Source: konyx-admin — Audit page · Verified: 2026-09-26 · Version: 1 · URL: https://konyxai.com/knowledge/use-cases#business-case-before-contract · Related: capabilities.savings-audit, pilot.baseline, proof.savings-audit-method_

### A shutdown list of thirty lines in a spreadsheet

Problem: a turnaround list arrives as a spreadsheet and each line would be a separate request. Konyx: drop the file into Ask Konyx; every row becomes a line on one request, matched against the catalog, with vendors ranked by how many of the lines they cover — then one RFQ goes to all of them.

_Source: konyx-erp — Ask Konyx with spreadsheets · Verified: 2026-09-26 · Version: 1 · URL: https://konyxai.com/knowledge/use-cases#spreadsheet-of-parts · Related: capabilities.ask-konyx, capabilities.vendor-ranking, capabilities.plan-limits_

### Where is my request?

Problem: the technician who asked for the part has to phone the buyer to find out what happened. Konyx: the request page shows where it is, who it is with and every step on its timeline; notes go back and forth on the request; the bell announces a note, a quote or an order; and the requester can change the request themselves before anything goes out.

_Source: konyx-erp — request page, notes, notifications · Verified: 2026-09-26 · Version: 1 · URL: https://konyxai.com/knowledge/use-cases#tracking-a-request · Related: capabilities.request-routing_

## Industries

Where Konyx fits: asset-heavy plants and the purchasing patterns they share.

### Refining

Refineries buy MRO parts under time pressure — turnarounds, unplanned outages, rush replacements for rotating equipment, valves and instrumentation — often against approved-vendor lists and contract pricing that the person raising the request never sees. Konyx puts the contract price, the last price paid and the approved vendors beside the request before it goes out.

- Typical requests: valves by class, size and material; pump and compressor spares; gaskets and seals; instrumentation; safety consumables
- What matters: a rush part sourced at the right price, not the first price; vendors who carry the exact manufacturer part; an audit trail for every purchase

_Source: konyxai.com — Who it's for · Verified: 2026-09-26 · Version: 1 · URL: https://konyxai.com/knowledge/industries#refining · Related: use-cases.rush-part-no-supplier, use-cases.last-paid-price, control.append-only-audit_

### Chemicals and petrochemicals

Chemical plants carry long catalogs of material-specific parts — the same valve in three alloys, the same seal in three elastomers — where an ambiguous request means the wrong part. Ask Konyx asks the material and size question up front with the usual answers to tap, and matching checks the manufacturer on both sides before it claims a part number.

- Typical requests: alloy and lined valves; seals and gaskets by elastomer; pump parts; filtration; PPE and consumables

_Source: konyxai.com — Who it's for · Verified: 2026-09-26 · Version: 1 · URL: https://konyxai.com/knowledge/industries#chemicals · Related: capabilities.ask-konyx, capabilities.catalog-matching, use-cases.supplier-part-numbers_

### LNG and energy

Energy sites are often remote and vendor-poor for niche parts, and lead time is the cost that matters. Konyx searches the web for vendors who carry the part when the company's own list has none, and the quote grid shows lead time beside price so the buyer can trade one for the other on purpose.

- What matters: lead time as a first-class figure; finding a distributor for an unusual part; one RFQ to several vendors at once

_Source: konyxai.com — Who it's for · Verified: 2026-09-26 · Version: 1 · URL: https://konyxai.com/knowledge/industries#lng-and-energy · Related: capabilities.vendor-discovery, capabilities.quote-comparison_

### Aerospace and precision manufacturing

Aerospace suppliers buy tooling, consumables and indirect materials under documentation discipline: who approved what, which vendor, which part number, when. Konyx separates drafting from sending and issuing, records every step in an append-only log, and keeps each vendor's own part number on the documents a vendor ships against.

_Source: konyxai.com — Who it's for · Verified: 2026-09-26 · Version: 1 · URL: https://konyxai.com/knowledge/industries#aerospace · Related: capabilities.roles-and-permissions, capabilities.activity-log, use-cases.supplier-part-numbers_

### Mills — pulp and paper, steel

Mills run continuous processes with heavy rotating equipment; bearings, couplings, belts and drives are bought again and again from a handful of distributors. Konyx turns that repetition into an advantage: the catalog match, the last price paid and the vendor ranking are all built from the mill's own history.

- Typical requests: bearings and housings; couplings; belts and drives; gearbox spares; conveyor parts

_Source: konyxai.com — Who it's for · Verified: 2026-09-26 · Version: 1 · URL: https://konyxai.com/knowledge/industries#mills · Related: capabilities.bought-before, capabilities.vendor-ranking_

### General manufacturing and MRO

Any plant with a maintenance store, a vendor list and a buyer who chases quotes by email has the problem Konyx solves. The product needs no ERP connector to start: vendors and catalogs come in from one spreadsheet, the team from another, and purchase history from an export.

_Source: Engineering Action Plan — Purpose · Verified: 2026-09-26 · Version: 1 · URL: https://konyxai.com/knowledge/industries#general-manufacturing · Related: capabilities.data-import, pilot.shape, integrations.erp_

## Questions and answers

The questions buyers, finance and IT ask before a pilot, answered once.

### Does Konyx replace our ERP?

No. The ERP stays the system of record for the order and the money. Konyx owns the work before the order exists — request, sourcing, RFQ, quotes, decision — and hands over a purchase order as a PDF and an email. There are no live ERP connectors in the current version; data comes in by spreadsheet export.

_Source: konyxai.com — Pilot defaults · Verified: 2026-09-26 · Version: 1 · URL: https://konyxai.com/knowledge/faq#replace-erp · Related: company.how-konyx-differs, integrations.erp_

### Does the AI send anything on its own?

No. Konyx never sends an RFQ, awards a quote or issues an order automatically. The AI reads and drafts; a named person with the permission reviews the exact email and presses Send, and the same is true for every purchase order.

_Source: Engineering Action Plan — decision log · Verified: 2026-09-26 · Version: 1 · URL: https://konyxai.com/knowledge/faq#auto-send · Related: control.person-presses-send, capabilities.autonomous-purchasing_

### How is our data kept separate from other companies'?

Each company's rows are isolated by row-level security in the database itself, enforced below the application: every tenant-scoped table has a forced policy, the application connects as a role that cannot bypass it, and an automated check fails the build if a table is missing its policy. Konyx staff manage a company through the same permission wall its own people use — never through a database console.

_Source: Engineering Action Plan — §3.1 · Verified: 2026-09-26 · Version: 1 · URL: https://konyxai.com/knowledge/faq#data-isolation · Related: control.tenant-isolation, control.architecture_

### Where does Konyx run?

The API and the database run on Google Cloud in the United States; the web applications and the public site run on Cloudflare. The browser never talks to the API directly — only the web application's own backend does, with a key the browser never holds.

_Source: DEPLOY.md · Verified: 2026-09-26 · Version: 1 · URL: https://konyxai.com/knowledge/faq#hosting · Related: control.architecture_

### Which AI models does Konyx use, and what sees our data?

Konyx calls OpenAI models through their API for request extraction, clarifying questions, column mapping, filtering web search results and writing the audit narrative — behind an abstraction so the provider can change. Catalog matching, purchase history and vendor ranking are database queries and never leave Konyx. Every model call is recorded with who made it, which prompt version and what it cost.

_Source: Engineering Action Plan — §3.8, §4 · Verified: 2026-09-26 · Version: 1 · URL: https://konyxai.com/knowledge/faq#ai-models · Related: how-it-works.what-the-ai-does, control.ai-provenance_

### Do our vendors need an account?

No. A vendor answers an RFQ through the link in the email — no account, no password. They price each line, add lead time and terms, and can revise; every revision is kept.

_Source: konyx-erp — vendor portal · Verified: 2026-09-26 · Version: 1 · URL: https://konyxai.com/knowledge/faq#vendor-account · Related: capabilities.vendor-quote-portal_

### Can we send RFQs from our own email address?

Yes. A toggle on the send screen — and a per-company default — prepares each vendor's message for the buyer's own mail app. The buyer sends it and ticks the recipients; Konyx records it and the quotes still come back through the vendor's link.

_Source: konyx-erp — own-email sending · Verified: 2026-09-26 · Version: 1 · URL: https://konyxai.com/knowledge/faq#own-email · Related: capabilities.own-email-sending_

### Does it work on a phone?

Yes, in the phone's browser, with nothing to install. Ask Konyx is built for a phone on the plant floor — voice, photos, the draft as a sheet — and every other screen, including the wide quote grid, stacks to fit a phone.

_Source: konyx-erp — phone-first layout · Verified: 2026-09-26 · Version: 1 · URL: https://konyxai.com/knowledge/faq#phones · Related: capabilities.native-mobile-app, capabilities.ask-konyx_

### How long does it take to get started?

Vendors and catalogs come in from one spreadsheet and the team from another, with problems shown before anything is committed. A pilot runs ninety days on one facility, and the baseline — a savings audit of your own purchasing history — is done before it starts.

_Source: konyxai.com — Pilot · Verified: 2026-09-26 · Version: 1 · URL: https://konyxai.com/knowledge/faq#onboarding-time · Related: pilot.shape, capabilities.data-import_

### What does Konyx cost?

Pricing is set per company in the pilot conversation and is not published here. Each company runs on a plan with limits — people, RFQs a month, items per RFQ — that Konyx sizes to the company. The savings audit that opens a pilot puts the company's own number on the table first.

_Source: konyxai.com — Pilot · Verified: 2026-09-26 · Version: 1 · URL: https://konyxai.com/knowledge/faq#pricing · Related: capabilities.plan-limits, pilot.baseline, company.contact_

### Can Konyx find vendors we do not already use?

Yes. After the company's own vendors and the Konyx network have answered, Konyx searches the web for vendors who carry the part, reads their contact pages and shows them with reasons and a score. A found vendor is only emailed once a person picks it and checks the address.

_Source: konyx-api — core/discovery · Verified: 2026-09-26 · Version: 1 · URL: https://konyxai.com/knowledge/faq#find-new-vendors · Related: capabilities.vendor-discovery, control.discovered-vendors-reviewed_

### Who can issue a purchase order?

Anyone holding the po.issue permission, which a company grants through its own roles. Approval rules by amount or category are planned; until they ship, the issuer's permission is the control, and every order is on the log with who issued it.

_Source: konyx-api — po.issue · Verified: 2026-09-26 · Version: 1 · URL: https://konyxai.com/knowledge/faq#who-can-issue-a-po · Related: capabilities.purchase-orders, capabilities.approval-rules_

### What is the Konyx network?

Vendors and catalogs that Konyx maintains and suggests beneath a company's own vendors, only when a catalog line matches the request. They are Konyx's data, not another customer's; choosing one copies it into the company's own list.

_Source: konyx-api — platform vendors · Verified: 2026-09-26 · Version: 1 · URL: https://konyxai.com/knowledge/faq#konyx-network · Related: capabilities.konyx-network_

### Is Konyx a marketplace?

No. Konyx is software the buying company uses. Vendors quote directly to the company through a link, the company issues its own purchase order, and Konyx does not stand between them.

_Source: konyxai.com — What Konyx does · Verified: 2026-09-26 · Version: 1 · URL: https://konyxai.com/knowledge/faq#marketplace · Related: company.how-konyx-differs_

### Is there an API or an integration with our systems?

Not yet. There is no public API and no ERP connector in the current version. Email (from Konyx or from the buyer's own mailbox) and spreadsheet import are the integrations today; sending through Microsoft 365 or Gmail by API is planned. The one public machine interface is this knowledge catalog.

_Source: Engineering Action Plan — §5 · Verified: 2026-09-26 · Version: 1 · URL: https://konyxai.com/knowledge/faq#api-and-integrations · Related: integrations.erp, integrations.api_

### What data do we need to give Konyx?

To start: a vendor list with contacts and their catalogs (one spreadsheet), the team (a five-column CSV) and, for the savings audit and last-paid prices, an export of purchasing history. Contracts, inventory and open orders are optional and come later.

_Source: konyx-erp — imports · Verified: 2026-09-26 · Version: 1 · URL: https://konyxai.com/knowledge/faq#what-data-do-we-provide · Related: capabilities.data-import, integrations.spreadsheets_

### What if the AI reads a request wrongly?

Nothing happens until a person confirms the draft. Every field shows whether it was confirmed, inferred or unknown, the person can change any of it or answer a question, and the buyer reviews every line again before an RFQ goes out. Where the extraction came from is stored with the request.

_Source: konyx-erp — Ask Konyx draft · Verified: 2026-09-26 · Version: 1 · URL: https://konyxai.com/knowledge/faq#wrong-extraction · Related: capabilities.ask-konyx, control.ai-provenance_

### Can we see who did what?

Yes. Every action is written to an append-only log in the same transaction as the change — who, what, when — and shown in plain sentences on the request, the person and the company. Actions taken by Konyx staff are written as done by Konyx.

_Source: konyx-api — activity log · Verified: 2026-09-26 · Version: 1 · URL: https://konyxai.com/knowledge/faq#audit-trail · Related: capabilities.activity-log, control.append-only-audit_

## Control, security and audit

How Konyx keeps a person in charge of every send, isolates each company, and records what happened.

### A person presses Send

AI reads and drafts; it never sends. Every RFQ and every purchase order waits for a named person who holds the permission to open it, review the exact email, acknowledge the review and press Send.

_Source: Engineering Action Plan — decision log, 15 Sep 2026 · Verified: 2026-09-26 · Version: 1 · URL: https://konyxai.com/knowledge/control#person-presses-send · Related: capabilities.rfq, capabilities.autonomous-purchasing_

### Permissions on every call

Drafting an RFQ and sending it are separate permissions, checked in the API on every request — not in the screen. An employee who cannot send escalates by design, not by convention; calling the endpoint directly is refused.

_Source: Engineering Action Plan — §3.1 · Verified: 2026-09-26 · Version: 1 · URL: https://konyxai.com/knowledge/control#permissions-on-every-call · Related: capabilities.roles-and-permissions, use-cases.employee-cannot-send_

### An audit trail that cannot drift

Every state change is written in the same transaction as the change itself, by the one function allowed to change a status, and the log is append-only at the database level. The trail cannot disagree with what happened because nothing else can write either.

_Source: Engineering Action Plan — §3.7 · Verified: 2026-09-26 · Version: 1 · URL: https://konyxai.com/knowledge/control#append-only-audit · Related: capabilities.activity-log, faq.audit-trail_

### Discovered vendors are reviewed

A vendor found on the web is never emailed until a person picks it and checks the address on the send screen. That one gate is the quality gate, the deliverability gate and the legal gate.

_Source: Engineering Action Plan — §3.4 · Verified: 2026-09-26 · Version: 1 · URL: https://konyxai.com/knowledge/control#discovered-vendors-reviewed · Related: capabilities.vendor-discovery_

### Each company is isolated in the database

Row-level security is forced on every tenant-scoped table and the application connects as a role that cannot bypass it. Two automated checks fail the build if a table lacks its policy or a query bypasses the scoped accessor, and a live test proves a cross-company read is refused. Konyx staff use the same permission wall, never a database console.

_Source: Engineering Action Plan — §3.1 · Verified: 2026-09-26 · Version: 1 · URL: https://konyxai.com/knowledge/control#tenant-isolation · Related: faq.data-isolation, control.architecture_

### Terms of Service and Privacy Policy

The Terms of Service and Privacy Policy are published at konyxai.com/terms and konyxai.com/privacy. Everyone signing in to the company app ticks a box agreeing to both, and the version each person agreed to, and when, is recorded against them and in the activity log.

The sign-in and activation forms refuse to go on without the box, and so does the API behind them. When the terms change, the next sign-in asks again.

Konyx does not sell personal information or use it for advertising. Google Analytics runs on the site and the company app only when switched on, with advertising features off; it receives page paths with record numbers blanked, counts and choices, and the person and company as internal codes — never names, emails or what anyone typed. It never runs on the vendor quote link, or when the browser sends Global Privacy Control.

- Terms of Service: https://konyxai.com/terms
- Privacy Policy: https://konyxai.com/privacy
- Recorded per person: terms version agreed to; when

_Source: konyxai.com — /terms and /privacy · Verified: 2026-10-01 · Version: 1 · URL: https://konyxai.com/knowledge/control#terms-and-privacy · Related: control.tenant-isolation, faq.hosting, faq.ai-models_

### No default accounts, anywhere

Companies and their owners are created only by Konyx staff from the console, which emails the owner a temporary password. Nothing can be signed into that a human did not deliberately create, and every credential has one auditable origin.

_Source: Engineering Action Plan — decision log, 15 Sep 2026 · Verified: 2026-09-26 · Version: 1 · URL: https://konyxai.com/knowledge/control#no-default-accounts · Related: control.architecture_

### The shape of the system

One backend owns the database, the sessions, the permissions, email and AI, and cannot be reached without a key the browser never holds. The web applications are database-free: the browser calls their own backend, which forwards to the API with that key and the person's session. Sessions live in an httpOnly cookie; the token never appears in a response body.

Every route that can be abused is rate-limited in the database, so every instance sees the same count: sign-in, activation, RFQ sending, AI requests, web vendor search, the vendor quote link, imports and the rest. State changes are refused unless the request came from the application's own origin. Security headers are set on every response; secrets live in a managed secret store, not in code.

_Source: Engineering Action Plan — decision log, 16 Sep 2026 · Verified: 2026-09-26 · Version: 1 · URL: https://konyxai.com/knowledge/control#architecture · Related: faq.hosting, control.tenant-isolation_

### Every model call is recorded

Each call to a model is recorded with who made it, which task and prompt version, and what it cost, and is shown per company and platform-wide. Each extracted field keeps its state, its evidence and the call that produced it, so the answer to why did it say that is always on file.

_Source: Engineering Action Plan — §3.8 · Verified: 2026-09-26 · Version: 1 · URL: https://konyxai.com/knowledge/control#ai-provenance · Related: how-it-works.what-the-ai-does, faq.ai-models_

## The pilot

How a company starts: one facility, ninety days, a baseline from its own purchasing history.

### One facility, ninety days

A pilot runs ninety days on one plant or business unit. It starts with a savings audit of the company's own purchasing history, brings in its vendors and team from spreadsheets, and ends with a decision made on measured adoption, accuracy, cycle time and savings.

These are process defaults, not customer results. The measurement plan is agreed with the company's team.

- Duration: 90 days
- Scope: one facility or business unit
- Baseline: the company's purchasing history, audited first
- Decision: validated savings and cycle time, reviewed together at day 90
- Your systems: the ERP stays the system of record

_Source: konyxai.com — Pilot · Verified: 2026-09-26 · Version: 1 · URL: https://konyxai.com/knowledge/pilot#shape · Related: pilot.baseline, pilot.adoption, pilot.decision_

### Baseline — before any contract

The company sends one purchasing export. Konyx computes the price gaps, cycle times and buyer hours from that file and writes the findings up, so the baseline is the company's own number, not Konyx's.

_Source: konyxai.com — Pilot · Verified: 2026-09-26 · Version: 1 · URL: https://konyxai.com/knowledge/pilot#baseline · Related: capabilities.savings-audit, proof.savings-audit-method_

### Adoption — real requests from week one

Vendors and catalogs come in from one spreadsheet, the team from another with invitation links, and people start with Ask Konyx on real requests. Roles are set by the company from the permission toggles.

_Source: konyxai.com — Pilot · Verified: 2026-09-26 · Version: 1 · URL: https://konyxai.com/knowledge/pilot#adoption · Related: capabilities.data-import, capabilities.roles-and-permissions_

### Decide with evidence at day 90

Adoption, extraction accuracy, cycle time and savings are measured in the product and reviewed together at day ninety. The company decides on its own figures.

_Source: konyxai.com — Pilot · Verified: 2026-09-26 · Version: 1 · URL: https://konyxai.com/knowledge/pilot#decision · Related: proof.customer-results_

### What Konyx needs from the company

An export of purchasing history for the audit; a vendor list with contacts and catalogs; a team list with who reports to whom; and one person who can decide roles. No ERP access and no installation.

_Source: konyx-erp — imports; konyx-admin — Audit · Verified: 2026-09-26 · Version: 1 · URL: https://konyxai.com/knowledge/pilot#what-we-need · Related: faq.what-data-do-we-provide_

## Integrations and data

What connects to Konyx today, what comes in by spreadsheet, and what is planned.

### Email (Live)

RFQs, purchase orders, invitations and notifications go out from Konyx's own sending domain, or an RFQ and an order can be sent from the buyer's own mailbox through their mail app. Vendor replies go to Konyx or to the team's own inbox, by company setting.

Vendor mail and account mail use two addresses on the same domain: RFQs and purchase orders come from an address of their own (rfq@ by default, shown as "the company via Konyx"), sign-in details and invitations from another, so a vendor's filter or reply never mixes with people's sign-in mail. Company Settings shows both.

- Konyx sends: RFQs with each vendor's link; purchase orders with the PDF; team invitations and credentials; a copy of an order to forward
- The buyer sends: RFQs and orders from their own mail app, recorded in Konyx

_Source: konyx-api — email; konyx-erp — send screen · Verified: 2026-10-01 · Version: 2 · URL: https://konyxai.com/knowledge/integrations#email · Related: capabilities.own-email-sending, capabilities.rfq_

### Spreadsheets and CSV (Live)

Vendors and catalogs, the team and purchasing history come in as CSV exports from whatever the company runs today, mapped on screen. A spreadsheet can also be dropped into Ask Konyx to become one request.

- Live today: vendors and catalogs, with contacts; team; purchasing history (for the audit and last-paid prices)
- Planned: inventory; open purchase orders; contracts and contract pricing

_Source: konyx-erp — imports · Verified: 2026-09-26 · Version: 1 · URL: https://konyxai.com/knowledge/integrations#spreadsheets · Related: capabilities.data-import, capabilities.savings-audit_

### ERP systems (Planned)

There are no live ERP connectors in the current version. The ERP stays the system of record; Konyx hands it a purchase order as a PDF and an email, and takes purchase history in by export. Connectors are on the list after the pilots, not before.

_Source: Engineering Action Plan — §5, explicitly not in v1 · Verified: 2026-09-26 · Version: 1 · URL: https://konyxai.com/knowledge/integrations#erp · Related: faq.replace-erp, faq.api-and-integrations_

### Microsoft 365 and Gmail (Planned)

Sending through the buyer's mailbox by API — so an RFQ appears in their Sent folder without the mail app — is planned. Today the same result is reached through the buyer's own mail app.

_Source: Engineering Action Plan — Next · Verified: 2026-09-26 · Version: 1 · URL: https://konyxai.com/knowledge/integrations#mailbox-connectors · Related: capabilities.mailbox-connectors, capabilities.own-email-sending_

### A public API and machine access (Planned)

There is no public product API. The one public machine interface today is this knowledge catalog: the same records served as JSON at /api/knowledge, as Markdown at /llms.txt and /llms-full.txt, and as pages under /knowledge.

- Knowledge, JSON: https://konyxai.com/api/knowledge
- Knowledge, Markdown: https://konyxai.com/llms-full.txt
- Index for assistants: https://konyxai.com/llms.txt

_Source: konyxai.com/knowledge · Verified: 2026-09-26 · Version: 1 · URL: https://konyxai.com/knowledge/integrations#api · Related: faq.api-and-integrations_

## Evidence

What Konyx can and cannot show yet, and how its claims are measured.

### Customer results

Konyx has no published customer results yet. The pilot defaults on the site are process defaults, not outcomes. Results from pilots will be published here with the customer's consent, with the measurement method beside them.

_Source: konyxai.com — Pilot · Verified: 2026-09-26 · Version: 1 · URL: https://konyxai.com/knowledge/proof#customer-results · Related: pilot.decision, proof.savings-audit-method_

### How savings are measured

Every figure in a savings audit is computed in code from the company's own file: the price gap against its own best price for the same item, against the Konyx network and, when linked to a company on the platform, its catalog; cycle time and late deliveries from dates; quote competition from vendor counts; rush and card spend from flags; buyer hours from the step count of the manual process against Konyx's two steps. The model writes the findings from those figures and cannot change them.

- Computed in code: price gaps; cycle time; late deliveries; quote competition; rush and card spend; buyer hours and calendar days
- Written by the model: the narrative of the findings, from the figures

_Source: konyx-api — core/savings-analysis.ts · Verified: 2026-09-26 · Version: 1 · URL: https://konyxai.com/knowledge/proof#savings-audit-method · Related: capabilities.savings-audit, pilot.baseline, capabilities.time-saved_

### How the product is verified

Each release runs type checks and lint in every app, a coverage check that every tenant table carries its isolation policy, a live test that a cross-company read is refused, unit and integration tests in the API, and an end-to-end run through the live servers as a signed-in user — admin creating a company, an owner importing a team, a request extracted by the live model, an RFQ sent, a vendor quoting twice, an order issued, isolation refused, and the test companies deleted.

- End-to-end checks: 297 in the current run
- Phone audit: 84 page states at two phone widths, zero pages wider than the screen

_Source: Engineering Action Plan — Build status · Verified: 2026-10-01 · Version: 2 · URL: https://konyxai.com/knowledge/proof#engineering-verification · Related: control.tenant-isolation, control.architecture_