Industry solution · Construction
Every job is its own project, and the quote gets lost along the way.
In construction the sale is technical and drawn-out: the engineer specifies, the buyer executes, and between them sits a quote that drags on, cubed freight, a tax that changes by state, and a different commercial policy for every builder. CWS Platform doesn't flatten this into a generic catalog: it models the commercial policy as an executable rule, from spec to order, under governance the company controls.
Inside the platform
From the project quote to the invoiced order, under each builder's rules
Three CWS Platform screens in a building materials sale: the quote on the phone, each role's approval limit and buying on terms within the builder's credit limit.
Project quote
The project quote already comes out with freight and state tax in the total
The rep builds the bill-of-materials quote on the phone, at the price that applies to that builder. Freight and state sales tax come in through the rule before the quote goes out.
Pain it removes: project margin that only shows up at closing.
CWS Platform demo screen, completed with fictitious data to show the use.
Limits by role
Each role's ceiling, by customer type and contract, becomes a rule
Consultant, coordinator, manager and executive board each have their discount and payment-term ceiling, by customer type and by price table or contract. Anything above the ceiling goes to approval, with the reason on record.
Pain it removes: commercial policy that depends on the rep's memory on every project.
CWS Platform demo screen, completed with fictitious data to show the use.
Invoiced on credit
The project buys on terms, within the builder's credit limit
At checkout the buyer picks invoiced terms and sees the limit, the open balance and what's available, under the company's contract terms. With room in the limit, the order is approved on the spot.
Pain it removes: projects that drop out at checkout because there are no payment terms.
CWS Platform demo screen, completed with fictitious data to show the use.
Target profile
US$30M to US$400M in revenue, regional chains plus cement, steel, plumbing and electrical manufacturers.
Core pain
Long quote, technical mix, cubed freight, state tax, and a different commercial policy for every builder.
Figures converted from Brazilian reais at R$5.00 = US$1.00.
What changes
CWS Platform turns each builder's commercial policy into an executable rule (Commerce Rules Engine, the CDL Workspace): price, freight, terms and composition negotiated at the same time, in the same order. Markup, cubed freight (CIF or FOB) and state tax stop being a calculation done on the side and get computed together (Contextual Pricing and Shipping & Fulfillment). The engineer keeps specifying and the buyer keeps executing: the platform bridges the gap between the specification and the order, so the quote doesn't get lost in between. Every job stays a project of its own, under rules the company defines, not under a single mold.
The jobsite challenges, on their own pages.
Job sites buying on terms inside the builder's credit limit are covered in B2B payment terms.
Construction and materials in 1 minute
By decision-maker angle
CEO
The pain: The technical sale that made the company the center of the decision is turning into a price fight in the middle of the chain.
The full pain and what changes for the CEO.
What changes: Technical reintermediation, with the company back at the center of the specification and the buying decision.
Commercial Director
The pain: The long quote loses information at every hand it passes through, and many proposals die between the specification and the order.
The full pain and what changes for the commercial director.
What changes: From quote to order with no loss in between, with each builder's policy applied by rule.
CFO
The pain: Markup, cubed freight and state tax go in as estimates, and the real margin on the job only shows up at closing.
The full pain and what changes for the CFO.
What changes: Markup, freight and state tax under margin control, calculated in the same order, with the concession recorded (Reason Codes).
CIO
The pain: The technical specification (memorial descritivo) lives in a loose document, far from the ERP and the job's purchasing flow.
The full pain and what changes for the CIO.
What changes: From spec to order in a flow integrated with the job, orchestrated over the ERP without replacing it.
Jobsite shipping
Freight calculated for the jobsite ZIP code.
On the product page, the buyer enters the jobsite ZIP code and sees pallet delivery to the address, with lead time and price, or store pickup.
The capability no one replicates
Per-builder policy as an executable rule
Each builder with its own policy (price, terms, composition, approval authority) running as a rule (Approval Workflows), instead of relying on the rep's memory for every job.
Markup, cubed freight and state tax in the same order
Markup in the composition, cubed freight (CIF or FOB) and state tax calculated together, in a single pass, so the job's price comes out right at the source.
Persona · Construction company buyer
The job quote arrives with freight and tax in it, and I don't redo the math.
The spec becomes the composition, and cubed freight and state tax are computed together in the same order (Contextual Pricing and Shipping & Fulfillment).
Persona · Building materials sales rep
Each builder's policy comes already applied, so nothing depends on my memory anymore.
The Commerce Rules Engine (CDL Workspace) runs each builder's price, terms, composition and approval authority as a rule, from quote to order with no loss.
The negotiation rails, in the vocabulary of the job site
The six jobsite rails.
In chat
From the job-site list to a cart, in one conversation.
The engineer or site buyer sends the materials list for the next phase, with quantities the way the site counts them. The Sales Copilot finds each product, asks for the size or unit when it is missing and hands back a cart, with delivery following the rules already set for that customer.
In operation
CWS Platform brings to the sector the mechanism of modeling each customer's commercial policy as an executable rule and calculating markup, cubed freight and state tax in the same order, preserving the technical role of the engineer and the buyer. Named proof, with a number, will go here as soon as there's a construction case cleared by the customer, without importing a number from another industry as if it belonged to this one.
Delivery by branch
One order, each branch delivers its share to the jobsite.
The confirmed order shows each branch with its share and its jobsite delivery time, in a single order.
Frequently asked questions
Every job is a project. You can't standardize it.
And CWS Platform doesn't standardize the decision: it models your commercial policy as a rule. Every job keeps its own project. What gets governed is the rule the company already uses, not the outcome.
Does the portal calculate markup, cubed freight and state tax, or does that stay in a spreadsheet?
It calculates them in the same order. Markup in the composition (BDI, the overhead-and-margin factor built into a Brazilian construction bid), cubed freight (CIF or FOB) and state tax come out together, so the job's price doesn't depend on a calculation done on the side.
The engineer specifies and the buyer executes. How does the portal cover both?
The technical specification feeds the governed order: the memorial becomes a composition, and the buyer executes on the policy already applied, without redoing the math or losing information along the way.