Konyx

Product capabilities

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

24 records · checked 27 October 2026 · this domain as JSON · whole catalog as Markdown

  1. Ask Konyx — request intake
  2. Matching against the company's own catalog
  3. Purchase history beside every line
  4. Vendors ranked with reasons
  5. The Konyx network
  6. Konyxions — vendors found on the open web
  7. One RFQ to all the vendors
  8. Sending from the buyer's own email
  9. The vendor's quote link
  10. Quotes side by side
  11. Routing, escalation, notes and notifications
  12. Roles and permissions
  13. The activity log
  14. The savings audit
  15. Time saved, RFQ by RFQ
  16. Bringing vendors, catalogs and people in
  17. Plan limits per company
  18. Buying a plan online
  19. Approval rules and the simulator
  20. Vendor replies by email, on the RFQ
  21. Quotes read out of an email
  22. Sending through Microsoft 365 or Gmail
  23. A native mobile app
  24. Autonomous purchasing

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.

On the Search plan, Ask Konyx stops at the vendors. It reads the request the same way — typed, spoken, a photo or a spreadsheet — and finds the company's own vendors, the Konyx network and Konyxions, ranked with reasons, each with its contact details and a link to the matching product where one was found, so the buyer contacts them directly. It creates no request or RFQ and sends nothing. Each new request asked counts as one of the plan's searches; moving to Starter or above adds RFQ drafts.

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

Related: Matching against the company's own catalog · Vendors ranked with reasons · Step 1 — Ask · The technician does not know the part number · Plan limits per company

Source: konyx-erp — the Ask Konyx screen; prompt request-extract v4 · Checked 27 October 2026 · Version 2 · capabilities.ask-konyx

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 in front of a vendor 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

Related: Purchase history beside every line · Vendors ranked with reasons · Which AI models does Konyx use, and what sees our data?

Source: konyx-api — core/item-match.ts · Checked 26 October 2026 · Version 3 · capabilities.catalog-matching

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

Related: Quotes side by side · What did we pay last time? · Spreadsheets and CSV

Source: konyx-api — core/purchase-context.ts · Checked 26 September 2026 · Version 1 · capabilities.bought-before

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 Konyxions — vendors Konyx 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.

Konyx network vendors and Konyxions are also ordered by where they are: when two cover the same lines, the one based in the buyer's country comes first. The buyer's country is the country of the requester's site, when their site in Konyx has one; otherwise the company's country; otherwise the country the request is being made from. It breaks a tie and never hides anyone: a vendor abroad that matches better still ranks above.

Order
  • the company's own vendors
  • the Konyx network
  • Konyxions — vendors Konyx found on the web
Reasons
  • lines covered
  • exact part numbers
  • lowest price on a line
  • volume pricing
  • contactable
  • near the buyer — based in the buyer's country (Konyx network and Konyxions)

Related: The Konyx network · Konyxions — vendors found on the open web · One RFQ to all the vendors

Source: konyx-api — core/vendor-rank.ts · Checked 26 October 2026 · Version 3 · capabilities.vendor-ranking

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.

A network or Konyxion product is found by its words, then checked once by a small model call — is it the item asked for, a close variant, or something else that merely shares a word — before the vendor is said to carry it. A close variant is labelled as one; anything else is not shown. The answer is kept, so the same question is never paid for twice.

Related: Vendors ranked with reasons · What is the Konyx network?

Source: konyx-api — platform vendors and catalogs · Checked 9 October 2026 · Version 2 · capabilities.konyx-network

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 them as Konyxions — with contacts, reasons and a link to the matching product on the vendor's own site, so the buyer can open it and check it is the right item. Konyxions are looked for worldwide, starting near the buyer. Nothing is emailed until a person picks the vendor and checks the address.

The search for Konyxions is not limited to one country. Each one is pointed at the buyer's country — the country of the requester's site, when their site in Konyx has one; otherwise the company's country, set in Settings, filled in from the billing address when a company signs up online, and settable by Konyx staff; otherwise the country the request is being made from, taken from the connection. Results are localised to that country, so nearby vendors come up first, and vendors elsewhere still appear.

A Konyxion based in that country gets a small boost and its card says it is near. It is a tie-breaker, not a filter: a vendor abroad that matches better still ranks above.

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 links to that product page, and that vendor's RFQ carries their number.

Konyxions 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, maker and a link to it
  • an explainable confidence score
  • their catalog, crawled in the background
Where
worldwide, localised to the buyer's country so nearby vendors come up first
Buyer's country, in order
  • the requester's site, when it has a country
  • the company's country (Settings; from the billing address at online sign-up; or set by Konyx staff)
  • the country the request is made from, taken from the connection
Never does
  • email a Konyxion automatically
  • scrape a search engine directly
  • leave out a vendor for being abroad

Related: Konyxions are reviewed · A rush part with no known supplier

Source: konyx-api — core/discovery · Checked 26 October 2026 · Version 4 · capabilities.vendor-discovery

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. A vendor's emailed reply always reaches a person: it comes back onto the RFQ where Konyx's reply address is switched on, and otherwise goes to the team's own inbox or to whoever sent the RFQ — by company setting, and never to an address nobody reads. An RFQ that bounces shows on the vendor's row with the reason, and Send retries only that vendor once the address is fixed. 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.

A company can set a standard opening paragraph in Settings, so every RFQ it sends starts with the same words; one RFQ can still be reworded before it goes. The reply-by date is never lost: when the opening does not state it, it follows as a sentence of its own.

Every RFQ — the email and the vendor's quote page — carries Konyx's referral code, KONYX, in a box beside the logo, so a supplier can tell the request came through Konyx.

Drafting RFQs comes with Starter and up; sending them comes with Growth and up. On Starter the draft and its email can be read and changed, but nothing goes out to a vendor and no quote link is handed out. The Search plan has no RFQs: Ask Konyx finds the vendors, with their contact details, and the buyer contacts them directly.

Plans
  • drafting: Starter, Growth, Professional, Enterprise
  • sending: Growth, Professional, Enterprise
  • Search: no RFQs — vendor search only
Send from
  • Konyx
  • the buyer's own mailbox, via their mail app
Opening
  • the RFQ's own words
  • the company's standard paragraph
  • Konyx's wording
Referral code
KONYX, beside the logo on every RFQ
Replies to
  • the RFQ in Konyx, with a copy to the buyer
  • the team's own inbox
  • the person who sent it
Permission
rfq.send, separate from rfq.create

Related: Sending from the buyer's own email · The vendor's quote link · Vendor replies by email, on the RFQ · A person presses Send · The same gasket has a different number at every supplier

Source: konyx-erp — RFQ page and send screen · Checked 27 October 2026 · Version 6 · capabilities.rfq

An RFQ 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.

It is a way of sending, so it comes with the plans that send RFQs: Growth and up.

Related: One RFQ to all the vendors · Email · Vendors must hear from the plant's own domain

Source: konyx-erp — send screen, mailto mode · Checked 26 October 2026 · Version 3 · capabilities.own-email-sending

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.

Related: Quotes side by side · Do our vendors need an account?

Source: konyx-erp — portal pages; konyx-api — portal · Checked 26 September 2026 · Version 1 · capabilities.vendor-quote-portal

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

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.

Related: Purchase history beside every line · The vendor's quote link · Step 4 — Compare and choose

Source: konyx-erp — quote comparison grid · Checked 26 October 2026 · Version 2 · capabilities.quote-comparison

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.

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

Related: Roles and permissions · An employee who may raise a request but not send an RFQ · Where is my request?

Source: konyx-api — core/request-state.ts, core/approver.ts, core/notify.ts · Checked 26 October 2026 · Version 2 · capabilities.request-routing

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 and sending it 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
  • vendor.discover
  • request.assign

Related: Permissions on every call · Routing, escalation, notes and notifications

Source: konyx-api — authz; 26 permissions · Checked 26 October 2026 · Version 2 · capabilities.roles-and-permissions

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.

Related: An audit trail that cannot drift

Source: konyx-api — core/audit.ts · Checked 26 September 2026 · Version 1 · capabilities.activity-log

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 past purchases, a row per purchase or per line, 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

Related: Baseline — before any contract · How savings are measured

Source: konyx-admin — Audit page; konyx-api — core/savings-analysis.ts · Checked 26 October 2026 · Version 2 · capabilities.savings-audit

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

Related: How savings are measured · One RFQ to all the vendors · Customer results

Source: konyx-api — core/time-saved.ts; konyx-erp — Time saved page; konyx-admin — Time saved · Checked 1 October 2026 · Version 1 · capabilities.time-saved

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.

Uploading the company's own vendor file — its own vendor database — comes with Professional and Enterprise. On Search, Starter and Growth, vendors are added one at a time, and come from the Konyx network and Konyxions; an earlier upload can still be undone.

Vendor file plans
Professional, Enterprise
Vendor file
one CSV: vendor, contacts, item, part number, price ladder
Team file
ID, Name, Email, Role, Manager
Purchase history
any export of past purchases, mapped on screen — used by the savings audit and for last-paid prices
Planned
  • inventory
  • open orders from the company's ERP
  • contracts

Related: Spreadsheets and CSV · Adoption — real requests from week one

Source: konyx-erp — vendor import, team import · Checked 27 October 2026 · Version 4 · capabilities.data-import

Each company has limits: how many RFQs it may create in a month, or on the Search plan how many searches it may make (a plan bought online counts by billing month, from the day the plan renews; a company Konyx sets up counts by calendar month), how many items one RFQ may carry, how many people may hold an account, and what it can do beyond searching for vendors: draft RFQs, send them, and upload its own vendor database. A plan bought online sets the RFQs per month, or the searches per month on Search — counted for the whole company, whoever creates or asks them — and what the company can do, and has no per-person pricing. They are enforced in the API and shown to the company under Settings → Plan and billing.

On the Search plan the count is of searches, not RFQs. One new request asked of Ask Konyx counts once, for the whole company, whoever asks; the answers to Konyx's follow-up questions on that request, and its Konyxions, are part of the same search. The count runs per billing month and starts again when the plan renews. When the 25 are used, Ask Konyx says so and a super user can move to a bigger plan under Settings → Plan and billing. Only Search counts searches: the other plans count RFQs and do not limit searches.

A company whose plan has ended keeps everything it has in Konyx, but no new RFQ can be created or sent — and on Search, Ask Konyx can't search for vendors — until a plan is chosen again. A failed payment changes nothing for seven days while Stripe retries the card; after that, or as soon as Stripe stops trying, the plan ends. A payment disputed with the bank, or reported as possibly unauthorised, stops the plan at once until Konyx lifts the hold. Each of these is emailed to the company's super users.

Plans bought online
  • Search: 25 searches per month — vendor search only: no RFQs drafted or sent — no free trial
  • Starter: 25 RFQs per month — vendor search and RFQ drafts — the first 14 days free for a company that signs up online
  • Growth: 50 RFQs per month — adds RFQ sending
  • Professional: 250 RFQs per month — adds the company's own vendor database
A search
one new request asked of Ask Konyx, counted once for the whole company; its follow-up answers and Konyxions are part of it; counted on Search only
Items per RFQ
30
People
no per-person limit on a plan bought online
Companies Konyx sets up
limits and switches for RFQ sending and the vendor upload set from the console (defaults: 5 people, 250 RFQs per month, 30 items per RFQ, both on); every change is written to the company's log

Related: What does Konyx cost? · Buying a plan online

Source: konyx-api — core/limits.ts, billing/plans.ts · Checked 27 October 2026 · Version 5 · capabilities.plan-limits

A company can start on its own: choose a plan on konyxai.com — Search, Starter, Growth or Professional — enter a name, work email, company name and password, confirm the email with a six-digit code, and enter a card on Stripe's page. Starter starts with 14 days free; Search, Growth and Professional are charged straight away. The company is created as soon as Stripe's page is completed, with that person as its super user, signed straight in.

Card details are entered on Stripe's own page and never reach Konyx. A super user changes plan from Settings → Plan and billing (the difference is settled on the next invoice) — a company on Search moves to Starter or above there to add RFQ drafts — and updates the card, downloads invoices or cancels on Stripe's billing page, reached from the same place; a cancelled plan runs to the end of the month paid for. The company's country is filled in from the billing address entered there and can be changed in Settings.

Starter's free trial: the card is entered on Stripe's payment page at sign-up and nothing is charged during the first 14 days. On day 15 Starter is charged at $99 a month, unless the plan was cancelled before then — Settings → Plan and billing → Card and invoices opens Stripe's billing page, where it can be ended. Moving up to Growth or Professional during the trial ends it, and that plan is charged straight away. Search, Growth and Professional have no trial, and a company whose plan ended and that chooses a plan again does not get another one.

An email address that already has a Konyx account cannot start a second company; the person is told by email, and the sign-up page says the same thing to everyone. Enterprise plans are arranged with Konyx and set up from the console.

Plans
  • Search: $29 a month — 25 searches per month
  • Starter: $99 a month — 25 RFQs per month
  • Growth: $249 a month — 50 RFQs per month
  • Professional: $499 a month — 250 RFQs per month
  • Enterprise: arranged with Konyx
Steps
  • choose a plan
  • name, work email, company, password
  • six-digit email code
  • card on Stripe's page — charged now, or on day 15 for Starter
  • company created, signed in as super user
Free trial
Starter only: 14 days, nothing charged, then $99 a month unless cancelled before day 15; once per company
Payment
monthly, by card, through Stripe
Change or cancel
Settings → Plan and billing

Related: What does Konyx cost? · Plan limits per company

Source: konyx-api — billing; konyx-erp — /signup · Checked 27 October 2026 · Version 3 · capabilities.online-signup

Approval rules that route a purchase or an RFQ for approval by amount, category or exception, with a simulator that shows who would approve a given one before the rule goes live. Not shipped yet; today the control is the permissions a company gives its roles, such as who may send an RFQ.

Related: Roles and permissions · A person presses Send

Source: Engineering Action Plan — §3.7, Next · Checked 26 October 2026 · Version 2 · capabilities.approval-rules

When a vendor answers an RFQ by email instead of using the quote link, the message appears on that RFQ exactly as they wrote it — their words, the address it really came from, their files, and the original to download — and a copy goes to the buyer's inbox. Where an installation has not switched Konyx's reply address on, the reply goes to the team's inbox or the sender instead.

Each vendor on an RFQ gets a reply address of their own, so a reply is matched to the right RFQ and vendor even when a colleague answers from a different address. The page says whether the sender is the address on file, someone at the same company, or unknown, and whether the sending mail server passed the usual checks; an unknown or unverified sender carries a plain warning before anything is acted on.

The message is shown as plain text, in full, never as a summary. A model may add one label from a fixed list — looks like a quote, a decline, a question, asks for a call — as a hint beside the message; it cannot write text onto the page or change a price, a status or anything else. Out-of-office and automatic replies are recognised from the mail's own headers.

A reply's prices are not read into the quote comparison: quotes are compared when a vendor fills in their quote link.

Kept from each reply
  • the text exactly as written
  • files up to 10 MB each
  • the original message
Not kept
  • programs, scripts, web pages and macro files
The buyer is told
  • on the RFQ
  • in the app's notifications
  • by email, with a reply that goes straight to the vendor

Related: One RFQ to all the vendors · The vendor's quote link · Email from outside is treated as untrusted · Email

Source: konyx-api — core/inbound-mail.ts, email/inbound.ts; konyx-erp — RFQ page, Replies by email · Checked 2 October 2026 · Version 1 · capabilities.email-replies

Reading the prices out of a vendor's emailed PDF or spreadsheet into the quote comparison, as a fallback to the quote link. Not shipped: an emailed reply is shown on the RFQ as written, but its prices are not extracted; quotes are compared when they come back through the link.

Related: Vendor replies by email, on the RFQ · The vendor's quote link · Email

Source: Engineering Action Plan — §3.6 · Checked 2 October 2026 · Version 2 · capabilities.email-quote-capture

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.

Related: Ask Konyx — request intake · Does it work on a phone?

Source: Engineering Action Plan — Scope decisions · Checked 26 September 2026 · Version 1 · capabilities.native-mobile-app

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

Related: A person presses Send · Principles Konyx is built on

Source: Engineering Action Plan — §3.7, decision log · Checked 26 October 2026 · Version 2 · capabilities.autonomous-purchasing