← All projects

Case studyProject Bidding1 day

Nodewave: Tender Lifecycle Management

An AI-powered CRM that streamlines the tender lifecycle for construction firms, automating discovery, document handling, and post-tender processes.

Key skills
Product Management
  • Product Roadmapping
  • Product Requirements Document
  • Product Strategy
User & Market Research
  • User Research
  • Value Proposition Canvas
  • Product Research
User Experience Design
  • User Flow
Tools
  • Google Docs
Illustration of business reports and charts

PRD - AI-Based CRM for Tender Lifecycle Management


1. Context

1.1 Current Scenario

State-owned construction enterprises (BUMN Konstruksi) currently face challenges in following project tender processes efficiently. Tenders come from various external sources such as LPSE and e-Proc, but the tender management process is often handled by different teams. Activities such as opportunity searching, document preparation, clarification, negotiation, and project execution are not yet managed centrally in a single integrated system. This leads to information fragmentation, process inefficiency, and a lack of cross-team visibility.

1.2 Limitations or Challenges

  • Relevant tenders are hard to find because they are scattered across many external platforms: The procurement team has to search manually across various LPSE sites, e-Proc, and other unstructured sources, which is time-consuming and prone to missed opportunities.
  • The documentation process is manual, error-prone, and time-consuming: The absence of document standards and automation tools forces the team to prepare tender files one by one.
  • Communication and negotiation are often poorly documented: Price or technical discussions usually take place over email, chat, or verbally, without a centralized record-keeping system.
  • There is no comprehensive tracking of tender status and post-award activities: Tender progress is hard to monitor in real time, and the transition from tender to project often loses track of information.
  • It is difficult to perform historical evaluation of past tender performance: There is no analytics system that stores historical tender data, wins and losses, and the factors that influenced them.

2. Objectives/Goals

2.1 Business Objectives

  • Improve tender process efficiency to accelerate time-to-submit: Reduce the time from tender discovery to submission through process automation and integration.
  • Increase the tender success rate through insights based on historical data: Provide tender strategy recommendations based on analysis of previous tenders.
  • Provide an audit trail and end-to-end visibility of the tender process: Record all tender activities in a single system for compliance, accountability, and transparency.
  • Standardize the tender process across teams and divisions in the organization: Create a unified workflow that all work units can follow without losing control or flexibility.

2.2 User Objectives

  • The procurement team can find potential tenders faster and with greater relevance: Supported by an AI search and classification system that filters tenders according to project category.
  • The document preparation team can easily prepare and upload files in the required format: Using dynamic templates and automatic validation so that documents always comply with the bidding requirements.
  • The legal team can record clarification and negotiation outcomes in a structured way: The system provides features for recording negotiation outcomes and official communications, minimizing the risk of losing technical or commercial information.
  • Stakeholders can monitor tender progress without having to ask other teams: Tender status is available visually and in real time on a shared dashboard.
  • Management can analyze tender performance based on history and AI predictions: Enables data-driven decision-making with insights from win history and market trend analysis.

3. Problem - Solution Mapping

User Role Pain Points Needs
Procurement Team Difficult to find tenders that match the company’s field and qualifications An AI system that can filter relevant tenders based on project category and technical qualifications
Has to check many external platforms manually every day An automatic tender watcher that pulls data from LPSE, e-Proc, and other platforms
No notification when a new matching tender appears Real-time notifications when the system detects a tender that matches the company profile
Document Preparation Team Tender documents are not standardized; each tender has a different format Dynamic templates that adjust automatically to the format of the target tender
Prone to forgetting important attachments or supporting documents An automatic checklist that displays required items before documents are submitted
Document validation is done only manually, with a risk of errors Automatic validation of format, size, and completeness before submission
Legal Team Outcomes of verbal negotiations or clarifications are not documented A negotiation recording feature that can be saved and linked to the related tender
Changes in price or technical requirements are not always communicated on time A notification system for important revisions from the tender organizer
Difficulty accessing the latest document version Integration with a file management system so the latest documents are always indexed and easy to find
Project Manager Information about won projects does not always reach the project team clearly Automated handover from the tender system to the project system when the status is “Won”
Details of the tender’s scope of work are often unknown Access to the tender summary and technical documents through the project dashboard
No system connection between the tender and project execution Integration of the project execution timeline into the CRM system as a post-tender stage
Management / Board of Directors Cannot see the company’s overall tender performance An aggregate analytics dashboard showing total tenders, win-rate, and performance per division
Does not know the win/loss patterns of previous tenders AI insights that visualize patterns from tender history for strategic decision-making
Difficult to evaluate each team’s contribution to tender success Team contribution analytics (procurement, documents, legal) on tender outcomes based on their involvement data

4. User Stories & Acceptance Criteria

4.1 Procurement Team

  • User Story: As a member of the procurement team, I want the system to automatically filter and display relevant tenders, so that I don’t have to search manually across various platforms such as LPSE and e-Proc.

    Acceptance Criteria:

    • The system automatically pulls tender data from at least 2 external sources (LPSE, e-Proc).
    • The displayed tenders match the company’s line of business and project value.
    • Each tender displays the project name, agency, deadline, and a link to the official source.
    • There are filter and sorting features by date, tender value, and field.
  • User Story: As a member of the procurement team, I want to receive a notification when a new tender matches the company’s field and qualifications, so that I can follow up on the opportunity right away before the deadline.

    Acceptance Criteria:

    • The system sends a push/email notification no later than 1 hour after a new relevant tender is detected.
    • Notifications are sent only for tenders that pass the predefined minimum relevance score.
    • The system provides an option to turn notifications on/off.

4.2 Document Preparation Team

  • User Story: As a member of the document preparation team, I want to use dynamic document templates that follow the current format, so that I can prepare bids quickly and accurately.

    Acceptance Criteria:

    • The system provides automatic templates based on the tender type.
    • Templates can be edited directly in the system.
    • Templates follow the official format of the tender organizer.
  • User Story: As a member of the document preparation team, I want the system to provide an automatic checklist based on the tender requirements, so that I don’t miss important documents during submission.

    Acceptance Criteria:

    • The checklist is displayed automatically after the template is accessed.
    • The checklist can be customized if the organizing agency has additional requirements.
    • Checklist items can be marked “Complete”, “Not Yet”, or “Not Applicable”.
  • User Story: As a member of the document preparation team, I want the system to automatically validate file format and completeness before submission, so that the risk of rejection due to technical errors is minimized.

    Acceptance Criteria:

    • The system checks file size, document format (PDF, DOCX), and completeness of attachments.
    • Failed validation is flagged with a clear error message.
    • Submission cannot be completed if required documents are incomplete.

4.3 Legal Team

  • User Story: As a member of the legal team, I want to record clarification and negotiation outcomes systematically, so that all sensitive information is documented and can be referenced when needed.

    Acceptance Criteria:

    • The system provides a negotiation journal module that can be edited and linked to the related tender.
    • Each entry records the time, the user who entered it, and the content of the discussion outcome.
    • Logs cannot be deleted once saved; only new revisions can be added.
  • User Story: As a member of the legal team, I want to receive automatic notifications when there is a new document, a revision of tender requirements, or a scheduled clarification, so that I can promptly conduct a contractual review.

    Acceptance Criteria:

    • The system sends automatic notifications when: a new tender document is uploaded, a document is revised, or a clarification/negotiation schedule is created.
    • Notifications include a highlight of changes for revisions, and brief info for new documents/schedules.
    • Users can view the document change history and past clarification logs in a single integrated view.
  • User Story: As a member of the legal team, I want to access the latest version of tender documents quickly and accurately, so that I can provide relevant legal input without version confusion.

    Acceptance Criteria:

    • The system displays only the latest version by default.
    • Previous version history can be accessed through the version log.
    • Accessed documents have a timestamp and the uploader’s identity.

4.4 Project Manager

  • User Story: As a project manager, I want to receive information automatically when a tender project is won, so that I can immediately start planning and preparing for project execution.

    Acceptance Criteria:

    • The system sends a notification when the tender status changes to “Won”.
    • The notification includes the project name, contract value, and start date.
    • Links to the tender summary and supporting documents are available directly from the notification.
  • User Story: As a project manager, I want to be able to view the scope of work and technical content of a won tender, so that I understand the context and scope that must be carried out in the field.

    Acceptance Criteria:

    • The tender summary displays the project description, scope of work, and deliverables.
    • All technical documents are available on a single project page.
    • The system visually marks important components (SoW, BoQ, specifications).
  • User Story: As a project manager, I want the project execution system to be connected to the tender system, so that all data and the initial timeline can be used immediately without re-entry.

    Acceptance Criteria:

    • The system allows tender data to be converted into an execution plan.
    • The initial timeline is populated automatically based on tender information.
    • The Project Manager can adjust the timeline before locking execution.

4.5 Management / Board of Directors

  • User Story: As a member of management, I want to view the company’s tender performance through an analytics dashboard, so that I can evaluate the effectiveness of the strategy and each team’s contribution to the tender process.

    Acceptance Criteria:

    • The dashboard displays the number of tenders entered, won, and lost per month, per project category.
    • Cross-team contribution is visualized as a strategic contribution chart (e.g., % of team involvement across all won tenders).
    • Data can be exported in Excel or PDF format for management reports.
  • User Story: As a member of management, I want the system to provide AI-powered insights from tender history, so that I can set tender priorities or negotiation strategies based on past data patterns.

    Acceptance Criteria:

    • The system displays recommendations of tender types with a high chance of winning based on history.
    • AI insights are displayed as charts, probability scores, and contributing factors.
    • Insights can be filtered by project category and tender value.
  • User Story: As a member of management, I want to analyze each team’s contribution to the outcome of each specific tender, so that I can identify areas that need improvement or further training.

    Acceptance Criteria:

    • Each tender has an activity log of the teams involved, along with timestamps and activity types.
    • Contribution metrics such as document preparation time, number of revisions, and clarification response are recorded and displayed per team.
    • The team performance dashboard is displayed weekly and can be filtered by specific tender or division.

5. User Flow

5.1 Login & Role Detection (All Users)

  1. The user opens the Tender CRM application
  2. The user logs in with their own credentials
  3. The system detects the user’s role (Procurement Team, Document Preparation Team, Legal Team, Project Manager, Management)
  4. The dashboard is displayed according to each role’s access rights

5.2 Tender Identification (Procurement Team)

  1. The AI system collects tender data from LPSE, e-Proc, and other sources
  2. Tenders are automatically filtered by project category, tender value, and line of business
  3. The Procurement Team views the list of recommended tenders
  4. The Procurement Team marks the tenders it wants to participate in as watchlist
  5. Notifications are sent automatically to the Document Preparation Team and the Legal Team

5.3 Document Submission (Document Preparation Team)

  1. The Document Preparation Team opens a tender that has been marked as “potential”
  2. The system displays a document template matching the tender format
  3. The team enters administrative and technical information into the template
  4. An automatic checklist appears to verify document completeness
  5. The system automatically validates the document format and structure
  6. After validation, the documents are sent through the Submit to Evaluator feature
  7. Notifications are sent to the Legal Team and Management for the next step
  1. The tender enters the clarification or revision stage by the tender organizer
  2. The Legal Team records clarification questions and answers in the system
  3. The Document Preparation Team revises documents if needed and uploads the latest version
  4. All communication is stored as a centralized evaluation log
  5. The system sends automatic reminders for revision deadlines
  1. If the organizer opens negotiations, the Legal Team enters the outcomes of price and technical requirement discussions into the system
  2. The system stores the entire history in the Negotiation Journal module
  3. Management reviews and approves the final price or strategic changes
  4. Once approved, the final documents are locked and submitted according to the tender platform’s format

5.6 Tender Outcome (Procurement Team or Document Preparation Team)

  1. The user records the tender announcement result: Won / Lost
  2. If the tender is won, the system automatically sends a notification to the Project Manager, activates the handover process, and grants the project team full access to the tender data
  3. If the tender is lost, the system stores the complete process history for evaluation and adds the data to the AI analytics insight module, such as the factors behind the loss

5.7 Project Execution (Project Manager)

  1. The Project Manager (PM) receives a notification that the tender has been won
  2. The PM opens the tender summary: scope of work, project value, and initial schedule
  3. The PM fills in the initial execution plan and assigns the project PIC
  4. The system connects the tender data to the project execution dashboard
  5. Project progress updates are recorded in the project module integrated with the CRM

5.8 Analytics & Dashboard (Management / Board of Directors)

  1. Management logs in and opens the analytics dashboard
  2. The system displays tender performance data, including:
    • Number of tenders participated in
    • Win rate
    • Average preparation time
    • Contribution of each team (procurement, documents, legal)
    • AI insights on win patterns and potential project types
  3. Management can filter data by period, project category, or work unit

6. Requirements

6.1 Technical Requirements

  • The application is built on a web architecture based on a RESTful API.
  • The system integrates with the LPSE and e-Proc platforms (via web scraping/public APIs).
  • AI modules are available for:
    • Tender classification and filtering
    • Historical insights and win prediction
  • The system supports sending notifications (real-time) via email and push notification
  • A relational database to store:
    • Tender information
    • Documents and revisions
    • Activity logs & process history
  • The authentication system supports SSO and Role-Based Access Control (RBAC).

6.2 Design Requirements

  • The user interface (UI) is responsive and supports cross-device access (desktop, tablet).
  • Each role (procurement, documents, legal, PM, management teams) has a customized dashboard view.
  • Document templates can be filled in directly within the application and follow the official structure of the tender organizer.
  • Colors, icons, and visual notifications must be consistent and easy to understand:
    • Green = Won
    • Red = Lost
    • Yellow = Revision or Clarification

6.3 Functional Requirements

  • Pull tenders from external platforms periodically (at least once per hour).
  • Filter tenders based on the company’s relevance criteria.
  • Provide notifications when new tenders appear or changes occur.
  • Display and facilitate the preparation of tender documents:
    • Automatic templates
    • Document checklist
    • Document validation
  • Store negotiation and clarification logs.
  • Perform an automatic handover to the Project Manager when the status is “Won”.
  • Provide tender analytics insights and dashboards for management.

6.4 Non-functional Requirements

  • Support at least 1,000 daily active users.
  • Maximum response time of 2 seconds for data requests.
  • Minimum system uptime: 99.5% (SLA).
  • All data communication is encrypted (TLS 1.2+), and storage uses AES-256 encryption.
  • Compatible with modern browsers (Chrome, Firefox, Edge).

7. Edge Cases

Module/Feature Edge Case Desired Handling
Login & Role Detection The user logs in successfully but is not redirected to their role’s dashboard The system performs a fallback to the default dashboard and records the anomaly in the admin log
Tender Watcher The same tender appears twice, from LPSE and e-Proc The system deduplicates based on project name, agency, and publish date
Tender Filtering Valid tenders do not appear because the relevance score is too strict The system displays a notification if there are too few results and suggests loosening the filter
Tender Notifications Notifications are not sent because the email server is down The system retries 3 times and records an error log on the admin dashboard
Analytics Dashboard Analytics charts do not appear because data is not yet available The system displays a placeholder with the message “Data not yet available”
Document Checklist The checklist does not appear even though the template has been opened The system automatically refreshes the checklist when the user re-accesses or reloads the page
File Upload The user uploads a file larger than the maximum limit The system blocks the upload and shows a clear error message along with the maximum size guidance
Document Validation A document fails validation even though it appears complete The system gives a specific reason (file size, wrong format, empty field)
Document Submission The user clicks submit twice (double click) The system prevents duplicate submissions by disabling the button after the first click
Finalization Process The tender is submitted but no submission confirmation appears The system saves a log of the last status and displays retry information or the upload status
Clarification A clarification is sent but not answered by the deadline The system sends an automatic reminder one day before the deadline to the legal team and PM
Handover to PM The PM does not receive a notification even though the “Won” status has been recorded The system logs all failed notifications and provides a manual resend button
Project Timeline The project start date is earlier than the tender submission date The system displays a warning and asks the Project Manager to reconfirm
AI Insight AI insights give irrelevant suggestions or reflect historical bias The system provides a “Report Irrelevant Insight” option for model evaluation
Activity Log An activity is performed but does not appear in the system log All activities are saved with a maximum delay of 10 seconds; the system shows a sync indicator if it is slow

8. Success Metrics

Category Metric Quantitative Target
System Adoption Number of weekly active users (WAU) ≥ 50% of total registered users
Number of tenders processed through the system ≥ 80% of the company’s total tenders
Average daily logins ≥ 4 days per week
Process Efficiency Average time from detection to document submission ≥ 30% faster than the previous manual baseline
Number of technical document validation errors Down ≥ 50% compared with before the system was used
Number of unrecorded clarifications 0 (all documented in the system)
Tender Performance Tender win rate Up ≥ 10% in the first 6 months
Number of projects that go directly into the execution dashboard 100% of won tenders
User Satisfaction User satisfaction score (CSAT) ≥ 85%
AI Insight feature usage rate by management ≥ 60% of weekly management logins
System Reliability System response time for general requests ≤ 2 seconds
Monthly system uptime ≥ 99.5%
Notification delivery success rate (push/email) ≥ 98%
Number of AI insights reported as irrelevant ≤ 5% of total insights displayed

9. Timeline (Delivery Plan)

Phase Estimated Duration Key Deliverables
Discovery & Planning 1 week Scope finalization, user flow mapping, drafting user stories and acceptance criteria
Design & Prototyping 2 weeks Wireframes & UI for all roles, UX flow mapping, document template finalization
Core Development 4 weeks User authentication, role-based dashboard, tender watcher module, notifications, AI insight
Extended Features 4 weeks Document builder, validation & checklist, activity log, clarification, handover to PM
Testing & QA 2 weeks UAT for all roles, AI & LPSE integration validation, bug fixing, technical documentation
Deployment & Training 1 week Deployment to production, training for the procurement, documents, legal, and management teams
Monitoring & Support Ongoing SLA monitoring, minor bug fixing, evaluation of advanced features based on user feedback