Our Delivery Framework
Build, Operate and Transfer
Most enterprise software leaves you with one of two bad outcomes. Either you rent a product forever and never own anything, or you commission a custom build that nobody can maintain after the team that wrote it moves on.
BOAT is our answer to both. We build the system, we operate it alongside your team while it earns its keep, and then we transfer it to you — documented, source code included, on your own infrastructure.
Why We Work This Way
The two ways enterprise software usually goes wrong
Buy a product
- Built for the average company in your industry
- You change your process to fit the software
- The thing that makes you different stays in a spreadsheet
- Priced per seat, so cost grows with headcount
- Rented forever; you never own anything
- Its AI can only see its own data
Commission a custom build, the old way
- Runs into quarters, sometimes years
- Costs more than most mid-market firms will approve
- Becomes legacy before it is paid off
- Poorly documented, so only the original team can touch it
- If the partner disappears, you are stranded
- No plan for who owns it at the end
Build, Operate and Transfer keeps what is good about both. You get a system built around your business, delivered in weeks because most of the platform already exists, run by people who built it during the year that matters — and then handed to you, so the dependency ends by design.
The Framework
What actually happens in each phase
Build
Assessment 2 weeks, then weeks to liveWe start by understanding what you run today and what it costs you — not in principle, but in your actual numbers. Then we build the system on your infrastructure, under your name, and get it in front of real users quickly rather than at the end.
What we do
- Map every system, subscription and spreadsheet the business currently depends on, and what each one costs
- Identify where money, time and effort are leaking today, in your own figures
- Define the modules, roles, stages and rules that reflect how you actually operate
- Configure the proven platform spine, then build the part that is unique to your business
- Deploy on your cloud, on your domain, under your own product name
- Build web and mobile together, so field and site users are included from day one
- Integrate with the finance, ERP or other systems you have a genuine reason to keep
- Migrate the historical data that matters and leave behind the data that does not
What you have at the end of Build
A working system your people can use, and the plan and business case behind it.
Operate
Year oneA system nobody uses is worse than no system, because now you are paying for both. The Operate phase is where the return actually appears, and it is the phase most vendors skip.
What we do
- Run the platform with your team, with support included
- Drive adoption to the last user, including field, site and shop-floor staff
- Train the people who will eventually own it, from the administrator down to the daily user
- Watch how the system is really used and refine the workflows that get avoided
- Add the AI use cases that pay back first, once there is enough clean data for them to work on
- Track the measures agreed at the start, and report against them honestly
- Handle changes, exceptions and the things nobody thought of during Build
What you have at the end of Operate
A system your people genuinely use, and evidence of what it returned.
Transfer
Year two onwardTransfer is not an exit clause buried in an annexure. It is the point of the whole engagement. From year two we step back on a defined schedule and your team steps forward.
What we do
- Fixed annual maintenance at an agreed fee, with a defined scope
- Structured, phased handover to your team rather than a single handover meeting
- Complete technical documentation, architecture notes and runbooks
- Knowledge transfer sessions and shadowing for your developers and administrators
- Full source code transfer, with repository ownership moved to you
- Support arrangements that taper as your team takes over, at your pace
What you have at the end of Transfer
Ownership, with no dependency on us.
Ownership
The questions every buyer asks us
Where does it run?
On your cloud, on your domain, under your own name. Your data stays in your environment.
What if Ambilio goes away?
You have repository access from day one. Nothing about the system depends on us continuing to exist.
Will it become outdated?
It is built on mainstream, well-supported technology with no proprietary runtime, so you are never frozen on a version you cannot upgrade.
Who can maintain it?
We do first, then your team, with full documentation. Any competent engineering team can take it forward.
Whose software is it?
Yours. The source code transfers to you and the platform carries your name, not ours.
What if we want to leave early?
Transfer can be brought forward. The handover process is the same, only the timing changes.
Where We Apply It
BOAT works wherever the operating system is a spreadsheet
The framework does not change by industry. What changes is what we build during the Build phase — the entities, the stages, the compliance rules and the language your people already use. These are the sectors where the pattern repeats most strongly.
Banking and financial services
Where it hurts
Case and request handling spread across email, spreadsheets and core systems, with reconciliation and regulatory reporting done manually.
What we build
A single operations layer over the core system, with case lifecycle, maker-checker approvals, audit trail, and reporting that assembles itself.
Insurance
Where it hurts
Policy servicing, claims and channel-partner management running in disconnected tools, with turnaround times nobody can prove.
What we build
End-to-end claim and servicing workflow with document intelligence, SLA tracking and partner performance visibility.
NBFCs and lending
Where it hurts
Origination, credit assessment, disbursal and collections handled in separate systems, with no single view of a borrower.
What we build
One borrower view across origination to collections, with document verification, exception routing and portfolio-level early warning.
Manufacturing
Where it hurts
Planning, procurement, quality and maintenance data trapped in separate systems and shop-floor registers.
What we build
Production, purchase and quality on one platform, with mobile shop-floor capture, three-way matching and downtime visibility.
Engineer-to-order and capital equipment
Where it hurts
Every order is a project, but the ERP only understands products, so project margin lives in spreadsheets.
What we build
Order-as-project tracking from estimation through manufacture, site installation and commissioning, with live margin per order.
Construction, EPC and interior fit-out
Where it hurts
Estimation, procurement, subcontractors, running bills and site progress spread across files, email and chat, with cash position known only after month end.
What we build
Full project lifecycle from enquiry to handover — budgets, commitments, RA billing with statutory deductions, subcontractor and labour tracking, geotagged site capture and a client progress view.
Real estate and facility management
Where it hurts
Multiple sites, contracts and service schedules managed by whoever remembers them, with breaches discovered only when a client complains.
What we build
Contract, asset and service-schedule management with preventive maintenance, ticketing, SLA alerts and site-level cost visibility.
Logistics and supply chain
Where it hurts
Bookings, fleet, driver and vendor information sit in different places, and exceptions surface only after the customer notices.
What we build
Consignment lifecycle, vendor and fleet management, proof of delivery capture, and exception alerts routed to an owner.
Healthcare, hospitals and diagnostics
Where it hurts
Clinical systems are covered, but procurement, maintenance, compliance and multi-site administration are not.
What we build
The non-clinical operating layer — purchase, biomedical asset maintenance, accreditation documentation and multi-site reporting.
Pharmaceuticals and life sciences
Where it hurts
Compliance-heavy processes evidenced through documents and email, with audit preparation becoming a project of its own.
What we build
Controlled workflows with electronic evidence, versioned documentation, deviation tracking and audit-ready trails.
Retail, distribution and dealer networks
Where it hurts
Head office cannot see what is happening at outlets and dealers without asking for it.
What we build
Outlet and dealer operations, claims and scheme settlement, field visit capture, and stock and performance visibility by location.
IT services and global capability centres
Where it hurts
Delivery, staffing, utilisation and client reporting spread across tools that each hold a fragment of the picture.
What we build
Engagement and resource lifecycle with utilisation, effort and margin per account, and client reporting that generates itself.
Professional services — consulting, legal and accounting
Where it hurts
Time, engagements, billing and compliance tracked separately, so realisation is only understood after invoicing.
What we build
Engagement lifecycle from proposal through delivery to invoice, with effort capture, realisation and deadline tracking.
Education and training institutions
Where it hurts
Admissions, fees, academic delivery, compliance and placements spread across systems that do not reconcile.
What we build
The student lifecycle end to end, with fee and compliance tracking, faculty workload and multi-campus reporting.
Energy, utilities and renewables
Where it hurts
Project execution, subcontractors, site commissioning and asset performance managed separately from finance.
What we build
Project and site execution with milestone billing, subcontractor management, commissioning checklists and asset performance monitoring.
Agriculture and agri-processing
Where it hurts
Procurement from a dispersed supplier base, quality grading and payments recorded on paper before reaching any system.
What we build
Mobile procurement and grading capture, supplier ledgers, payment workflows and traceability from source to processing.
Hospitality and multi-location services
Where it hurts
Every location runs slightly differently, and head office only sees the financial result, not the operation.
What we build
Standardised operating checklists, purchase and maintenance workflows, and location-level performance comparison.
Public sector, cooperatives and member organisations
Where it hurts
Process is heavily governed, but the evidence lives in files and registers, making transparency and audit slow.
What we build
Governed digital workflows with permissions, complete audit trails, member and citizen self-service and public reporting.
If your industry is not listed, the question is simply whether your business runs on stages, approvals, money and evidence. Almost all of them do.
Deliverables
What you have in hand at each stage
| Phase | Timeframe | What you receive |
|---|---|---|
| Assessment | 2 weeks | Current system and cost map, leakage analysis in your own numbers, module map, build plan, business case |
| Build | Weeks | Live platform on web and mobile, on your cloud and domain, integrations, migrated data, trained core users |
| Operate | Year one | Support, adoption across all user groups, workflow refinement, AI use cases in production, reporting against agreed measures |
| Transfer | Year two onward | Fixed-fee maintenance, phased handover, complete documentation and runbooks, knowledge transfer, full source code and repository ownership |
Assessment
2 weeksCurrent system and cost map, leakage analysis in your own numbers, module map, build plan, business case
Build
WeeksLive platform on web and mobile, on your cloud and domain, integrations, migrated data, trained core users
Operate
Year oneSupport, adoption across all user groups, workflow refinement, AI use cases in production, reporting against agreed measures
Transfer
Year two onwardFixed-fee maintenance, phased handover, complete documentation and runbooks, knowledge transfer, full source code and repository ownership
The assessment is a paid, standalone engagement and is adjusted against the build if you proceed. You keep the findings either way.
Commercials and Governance
Structured so that neither side is trapped
Fixed-scope assessment
A defined two-week engagement with defined outputs, priced separately and adjusted against the build if you go ahead.
Fixed-price build
Scope, modules and timeline agreed in writing before work starts, so the build does not drift into an open-ended project.
Annual maintenance, agreed in advance
A fixed fee with a defined scope from year two, so the ongoing cost is known before you commit to anything.
Measures agreed at the start
We agree upfront which measures the engagement will be judged on, and we report against them rather than around them.
