01 / FEATURE
2–3 embedded senior engineers
Named individuals, full-time on your engagement. Inside your repos, your stand-ups, your code reviews, not a far-away agency silo. A delivery manager keeps the workstream on cadence.
Deploy, production AI with an SLA you can hold us to.
For enterprise teams running mission-critical AI in production. Two to three embedded engineers, full FORGE methodology, monitoring, governance, and on-call support. SGD 35,000/month over 6–12 months. Up to 50% government co-funded.
The engagement
A production system and the people who run it.
Deploy is for organisations that have validated the use case and now need a system that runs reliably, with governance, observability, an SLA, and a named team behind it. Not a pilot. Not a prototype handed over a wall. A live system, monitored from day one, accountable to outcomes your CIO and CISO can both sign off on.
What's included
Ten workstreams under a single monthly engagement, engineered, governed, monitored, and accountable to a written SLA.
02 / FEATURE
Full FORGE methodology
ASSESS → ARCHITECT → BUILD → OPERATE applied end-to-end, with phase gates, written deliverables, and a documented evidence trail your auditors will thank you for.
03 / FEATURE
Production-grade architecture
CI/CD pipelines, infrastructure-as-code, automated testing, and rollback strategy included from sprint one. Nothing ships that can't be redeployed in fifteen minutes.
04 / FEATURE
Service Level Agreement
Written uptime, latency, and incident-response targets with financial remedies. Typical SLAs: 99.9% availability, P99 under 800ms, P1 response under 30 minutes. Negotiated to your context.
05 / FEATURE
Monitoring & observability from day one
Dashboards, alerting, distributed tracing, and AI-specific telemetry (drift, hallucination rate, cost per request) live before the system goes live. Not a follow-up project.
06 / FEATURE
On-call support
Business-hours or 24/7 coverage, your choice. Pages route to named humans, not auto-responders. Post-incident reviews delivered in writing within five business days.
07 / FEATURE
Governance & compliance built in
AI Verify aligned, NIST AI RMF mapped, OWASP LLM Top 10 hardened, PDPA controls in place. Evidence pack delivered alongside the system, not bolted on after launch.
08 / FEATURE
Continuous optimisation
Monthly tuning cycles on accuracy, latency, and unit cost, with written reports, measurable deltas, and quarterly business reviews with your sponsors.
09 / FEATURE
Knowledge transfer & runbooks
Every system ships with operating runbooks, architecture decision records, and a four-week handover plan. Your team can run it independently the day we leave.
10 / FEATURE
Up to 50% co-funded
Eligible for IMDA co-funding in Singapore and equivalents across Malaysia, Indonesia, the Philippines, and Thailand. We handle the paperwork end-to-end.
The Framework
A 6–12 month engagement, in four governed phases.
Production from day one means we ship operability before features. The first system goes live in month four; optimisation starts immediately after.
PHASE 01
ASSESS
Months 1–2. Use-case validation, data audit, governance gap analysis, success-metric definition, and SLA scoping with your sponsors and security team.
Deliverable
Readiness scorecard + SLA spec
PHASE 02
ARCHITECT
Months 2–3. Reference architecture, governance controls mapped, security model reviewed by your CISO, and a sprint-by-sprint build plan with named owners.
Deliverable
Architecture blueprint + build plan
PHASE 03
BUILD
Months 3–6. Dual-workflow sprint engineering, CI/CD pipelines, observability stack, human-in-the-loop validation. Production launch with monitoring live.
Deliverable
Production system + dashboards
PHASE 04
OPERATE
Months 6–12. SLA-backed operation, on-call coverage, monthly optimisation cycles, quarterly business reviews, and a documented handover when you're ready.
Deliverable
Live system + trained ops team
Ideal for
Deploy fits enterprises moving validated use cases into mission-critical production, where uptime, governance, and accountability matter as much as features.
Enterprise CIOs & CTOs
Technology leaders who need to put AI in front of customers or core operations and cannot accept best-effort uptime or ungoverned outputs.
99.9% SLA
Mission-critical workloads
Customer-facing systems, revenue-generating workflows, and regulated processes where downtime or wrong answers carry real commercial consequence.
P1 < 30 min
Regulated industries
Financial services, healthcare, insurance, and public sector, where AI Verify, NIST, MAS, and PDPA evidence is required before go-live.
Audit-ready
Post-Accelerate graduation
Teams who validated the use case under Accelerate and now need production-grade infrastructure, SLAs, and on-call coverage to scale safely.
Scope inherited
Replacing in-house gaps
Organisations with strong product and data teams but without senior AI engineering, Deploy fills the gap without the 6-month hire cycle.
Onboard in 2 weeks
Multi-system rollouts
Companies running 2–4 production AI systems in parallel, RAG knowledge bases, agentic workflows, vision pipelines, under one delivery team and one SLA.
1 contract
We had a working RAG prototype that nobody trusted in production. EIS deployed two engineers, rebuilt it on Neo4j with proper observability, and put a real SLA behind it. Accuracy jumped from 71% to 96%, P99 latency dropped under 600ms, and our ops team now sees every drift event before our customers do. Eight months in, and the system has paid for itself twice.
Director of Digital Platforms · Regional Bank · 12-month Deploy engagement
FAQ
Deploy, frequently asked
How the SLA works, how on-call is structured, what happens at month 12, and how co-funding flows.
Q01What does the SGD 35,000/month actually cover?
A named team of 2–3 senior engineers full-time, a fractional delivery manager, full FORGE methodology, production infrastructure design, monitoring stack, written SLA, business-hours on-call, monthly optimisation cycles, and quarterly business reviews. 24/7 on-call and additional engineers are quoted on top.
Q02How is the SLA structured and enforced?
Every Deploy engagement ships with a written SLA covering uptime, P50/P99 latency, P1/P2 incident response times, and AI-specific quality metrics (accuracy thresholds, drift bounds). Targets are negotiated against your business context. Misses trigger service credits against the next month's invoice, typically 10–25% per qualifying incident, capped at 100%.
Q03Is on-call business-hours or 24/7?
Business-hours coverage (8am–8pm SGT, Mon–Fri) is standard. 24/7 coverage with a 30-minute P1 response is available as an add-on, typically SGD 8,000–12,000/month depending on system complexity. Either way, pages route to named humans on the EIS team, not a generic queue.
Q04Do we own the code, models, and IP?
Yes, everything we build is yours from the moment it's committed. Source code, architecture decision records, model weights (where applicable), runbooks, and all documentation. EIS retains no commercial rights to client work.
Q05Can we co-fund Deploy under IMDA or equivalent?
Yes, Deploy is eligible for up to 50% co-funding under IMDA in Singapore and equivalent schemes across Malaysia (MDEC), Indonesia, the Philippines, and Thailand. We assess eligibility in the first scoping call and handle paperwork end-to-end. Approval typically lands in 4–6 weeks.
Q06What happens at month 12, does the engagement end?
Three options. (1) Hand-over: we run a four-week transition, your team takes over operations, we step back. (2) Extend Deploy: continue at the same monthly rate against new outcomes. (3) Graduate to Evolve: scope expands across business units under a multi-year transformation contract. Your call, agreed at the month-9 review.
Q07Can we start with Deploy directly, or do we need Ignite/Accelerate first?
You can start with Deploy directly if the use case is validated and the data is ready. If either is uncertain, we usually recommend a 2–4 week AI Sprint up front, fixed scope, fixed fee, to de-risk the architecture before committing to 6–12 months.
Q08How fast can a Deploy team onboard?
Two weeks from contract signature to first sprint, typical. Engineers are named, security clearance and laptops are pre-staged, and the ASSESS phase begins in week one. We do not staff from a bench after the contract, your team is identified during scoping.
Scope a Deploy engagement.
30-minute call to size the team, define the SLA, and confirm co-funding eligibility. We'll also tell you honestly if a smaller engagement should come first.
Start Deploy
30 minutes · reply within 1 business day