Buy hours priced by seniority, or buy a platform priced once — and notice which one has a ceiling
On ibl.ai you own all the code and the data, run it model-agnostic across any LLM, and pay with no per-seat pricing — so you can deploy anywhere, from your own cloud to a fully air-gapped network.
Last updated:
A rate card is a price list: architect, senior engineer, data engineer, project manager, each with an hourly figure, often blended into a single number for simplicity.
It is a clean way to buy labour and a poor way to buy an outcome. Nothing in a rate card refers to what gets delivered — it prices the input, and the relationship between input and result is exactly what neither party can predict on AI work.
A flat platform licence prices the other side of the equation. The platform costs what it costs, the compute costs what it costs, and neither figure moves because a discovery in month three added six weeks.
The distinction that matters is not the hourly number. It is whether the arrangement has a ceiling.
by ibl.ai
Licensed platform, source included, bounded integrationby Consultancies and integrators
Hourly rates per labor category| Criteria | Owned Platform + FDE | Rate Card |
|---|---|---|
| Who Carries Scope Risk | The platform's cost is fixed and already incurred; only the integration is variable, and it is scoped against something that exists. | Carried by the buyer, entirely — the rate is fixed but the hours are not. |
| Is There a Ceiling | Yes — a flat licence plus the compute you choose to run. The ceiling is the price. | Billed as hourly rates per labor category, or a blended hourly rate, so the total depends on how wrong the estimate turns out to be. |
| Incentive Alignment | Paid the same whether delivery takes six weeks or twelve, so the incentive is to finish. | Bill more hours at higher-seniority rates. |
| Budget Defensibility | A known line item that survives a budget review and can be forecast years out. | Forecastable only as well as the underlying estimate, which is the thing in question. |
| Criteria | Owned Platform + FDE | Rate Card |
|---|---|---|
| Reliability of the Estimate | High, because the platform is finished. What remains is integration with known systems. | Low on from-scratch builds — the reason this model is reached for at all. |
| Handling Changed Requirements | Absorbed as engineering, because you hold the source code and can change it directly. | Handled commercially, through re-estimation or change orders. |
| Time to First Production Workload | Weeks — the construction phase does not exist, because the platform already runs. | Quarters, most of them spent building infrastructure that is not specific to you. |
| Depth of Customization Available | Extensive, on top of a working base, with the source in your possession. | Unlimited in principle, which is exactly why it is unbounded in practice. |
| Criteria | Owned Platform + FDE | Rate Card |
|---|---|---|
| Source Code Ownership | Full source under a perpetual licence, running on your infrastructure. | Determined by contract clauses rather than by the delivery model — commonly a delivered system and an invoice history, with ownership set separately. |
| Ability to Operate Independently | Your team runs it; the platform is documented, supported, and maintained beyond any engagement. | Depends on knowledge transfer, which is the step most engagements shorten first. |
| Model Freedom | Model-agnostic by construction — run any LLM and switch without rewriting the platform. | Whatever was built in, and whatever the team is willing to maintain. |
| Deployment Flexibility | Any cloud, on-premise, or fully air-gapped, from the same deployment. | Whatever was engineered; air-gapped operation is significant additional scope. |
A flat licence plus compute has an actual ceiling: adding the ten-thousandth user or the third department changes utilisation, not the invoice.
A rate card fixes the price per hour and leaves the number of hours entirely open. Negotiating the rate down 10% while the hours grow 40% is a common and expensive outcome.
Cost control comes from bounding the quantity, not the unit price. Rate-card negotiations optimise the wrong variable.
When the platform already exists, the mix question largely disappears — there is far less work, and the work that remains is integration by people who know the system.
A blended rate averages an architect and a junior engineer into one number, which makes the invoice simple and the staffing mix invisible. The mix is what determines whether the hours were well spent.
Ask what the hours were spent on, not what they cost. On from-scratch builds, most of them go to infrastructure that already exists elsewhere.
A licence is a known line item that can be defended in a budget review, and the asset persists after the engagement.
An open hour count is difficult to forecast and harder to defend when finance asks what next year looks like.
Predictability is not a luxury in public and regulated budgeting — it frequently determines whether a programme continues at all.
For a short, specialist intervention with a clear end, hourly rates are simple and appropriate.
Over several years an open hour count compounds, while a licence plus compute stays a defensible, forecastable line item.
Budget defensibility often decides continuation. A ceiling is worth more than a lower unit rate.
Comparing rate cards compares inputs. Compare the total cost to a working outcome, including what you own at the end.
Timeline: Four to eight weeks for a typical in-flight engagement
Timeline: Days to weeks to contract
ibl.ai is the agentic AI platform where you own all the code and the data. You self-host the entire stack inside your own perimeter, run it model-agnostic across any LLM and switch anytime, and pay by usage with no per-seat pricing — so you can deploy anywhere: your cloud, on-premise, GovCloud, or fully air-gapped.
ibl.ai is licensed flat rather than billed by the hour, and the licence includes the full source code running on your infrastructure. Cost is bounded by the compute you choose to run, not by how long an engagement takes. Engineering is still real — integration with your systems, agents specific to your workflows — but it starts from a platform already used by 1.6M+ users from 400+ organizations, so it is a fraction of the hours a from-scratch build consumes. You own all the code and the data, run it model-agnostic across any LLM, with no per-seat pricing, and can deploy anywhere including fully air-gapped.
Full source code under a perpetual license, running on your infrastructure. Not API access to someone else's platform — the stack itself is yours.
Run any LLM — Claude, GPT, Gemini, Llama, Command, or your own fine-tune — and switch providers without rewriting the platform.
Usage-based billing against a budget cap you set. Cost tracks what your organization actually uses, not how many people you employ.
Your cloud, your VPC, on-premise, GovCloud, or a fully air-gapped network with no outbound connectivity.
1.6M+ users across 400+ organizations run the platform this way, including NVIDIA, MIT, and Syracuse University.
ibl.ai is family-owned and operated from New York, NY — a U.S.-headquartered, domestically-owned long-term partner, not a vendor that sells licenses and moves on.
See how ibl.ai deploys AI agents you own and control—on your infrastructure, integrated with your systems.