Built for large programmes
Programmes, not just projects.
Large programmes carry board-level stakes: significant investment, firm commitments and many teams to align. They need more than good engineers. They need governance you can audit, stage gates you control, security and reporting your board and executive team can rely on, and one accountable partner from the first circuit board to the last dashboard.
Why Intellobots
What changes when one team owns the whole programme
01
One accountable team, every layer
Hardware, firmware, cloud, data, AI, apps and integration under one programme lead. No finger-pointing between vendors at the joins.
02
We've run programmes for the Indian Army
Three systems across 16 ECHS polyclinics, launched on Army Day, felicitated by the GOC and briefed to Army HQ.
03
We build and run our own products
ThingsX labels, gateways and cloud are designed, built and supported by us, so we know what production really takes.
04
Enterprise discipline, startup speed
Decades of enterprise architecture and SAP experience in leadership, with a team that ships working software every week.
Governance
Decisions at the right level, on a rhythm you can plan around
Steering committee
Your sponsor · our Managing Director and CEO
Scope, budget, priorities and stage-gate decisions
Monthly, and at every gate
Programme office
Programme manager · solution architect · your product owner
Plan, risks, dependencies, change control and reporting
Weekly
Workstreams
Hardware · firmware · cloud & data · AI · apps · QA · rollout
Build, test and deliver in two-week increments
Daily stand-ups, demo every sprint
What you get every week and month
- Programme charter and RACI
- Integrated plan with milestones and critical path
- RAID log (risks, assumptions, issues, dependencies)
- Change-request log with impact on scope, time and cost
- Weekly status: progress, burn-up, quality, risks
- Monthly executive review pack
Stage gates
You commit one stage at a time
2–4 weeks
Discover
Requirements, current-state map, success metrics, risks, solution options
Gate: Scope and business case signed off
3–6 weeks
Design
Architecture, security design, hardware and data plan, integration contracts, release plan
Gate: Architecture and plan approved
Increments of 2 weeks
Build
Working software and hardware every sprint, demoed to your team
Gate: Feature-complete for the release
2–6 weeks
Validate
System and integration testing, UAT, performance and security tests, certification, pilot site
Gate: Acceptance criteria met and signed
Phased
Roll out
Site-by-site deployment, data migration, training, hypercare
Gate: Each wave accepted before the next
Ongoing
Run & improve
SLA support, monitoring, updates, quarterly roadmap reviews
Gate: SLA reports and service reviews
Your first 90 days
From signature to a working thin slice
Week 0
Mobilise
NDA, charter, RACI and access. Programme manager and architect named; kick-off with your sponsors.
Weeks 1–4
Discover
Workshops, site visits and system walkthroughs. Current-state map, risks and success metrics agreed.
Weeks 5–8
Design & prove
Target architecture, security design and a working thin slice through every layer, demoed end to end.
Weeks 9–12
Plan the build
Release plan, budget baseline and stage gates locked. First increments in your environments.
Security & quality
Evidence your leadership, security and audit teams can check
Secure development
Code review on every change, automated dependency and vulnerability scanning, secrets kept out of code, signed releases.
Access & data protection
Least-privilege access, SSO and MFA, encryption in transit and at rest, data kept in your cloud and region.
Device security
Secure boot, signed over-the-air updates, per-device credentials and encrypted links from device to cloud.
Testing before go-live
Penetration testing before launch (by an independent firm when you need it), with findings fixed and retested.
Privacy by design
Practices aligned with India's DPDP Act and GDPR principles: purpose limits, minimal data, retention and audit trails.
Quality management
ISO 9001:2015 certified quality management, with documented reviews, test evidence and traceability.
Support after go-live
The team that built it keeps it running
L1 · Service desk
Logging, triage, known fixes and user help, through your channel of choice.
L2 · Application & device support
Configuration, data fixes, device swaps, root-cause analysis.
L3 · Engineering
Code and firmware fixes by the team that built it, released through the same pipeline.
| Priority | Meaning | How we respond |
|---|---|---|
| P1 | Service down or safety risk | Immediate response, continuous work until restored |
| P2 | Major function impaired | Same-day response, workaround then fix |
| P3 | Minor issue | Next-business-day response, fix in a scheduled release |
| P4 | Request or question | Planned into the backlog |
Response and resolution targets per priority, support hours (business hours or 24×7) and service credits are written into the contract.
Commercials & contracts
Ways to buy, and terms that protect you
Fixed price per stage
A fixed price and scope for each stage gate. You commit one stage at a time.
Milestone-based
Payments tied to accepted milestones, not to hours spent.
Dedicated programme team
A named, cross-functional team at a monthly rate, with a ramp plan agreed up front.
Time & materials
For discovery and evolving scope, with weekly timesheets and a budget cap.
Managed service
Devices, platform and support as one service with SLAs.
In every contract
- NDA before discovery
- The IP we build for you belongs to you
- Source code in your repositories from day one
- Documented handover and knowledge transfer
- Change control with impact on scope, time and cost
- Acceptance criteria agreed before each stage
Risk
The risks that sink large programmes, and what we do about them
Integration surprises
A thin slice through every layer in the first 8 weeks, against your real systems.
Hardware lead times and certification
Long-lead parts ordered at design, pre-compliance tests in our lab before formal certification.
Scope creep
Change control with visible impact, and a steering committee that decides.
Adoption
Pilot with real users, training and hypercare planned into every rollout wave.
Key-person dependency
Pairing, documentation and code reviews, so knowledge never sits with one person.
Vendor lock-in
Your cloud, your repositories, open standards and a documented exit plan.
What we report on
Next step
Planning something big?
Start with a 30-minute architecture call with our leadership. You'll leave with a view on approach, risks and the first stage, whether or not we work together.