Why we’re building Margevia around the review.
The thinking behind a product concept that keeps source evidence, human judgment and the next action in the same picture.
Margevia begins with a small question: does this invoice match what was agreed and delivered? We are building a product concept around making that question easier to answer, and making the next action easier to follow.
The product should help someone understand a difference and decide what to do. The evidence matters as much as the flag.
Start with a decision someone has to make.
A price list describes an agreement. A receiving note describes a delivery. An invoice asks for payment. Each record can be clear on its own, while the relationship between them still takes effort to reconstruct. That relationship is the starting point for Margevia.
The concept is designed for purchasing, operations and finance teams at small restaurant groups and independent caterers. We are not treating every team as if it has the same process. The person who knows whether a replacement was accepted may be different from the person checking the invoice, and a useful tool needs to respect that handoff.
Put the evidence beside the conclusion.
A discrepancy flag should invite inspection. It should show which figures were compared, where they came from and what assumption connects them. If the units do not match, the applicable price is uncertain or a delivery record is missing, that uncertainty should stay visible.
This principle affects even a small interface decision. In the preview, the invoice line sits beside the reference figure, and the supporting record is named below. The amount is labeled for review. A reviewer can see the question before deciding whether it deserves a supplier conversation.
Make the idea tangible before making promises.
The first public version is a lightweight interactive preview. It has three fictional invoices: a price-difference example, a delivery-difference example and a matched invoice. Visitors can move between them, inspect the numbers and try a local review action.
That is deliberately narrower than a production service. The preview does not process uploaded invoices, connect to accounting tools, send supplier messages or recover money. It gives the product conversation something concrete to refer to without presenting unbuilt capabilities as available.
Let the workflow shape the next build.
The next useful questions are about the work itself. Where does a team keep the current agreement? Which delivery details are reliable? Who decides that a difference is valid? What evidence is needed before a case can be closed? Those answers should shape what gets built next.
We also want to learn where an extra tool would create friction. A clearer comparison is not enough if someone must duplicate records or maintain another disconnected list. A focused pilot would need to examine the whole handoff, including the work that remains manual.
This journal will share the thinking behind that process alongside practical review guides. Margevia is still a concept in development. The purpose of the preview is to make the idea understandable, invite specific feedback and give the next iteration a better foundation.
Try the idea with a sample invoice.
Explore the Margevia preview with fictional records and visible source evidence.
Explore the demo
