A product becomes easier to understand when you can point to a decision it helps someone make. For Emilia, that may be whether a client should receive a follow-up. For Juris Global, it may be which programme deserves a closer look and which question still needs an answer.
Those decisions shape the information an interface needs to show, the actions it offers and the history it should retain. Here are four examples from the products featured on CLVR, with the scope of each made explicit.
Emilia gives review its own place
A prepared message can look finished before anyone has decided whether it should be used. Emilia keeps that decision visible. The clinic team can inspect a follow-up, review the draft, hold it or mark the client do-not-contact.
The distinction matters when a booking or reply changes the situation. An operator needs to see both the proposed message and the reason the client appeared in the queue. Reviewing the text alone would miss part of the decision.
Review and dispatch also remain distinct. The clinic portal does not enable live sending. An approval within that review process should therefore be described as a review decision, with its own history. The interface and the language need to agree about what has actually happened.
MarginFlow checks whether the reminder still belongs
An enquiry provides the starting point for a quote: the customer, requested work and information needed to price it. MarginFlow links the quote and its line items back to that enquiry, alongside the conversation.
The follow-up logic checks for a customer reply and a won or lost status before sending another scheduled reminder. The original schedule is only part of the decision. The latest state of the opportunity matters too.
MarginFlow is in development, with the described scope centred on enquiries, quotes and follow-ups. This is why its CLVR overview shows a quote awaiting a response. The example should explain the work the product addresses today.
Four workflows seen together
These diagrams simplify each product to the decision discussed here. They show a shared interest in review and traceability; they do not imply that the products use one backend or have the same availability.
Four decisions in view
- 01Emilia
Should this client be contacted?
ClientChecksReviewDecision - 02MarginFlow
Does this quote need a reminder?
EnquiryQuoteReply checkFollow-up - 03Verified
Does the payment match the approval?
RequestApprovalPaymentCheck - 04Juris Global
What supports this option?
ExploreCompareSourcesShortlist
Review before outreach
A return window brings a client into consideration. The team checks the history and contact preferences, then records whether to proceed with review, hold or stop.
Let the reply change the plan
The quote stays with its enquiry. A reply or a won or lost decision changes whether the next scheduled reminder should be sent.
Keep the comparison possible
The design connects the request and approval to the payment record. The recipient, amount and reference provide the basis for a later check.
Give research a route back
Programme details lead into a comparison and shortlist. Sources and research notes help the reader revisit a claim and prepare questions for an adviser.
Verified keeps the approval within reach
The payment-control design for CLVR Verified begins with a structured request: who is to be paid, how much, for what purpose and with which supporting material. The approval refers to those details.
Verification then needs a basis for comparison. The intended record connects the payment reference to the approval so the recipient, amount and reference can be checked. A difference becomes something to investigate, with the relevant material available to the reviewer.
This describes the product’s design intent. The dedicated Verified site sets out the proposed workflow, and the product team can discuss requirements and availability. The diagram is an explanation of that workflow, not evidence of a payment being processed.
Juris makes the source part of the answer
A research answer is more useful when the reader can inspect what supports it. Juris Global brings programme details into dossiers, provides a comparison of up to three programmes and is designed to include source references in Ask JURIS responses.
The important choice is to carry the research forward. A shortlist can retain the options under consideration while notes and source references support a later discussion. Questions about a person’s circumstances belong in the advisory conversation that follows.
That creates a practical test for a research interface: after reading an answer, can someone find its source, recognise what remains unresolved and explain why an option is on their shortlist?
Let the decision shape the interface
These products require different information and different controls. A clinic operator needs a client history. A commercial team needs the latest reply. A finance reviewer needs the approval details. A researcher needs a route back to the source.
The common approach is to start with that need and make it visible. Good product detail makes a decision easier to understand before it is made, and easier to explain afterwards.
Explore the full product studies for the workflows behind each example.