Page 1 of 5
BidIQ System Requirements Document
1. Introduction
BidIQ is an enterprise AI procurement platform designed to revolutionize the strategic sourcing process for Fortune 500 procurement organizations. This document outlines the system requirements for BidIQ, ensuring it meets the highest standards of functionality, design, and user experience.
2. System Overview
BidIQ is a fully functional, authenticated SaaS web application that leverages AI-first workflows to streamline the procurement process. It offers a modern UI and is designed to be sold to large enterprises, providing features for RFP creation, supplier collaboration, evaluation, scenario modeling, negotiation, and analytics.
3. Functional Requirements as Story Points
- As an Administrator, I should be able to manage user roles and permissions.
- As a Chief Procurement Officer, I should be able to view executive dashboards with key procurement metrics.
- As a Category Manager, I should be able to create and manage RFPs using the RFP Builder.
- As a Procurement Manager, I should be able to evaluate supplier responses and generate AI-driven insights.
- As a Business Stakeholder, I should be able to collaborate on RFPs and provide approvals.
- As a Finance user, I should be able to access financial analytics and reports.
- As a Legal user, I should be able to review and approve contracts.
- As a Risk user, I should be able to assess supplier risks and compliance.
- As a Supplier, I should be able to upload responses and track submission progress.
- As an Executive Viewer, I should be able to view high-level procurement analytics and reports.
Page 2 of 5
4. User Personas
- Administrator: Manages the platform, user roles, and permissions.
- Chief Procurement Officer: Oversees procurement strategy and analytics.
- Category Manager: Manages specific procurement categories and RFPs.
- Procurement Manager: Handles supplier evaluations and negotiations.
- Business Stakeholder: Collaborates on procurement projects and approvals.
- Finance: Manages financial aspects of procurement.
- Legal: Reviews contracts and ensures compliance.
- Risk: Assesses and manages supplier risks.
- Supplier: Provides responses to RFPs and manages submissions.
- Executive Viewer: Accesses high-level analytics and reports.
5. Core User Flows
- User logs in -> accesses dashboard -> views active RFPs and analytics.
- Category Manager creates RFP -> uses AI to generate sections -> collaborates with stakeholders -> publishes RFP.
- Supplier logs into portal -> uploads response -> tracks progress -> submits response.
- Procurement Manager evaluates responses -> uses AI insights -> ranks suppliers -> finalizes evaluation.
- Scenario modeling -> adjusts variables -> compares scenarios -> selects optimal sourcing strategy.
Page 3 of 5
6. Visuals Colors and Theme
- primary: #001F3F (Navy)
- primary_light: #0074D9 (Blue)
- secondary: #39CCCC (Teal)
- accent: #FF4136 (Red)
- highlight: #FFDC00 (Yellow)
- bg: #FFFFFF (White)
- surface: #F2F2F2 (Light Grey)
- text: #111111 (Black)
- text_muted: #555555 (Grey)
- border: #DDDDDD (Light Grey)
7. Signature Design Concept
Interactive Procurement Galaxy: The homepage features an interactive galaxy map where each star represents a feature or section of the platform. Users can click on stars to open detailed views, drag to rotate the galaxy, and hover to highlight connections between features. This concept uses @react-three/fiber and gsap for 3D interactions and animations.
Landing Hero Motion Brief
The landing hero showcases a dynamic transformation of procurement data into actionable insights. The animation begins with raw data inputs swirling around a central AI core, which processes the data into a clear, visualized report. This looped animation uses motion/react for smooth transitions and interactive elements, ensuring a captivating first impression.
Page 4 of 5
8. Interaction Model & Motion Direction
- Intended Interaction Model: Animated
- Description: The landing page features moderate scroll-triggered reveals, hover transitions, and spring physics on interactive elements. This approach is ideal for showcasing the platform's features and capabilities in a polished, professional manner.
9. Non-Functional Requirements
- The application MUST support high availability and scalability to accommodate enterprise-level usage.
- It MUST ensure data security and compliance with relevant regulations.
- The platform SHALL provide a responsive design for optimal performance on various devices.
- It MUST support role-based access control to protect sensitive information.
10. Tech Stack
- Frontend: React for Web
- Backend: Python, FastAPI
- Database RDBMS: MySQL or MariaDB, use alembic for migrations
- Database NoSQL: MongoDB
- Local orchestration: Docker, docker-compose
- Server-side orchestration: Kubernetes
11. Assumptions and Constraints
- The platform will be deployed in a cloud environment to ensure scalability.
- It is assumed that users will have access to modern browsers for optimal performance.
- The application must integrate with existing enterprise systems for data exchange.
Page 5 of 5
12. Glossary
- RFP: Request for Proposal
- AI: Artificial Intelligence
- SaaS: Software as a Service
- UI: User Interface
- UX: User Experience
- KPI: Key Performance Indicator
This document outlines the comprehensive requirements for the BidIQ platform, ensuring it meets the needs of enterprise procurement organizations with a focus on modern design, AI-driven workflows, and robust functionality.
No comments yet. Be the first!