Skip to content
GullySales

Industrial product configurator and RFQ experience design · Marketing

Let a buyer choose the right variant and send a quotation request your team can price.

A buyer of pumps, panels or packaging machines does not want a brochure. The buyer wants to know whether your model fits a duty, a voltage, a material or a pack size, and then to ask for a price. If the site cannot answer the first question, the second never gets sent.

Scope, fee, reporting and term are agreed in writing after we have read your brief and spoken to you.

Colleagues review equipment options and pricing with a product catalogue

In one paragraph

Product configurator and RFQ experience design is the plan for how a buyer selects a product variant on your website and asks for a quotation. GullySales designs the selection logic, the specification fields, the request form and the route into your sales team, then tests the whole path with real requests.

The same buyer, once convinced, fills a form that asks only for a name and a message. Your estimator then calls back to ask for the flow rate, the quantity and the delivery site. Each missing detail adds a round of calls before anyone can price anything.

GullySales designs both halves: how a buyer narrows a range to a variant, and what the request must carry so your team can quote without chasing. Building the site is website design and development. Custom configurator software and price-calculation engines are scoped separately, and the design here is the brief they would need.

Who it is for

This is written for you if these sound familiar.

  • Manufacturers selling a range with variants in size, rating, material or finish, where buyers cannot tell which model fits
  • Distributors and dealers who quote from a catalogue and field the same specification questions every day
  • Makers of made-to-order goods, such as panels, furniture or fabricated parts, whose quotations depend on drawings and dimensions
  • Equipment suppliers whose estimators lose time because requests arrive without the details a quotation needs
  • Software and service firms with tiered products whose sales team answers the same fit questions before every proposal

Before you decide

When this may not be the right fit.

  • You need the website itself built or replaced. That is website design and development; this work plans one part of it.
  • You want a working configurator with live pricing and drawings generated. Custom software development is scoped separately, and GullySales supplies the design it would be built from.
  • You sell a few fixed products with a published price and a cart. Online ordering belongs under e-commerce website development.

The problem

Does this sound like your business?

Common situations this work addresses.

  • “Buyers cannot tell which model fits”

    The catalogue lists every variant in one table of codes. A buyer who does not know your naming scheme leaves, or asks for the wrong model and loses a round of correspondence.

  • “Every request needs three calls before we can quote”

    The form collects a name and a message, so the estimator asks for quantity, duty, site and deadline by phone. The buyer waits, and a competitor with a clearer form replies first.

  • “The configurator offers combinations we cannot build”

    A choice made in one field contradicts another, or the options reflect an old range. Your team then has to tell the buyer that the selection cannot be supplied.

  • “Requests land in the wrong inbox”

    A request for a custom variant goes to the general address and waits. Nobody owns the request, so nobody replies, and the buyer assumes the enquiry was ignored.

Choose the right scope

Start with the work your business needs.

  1. A large range with confusing model codes

    Your catalogue has dozens of variants and buyers cannot read the codes. The work turns the range into a short run of questions about the application, ending in two or three suitable models with a plain statement of why each fits.

  2. Quotations delayed by missing details

    Your estimator spends the first day of each request asking for basics. The field list moves those questions into the form, with units, examples and an upload for a drawing, so the request arrives ready to price.

  3. Made-to-order work with a long specification

    A panel, fabrication or furniture order depends on dimensions, finish and a site. We design a staged request that gathers the essentials first and invites the drawing second, so a buyer is not defeated by a long form.

  4. Distributors asking the same fit questions

    Dealers phone your team for compatibility answers that your engineers already know. A selection path with rules your product lead has approved answers them on the page and sends the unresolved ones to the right person.

  5. Requests that vanish after submission

    Forms send mail to an address nobody watches. The routing table names an owner for each type of request, and the live test confirms that each type reaches that owner.

What we do

The work we can include.

Each deliverable and the purpose it serves. Your written scope confirms what is included, who is responsible, and what it costs.

  1. Product range and variant map

    A sheet that lists every product family, the options within it and the rules between them: which size takes which motor, which material excludes which finish. Your product or engineering lead checks every rule, because only your team knows what can be built.

  2. Selection logic and question order

    The sequence of questions a buyer answers to reach a variant, written as a flow from the buyer's first known fact, such as the application or the duty, to a short list of models. We test the order with the questions your salespeople are asked.

  3. Specification field list

    Each field the request carries, with its unit, whether it is required, the permitted values and the reason your estimator needs it. Fields your team never uses are removed, so the form asks no more than the quotation needs.

  4. RFQ form and confirmation design

    The layout, wording, error messages and confirmation screen for the request, with a route for an attached drawing or specification sheet. The confirmation says what happens next in the buyer's terms and states no promised reply time.

  5. Routing and ownership rules

    A written rule for where each type of request lands: standard variant, custom variant, spares, a distributor query. Each rule names the person or inbox that owns the reply, and you confirm those names before anything is built.

  6. Content for each selection step

    The short explanations that sit beside each choice, such as what a rating means and when to pick the larger option. Your engineers approve the technical statements; GullySales writes them in plain words.

  7. Wireframes and a written build brief

    Screen layouts for phone and desktop, with the logic, fields and routing attached, ready for your developer or a software vendor. A separate build quotation covers the code.

  8. Tracking plan and test record

    The events that record a started selection, a completed selection and a submitted request, named so they work with your analytics. The test record shows real requests passing through to the owner's inbox.

How the result is measured

  • Selections started and completed, shown separately from requests submitted
  • Requests received with every required field complete
  • Requests the estimator could price without a further call
  • Requests routed to the named owner, against requests found in a general inbox
  • Quotations issued and orders confirmed in your own records
  • Requests a buyer abandoned at a particular question

Recorded as a baseline before work starts, so every later report has an honest comparison.

Marketing and sales together

Your estimator receives a request that can be priced on the first read.

The handoff is the field list, the routing table and a quotation request that arrives with the model, the quantity, the application and the site. Your estimator records whether the request was complete, whether a quotation was issued and whether an order followed. A started selection is website activity only. It becomes a sales record when your team confirms the enquiry in its own register.

Decisions to make before the work starts

  1. Rules come from your engineers

    GullySales structures the logic but does not decide what your products can be built to do. Every compatibility rule is approved by your product lead. A rule that is wrong in the design will be wrong in the finished tool.

  2. Build, hosting and pricing engines

    Writing the working configurator, connecting it to stock or price data, and generating drawings are software development and are quoted separately. The design stands on its own and can be built by any competent developer.

  3. Quotations stay with your team

    GullySales designs the request and its route, but the price, the terms and the commitment in each quotation are decided and signed by your people. Privacy wording for the form comes from your own adviser.

  4. Limits of what the tracking shows

    Tracking records selections and submissions that the website can observe. It cannot see an abandoned phone call or a conversation held elsewhere, and it does not prove which step caused a buyer to decide.

This or a nearby service

Which piece of work fits your situation.

These services sit close to each other. The line between them, in plain words.

Quotation management
Choose quotation management when requests already reach you and the trouble lies in how quotations are built, approved, numbered and revised. Choose product configurator and RFQ experience design when buyers cannot pick the right variant on the website or send a request your team can price.
Form and enquiry funnel optimisation
Choose form and enquiry funnel optimisation when a form exists and enquiries drop out or arrive broken between the click and your inbox. Choose product configurator and RFQ experience design when the form is the wrong shape, because a buyer must specify a variant before anyone can price it.
CPQ consulting
Choose CPQ consulting when your team needs rules for which options can be sold together, what each combination costs and who approves an exception. Choose product configurator and RFQ experience design when the open question is how a buyer selects a variant and asks for a quotation on your website.

A sample of the output

A selection step sheet shows each question a buyer answers and what it decides.

This sheet follows a pump dealer's configurator. Each row is one screen: the question put to the buyer, what the answer narrows down, and what happens when the buyer cannot answer. Read each row left to right.

Illustrative example, not client data. Yours is built from your own records.
StepQuestion askedWhat the answer decidesIf the buyer is unsure
ApplicationWhat will the pump move?Which pump family appears on the shortlistOffer a short description box and flag for review
Liquid typeIs the liquid clean water, sludge or a chemical?Material of the parts that touch the liquidRoute the request to a sales engineer
Flow and liftWhat flow and lift does the job need?Which models stay on the listAccept a range and mark it as approximate
Power supplyWhich electrical supply is on the site?Motor options that are offeredAsk for a photo of the existing nameplate
Site and quantityHow many units are needed, and where do they go?Which branch or dealer owns the requestSend to the head office queue

Before we start

What we need from you.

The work depends on these. Each says why it is needed and what happens when it is missing.

A list of products and variants
The selection logic is built from your real range, so the list must name each product family, model code and the options that change the specification. A rough spreadsheet is acceptable. Without it the questions are guesses and design stops at the first review.
Recent quotation requests you received
Real requests show which details buyers forget and which questions your team asks twice. Share messages, forms or call notes, with customer names removed if you prefer. Without them the field list reflects opinion rather than what buyers actually send.
A named owner for incoming requests
The route into your sales team needs a person or queue that receives each request, plus cover when that person is away. A role is enough. Without an owner the form is designed but requests still sit unanswered.
Access to the current form and mailbox
Testing the whole path needs view access to the present form, its notification settings and the inbox or CRM where requests land. Without it the live test cannot be run and the routing stays unproven.
Examples of requests nobody could price
A few requests that stalled for missing details show where questions must be strict. Include one made-to-order case. Without them the design is tuned to easy requests and fails on the awkward ones.

How it works

How the work runs

The work itself, in order. How an engagement starts, from your brief to a written scope, is set out on our method page.

  1. 1

    Scope and range review

    You send the requirements brief, then we discuss your range and how quotations are prepared today. GullySales puts the scope, fee and term in writing before work starts, including what you will supply: catalogues, price logic and sample past requests.

  2. 2

    Request audit

    We read a set of real requests and the replies that followed. This shows which details the estimator always has to ask for and which questions buyers keep getting wrong.

  3. 3

    Logic and field approval

    We draft the variant map, the question order and the field list. Your product lead approves every rule and your estimator approves every field before any screen is drawn.

  4. 4

    Screen and routing design

    Wireframes show the selection steps, the form and the confirmation on a phone and a desktop. You approve the layout and the routing table, including who receives each type of request.

  5. 5

    Walk-through with your team

    Your salespeople and estimator work through the design with real past enquiries. Every request that cannot be completed, or cannot be priced from the fields, is corrected before the brief is finalised.

  6. 6

    Handover and live test

    You receive the build brief, content and tracking plan. Once your developer has built it, we test live requests end to end and record what reached the owner. Any code changes remain with the builder.

Before you hire anyone

Do this first yourself.

Look at ten recent quotation requests and the replies your team sent before changing anything.

  1. List every detail your estimator had to ask for that the request did not carry.
  2. Note which requests were for a model you do not make or a combination you cannot build.
  3. Write down who receives a website request today and who replies to it.
  4. Submit a test request yourself and time how long it takes to reach a person who can answer.
  5. Ask two salespeople which fit question buyers ask most and write their answers down.

Judge any provider

What to ask any provider of this service.

Useful whoever you choose, including us.

  • Who approves the compatibility rules, and what happens if a rule is wrong?
  • Will I own the variant map, field list and routing table as documents?
  • Where does the design end and the software build begin, and who quotes the build?
  • How will you test the design against our real past requests?
  • What will you not promise about enquiries or orders?

Where this fits

Three pieces of sales work, in this order.

This work sits inside sales process design, at stage 1, prospecting and lead generation. The audit comes before it, and sales management keeps it running.

  1. Step 1

    Sales audit

    Find where deals are being lost and what to fix first.

    Start here if you cannot say where orders are lost.

  2. Step 2 · you are here

    Sales process design

    One written way to sell, from first enquiry to repeat order.

    Start here if every salesperson sells differently.

  3. Step 3

    Sales management

    A target, a review routine and someone who owns the number.

    Start here if the team has targets and no routine.

Tell us what you need Your brief is read before we call. Scope, fee and term in writing.

FAQ

Questions owners ask before they call.

Not here? More answers, or ask on WhatsApp.

Is this a software product you install on our site?
No. GullySales designs the logic, fields, screens and routing, and hands over a written brief. A working configurator is software development, scoped and quoted separately, whether your own developer or a vendor builds it.
Do we need a configurator, or is a better form enough?
A better form is enough when buyers already know which model they want. A guided selection earns its place when the range is large or the naming is hard to read. The request audit shows which applies to you.
Will the tool show prices?
Only if you decide to publish them. The design can carry a price display, but price logic is your decision and a calculation engine is software work. Where prices stay private, the design asks for a quotation instead.
What if our custom orders do not fit a form?
They get their own route. The design separates standard variants from custom requests, collects a drawing or description for the second, and sends it to the person who can judge it. Nothing is forced into a fixed list.
Who owns the logic and the data afterwards?
You do. The variant map, field list and routing table are delivered to you as documents, and the final site and its form sit under your accounts. Your own adviser decides how personal details in requests are stored and used.
What decides the fee?
The size of your range, the number of rule sets, and how many request routes you have. After the brief and a first conversation, the written scope sets the fee and the term. Software build costs are separate and quoted by whoever builds.

Your next practical step

Tell us what you are trying to grow, and we will read it before we call.

Eight short steps, mostly taps. Skip anything you would rather answer on the call.