Quote generation with AI
Turn price requests into quotes. With your prices.
An email, a PDF, an Excel list: feld.ai reads the request and prepares line items for matching with your products and terms. Together, we build your quoting workflow — through to sending after human approval.
Your price source, your template and clear approval rules. Setup and integration are scoped to your business.
From request to draft
Less Copying. More Time for the Right Quote.
Much of the work happens between the request and the ERP: identifying customers, matching items, understanding quantities and finding the right prices. We connect these steps into a traceable workflow.
- 01
Read the Request
Bring the email and attachments together. Extract items, quantities, specifications and requested dates into structured data.
- 02
Match Your Data
Identify customers and items. Apply prices and terms from the agreed source. Flag anything that remains unclear.
- 03
Prepare the Quote
Transfer line items into your template or a draft in your ERP. Your team reviews matches, prices and exceptions.
- 04
Approve and Send
Optionally prepare the reply with the quote and send it through the configured email workflow only after human approval.
What your workflow could look like
One Request. Three Items. Two Questions to Resolve.
Incoming price request
“Please send us a quote.”
Hello,
we need 40 seals, 6 mm, 2 boxes of M8 screws and a replacement valve like the one in our last
order.
Please see the attached specification and include delivery to Linz.
Prepared quote draft
Review needed40 × seal, 6 mm
€3.20 / piece · €128.00 net
Source: current customer price list · Item D-006
2 boxes of M8 screws
How many pieces are in one box?
Source: email · Pack size missing
1 replacement valve
Which variant was requested?
Source: email · Previous order reference unresolved
Illustrative example with fictional data, not a product screenshot. The quote draft and review rules are configured for your workflow.
ERP, master data & price lists
Your Systems Supply the Authoritative Data.
Item numbers, customer terms and valid prices stay in the source you choose. feld.ai can match extracted line items against supplied reference data. For the complete quoting workflow, we connect this matching step with your pricing rules and ERP.
A pilot can start with a CSV export from Excel. For SAP, Microsoft Dynamics or another ERP, we assess interfaces, version and permissions: which data can be read, how a draft quote can be created and who may approve it.
Previous quotes help put a request in context. The quote price comes from the agreed, current price source. Setup, pricing rules and writing back to the ERP are part of the integration project.
Explore the platformYour data source
ERP or Approved Price List
Customers · Items · Prices · Terms
Matching in feld.ai
Line Items with Sources and Open Questions
Match · Review · Prepare the quote draft
Agreed handover
Reviewed Draft in Your Target System
Format, status and approval follow your process
Email with human-in-the-loop approval
The Reply Is Ready. You Decide When to Send.
We can optionally connect your sales mailbox to the workflow. The request, attachments, quote draft and reply then belong to the same case. Sending after human approval is configured as a separate step.
Example after all items are clarified
Draft- From
- Your authorised sales mailbox
- To
- purchasing@example-customer.example
- Subject
- Your quote for seals, screws and a replacement valve
Hello,
thank you for the additional details. Please find our quote attached, including the agreed
items and terms.
We are happy to help with any questions.
Awaiting approval
What Approval Should Cover
- The correct recipients, including CC.
- The exact message and the complete set of attachments.
- The reviewed quote version with its prices and terms.
- A new approval whenever content, recipients or attachments change.
Only the approved version may leave through the configured sending workflow. Transfers and sending must be traceable; failures remain open for review.
You can also stop at the draft and send it yourself. Mailbox access, sending permissions and approval logic are configured and tested separately as part of the project.
The details of everyday work
Small Ambiguities Need a Clear Process, Too.
Different Item Descriptions
Customer descriptions do not always match internal item numbers. Ambiguous matches remain open for selection, with the source in the request available to support the decision.
Pieces, Boxes or Metres?
Quantities, units and pack sizes are captured separately. Conversions need confirmed master data or an agreed rule.
Customer Prices and Discounts
Which price list applies? Which quantity break or framework agreement? We define the price source, validity and approval thresholds in advance.
Delivery Dates and Alternatives
Availability is only confirmed when a suitable data source is connected. Substitute items and different delivery dates need an explicit decision.
Changes and New Versions
A changed quantity or a new attachment can change the quote. In the configured workflow, every approval belongs to one specific version.
Freight, Tax and Currency
Shipping costs, currency, tax and payment terms must come from agreed rules or the target system. Missing information remains visible.
Start with real requests
A Focused Pilot for Your Sales Team.
We choose a specific type of request and agree what a good result looks like: the correct items, supported prices, all unresolved questions identified and a draft your team can review.
Then we test with your examples. This shows which steps can be automated and where your team needs to make a decision.
Discuss a pilotUseful Starting Materials
- Typical requests with their attachments
- Current item and customer pricing data
- A quote template and your approval rules
- Contacts for sales, ERP and email
Setup, customisation and integration are scoped separately. See pricing
Good to know
Frequently Asked Questions
Which price requests can feld.ai process?
feld.ai can extract content from PDF, Word and Excel documents, as well as EML and MSG files including attachments, into an agreed data schema. During the pilot, we test your actual requests, item descriptions and required fields. Ongoing ingestion from a mailbox is connected separately.
Where do items and prices come from? Can we start with Excel?
Yes. For an initial pilot, you can provide item and customer data from Excel as CSV. For the subsequent workflow, we agree on the authoritative price source, such as a current customer price list or your ERP. Previous quotes can provide context; they do not replace valid prices and terms. Discounts, quantity breaks and validity periods are handled through specific rules.
Can you connect our ERP, such as SAP or Microsoft Dynamics?
Connecting an ERP is an integration project. Together with your team, we assess the system, version, available interfaces and permissions. We agree which customer, item and pricing data will be read and whether the result can be written back as a draft quote. We do not assume a ready-made connector for every ERP.
Can requests come directly from Microsoft 365 or Google Workspace?
The intended mailbox, such as a shared sales inbox, is assessed and connected as part of the project. For Microsoft 365 or Google Workspace, we work with your IT team to define access, folders, attachments and how messages relate to a case. You can also start with file uploads. Reading email and permission to send are configured separately.
Can the quote email require human approval before sending?
Yes, we can configure this workflow as part of your project. Your team reviews recipients, message, quote version and attachments. Only that exact approved version may be sent; any change requires a new approval. Alternatively, automation can stop at the draft and your team sends it manually. The configured sending workflow must be tested before going live.
What happens if a price is missing, an item is unclear or sending fails?
Missing or unclear information is presented with its source and the reason for review. A missing price is not replaced with an estimate. Depending on the agreed workflow, a clarification request is drafted or the case is assigned for review. A failed ERP transfer or email remains open and must be resolved before the case is marked complete.
What do we need for a pilot, and what will be agreed?
We start with representative requests, a current item and price source, and your quote template. Together, we define required fields, approval rules and measurable acceptance criteria. Setup, customisation and integration are scoped and quoted separately. The scope depends on data quality, pricing rules and target systems.