The Diagnosis
Know what to change before you pay to build it.
The Diagnosis is Murarum's entry engagement: a fixed-scope review of how work moves through your company, before anything is built. We map the process, measure the baseline, check data readiness where AI is in scope and rank the changes by value. You receive a written diagnosis you keep and can act on with us or without us.
What it is
The Diagnose stage, on its own.
Scoped before it starts.
We agree in writing which processes and teams the diagnosis covers and what it costs, before any work begins. If the scope needs to change, we agree that in writing first.
Done by the people who would build.
The senior people who diagnose are the people who would design and build the change. There is no handover to a junior team.
Yours to keep.
The written diagnosis belongs to you. Act on it with us, with another supplier or with your own team.
Who it is for
When it fits, and when it does not.
The diagnosis is for companies where growth is pushing on how work runs. It is not the answer to every question, and we say so in the first conversation.
It fits when
- Processes built for a smaller company now slow down a bigger one.
- You know something is slow or costly, but not exactly where or how much.
- You are weighing AI or new software and want to know if the process is ready for it.
- You want a plan your own team can act on, whether or not we build it.
It does not fit when
- You need a tool installed this week, not a decision about what to change.
- The process is simple, one person runs it and there is no volume that would justify a system. A good freelancer serves you better.
- You want a deck for the board instead of a change in how work runs.
- The scope is set by a grant file, not by the outcome.
What we do
Five steps, one written result.
No code is written during the diagnosis. We watch, we measure and we write it down.
- 01
Map how work moves
We sit with the people who do the work. We follow an order, a request or a report through the company and see where it stalls, where data is re-entered by hand and where decisions wait on one person.
Output: a map of the process as it runs today.
- 02
Measure the baseline
Before we suggest any change, we measure how work runs now: cycle time from request to completion, error and rework rate, and hours per week spent on manual steps. Every later change is judged against these numbers.
Output: a baseline, measured before any change.
- 03
Check data readiness, where AI is in scope
Where AI could earn its place, we check what data exists, where it lives and whether it can be used. Candidates without usable data are dropped here, before anyone pays to build them.
Output: a data readiness note for each AI candidate.
- 04
Rank the changes by value
We weigh each possible change by what the problem costs today, what the fix would take and what depends on it, then put the changes in order. Some are dropped. That is the point.
Output: a ranked list of changes, with the case for each.
- 05
Write the case
We write down what to change first, what it should move, what it would take and what to leave alone. If no change is worth its cost, we write that too. A written case for none is a valid result.
Output: the written diagnosis and a scoped plan.
What you receive
A written diagnosis you keep.
One document, in plain language, that your team can read without us in the room.
- A map of how work runs today, step by step
- A baseline: cycle time, error rate and manual hours, measured before any change
- Data readiness notes, where AI is in scope
- A ranked list of changes, with the written case for each
- A scoped plan you can act on with us or without us, with a quote if you want us to build it
- Or a written case for none, when nothing is worth changing yet
How it ends
It ends with a decision. Yours.
The diagnosis ends when you hold the written case. The fee and the scope are agreed before we start, and they are the only commitment. There is no obligation to continue.
- Build it with us. We quote the design and build from the scope the diagnosis defined, as a fixed scope with a fixed team.
- Build it without us. The plan is written to be used by your own team or another supplier.
- Do nothing yet. You keep a clear picture of how work runs and where it would break.
Questions about the diagnosis
How long does the diagnosis take?
From a few days to 2 weeks, depending on how many processes and teams are in scope. We agree the length together with the scope, before we start.
We have already decided what to change. Is there a shorter version?
Yes. If you already know which process you want to change, we keep the diagnosis to that one flow, usually 2-3 days. You still get the map, the baseline and a scoped plan for that flow, without a review of the whole company.
Do you come to our office?
For companies in Moldova, the north-eastern region of Romania around Iași, yes: we do the diagnosis at your office, next to the people who do the work. For companies elsewhere, we agree the format in the first conversation, on site or remote.
What does the diagnosis cost?
It is priced on scope: which processes, how many teams and whether AI is in scope. We agree the scope and the fee in writing before we start. There is no public price, because a price before we understand the problem would be a guess, and you would pay for the guess.
What do you need from us?
Access and candour. A few hours from the people who do the work, access to the tools and data the process touches, and one decision-maker who can say yes or no. We do not need a brief. The diagnosis produces it.
What happens after the diagnosis?
You decide. You can ask us to design and build the change, and we quote it from the scope the diagnosis defined. You can act on the plan with your own team or another supplier. Or you can stop there and keep the diagnosis. There is no obligation to continue.
Is the diagnosis only for AI projects?
No. Most diagnoses start from a process that is slow, manual or error-prone. AI is one possible answer among several, and often not the first. Where AI is in scope we also check data readiness. Sometimes the right change is a simpler process, a better integration or software without AI.
By industry
See what the diagnosis looks like in your industry.
Start with the diagnosis.
Tell us which process is slowing you down. We reply within two working days and tell you whether a diagnosis makes sense and what it would cover.