---
title: "How We Price Transformation Work | Murarum"
description: "How Murarum prices process, digital and AI work: on scope set by a diagnosis, with running costs kept visible and a written quote before you commit."
url: https://murarum.ro/en/approach/pricing
language: en
alternate_ro: https://murarum.ro/cum-lucram/pret
---

How we price

# How we price. Scope first, then the quote.

Murarum prices every engagement on scope, and the scope comes out of the diagnosis. We do not sell hours or packages. We first learn how work runs, what has to change and which systems it touches, then quote a defined piece of work in writing. You know what it covers and what it costs before you commit.

What moves the price

## Six things decide the size of the work.

None of them can be read from a call. All of them come out of the diagnosis.

### The scope of the change

One process or several, one team or the whole company. The more the change touches, the more there is to design, build and hand over.

### Systems and integrations

Each system the change has to talk to, such as an ERP, a CRM, email or documents, adds design, integration and testing work.

### Data readiness

Clean, reachable data keeps the work short. Data spread across files, inboxes and people has to be found, cleaned and connected first.

### Team composition

The mix of senior people the work needs: process, engineering, AI, product. We staff for the problem, and the same people design and build.

### Time

How long the work runs, and whether a fixed date forces more people onto it at once. We will not rush a build where the date matters more than whether it holds.

### The ongoing part

Whether you want us to keep measuring and extending the system after launch, or your team takes it over at handover.

Engagement models

## Three ways to work, three ways to price.

Every engagement starts with a diagnosis. What follows depends on what it finds.

### A scoped diagnosis

The Diagnose stage on its own. You get a written diagnosis and a plan you can act on with us or without us.

How it is priced

A fixed scope, known after the first conversation. You pay for the diagnosis, not for a project you may not need.

### A build engagement

Design and Build for one defined change, from blueprint to production.

How it is priced

Quoted as a fixed scope with a fixed team and a clear end. If the scope changes, the quote changes in writing, before the work.

### An ongoing partnership

Scale as a standing arrangement: a senior team that keeps measuring, improving and extending your systems.

How it is priced

A standing arrangement agreed in advance, billed monthly for the hours actually worked.

Running costs

## What you pay that is not our fee.

A system in production has costs of its own. They are separate from our fee, and we keep them in view from the design stage on.

### Model usage

For AI workflows, billed by the model provider per token or per request.

### Hosting and monitoring

The system around the model or the software: hosting, monitoring, logging.

### Licences

Software the solution runs on or connects to, such as an ERP, a CRM or a document platform.

### How we keep them visible

- During Design we estimate the cost per task and per month from your real volumes, not from a demo.
- We choose the smallest model that passes the evaluation set.
- In production we set a budget limit with alerts, and monitor cost next to accuracy and latency.

You own the code and everything we build for you, from the first commit. Provider, hosting and licence accounts are opened in your name and billed to you directly, so nothing is locked to us.

Never an extra

## Part of the scope, every time.

Some things are not a line you can remove from the quote. They are how we work.

- Documentation for every system we ship.
- Training for the people who will run it.
- Admin access in your name.
- The code, owned by you, in your repository.
- A clean handover, so your team can run the system without us.
- A 12-month bug warranty after launch.
- A written change to the quote before any change to the scope.

Before you commit

## You see the scope before you sign.

No work starts on a guess. Each step ends with something in writing.

1. ### The first conversation  
One call with the senior people who would do the work. We ask how work runs today and where it breaks.  
You know whether a diagnosis makes sense, what it would cover and what it costs.
2. ### The diagnosis  
We measure where work stalls and what that costs, then write down what to change first.  
A written diagnosis and a scoped plan with a quote: what we change, in what order, what it costs.
3. ### Your decision  
You build it with us, build it without us, or stop. If the diagnosis says the change will not pay for itself, we say so.  
You keep the diagnosis whatever you decide.

[How the diagnosis works](https://murarum.ro/en/approach/diagnosis)

## Questions about price

### Why is there no price list?

Because every engagement is priced on scope, and scope comes out of the diagnosis. A price list would mean quoting before we understand the problem. That quote would be a guess, and you would pay for the guess. We scope before we quote.

### Can you give a ballpark before a call?

Not one we would stand behind. Two companies asking for the same thing can need very different work once we see their systems and data. The first conversation is short and free of slides, and at the end of it you know whether a diagnosis makes sense and what it costs.

### Who owns what you build?

You do. The code, the repository and the documentation are yours from the first commit. No licences owed to us, no retained rights, no lock-in.

### What happens if something breaks after launch?

We fix it. Any bug that shows up after launch is covered by a 12-month warranty: if something we built does not work as it should, we fix it, and that is part of the scope, not an extra on the quote. New features or changes to what the system does are new scope, quoted in writing before the work, or part of an ongoing partnership.

### Do you add a markup to AI model usage?

Model usage is billed by the provider per token or per request, and we estimate it from your real volumes during Design. The provider bills you directly, on your own account, and we add no markup.

### Do you work on fixed price or time and materials?

A diagnosis has a fixed scope. A build engagement is quoted as a fixed scope with a fixed team, and if the scope changes, the quote changes in writing before the work. The ongoing partnership is time and materials: billed monthly for the hours actually worked, at a rate agreed in advance.

### What are your payment terms?

Quotes are in EUR and invoices are issued in RON at the BNR exchange rate of the invoice date. A diagnosis is invoiced 50% at the start and 50% when we deliver the report. A build is invoiced in the stages set out in the quote. The ongoing partnership is invoiced monthly, for the previous month's hours. Invoices are payable within 14 days.

[Still have questions? Write to us](https://murarum.ro/en/contact)

## Get a scope, not a guess.

Tell us how work runs today and where growth is pushing. After the first conversation you know what a diagnosis would cover and what it costs.

- [Let’s talk](https://murarum.ro/en/contact)
- [About the diagnosis](https://murarum.ro/en/approach/diagnosis)

[office@murarum.ro](mailto:office@murarum.ro)

## Contact

- Email: office@murarum.ro
- Phone: +40 761 339 149
- Let’s talk: https://murarum.ro/en/contact
