How Cifral Custom works

The six-step workflow

1. 01

   RFQ comes in

   A customer, prospect, or colleague sends a request. It could arrive by email, through a form on your site, or through an internal request system. Cifral captures the request and routes it into the intake flow.

   InputEmail / Form / Internal system↓RFQ captured
2. 02

   Required information identified

   The system captures the variables that drive the quote: product configuration, quantities, delivery location, lead time requirements, special conditions. It is built around your specific quoting variables, and it flags missing or uncertain information instead of guessing.

   PreparationConfiguration · Quantity · Lead time↓Missing information flagged
3. 03

   Approved company data retrieved

   Relevant technical information, product data and approved content are pulled from the controlled sources agreed for your implementation: spec sheets, previous approved proposals, CRM or ERP records. Depending on the setup, one or several of these are connected.

   PreparationSpec sheets / CRM / ERP↓Approved content
4. 04

   Pricing and commercial rules applied

   Your team enters the hours and materials for the job; Cifral takes it from there and applies your rate card, margin, risk and discount rules, building the line-by-line price table without a spreadsheet to assemble by hand.

   PreparationHours + Materials + Rules↓Price table
5. 05

   Review-ready proposal assembled

   The system assembles the draft in your existing document template. Header, scope section, technical write-up, pricing table, terms and cover page follow your standard format.

   OutputContent + Your template↓Editable draft / Word · PDF
6. 06

   Engineer reviews and approves

   The responsible engineer receives a notification, reviews the draft, and edits or approves it. Only after approval is the proposal delivered, as PDF or Word, with a copy placed in the existing document environment agreed during scoping.

   Human controlReview → Adjust → Approve↓Delivery after approval

You do not have to automate all six stages at once. Many teams start with the single stage that consumes the most time: data collection, pricing, or document assembly: and expand from there.

Trying this on the public demo? Step 6 works a little differently: the sample goes straight to your own inbox, clearly marked as a demonstration, since there is no live customer on the other end for an engineer to protect.