Why Fixed-Price Compliance Beats Hourly Consulting
Hourly compliance consulting penalizes efficiency. The longer the engagement, the higher the invoice. Fixed-price aligns incentives: done fast, done right, done.
Compliance projects have a perverse incentive structure when billed hourly. The consultant’s financial interest (more hours) directly opposes the client’s interest (fewer hours, faster completion). Every hour of ambiguity, every scope expansion, every “let me research that” is billable time.
Fixed-price eliminates the conflict. The fee is set at the start. The consultant’s incentive is to finish, and the economics work out that way — every hour of ambiguity is now the consultant’s problem, not the client’s.
What goes wrong with hourly
Scope ambiguity becomes revenue.
EU AI Act compliance is inherently ambiguous. The regulation is over 50,000 words, plus extensive annexes. The delegated acts and implementing acts multiply that figure. An hourly consultant can spend weeks interpreting a single article because every hour of interpretation is billable. The question is whether the client is the one who should be paying for that interpretation.
In practice, the client pays for the consultant to figure out what the law means for their specific systems. A single article — Art. 6 on high-risk classification — generates billable research, billable drafting, and billable calls to “clarify interpretation.” The deliverable that surfaces out of that time is often a preliminary memo that reads like a learning exercise. By the time the client gets it, the consultant has already billed through the problem and the next engagement is already on the books.
The meter runs during downtime.
Typical compliance engagements spend 30 to 40 percent of the calendar time waiting on the client. Waiting for a data inventory response. Waiting for a stakeholder interview slot with the CTO. Waiting for a legal review of a vendor agreement. These delays are real pauses. In an hourly engagement they are billable pauses regardless.
The dynamic changes client behavior too. A company whose hourly clock is ticking but whose regulatory questions are still open is going to put off those questions. Committing to an email that will generate a three-hour billing pulse means the clarification gets delayed. When decisions get made without the right information in hand, the client pays again on the remediation side.
No natural endpoint.
“Compliance” is not a binary state. Article 9 calls for an ongoing risk management process. Article 17 requires a standing quality management system. Article 21 requires human oversight at the point of use for every high-risk system that ships. An hourly engagement has no structural reason to finish any of it.
Clients who begin with a four-week scope tend to end up with a scope that includes policy templates, a second round of stakeholder interviews, the QMS framework, and a pre-read for the board presentation. Each addition is reasonable on its own. Together they carry the engagement past the original conclusion. The consultant is not defrauding anyone — they are working to the scope they have. The scope just keeps expanding.
What fixed-price enforces
Scoping discipline.
You cannot name a price without naming the boundaries. A fixed-price engagement starts with a signed statement of work: the systems in scope, the templates to deliver, the gaps to analyze, the date the deliverable ships. The signed document is not decoration. It is the reference point when a legitimate scope question comes up — and it is the answer when the conversation drifts toward additional work.
Scope discipline doesn’t mean the scope never changes. It means the scope change is priced and signed before anyone picks up a new task.
Efficiency as a feature.
The hourly model rewards meeting attendance and document volume. Fixed-price rewards the opposite. A consultant who produces a clean, defensible classification table in one call generates less billable time than a consultant who produces it in four. In an hourly engagement that earns the first consultant less money. In a fixed-price engagement the framework built during the first project is reused verbatim on the twelfth — the investment the hourly model penalizes is the investment the fixed-price client captures.
A real deadline.
A client who signs a fixed-price engagement on February 1 knows the deliverable ships March 1. That date is set in the statement of work, and if the consultant misses it the consequence stays on their side. A fixed deadline doesn’t magically make the work simpler. It removes the open-loop on both sides: the consultant has no incentive to engineer a longer engagement, and the client is not caught in a bill that grows without a date they can point to where they can stop it.
The Thorian model
€4,999. 30 days. EU AI Act readiness assessment.
System inventory, risk classification against the Annex III categories, gap analysis against Articles 6 through 55, and a prioritized compliance roadmap that traces every finding to the specific article it comes from. Fixed scope, fixed timeline, fixed price.
When we find more complexity in your AI portfolio than our initial estimate captured, that is our problem to resolve — not yours to fund. Complexity is part of the engagement. We do not bill for learning it.
Before you sign, we will ask hard questions: how many AI systems do you deploy, at what risk tier, and what level of documentation do you already have. Those questions shape the scope. We do not offer a flat engagement to every prospect because they want a flat price.
What you have on day 30 that you did not have on day 1 is a document an auditor can use. A gap table with article references, a risk register, and a list of remediation priorities ordered by deadline and difficulty. You also know which obligations are live now, which activate in August 2026, and which AI systems the obligation applies to. On day 31 you can have a conversation with a regulator, a customer, or a board member that references something written down instead of a best-effort summary produced under pressure.