The Internal Business Case | Agentic for Business

The proposal

What is being proposed.

Say this part plainly, because most internal resistance comes from people picturing something larger than what is actually on the table.

The systemA private AI system that performs defined work inside infrastructure your organisation controls. It is not a subscription to someone else's tool, and your data is not pooled with anyone else's.

The scopeOne workflow, or one decision that your people make over and over again. Narrow on purpose. A first build that tries to cover everything is a first build that proves nothing.

The starting pointA paid assessment before any build. It maps where the work actually goes, identifies the one workflow worth doing first, and produces the scope, the success measure and the fixed price for the build.

OwnershipYour environment, your sign-in, your keys. You own the data and the configuration. Export and handover are written into the contract from the start.

What it is notIt is not a company-wide programme, not a replacement for your existing systems, and not a request to commit to anything beyond the assessment.

Commercial structure

What it costs, and how it is structured.

No figure appears on this page, and no figure belongs in an internal note before the scope exists. What follows is the shape of the arrangement. Pricing follows the size and complexity of the operation and is settled in a conversation, once the assessment has defined the work.

A paid assessment

A defined, paid piece of work that produces the scope, the written success measure and the price for the build. The assessment fee is credited in full against the build if you proceed. If you do not proceed, the assessment is yours to keep and nothing further is owed.

A fixed-price build

One price, agreed in writing before any build work starts, billed by milestone. Each milestone has a deliverable you can inspect and a gate where you can stop. Anything outside the agreed scope is priced and approved separately, in writing.

A monthly managed operation

A monthly fee to run the system once it is live: monitoring, quality evaluation, incident response and change control. It is a service, ended under the terms in the contract, with export and handover if you end it.

Cloud and model consumption is billed to you directly, at cost, with no markup and a meter you can open at any time. Our margin is the build and the management, never a hidden spread on your usage.

Internal review

The three objections you will hear, and the answers.

Each of these is a reasonable objection. Take the answer into the room with you, and take the list of things to ask us for.

Finance

How do we know it will not overrun?

Because the number is not a guess, and because you hold a stop control at every stage.

The price is fixed, and it is scoped from a paid assessment rather than estimated from a first conversation.
Billing is by milestone, against deliverables you can inspect before you pay for the next one.
The success measure is agreed in writing before the build starts, so nobody argues later about what finished means.
There is a gate at the end of every phase. You can stop at a gate and keep everything produced up to that point.

Ask us for: the assessment scope, the milestone schedule, and the written success measure.

Technology

What happens when it breaks, and are we locked in?

Breakage is assumed, measured and handled. Lock-in is designed out, deliberately.

Every build ships with an evaluation harness that measures whether the system is still correct and whether its quality has drifted.
Production monitoring, cost caps and anomaly alerts run from the first release, on a dashboard your team can read without calling us.
A documented incident process, with defined severities, escalation and communication. Incidents are reported to you, not managed around you.
Documented exit, export and handover in the contract. Your organisation owns its data and its configuration. A system that traps you is a system we consider badly built.

Ask us for: the evaluation approach, a view of the monitoring dashboard, and the exit clause.

Risk and compliance

Where does our data go, and who approved what?

Four boundaries, disclosed separately and in writing, plus a complete record of every action taken.

Storage, processing, logging and support access are each disclosed on their own. We will not give you one blended residency claim, because a blended claim hides the boundary that matters.
A written data-flow schedule sits in the contract: what enters the system, where each copy is stored, what processes each field, which region may receive it, retention and deletion.
Approval gates stop anything that sends externally, commits money or changes a record that matters. Gates are policy. The system cannot approve its own work.
Every important action is recorded: what was done, by which agent, on whose approval, with what data. The log is exportable for audit, with retention rules your compliance team sets.

Ask us for: the security pack, the data-flow schedule, and a sample action log. Your standard vendor questionnaire is welcome.

The decision

What we are asked to approve.

This is the entire decision in front of the room today.

Approval of one paid assessment. That is the whole request.

Not a programme, not a platform commitment, and not a change to any system you run today.

The assessment produces a scope, a written success measure and a fixed price for the build.

The build is a separate decision, taken later, with those three things on the table.

The assessment fee is credited in full against the build if you proceed.

If the assessment concludes that the work does not justify a build, we will say so in writing. That is a valid outcome, and a far better place to learn it than halfway through a build.

Diligence

How to check us.

You are not required to take any of this on trust. Three things are published, and your reviewers can read them before anyone speaks to us.

The platform we run ourselvesWe designed, built and operate Gulf Commercial Insights, a production intelligence platform with real users, not a demonstration. The build story sets out the architecture, the things that went wrong and what we changed. Gulf Commercial Insights is commercial diligence intelligence, not investment advice. Read the build story

Security and governanceThe four boundaries, the autonomy levels, action logging, incident response and handover are written down and public. Send that page to your security reviewer before you send anything to us. Read the security posture

JurisdictionBoost My Business AI Innovation Limited, Trade Licence CL11954, DIFC Innovation Hub, Dubai International Financial Centre. Registered in the DIFC as a technology company. Not a regulated financial services firm.

Test us directlySend your standard security and vendor questionnaire, or bring your risk and technology leads to the briefing. We would rather meet the hard questions in the first meeting than in the third. We reply within one business day.

The internal case, on one page.