| Capability | Mechanism | Scale / standard |
|---|---|---|
| CMS roles | Administrator, Publisher, Editor — with a review → preview → approval workflow before anything publishes | Role-based access control |
| Content model | Post/announcement with title, description, slug, date; one post can map to multiple categories; Draft / Published / Archived | Archive hides from public, retains in DB |
| Migration & sync | ~30,000+ pages and ~97,000+ resources migrated with existing URLs preserved | See Delivery → Migration |
ICAI Digital Transformation
Reimagining the Digital Future of ICAI
We propose a unified digital ecosystem — connecting ICAI.org, the Unified CMS, ICAI NOW and an Enterprise AI Assistant into one intelligent platform.
Delivered by
Sarvika Technologies
12+ years building enterprise digital platforms — we propose to build this as a digital transformation partner working across enterprise web, mobile and AI platforms since 2013.

Today's Digital Reality
The Cost of Fragmentation
The starting point for this transformation.
Disconnected by Design
Website, CMS, mobile and AI evolved separately — three systems, three teams, no shared source of truth.
Buried in Documents
95,000+ PDFs, and no way to search inside them — the answer exists, but it can't be found.
Content Without Control
~30,000+ webpages and ~97,000+ resources, grown for years without one governing system.
Expectations Have Moved On
People expect the same speed and intelligence everywhere else — ICAI's members and students are no exception.
Our Vision
A Digital Institute as Trusted as the Profession It Represents.
Built on 77 years of institutional trust — we propose to carry it forward into a connected, intelligent, always-on generation.
The Transformation
What We Propose to Change
From fragmented systems to one connected platform.
Multiple disconnected systems
Independent content management
Search that can't see inside a PDF
Manual publishing, no workflow
Fragmented, web vs. app
One connected platform
One governed Unified CMS
Every PDF, instantly searchable
Governed approval, before anything goes live
Same content, same assistant, everywhere
Who Benefits
Designed for Every ICAI Stakeholder
One ecosystem, built around the people who use it.
Students
Exam updates, study resources and instant assistance.
Members
One personalized home for CPE, UDIN and renewals.
Firms
Faster access to the directory and services they rely on.
General Public
Clear, trustworthy information, without the runaround.
ICAI Administrators
One governed platform, not a patchwork of systems.
Content Teams
One place to author, approve and publish, everywhere.
This is more than a website redesign.
It's our proposal for ICAI's next digital foundation.
We propose one governed digital foundation, built to grow with ICAI's members, students and firms for years to come.
Our Solution
One Platform, Engineered as One System
We propose to connect ICAI.org, the Unified CMS, ICAI NOW and an Enterprise AI Assistant on shared foundations — one content model, one knowledge index, one AI engine — so nothing has to be built, published or governed twice.
Not Three Systems — One
What "Unified" Actually Means
Three shared foundations connect every module — not just a shared visual style.
One Content Model, Every Channel
Publish once in the Unified CMS, and it's live on ICAI.org and inside the ICAI NOW app at the same time — the same content, automatically kept in sync. Nothing is entered twice, and nothing drifts out of date between web and mobile.
One Knowledge Index, Two Doors
The same indexed content — every page, every OCR'd PDF — powers both the public Advanced Search bar and the Enterprise AI Assistant's retrieval. Improve the index once, and both get smarter together.
One AI Engine, Every Surface
The assistant embedded on ICAI.org and inside ICAI NOW is the same engine, the same knowledge base, the same guardrails — not two chatbots that can drift apart or disagree with each other.
One Audit Trail, Every Module
A CMS edit, a chatbot configuration change, a mobile update — every admin action writes to the same governed log, so oversight covers the whole platform, not just one piece of it.
The Four Deliverables
What We Propose to Build
Four connected pieces, delivered as one platform.
Website
A redesigned, high-performance ICAI.org — every existing page and resource migrated with its URL intact.
Unified CMS
One governed publishing system — structured content, an approval workflow, and a media library every author works from.
ICAI NOW
The existing app, evolved — identity, directory, live streaming, notifications and role-based dashboards, unified with everything else ICAI runs.
Enterprise AI Assistant
A conversational assistant grounded only in ICAI's own content — every answer traceable to a real source.
The Content Lifecycle
From One Publish to Every Channel
The path every piece of ICAI content follows.
Create
Drafted by an author in the CMS.
Govern
Reviewed and approved before it's live.
Publish
One action, not three separate ones.
Reach
Website, app and AI Assistant, automatically.
Discover
Found through search or a conversation.
Measure
Usage visible across every channel.
This Is a Platform,
Not a Bundle.
We propose one system, engineered to work as one — see how each surface actually works, next.
Experience Design
Experience the ICAI Digital Ecosystem
Four connected experiences, one ecosystem. Select one to explore.
Four Experiences.
One Connected Ecosystem.
ICAI.org · Digital Experience
The Website, Built Around ICAI's Design
The user interface and user experience of ICAI.org will be provided by ICAI. Our scope is what makes that design real, fast and governed.
What We Deliver
Responsive Implementation
Every breakpoint, built to spec.
Pixel-Perfect Development
Matches the approved design, exactly.
Unified CMS Integration
Every page, governed and publishable.
Accessibility (GIGW)
Compliant by default, not by patch.
Performance Optimization
Fast on every device, every network.
SEO Readiness
Structured for discovery, out of the box.
Security
Hardened against the OWASP top risks.
Content Migration
Every existing page, carried forward.
Enterprise Search Integration
Unified Search, wired in from day one.
AI Assistant Integration
The same assistant, embedded here too.
From Design to Deployment
Enterprise AI · Intelligent Experience
One Assistant, Shared Everywhere
Not a separate product — the same intelligence, embedded in both surfaces.
Meet ICAI Enterprise AI
A Conversation Grounded in ICAI Knowledge
Here's the official ICAI registration process, with direct links to the relevant forms and pages.
The latest Accounting Standards publication, with its publication date and official ICAI reference.
A summary of this week's ICAI notifications, each linking to the original notice.
A step-by-step walkthrough of the membership renewal workflow, start to finish.
What It Does
Natural Language Conversations
Ask questions in plain English.
Publication Discovery
Find the right ICAI publication, fast.
Document Intelligence
Search inside PDFs and scanned documents using OCR.
Contextual Conversations
Follow-up questions, naturally, within a session.
FAQ Handling
Instant answers to common questions.
Source Citations
Every answer traceable to its ICAI source.
Task Assistance
Guided help for registration, renewal and more.
Fallback Handling
Points to the right page or contact, never guesses.
Responsible AI
Trust, Built In
Grounded Responses
Answers are generated only from ICAI-approved knowledge sources.
Source Citations
Every response links back to official ICAI content.
Privacy & Security
Enterprise-grade security with governed access, data protection and compliance.
Continuous Knowledge
Reflects updates made through the Unified CMS, so answers stay current.
Two deployment paths are available — AWS Bedrock or a dedicated GPU — presented neutrally, with no recommendation either way. See Governance → Architecture for the full technical comparison.
Governance · CMS
Control, Not Just Authoring
One source of truth
What changes once content, search and the assistant share one CMS.
Governance · Security
Hardened by Default
| Area | Approach | Standard |
|---|---|---|
| Website & CMS security | OWASP Top 10 hardening, secure headers (CSP, HSTS, X-Frame-Options), hardened admin/CMS login with optional 2FA | GIGW security standards |
| Penetration testing | VAPT covering the full site and CMS, critical and high-severity findings resolved | Required before go-live |
| Encryption & segregation | Encryption at rest and in transit, controlled geographic hosting, and logical segregation from any multi-tenant environment | Applies to AI data too |
| Auditability | Admin actions, login attempts, content changes, and chatbot events all logged | Tamper-resistant audit trail |
Governance · Compliance
GIGW & DPDP Act, 2023
| Control | What it guarantees |
|---|---|
| Public accessibility | WCAG conformance plus a user-facing toolkit: dyslexia-friendly mode, blue-light filter, large font, night mode, translation assistance |
| PII masking | Usernames, passwords, emails, phone numbers, membership numbers, and IP addresses are never included in prompts sent to any external LLM API — sanitized and redacted beforehand |
| Data residency & ownership | Source documents, embeddings, vector indexes, logs, analytics, and conversation history stay within ICAI-approved infrastructure at all times; ICAI retains full ownership |
| DPDP Act compliance | Lawful processing, purpose limitation, data minimization, storage limitation, and breach-notification support |
| Compliance sign-off | GIGW compliance report submitted before go-live, ahead of ICAI's external GIGW/STQC audit |
Governance · Architecture
How It's Put Together
Platform targets, from the RFP
Concrete service levels from the Scope of Work, not marketing numbers.
P95 chatbot response latency, either architecture.
Chatbot uptime SLA; 100% uptime target for the site.
Concurrent chatbot sessions supported.
Homepage load time at 2M hits on a peak day.
Ask
A member or student asks a question on the website or in the app, in natural language.
Retrieve
The question is matched against the indexed ICAI corpus — documents, publications, and FAQs — to find the most relevant passages.
Ground
Retrieved ICAI passages are supplied to the model — Amazon Nova Lite on the Bedrock path, or the dedicated-GPU open-source LLM on the other — as the only allowed context. Out-of-scope questions are declined.
Answer with citations
The model produces a conversational answer and cites the ICAI sources it used, so the answer is verifiable. A response with no citation is treated as a defect, not a valid response.
The RFP specifies two independent, mutually exclusive technical paths. We can deliver either; ICAI chooses at contract award. Presented here neutrally, with no recommendation either way.
Path A — AWS Bedrock
Amazon Nova Lite for inference and Titan Embeddings V2 for retrieval, with Amazon Bedrock Knowledge Base and Guardrails (content filtering, denied topics, PII redaction) over an Amazon OpenSearch Serverless vector store.
Compute: AWS Lambda + ECS Fargate behind an API Gateway WebSocket for streaming, with ElastiCache Redis for repeated queries. Scale: ~1.3 crore inferences/month.
Cost model: ICAI pays AWS/Bedrock usage billing directly, post go-live. We quote development, integration, and maintenance only.
Path B — Dedicated GPU
An open-source LLM (Mistral Large 3, or equivalent) on dedicated AWS g5.12xlarge GPU instances (4× NVIDIA A10G, 96 GB VRAM each), minimum 2 active-active for high availability, on Amazon EKS.
Throughput: minimum 40 tokens/second per concurrent request, auto-scaling 2 → 4 instances above 70% GPU utilization. Same latency and uptime targets as Path A.
Cost model: we bear all infrastructure/GPU/cloud costs for the full 3-year term — the key difference from Path A.
Engine components
What each part of the AI engine is responsible for.
| Component | Responsibility | Guarantee |
|---|---|---|
| Knowledge ingestion | Index ICAI documents, publications, FAQs | Managed via the admin panel |
| Retriever | Find the most relevant ICAI passages | Only ICAI sources are eligible |
| Generation model | Generate the conversational answer | Nova Lite (Bedrock path) or Mistral Large 3 (GPU path) — grounded in retrieved context only |
Connecting to ICAI's systems
Back-end integrations behind the unified member/student dashboard.
UDIN
Surfaced on the unified member/student dashboard via API.
CPE
Continuing education records integrated into the same dashboard.
SSP
Self-Service Portal data joined by mobile number, membership number, or SRN.
Dashboard data reflects the uptime of the external ICAI system it's fetched from — this is an explicit RFP caveat, not a gap in this platform.
Delivery · Timeline
14–15 Weeks, Letter of Intent to Go-Live
Kickoff & Requirements
Project kickoff, requirement gathering, and stakeholder interviews across the website, ICAI NOW app, and chatbot.
Design Finalization
Wireframes and mockups finalized against ICAI's supplied visual design, for the CMS, chatbot, and app screens.
Development, CMS & UAT
Build and CMS integration across all three modules, followed by User Acceptance Testing and refinements.
Go-Live, Training & Docs
Final deployment to production, ICAI staff training, and handover documentation.
Delivery · Migration
Nothing Breaks, Nothing Is Lost
~30,000+ webpages and ~97,000+ resources move to new AWS infrastructure, with every existing page and resource URL kept unchanged.
2 million hits on a single peak day, 15,000–20,000 concurrent requests, ~1 second homepage load, 100% uptime.
Delivery · Support
