Text
A free answer for a brief, address, comment or constraint.
PROPOSALS · SCENARIO & CALCULATION
PREVIEW · DEVFrom a client request to a calculated proposal.
The editor defines questions, conditions, catalogs and calculation rules. The request keeps its source data, the team checks the result, then publishes a web/PDF version or continues the work in CRM and Finance.
- ScenarioSteps, questions and conditional logic.
- CalculationCatalogs, components, modifiers and breakdown.
- VersionsPreview, history, publishing and rollback.
TEMPLATE
The template controls the scenario, calculation and result.
The editor defines not only the client questions, but also data sources, calculation order and what the client sees after submitting.
-
Scenario
Steps, questions, required state, options and conditional visibility.
-
Catalogs
Reusable records for options, categories, rates and services.
-
Total price
Components, computed values, modifiers and calculation order.
-
Result & Appearance
Result sections, copy, logo, theme and the client-facing presentation.
SCENARIO
Questions change with the client's answers.
A template supports different question types and hides steps that do not apply. Conditional logic asks only for data needed for the selected option.
Number
Area, quantity, deadline or another value used in calculation.
Single choice
One project type, rate, object or meeting format.
Multiple choice
A set of works, functions or materials selected together.
List
A reusable option list sourced from Catalogs.
Table choice
A row and value selected from a tabular set.
Contacts
Name, phone, email and additional request participants.
Info block
An explanation or condition without an answer field.
Repeatable rows
Several similar items with child fields.
A hidden question is not considered complete and does not affect the result until its condition makes it visible.
TOTAL PRICE
The calculation shows what makes up the total.
The system stores price composition as separate entities. Intermediate values and rule changes stay visible for review.
- 01Components
Separate price lines for work, material, delivery or service.
- 02Computed values
Intermediate values used by later expressions.
- 03Modifiers
A coefficient or change applied to a selected scope in a defined order.
- 04Breakdown
A detailed result composition, not just one total number.
calculation checkedBreakdown
A catalog can affect calculation through a bound modifier. The team still reviews the final scope and conditions.
REQUEST
A submitted request does not change retroactively.
The request stores source answers at submission time. The team can refine the current proposal without rewriting the request history.
REQUEST SAVEDA submitted request does not change retroactively.
The snapshot fixes the request inputs. It does not mean that price or scope has been automatically approved.
- Project type
- Home lighting
- Area
- 240 m²
- Deadline
- To be clarified
- Status
- Under review
CONTROL
The system calculates. The team approves.
Permissions separate viewing, editing and publishing. Preview checks the scenario before a version becomes available to a client.
Viewer
Opens a template and runs Preview without changing the model.
Editor
Changes questions, catalogs, calculation, result and appearance.
Approver
Publishes a checked version and rolls it back when needed.
Rollback restores the selected version definition, not just one rate or text fragment.
EDITOR & PUBLISHING
One scenario, from configuration to a published version.
Three Proposals screens show the editor, a saved request and the published client-facing result.
EDITOR
The editor builds the proposal model across tabs.
Scenario, Catalogs, Total price, Result and Appearance separate form, calculation and client-facing output.
template model
AFTER THE PROPOSAL
The work continues after the proposal.
Proposals does not end on the result page: a checked document can move into connected work processes.
- 01Public scenario
The client answers the questions defined by the selected template.
- 02Request
Answers are stored as a request with its source snapshot.
- 03Calculated proposal
The team reviews scope, conditions and the calculated total.
- 04Web / PDF
The client receives the published proposal version.
- 05CRM / Finance
After review, the process can continue in CRM or Finance.
Connected actions are performed by a team member after request review; the quiz does not create a deal or financial document by itself.
PROPOSALS QUESTIONS
What to check before launch.
Editor, calculation and publishing are separate. These boundaries matter when configuring a scenario.
How does a proposal scenario work?
The template defines steps, questions, options and visibility conditions. After submission, a request with a snapshot of the answers is created.
Can the total be calculated?
Yes, when the template contains components, computed values and modifiers. The team reviews scope and conditions before publishing.
How is Preview different from publishing?
Preview checks the scenario and result without creating a request or publishing. A client sees only a published version.
Who publishes and rolls back a version?
Publishing and rollback require Approver rights. An Editor changes content; a Viewer only reviews and runs Preview.
PROPOSALS LAUNCH
We will shape the scenario around your sales process.
We will map the questions, catalogs, calculation rules, review roles and the format the client should receive.
Start with the form, quiz or proposal template you already use.