Sales

Everything between a request and a confirmed order. RFQs come in from email and PDF, quotes and estimates are built from your catalog and costs, customer orders are confirmed against stock and terms, and pricing rules and approvals sit in between. One app, one record per deal, from the first request to the order.

  • Owns
  • RFQs
  • Quotes & estimates
  • Customer orders
  • Proposals
  • Price rules
  • Approvals

A few of the views inside Sales.

Inside the app

What lives in Sales.

One app owns the whole domain. These are the workflows, views, and features inside it, rather than a separate tool for each.

  • RFQ intake from email and PDF
  • Quotes and estimates from your catalog and costs
  • Customer orders, confirmed against stock and terms
  • Proposals and order confirmations on your templates
  • Price lists, terms, and discount rules
  • Approvals before anything goes out
  • Follow-ups on open quotes
AI inside the app

What your agent does in Sales.

  • Turns an RFQ email or PDF into a structured request, matched to the customer and products
  • Drafts the quote or estimate from your catalog, costs, and the customer's terms, on your template
  • Turns a PO email into a customer order and checks price, stock, and credit before you approve
  • Routes discounts and exceptions to the right approver and sends on approval
  • Chases open quotes and explains why a bid was lost when you ask

Every person gets their own agent; teams can share one. Sensitive actions wait for approval, and every action is logged with the data it used and the outcome.

Built with AI

Need it different? Describe it.

Add a field, a stage, a rule, a view, or a workflow inside this app. It's built on the same records and permissions, as open code you can change again.

Add a "sales" view for my team: only what's mine, due this week, with the agent's drafts on top.

See Sales on your data.

Book a demo and bring a real example. We'll show you the app on your data, with the agent doing the work.