25%
of respondents have moved 40% or more of their AI pilots into production.
Deloitte, 21 January 2026Survey of 3,235 leaders in 24 countries, August to September 2025
Delivery process
How We Work: From AI Assessment to Managed Support
REIT Limited, a Bangladesh-based AI services and technical-delivery company, delivers in stages. Each stage has a purpose, inputs from you, outputs from us, evidence that it is complete, and a named person who approves the move to the next one.
The process in brief
An engagement moves from discovery to workflow design, prototype, evaluation, approval, controlled launch and handover, followed by optional ongoing support. You can stop or re-scope after any stage. Nothing reaches production until the acceptance checks agreed at the start have been met.
How long does a first engagement take?
A typical first engagement runs about 18 weeks from assessment to steady support: one week of assessment, a four-week pilot, a one-week evaluation and decision, about eight weeks of implementation, then launch and handover.
- AI assessment1 week
- Scoped pilot4 weeks
- Evaluation and decision1 week
- Production implementation8 weeks
- Launch and handover1 week
- Managed support3 weeks
View data table
| Stage | When |
|---|---|
| AI assessment | weeks 1 to 1 |
| Scoped pilot | weeks 2 to 5 |
| Evaluation and decision | weeks 6 to 6 |
| Production implementation | weeks 7 to 14 |
| Launch and handover | weeks 15 to 15 |
| Managed support | weeks 16 to 18 |
Sample data
22%
of organisations have successfully scaled AI across multiple business units or adopted an AI-first approach.
Gartner, 1 September 2026Survey of 1,303 organisations with at least USD 50 million revenue, January to April 2026
40%+
of agentic AI projects will be cancelled by the end of 2027 because of escalating costs, unclear business value or inadequate risk controls, Gartner predicts.
Gartner, 25 June 2025Analyst prediction, not a measured result
What happens at each delivery step?
The five phases contain eight delivery steps: discovery, workflow design, prototype, evaluation, approval, controlled launch, handover and ongoing support. Each step has a purpose, inputs from you, outputs from us, evidence that it is complete and a named approver.
Discovery is the AI assessment; design and prototype make up the scoped pilot; approval, controlled launch and handover belong to production implementation.
| Step | Purpose | Client inputs | REIT Limited outputs | Acceptance evidence | Approved by | Next step or stop |
|---|---|---|---|---|---|---|
| Discovery | Decide whether the process is worth improving and feasible. | A description of the process, access to the people who run it, the systems involved. | A process and dependency map, constraints, and a recommendation to proceed, prepare or stop. | You confirm the map is accurate. | Your process owner | Proceed to design, or stop if the fit is poor. |
| Workflow design | Fix the path before anything is built. | Approval rules, exceptions, access details. | A design showing triggers, steps, approval points, data used and acceptance checks. | The design and acceptance checks are signed off. | Your process owner | Proceed to prototype, or revise the design. |
| Prototype | Show the design working on representative cases. | Sample cases and test accounts. | A working prototype in a test environment. | The prototype runs the sample cases end to end. | REIT Limited delivery lead | Proceed to evaluation. |
| Evaluation | Measure the prototype against the agreed checks. | Reviewers to judge outputs; expected results. | Test results, findings, limitations and a go or no-go recommendation. | Results are compared with the acceptance checks. | Your process owner | Approve, re-scope, or stop. |
| Approval | Make the production decision deliberately. | A decision-maker with authority over the process. | A release plan with a rollback route and operating responsibilities. | Written approval to launch. | Your decision-maker | Proceed to launch. |
| Controlled launch | Release without disrupting operations. | Production access and a launch window. | The system live for an agreed scope, monitored closely. | Launch checks pass and no rollback is triggered. | Both parties | Proceed to handover. |
| Handover | Leave your team able to run it. | The people who will operate the system. | An operating guide, access records, a handover session. | Your team operates a live case unaided. | Your operating owner | Close the project or start support. |
| Ongoing support | Keep the system reliable after launch. | A support contact and change approver. | Monitoring, incident handling, controlled changes and maintenance reports. | Reports against the agreed support scope. | Your operating owner | Review at the agreed interval. |
What does each engagement model cost?
There are five engagement models. The AI assessment costs USD 500. A scoped pilot is priced from USD 2,500, a production implementation from USD 6,000, managed support from USD 600 per month and a dedicated technical team from USD 3,200 per month.
AI assessment
USD 500
5 working days
One process reviewed for fit, dependencies and risk.
- Process map and data check
- Feasibility of each integration
- Fixed-scope pilot proposal
Scoped pilot
from USD 2,500
3 to 4 weeks
One bounded use case built and tested on real cases.
- Working workflow, agent or module
- Acceptance checks agreed first
- Evaluation report
Production implementation
from USD 6,000
6 to 10 weeks
The accepted pilot hardened, connected and launched.
- Monitoring, logging and rollback
- Operating guide and training
- Handover or support start
Managed support
from USD 600 per month
Monthly, cancel with notice
Monitoring, changes and incidents under agreed targets.
- Monthly service report
- Controlled releases
- Response targets by priority
Dedicated technical team
from USD 3,200 per month
Monthly, cancel with notice
Named engineers working to your backlog.
- Engineer plus delivery lead
- Weekly demonstration
- One-month notice
Sample pricesPrices exclude third-party licences, model usage and taxes. The proposal sets the final price for your scope. Invoices are issued in USD; GBP, EUR and AUD are available on request.
| Included in the price | Billed separately |
|---|---|
| Design, build, testing and documentation within the agreed scope | Third-party software licences and automation-tool subscriptions |
| Acceptance testing against the agreed checks | AI model usage charged by the model provider |
| Operating guide and one handover session | Hosting and infrastructure in your own accounts |
| Thirty days of launch support after go-live | Work outside the agreed scope, quoted as a change request |
What each engagement stage costs and delivers
Implementation is a one-off cost. Tool and model usage and support are recurring. The proposal shows them separately.
| Stage | Decision it resolves | Outputs to confirm | Cost categories | Indicative price |
|---|---|---|---|---|
| Assessment | Is this process feasible and worth improving? | The highest-value process to automate first, an estimate of time saved and operational risk, a dependency map, a roadmap and a fixed-scope pilot proposal, or a reason not to proceed. | Assessment effort and any agreed discovery access. | USD 500, 5 working days |
| Scoped pilot | Does one bounded use case meet the agreed checks? | Prototype, representative test cases, findings, limitations, go or no-go recommendation. | Pilot work, third-party licences and API usage, your review time. | from USD 2,500, 3 to 4 weeks |
| Production implementation | Is the agreed system ready for controlled use? | Approved integrations, release and rollback plan, operating documentation, handover. | Build and integration work, hosting, vendor usage, agreed change requests. | from USD 6,000 |
| Ongoing support | Who keeps the system operable? | Defined coverage, monitoring, incident and change process, maintenance reports. | Support scope, recurring tools and usage, separately agreed improvements. | from USD 600 per month |
The first paid step is the assessment. An enquiry is not an appointment, an assessment is not a commitment to a pilot, and a pilot is not a commitment to production. Additional workflows, connections, channels and hours of cover change the scope and the price.
Which delivery option suits your business?
What each option requires of you. None is right for every business.
| What it requires | Delivery partner such as REIT Limited | In-house hire | Freelancer | Leave the process as it is |
|---|---|---|---|---|
| Your time | Process owner's time for discovery, review and approval | Hiring, onboarding and management | Close direction and review of one person | The current manual effort continues |
| Skills you must supply | Knowledge of your own process | Technical leadership to direct the work | Scope, testing and continuity planning | None beyond today's |
| Time to start | After a one-week assessment | After recruitment | Often within days | Not applicable |
| Continuity risk | Covered by a team and a support arrangement | Depends on retaining the person | Depends on one person's availability | Depends on staff who know the manual steps |
| Ownership of the work | Set out in the proposal before the pilot | Yours by employment | Set by the freelance contract | Not applicable |
| Cost of leaving | Handover session, guide and export of the work | Notice period and knowledge transfer | Whatever documentation exists | None |
| Good fit when | The need is defined and the process owner is available | AI work will be continuous and central | The task is small and self-contained | Volume is low and errors are cheap |
Ownership, access and exit
Before a pilot starts, the proposal should state who owns and can export each of the following, and how access is removed at the end:
- Client data and the accounts it lives in
- Custom code, workflows and prompts
- Third-party software and licences, with their own terms
- Documentation and operating guides
- Export formats and the handover of credentials
Accounts and data remain the client's. Terms for custom work and third-party components vary by project, so they are written into each proposal and not promised on this page.
Working with a team in Dhaka
REIT Limited works from Dhaka, Bangladesh (GMT+6). Office hours are Sunday to Thursday, 09:00 to 18:00 Bangladesh time (GMT+6), which overlaps with 09:00 to 12:00 UK time (to 13:00 during British Summer Time). Project communication runs in English through the channel agreed in the proposal, with a named delivery contact, scheduled review calls and written summaries after each one.
Client data is handled inside the client's own accounts wherever possible. Where any processing takes place elsewhere, the proposal says where and why. See the Privacy Notice for how this website handles enquiry data.
- REIT Limited at work (09:00 to 18:00 Dhaka)
- Your 09:00 to 17:00 working day
- DhakaGMT+6, office time09:00 to 18:00
- LondonGMT (GMT+1 in summer)03:00 to 12:00
- BerlinCET (CEST in summer)04:00 to 13:00
- DubaiGST07:00 to 16:00
- New YorkEST (EDT in summer)22:00 to 07:00
- SydneyAEST (AEDT in summer)13:00 to 22:00
View data table
| City | REIT Limited office hours in local time |
|---|---|
| Dhaka | 09:00 to 18:00; overlap with a 09:00 to 17:00 day: 09:00 to 17:00 (8 h) |
| London | 03:00 to 12:00; overlap with a 09:00 to 17:00 day: 09:00 to 12:00 (3 h) |
| Berlin | 04:00 to 13:00; overlap with a 09:00 to 17:00 day: 09:00 to 13:00 (4 h) |
| Dubai | 07:00 to 16:00; overlap with a 09:00 to 17:00 day: 09:00 to 16:00 (7 h) |
| New York | 22:00 to 07:00; overlap with a 09:00 to 17:00 day: none in office hours |
| Sydney | 13:00 to 22:00; overlap with a 09:00 to 17:00 day: 13:00 to 17:00 (4 h) |
Calculated from UTC offsets in standard time. In local summer time the blue bar starts one hour later in London, Berlin, New York and Sydney.
Sample office hoursTo prepare for the first conversation, use the Workflow Scoping Checklist and read the AI Project Buyer Guide. Services are listed on the Services page.
Questions buyers ask
How do an assessment, a pilot and ongoing support differ?
An assessment decides whether one process is feasible and worth improving, and produces a map and a recommendation. A pilot builds one bounded use case and tests it against agreed checks. Ongoing support keeps a launched system reliable through monitoring, incident handling and controlled changes. Each is scoped and priced separately.
What must the client prepare before an assessment or pilot?
A description of one process: its trigger, inputs, systems, exceptions, approvals and outputs. You also need a process owner who can answer questions, and access to the systems involved. The workflow scoping checklist in Resources lists each item. Sensitive sample data is exchanged only by an agreed secure method.
Who owns the code, prompts and workflows after handover?
Client data and accounts remain the client's. Ownership and licence terms for custom code, workflows and prompts are set in the proposal, along with third-party licence limits, export options and how access is revoked. Buyers should read those terms before the pilot begins.
How does remote communication work across time zones?
Work is planned around the overlap between Dhaka office hours and yours. A named delivery contact, scheduled review calls and written summaries keep decisions on record. Response and support hours are stated in the proposal for each engagement.
Start with an assessment
One process, one recommendation, and a clear decision about whether to go further.
- Assessment before any build
- A person approves customer-facing actions
- Registered in Bangladesh, RJSC No. C-169247/2021