Context has to be collected by hand
A free message often leaves the manager with only a name and a callback request. Important details have to be asked again.
QUIZscenario screen
01QUIZ
02REQUEST
03PROPOSAL
What needs to be built?
scenario screenLighting design
TypeLighting
Deadlineto be confirmed
open for client A Marquiz-style quiz
Turn a clear request into a reviewed proposal.
The client answers the right questions, the request keeps a snapshot, and the manager reviews scope and price before publishing a proposal.
TaskWhat needs to be done and what result the client should receive.
The quiz does not vanish after sendingA snapshot records the inputs. It does not mean that the project has been reviewed or approved.
Publish a versionAfter review, the current version goes out while working drafts stay inside.
Grew from Marquiz
A quiz is only the start of the commercial process
We took Marquiz-style request capture and added answer snapshots, manager review, versions, proposal publishing, and links to CRM, Finance, and Documents.
Source model
Marquiz
SHD version
Proposals
From Marquiz to a commercial process
A quiz collects the task, not just a contact
Marquiz-style questions make the first conversation clearer. SHD carries it to a reviewed proposal instead of leaving it in a lead list.
Questions lead to a request
The quiz asks scenario-specific questions and saves the answers in a request snapshot. It starts the process; it is not an approved public proposal.
Answers do not disappear after sending
Proposal template
Five blocks for a clear proposal
A proposal is built from clear parts: scope, terms, calculation, and the next step. The client sees the result instead of internal notes.
01
Task
What needs to be done and what result the client should receive.
02
Starting data
Area, object, constraints, and answers that came from the request.
03
Timing and stages
When work starts, what happens along the way, and where a check is needed.
04
Price
The price scope and boundaries without promising an automatic calculation.
05
Next step
What the client should do to move from reading to a decision.
The template keeps the order. The team remains responsible for content and price.
Client path
From an answer to a published version
Every stage leaves a trace: an answer becomes a request, a request becomes a working snapshot, and a checked snapshot becomes a client proposal.
- 01
Answer the questions
The client chooses parameters that genuinely affect the next conversation.
- 02
Check the snapshot
Before sending, see exactly what the manager will receive and whether anything is missing.
- 03
Clarify with the manager
The team adds conditions, checks boundaries, and asks the remaining questions.
- 04
Open the proposal
The client receives a published version with clear scope and a next action.
Request snapshot
The quiz does not vanish after sending
A snapshot preserves the original answers and helps compare them with what entered the proposal.
- Project typeHome lighting
- Area240 m²
- DeadlineTo be confirmed
REQUEST SAVED
Open the proposal
A snapshot records the inputs. It does not mean that the project has been reviewed or approved.
A published version is the result of a check, not an unprocessed quiz answer.
Manager work
The manager sees the original request
A person makes the decision and owns the content. The module helps keep the path from question to publication.
01
No repeated questions
The client's answers are already in one snapshot, not scattered across emails and messages.
02
Add the conditions
The manager clarifies scope, exceptions, timing, and what belongs in the proposal.
03
Publish a version
After review, the current version goes out while working drafts stay inside.
Automation preserves context, but the manager still owns the commercial decision.
Before the request
The boundaries in brief
The module connects questions, a request snapshot, and a proposal. It does not turn them into an automatic deal.
Is this just a quiz?
No. The quiz is the entry scenario. After submission, a request with an answer snapshot appears for a manager to review and turn into a published proposal.
Can a template calculate the amount?
If the template defines it, the module can calculate a value. The manager still checks the scope, terms, and final price before publication.
Is the number of steps always the same?
No. Screens, questions, and routing depend on the active template.
Does the client see a draft?
No. Until publication, the proposal remains inside the work process.
Can the request change after sending?
Yes. A new agreement should enter the current version instead of erasing the history.
Is this an automatic deal or AI?
No. The module records the path and proposal version; the decision and contact remain with the team.
Proposal context
Turn an incoming request into a clear next step.
We will review which questions the client needs, what to preserve in a snapshot, and where the manager should decide.
We will start with the current quiz, form, or chat and build a path without extra promises.