“Operating systems for real-world business workflows” is the central message of CLVR. It describes the kind of software we want to build and the work it should help people do.
Here, an operating system means a place where a business task can be understood, reviewed and carried through, with a record of the decisions along the way. The scope is deliberately specific: a clinic follow-up, an enquiry and quote, a payment review or a research question.
That definition gives us a standard to work towards. A product should make the work easier to follow from the perspective of the person responsible for it.
Start with a task someone recognises
“Review this client’s follow-up” describes a piece of work. So does “find out whether this quote needs another reminder.” Each has information to inspect, a choice to make and a person who needs to understand the result.
Starting there changes the questions we ask of a product. What would the person need to know before acting? What could make the proposed action inappropriate? If they pause the task, how will a colleague know why?
The interface can then take its shape from those answers. The status label, review controls and history each have a purpose. A screen is useful when it helps someone decide what to do with the task in front of them.
The connection we care about
This diagram expresses our design approach. It is a way to examine a product idea, rather than a claim that every CLVR product shares a technical platform.
Build from the work
- 01The task
Name the work
- 02The decision
Expose what matters
- 03The system
Make the choice usable
- 04The record
Keep the explanation
Start with something concrete
Identify a task someone recognises, such as reviewing a follow-up or checking an unanswered quote. Give the product a specific problem to address.
Find the information the choice needs
Ask what the person needs to see before acting, and what could change their decision. Those answers determine the checks and information shown.
Give the work a place to happen
Bring the task, its information and review controls together. Make a hold, a request for more information and a completed review understandable states.
Carry the learning forward
Retain the decision and its reason for the next person. Use that history to ask whether the task or the interface needs to change.
The last stage leads back to the first. A record can reveal that the original task was misunderstood, that a check was missing or that the interface needs a better way to explain a pause. Those are useful questions to bring into the next revision.
Different products keep their own purpose
CLVR brings together Emilia, MarginFlow and CLVR Verified. The site also features Juris Global, co-founded by Jethro Xavier, who founded CLVR. Their fields differ, and that difference should be apparent in how they are presented.
Emilia’s review queue belongs to the work of a clinic. MarginFlow’s enquiry and quote history belongs to a commercial conversation. Verified’s proposed payment record needs an approval to compare against. Juris needs programme information and sources a researcher can inspect.
A common approach should allow those differences to remain useful. It should help us ask better questions about each product without forcing every workflow into the same sequence or vocabulary.
Be precise about progress
Explaining a product is part of building it. A design illustration should be identified as an illustration. A development status should say something about availability. A proposed workflow should be described in terms that distinguish it from a demonstrated operation.
That is why the CLVR site keeps MarginFlow’s development label, explains the distinction between Emilia’s review process and live sending, and describes Verified in terms of its payment-control design. The details give a reader a sounder basis for deciding what to explore or ask about.
For these opening notes, progress means making the products and the choices behind them easier to inspect. The Approach page gives each product a deeper explanation. These articles make room for the reasoning that sits alongside those explanations.
What belongs in these notes
We want Company notes to describe meaningful decisions: what we are trying to make clearer, what a product needs to account for and what changes as the work develops. Specific examples will matter more than broad statements of ambition.
The other two strands serve that purpose from different angles. How work works starts with an everyday situation. Inside the build looks at the product choices that respond to it.
Together, they should make CLVR easier to understand through the work itself. That is the standard we want this site, and the products it introduces, to meet.