Do set-up rules also need a simple list of components?

If the list recurs and its compatibility has already been approved by the customer, a normal offer may be sufficient. The benefits of the rules occur when a change in one option affects other components, licenses or technical result.

How does the bidding solution use existing product and pricing data?

Technical set-up rules are obtained from verified manufacturer sources, and prices and discounts come from the pricing system used by the company. The manager makes a proposal based on these data. It is important to check who oversees the rules and how their changes are transmitted before installation.

How can the proposal not miss the necessary equipment components?

The set rules check mandatory attachments, licenses and compatibility before the price is delivered to the customer. An unclear condition is passed on to a technical specialist. The approved set continues to be used for the order so that the sale does not have to re-compile it.

Does an approved technical kit allow the price to be maintained if the supplier's offer has expired?

The technical suitability and validity of the commercial conditions are checked separately. The expired price must be updated before a new obligation to the customer; a significant change receives the necessary approval.

Electrical and IT equipment quote configurator

The manager makes an equipment offer with the necessary components, accessories and licenses. The customer-approved set-up is saved for the order so that the related requirements are not missed when changing the parts.

Equipment components, licenses, accessories, and design prices are combined in separate tables. Changing the set-up does not always recalculate the full amount of the offer and verify compatibility. The customer may not be offered the entire required set, which must then be replenished at a different price. Unreviewed discounts reduce the margin of the transaction and make it difficult to explain the price.

How the solution works

Client requirements are linked to parts of the project and approved technical choices.
The kit is checked against the necessary accessories, licenses and manufacturer restrictions.
Relevant costs and design conditions are compatible with the employee entitled to be approved.
The customer accepted version of the offer is transferred to the order with the same codes and obligations.

Key challenges

Design proposals and sets are manually controlled

Solution capabilities

Structure of technical requirements

The customer's need is broken down into technical criteria and parts of the solution.

Sets and Dependencies Rules

The system checks that the proposal contains all the necessary components and compatible versions of them.

Design pricing and margin

Cost, source of supply, project discount and margin are managed in a single bid.

Versions of proposals

Each change retains the previous technical setup, cost and approval history.

Conversion of an Approved Proposal

The approved set-up is transferred to ERP without the need for a re-combination of codes.

Business context

Design proposals and sets are manually controlled: Equipment components, licenses, accessories, and design prices are combined in separate tables. Changing the set-up does not always recalculate the full amount of the offer and verify compatibility. The customer may not be offered the entire required set, which must then be replenished at a different price. Unreviewed discounts reduce the margin of the transaction and make it difficult to explain the price.
The proposal shows all the necessary equipment: It is important for a business buyer to compare running sets, including attachments and licenses. The missing component can make a seemingly cheaper offer inappropriate. Consistent set-up helps the seller explain the price and discuss additional equipment based on the customer's actual need for use.

Core features

Structure of technical requirements
Sets and Dependencies Rules
Design pricing and margin
Versions of proposals
Conversion of an Approved Proposal

Key integrations

Product information management system (PIM): Technical attributes, analogs and set rules.
Enterprise resource planning system (ERP): Customer, prices, cost and order.
Supplier Integration Layer: Prices, terms and availability.
Customer relationship management system (CRM): Project and Sales Opportunity.
Sources of licence management: License types, terms and dependencies.

Potential impact (%)

The ranges indicate an illustrative relative change in the metric under the stated assumptions. Results depend on the starting position and actual use of the solution. Percentages for different metrics must not be added together.

Active technical proposal preparation time

12–36%Decreasing

This illustrative scenario assumes that 30-60% of manual data entry and handover work can be addressed. That share is assumed to fall by 40-60%. Company data is needed to verify both the addressable workload and the resulting change.

Compare offers of similar set-up complexity, separately marking the wait for the customer and the manufacturer.

Part of orders corrected for incomplete or outdated version

12–42%Decreasing

This illustrative scenario assumes that 30-60% of errors can be addressed through the data and rule checks described. That share is assumed to fall by 40-70%. Company data is needed to verify both the addressable share and the resulting change.

For these confirmed reasons, the number of orders corrected is divided by all comparable orders for the period and multiplied by 100.

Parts of equipment proposals that have been converted into orders

5–18%Increasing

Sample starting part - 40%. Assumption: 15-30% of the remaining cases involve unclear equipment setup and bid price; a solution would help solve 20-40% of these cases.

Tenders that have been converted into orders are divided by all equipment offers submitted by the same group. Price, discounts, terms of preparation and supply of the offer are separately assessed.

Conditional calculation scenarios. The assumptions have not been validated against client measurements.

When this solution is relevant

When one component is changed in the bid suite, compatibility of the other components needs to be checked and the price recalculated.
Project prices, margin and customer changes are combined in individual files, and the approved proposal is rewritten into a business management system.

Implementation requirements

The automation of technical offers depends on the approved combinations of equipment, accessories and licenses. Sales and technical teams combine price validity and re-approval conditions, and the available bidding system evaluates the ability to maintain these connections by changing the set.