Statement of Work
AI Revenue Operating System
Between RapidData ("Vendor") and PruTech ("Client") for the design, build, and hand-off of an agentic AI platform unifying RFP intelligence and sales pipeline execution.
- Effective Date
- May 8, 2026
- Duration
- 7 weeks
- Engagement
- Fixed-scope build + hand-off
- Document Status
- Draft v1.0
Section 1
Parties & Stakeholders
Vendor
RapidData
Primary contact: Biren Saini
Client
PruTech
Sponsor: Deepak Chopra, Chief Executive Officer
Section 2
Background & Objectives
Background
PruTech currently relies on manual review of public-sector solicitations (RFPs, RFQs, RFSs, RFIs etc.) sourced from GovSpend, FedMine, SAM.gov, GSA eBuy, and one state portal. Given the dependence on available human resource bandwidth, this sourcing effort is not scalable and often lags the speed of RFX.
Objectives
The objective of this engagement is to deliver an agentic AI platform that automates discovery, qualification, and ranking of solicitations against PruTech's capability profile, and provides a collaborative workspace for "Go" decisions and pipeline hand-off.
Using AI-enablement, the engagement is intended to deliver:
- Scale: in quality and volume of sourcing.
- Reduction: in lead-times for triaging and responding to solicitations.
- Optimization: in the effort expended on business development and oversight.
It delivers these by:
- Surfacing opportunities tightly aligned with PruTech's configuration set (dimensions such as agencies, technologies, NAICS codes, and buyer-budget thresholds).
- Providing in-app chatbot trained on prior-won RFPs and capability narratives, to ramp knowledge and engagement for existing and new business-development reps.
- Consolidating a single dashboard for review, ranking, and in-tool collaboration.
Section 3
Scope of Work
3.1 Platform Deliverables (MVP)
- Solicitation ingestion pipeline from GovSpend, FedMine, Orange Slices, GSA eBuy, SAM.gov, and selected state portals (direct).
- Configurable matching engine consisting of criteria such as: NAICS / commodity codes (e.g., 541511, 541512, 541519); agencies; technology keywords (e.g., low-/no-code, enterprise software engineering, Salesforce, Dynamics, Power Apps, Java, AI; exclude SAP); buyer size & budget gating; hard vs. weighted rules.
- Per-source search criteria.
- Executive dashboard — single-screen daily review of new solicitations, rankings, and status.
- In-tool collaboration — comments, @mentions, activity feed on each solicitation.
- AI-generated dossier per solicitation: summary, fit rationale, key clauses, risks, and recommended actions.
- In-app chatbot available on every screen for triage, onboarding, and capability lookup (no commercials exposed).
- Push "Go" RFPs into PruTech's pipeline of record (Salesforce).
3.2 Enablement & Hand-off
- In-app documentation & help
- Two weeks of post-launch hypercare.
- Application source code & configuration export delivered to PruTech.
- The handoff will include three things:
- A user guide and admin guide,
- Two one-hour sessions with the team - one for a live demo walkthrough, one for Q&A, and
- A written confirmation from both PruTech and RapidData acknowledging successful completion of all closure activities.
3.3 Out of Scope (this SoW)
- Proposal generation — Option 1: integrate RapidData generator (later phase); Option 2: continue with PruTech's existing generator.
- Custom Salesforce development beyond the documented Go-RFP push.
- Migration of historical RFP archives beyond agreed seed set.
Section 4
Timeline & Milestones
| Week | Milestone |
|---|---|
| W1 | Kick-off, data-source access, config workshops. |
| W2 | Ingestion pipeline live; first matching rules wired. |
| W3 | Dossier generation, dashboard skeleton, internal review. |
| W4 | First usable version available to PruTech for hands-on use. |
| W5 | Collaboration features, chatbot, refinement on real solicitations. |
| W6–W7 | Full delivery (Sections 3.1 and 3.2), training, hypercare begins. |
| W7 | Hand-off. |
Section 5
Engagement Model
RapidData delivers
- Build, host (during build), and configure the platform.
- Weekly demos and async written status.
- Push "Go" RFPs into PruTech's chosen pipeline of record.
- Hand-off package and post-launch hypercare.
PruTech provides
- Day-1 inputs: NAICS / commodity codes used today.
- Inputs for the configurable matching engine.
- Decision on system-of-record for Go RFPs (Salesforce vs. in-tool pipeline).
- Sample of recently won RFPs to seed the chatbot.
- Timely review and feedback within agreed cadence.
- Cloud environment and necessary infrastructure, subscriptions, and resources to provision the software for production use — including compute (e.g., VM), storage (e.g., Azure Storage), caching, vector databases, and LLM providers (OpenAI, Azure AI, Anthropic, etc.).
Section 6
Commercials
Buy-out
$25,000
One-time. PruTech continues to use the delivered version as-is, including in-app documentation and chatbot help. RapidData hands off; perpetual license included.
Milestone-based Payment Schedule
| Milestone | Trigger | Amount |
|---|---|---|
| MS1 | Upfront — on SoW execution / kick-off | $10,000 |
| MS2 | On Go-Live and on all Acceptance Criteria (section 7) being met and mutually signed off in writing by both parties | $10,000 |
| MS3 | 30 days after Go-Live | $5,000 |
| Total | $25,000 |
Section 7
Acceptance Criteria
- Ingestion runs daily across configured sources with monitored health.
- Matching engine returns ranked RFPs with rationale; near-miss explanation when zero results.
- Dashboard, dossier, and collaboration features operational on production data for two consecutive weeks.
- Training delivered and documentation accessible in-app and via chatbot.
- Source code & configuration export delivered.
Section 8
IP, Licensing & Confidentiality
- PruTech receives a perpetual, non-exclusive license to the delivered application for internal use.
- RapidData retains rights to underlying frameworks, generic components, and know-how reused across engagements.
- All PruTech data, won-RFP corpus, and configuration remain the property of PruTech.
- Both parties bound by mutual NDA; no disclosure of commercials or proprietary data.
Section 9
Change Control & Governance
- Weekly working session with Deepak Chopra, Krishnamurthy Iyer, and RapidData lead; written status follows.
- Scope changes captured as a written Change Request with impact on timeline/cost; effective once countersigned.
- Escalation path: RapidData lead → Biren Saini; PruTech lead → Deepak Chopra.
Section 10
Sign-off
For RapidData
Name
Biren Saini
Signature
Date
For PruTech
Name
Shannon Cardone, Executive Director of Contracts
Signature
Date