Skip to content
Skip to content
Leone Intelligence Systems
Book a workflow review
Leone Intelligence Systems
Book a workflow review
EnglishItalianoالعربية

Pricing

What it costs, and when you pay.

There is no price list, because every build is priced against acceptance gates you approve. Here is how the money works before we have spoken — the review, the gates, the bands the form asks for, and what is never billed.

Book a 30-minute workflow reviewRead the specimen verdict
Step one

The first review costs nothing.

Thirty minutes on one workflow: the owner, the decision, the data boundary, the acceptance tests, and the reasons not to build it. You leave with a written stop/go.

  • No production access and no NDA are needed to start.
  • A do-not-build verdict is a valid result, and you keep it — the fit verdict, the red flags, the timing assumptions, and the decision criteria.
  • The format is published in full on an invented case, so you can read what you will get before you book.
Step two

Builds are priced against gates, not hours.

A build is a fixed scope with named acceptance gates — fail conditions, owners, excluded data, and handover criteria — signed off before any code is written. Each milestone is tied to a gate.

  • Miss a gate and the milestone is not billed.
  • Handover is itself a named gate: if your team cannot run the system without us, the milestone is not complete.
  • Source, runbooks, traces, and deployment knowledge are deliverables, not upsells. Nothing keeps running only while you keep paying us.
Procurement

Mid-RFP? The answers come in your format.

If your buying process is already running, the procurement path answers scope, security, evidence, and handover questions in the format your evaluation uses — with or without us on the shortlist.

  • An RFP-ready scope grounded in evidence, ownership, and constraints.
  • Delivery, security, and handover gaps surfaced before the award, not after.

The bands the brief asks for

The second step of the brief asks for an indicative budget range. It exists to route you, not to anchor a quote: a named band at or above EUR 10k, together with an accountable owner and a start date, opens the calendar the moment you send the brief. Every other answer — including the two at the ends of the list — goes to a person who replies within two business days.

The bands are in euro because that is how most briefs arrive; a proposal is written in the currency your procurement needs.
  1. Under EUR 10k
  2. EUR 10k–25k
  3. EUR 25k–50k
  4. EUR 50k–100k
  5. EUR 100k–250k
  6. EUR 250k+
  7. Prefer not to disclose

What is never billed

  • The first review, whatever its verdict.
  • A build the review declined.
  • A milestone whose acceptance gate was missed.
  • Handover work your team needs in order to run the system without us.

The pricing questions that usually come first

Can you quote before the review?

No, and you should be wary of anyone who can. The review is what makes a quote honest: it fixes the workflow boundary, the acceptance tests, and the risks a price has to carry. A quote that skips it is a guess with a number on it.

Is the review really free, even if we go ahead?

Yes. It is not billed either way and it is not rolled into a later invoice. It exists so that both sides can decide with something written in hand.

Who owns what we pay for?

You do. Source, runbooks, traces, and deployment knowledge transfer at handover, and the handover is an acceptance gate. You can run, audit, and extend the system without calling us back.

What if our budget is below EUR 10k or we cannot disclose it?

Send the brief anyway. Those answers are on the form because they are real. They take the manual path — a person reads the brief and replies within two business days — rather than the instant calendar.

Book a workflow review