The quote pipelinemoved onto one board.
In a global trading operation the quote and client pipeline ran across several channels. The subject of the build was not adding another tool; it was tying a scattered pipeline to a single record.
Sector
International trade
Built
Quote and client pipeline
Scope
One board
Status
Live
What the situation wasbefore the build.
The quoting process had spread across several channels and the status lived with individuals.
- Which quote had gone to which client, at which stage, could not be read from one place.
- The client record and the quote record were kept in separate places.
The pieces builtfor Merjan Global.
- 01
One record
The client record and the quote record were merged into the same structure. Which client a quote belongs to is read from the record itself.
- 02
The stage is visible
Every quote carries its own stage; instead of asking for the status, you read it off the list.
- 03
Reporting is defined
Which report goes to whom, and when, was written during the build.
A scattered pipelinetied to a single record.
No before and after measurement was taken on this build, so we do not publish a number. What we can describe is the structure itself.
No before and after measurement was taken on this build. The items below are not a measured result; they are the way of working that changed with it.
- The quote and the client sit in the same record.
- Stage information lives in the system, not with a person.
The products usedin this build.
CRM and customer management
The proposal and the customer record merged into the same structure.
Document and report generation
When the report goes out and who it goes to was written during the build.
Integrations
The flow from scattered channels was tied to one record.
The process first, the proposal after
In a short discovery call we map the process together and tell you plainly whether it is worth automating. If it is not, we say that too.
30 minutes · no preparation needed
