A bounded AI sales workflow starts with one customer request and one controlled price list, pauses for human review, and produces a reviewed quote link. qraft demonstrates this narrow loop as a reusable FDE foundation.
This note is for salespeople, estimators, and operations teams who want to test one repeatable handoff without handing the customer relationship or commercial decision to an automated system.
Quick answer
A bounded AI sales workflow has a clear user, input, review point, output, and failure boundary. A salesperson supplies the request and price list, reviews the proposed line items, and decides whether the result is ready to become a quote link.
This article answers
- →What makes an AI sales workflow bounded?
- →Why start with one quote workflow?
- →What does the user review?
- →What happens when catalog data is missing?
- →Where does qraft fit?
Start with one user and one job
The user is a salesperson, estimator, or operations teammate who already receives quote requests. The job is not to automate every sales activity. It is to prepare one quote from a request and a known price list.
Keeping the boundary narrow makes the workflow understandable. The team can see what the system received, what it proposed, what the user changed, and what became the final output.
Define the input before adding AI
The input has two parts:
- the customer request, such as the required items, services, quantities, location, and timing
- the controlled source, such as a price list, catalog, service package list, or saved rate table
The source data is a boundary, not decoration. If a product or service is not in the source, the workflow should mark the gap for review instead of filling it with a confident guess.
Let AI prepare a draft, not a promise
AI is useful in the middle of the workflow. It can turn informal notes into a structured brief, find likely catalog matches, group line items, and prepare client-ready descriptions.
The output at this stage is a proposed draft. It is not a saved quote, a published quote link, or a message to the customer.
The user reviews:
- the selected products or services
- quantities and units
- scope, exclusions, and delivery details
- taxes, discounts, terms, and client information
- whether the request contains enough information to proceed
The human review is the control point. The user can correct the draft, ask for clarification, or stop the workflow.
Define the failure boundary
A useful workflow says what it cannot do. It should stop when the request is ambiguous, the catalog has no reliable match, the quantity is unclear, or the commercial details require judgment that is not represented in the source data.
The safe result of a failure is a clear exception for the user to resolve. It is not an invented SKU, an assumed quantity, or an unreviewed client message.
Produce one reviewed output
After review, the user can save the draft or prepare a client-facing quote link in the web workspace. The link is the visible output of the workflow. It gives the buyer one page to review while the team retains the full editing and approval context in the workspace.
The workflow can also leave a view signal for follow-up. That signal is context for the team, not a substitute for a direct conversation or a decision about what to send next.
qraft as a working FDE demonstration
qraft demonstrates this workflow as a working slice: request, controlled catalog input, prompt-assisted draft, human review, quote link, and follow-up context.
The implementation is also a foundation for forward-deployed engineering. A pilot team can bring one real handoff, map where the information is lost, and shape the working software around that operation. The reusable part is the discipline of bounded input, explicit review, measurable output, and visible failure handling.
Keep the web workspace in charge
The web app remains the full workspace for catalog data, client details, quote editing, final review, and team controls. A command layer can help start or revise work, but it should not become a second, unbounded system of record.
For teams that begin in WhatsApp, the WhatsApp command-layer note describes the same boundaries in a phone-first workflow.
A practical pilot slice
Choose one repeatable quote request. Bring the relevant source data into the workspace. Run the request through the draft step, review every proposed line, and record where the user had to correct or stop the workflow.
That review record tells the team what the next working slice should solve. It also keeps the pilot honest: the outcome is a reviewed operational handoff, not a claim that an AI system can own the whole sales process.
Frequently asked questions
What is a bounded AI sales workflow?
It is a narrow workflow with a known user, input, review point, output, and failure boundary. In this example, a salesperson starts with a customer request and controlled price list, reviews the proposed quote, and decides what happens next.
How can AI help with a quote?
AI can turn a rough request into a structured brief, suggest matches from known catalog data, and prepare draft descriptions. A salesperson still reviews the items, quantities, scope, and client details before saving or publishing anything.
What should a human review before a quote is sent?
The user should review the catalog matches, quantities, scope, taxes, discounts, terms, client details, and whether the result should remain a draft or become a client-facing quote link.
What happens when the workflow cannot find a reliable match?
The workflow should stop and ask for clarification or move the request to the web workspace for manual handling. It should not invent a product, quantity, or price.