01Free
Free initial call
Can we help with this problem?
- Real bottleneck and a responsible person
- Basic fit for urcase
- No process mapping or architecture
- No effort estimate or solution design
Paid process analysis
Understand first. Then decide.
The free initial call establishes whether urcase can help. In the separately commissioned process analysis, we examine the workflow, compare alternatives and recommend a next step.
02Paid service
Process analysis with recommendation
Compare the workflow, alternatives and risks.
- Agreed analysis and documented outcome
- Recommendation, objections and measurement plan
- Price and timeframe follow scope
- Delivery remains a separate engagement
Open-ended analysis
You receive a recommendation, not an automatic software project.
You see how the workflow works today, which assumptions remain open, which alternatives exist and which next step makes sense.
Current workflow
We document roles, systems, data, handovers, normal cases and exceptions. Facts, assumptions and open questions remain separate.
Comparison of alternatives
Organisation, standard software, integration, automation, custom software and deliberate non-build are assessed against the same criteria.
Recommendation with objections
The recommendation also states the strongest argument against it, important conditions, risks and a measurement plan.
Clear next step
A plan names acceptance criteria, owners, exit points and open decisions. Delivery is a separate engagement.
Anonymous sample
What the outcome can look like.
The sample shows the structure of a process analysis. It contains no client data, invented metrics or case-study claims.
Important: The exact deliverables are agreed in writing for each engagement. The sample is not a proposal.
URCASE / PA-01Decision record
SampleClear decision question
Which workflow should change, how, and how will we recognise the value?
- 01Current workflowRoles · systems · cases · controlsdocumented
- 02AlternativesValue · cost · risk · ease of reversalcompared
- 03RecommendationObjections · conditions · open questionsreviewed
- 04Measurement and next stepsAcceptance · ownership · exit · next stepdefined
Before commissioning
This is agreed in writing.
There is no blanket fixed price. Price, timing, the help required from you and usage rights depend on the question and agreed work.
Based on the agreed work
The workflow, people and systems involved, data quality, exceptions and review effort determine price. It is agreed in writing before commissioning.
A clear timeframe, not a blanket promise
The timeframe depends on scope and available material. Missing information or additional systems are identified as a change.
A responsible person and real cases
A responsible person, typical normal and exceptional cases, and depending on scope the business team and internal IT are required.
Delivery is a separate engagement
Production code, access, migration and operations are not part of the analysis. They require a separate engagement and approval.
No automatic delivery lock-in.
Usage rights, handover format and reuse are agreed in advance. Where agreed, the decision record can also be used with another provider.
Approach
How the analysis works.
Assess the enquiry
We personally assess whether the problem, ownership and potential value fit urcase.
Examine the workflow
We capture normal cases, exceptions, roles, data and systems using existing material and real cases.
Compare options
Automation, integration, custom software and deliberate non-automation are assessed against the same criteria.
Document the decision
The recommendation, objections, risks, success criteria and next step are recorded in writing.
FAQ
Questions before commissioning.
01Is the process analysis already a delivery project?
No. It creates the basis for a decision and includes no production code, access setup, migration or operating commitment. Technical delivery is scoped, proposed and approved separately.
02What does the process analysis cost?
urcase does not currently offer a blanket fixed price. Price depends on scope, people and systems involved, data quality, exceptions and review needs. It is agreed in writing first.
03How long does the process analysis take?
The timeframe is stated in the proposal and depends on scope and available material. Missing information or additional systems are identified as changes.
04Do we need to know which technology we need?
No. The starting point is the real workflow. Automation, integration, custom software or deliberately making no technical change are compared before a decision.
05Who needs to take part and which materials are needed?
A person responsible for the workflow is required. The business team and internal IT join depending on scope. Real normal and exceptional cases, process descriptions, system overviews and known metrics are helpful.
06Will we receive an effort estimate?
When the workflow is sufficiently understood and the next step is clearly described, the result includes a planning basis. Unknown dependencies are stated openly.
07What if automation is not worthwhile?
That conclusion is documented. Choosing not to automate or first resolving an organisational bottleneck is a valid recommendation.
08Can we use the result with another provider?
The process analysis does not automatically bind delivery to urcase. Usage rights and handover are agreed in advance; where agreed, the result can be used independently.
Tell us where work gets stuck.
Briefly describe today’s workflow, the systems involved and what should improve.
Free · no process mapping or solution design yet
Request an initial call