The Assette RFP Module enables your firm to efficiently generate accurate, data-driven responses to Requests for Proposals (RFPs), using approved content from your Assette environment. This article outlines the standard implementation process for the RFP Module, including required setup steps, timeline expectations, and system dependencies.
Implementation of the RFP module is a fairly straightforward set of tasks, as outlined below. Unlike other Assette modules, the RFP module does not require any data integration.
Work Group Set-Up #
If your firm hasn’t already set up
Historical Request for Proposals (RFPs) #
To further refine the RFP response library, Assette will assist in pulling and organizing the following types of content:
- Past RFP responses and answer libraries.
- Factsheets and pitchbooks used in sales and marketing.
- Any standard firm language or content typically required in proposals.
This information is added to the response library to enable faster and more accurate RFP response generation moving forward.
Training & Session Walkthroughs #
Assette will conduct working sessions to walk your team through the RFP workflow, content retrieval, and customization capabilities. These sessions are designed to:
- Review how sales materials and approved content are pulled into the module.
- Clarify system behaviors and customizations.
- Enable hands-on familiarity with the module.
Additional Resources #
For more detailed guidance on working with Assette’s RFP Module and related data setup, refer to the following resources:
Assette RFP Module Implementation Template
This template outlines all required steps to implement the Assette RFP Module in your environment. For each step, we have included the purpose (“Why”), a description of the task (“What”), and specific items for your team to complete (“Action Items”).
This template is intended to be used in collaboration with your Assette implementation team and can be adapted based on your firm’s technical setup, content maturity, and team structure.
Step 1: Launcher Deployment #
What: Deploy the Assette RFP Launcher in your environment.
Why: The RFP Launcher initiates the RFP Module and must run within your environment to ensure secure and seamless access to data and approved content.
Action Items:
- Confirm deployment location and resource owner(s).
- Work with Assette to deploy the launcher in your Azure environment.
- Validate authentication mechanisms (Single Sign-On, user permissions).
- Test launcher accessibility from relevant user roles.
Step 2: Azure Resources and Cosmos DB Alignment #
What: Set up necessary Azure infrastructure, including Cosmos DB, to support RFP Module data storage and retrieval.
Why: The module relies on cloud-based storage to retrieve and manage RFP-related content and structured data through Data Objects (DOs).
Action Items:
- Provision or confirm access to Azure resources.
- Align Cosmos DB instance with Assette’s data architecture.
- Assign technical contact to coordinate with Assette engineering.
- Validate storage configuration and access roles.
Step 3: Data Object (DO) Review and Updates #
What: Review and update existing Data Objects to ensure necessary data is available for RFP responses.
Why: Data Objects are the core mechanism used to populate dynamic, data-driven content in RFP answers. They must be configured accurately to ensure correct information is surfaced.
Action Items:
- Review existing DOs used for factsheets, pitchbooks, and standard reporting.
- Identify which DOs should be embedded in RFP answers.
- Work with Assette to create or update DOs as needed.
- Confirm ownership of ongoing DO maintenance.
Step 4: Qualitative Content and Response Library Preparation #
What: Identify and prepare qualitative content (non-data-driven) used in RFP responses.
Why: Many RFP responses include narrative or compliance language that is not system-generated. This content must be prepared and reviewed for reuse in the module.
Action Items:
- Gather commonly used answers, boilerplate responses, and compliance-approved text.
- Review and clean up past RFP responses for relevance and reuse.
- Organize responses by category (e.g., firm overview, investment process, risk).
- Provide this content to Assette for ingestion into the content library.
Step 5: SME Setup and Content Review #
What: Involve subject matter experts (SMEs) to validate the content library and embedded data.
Why: SMEs ensure that RFP answers reflect accurate and up-to-date firm positioning, strategy descriptions, and compliance policies.
Action Items:
- Identify SMEs for key RFP content areas (e.g., investment, operations, compliance).
- Coordinate reviews of content library and embedded data.
- Provide feedback on structure, clarity, and correctness.
- Approve content for use in production.
Step 6: QA and Initial Testing #
What: Conduct thorough testing of the launcher, content retrieval, and formatting before launch.
Why: QA ensures that all components work as expected and the RFP responses meet quality standards before users rely on the system.
Action Items:
- Perform structured walkthroughs of the module.
- Test various RFP scenarios, using both data-driven and qualitative content.
- Validate formatting, consistency, and data accuracy.
- Log and resolve any issues or discrepancies.
Step 7: Data Tuning and Module Integration #
What: Finalize system setup and tune the module to reflect firm-specific behaviors and preferred workflows.
Why: Tuning improves usability and ensures the module reflects how your team works—enhancing efficiency and reducing manual editing.
Action Items:
- Review how content is grouped and surfaced in the module.
- Adjust settings for content prioritization and answer formatting.
- Customize workflows, filters, and search behaviors.
- Confirm alignment with firm-specific RFP process stages.
Step 8: Sales Material and Past RFP Import #
What: Ingest sales documents and recent RFPs to enhance content coverage.
Why: Leveraging past materials ensures you start with a robust response library and eliminates the need to re-author existing content.
Action Items:
- Provide past pitchbooks, factsheets, and RFP responses.
- Identify which materials are approved for reuse.
- Tag and categorize documents for easier retrieval in the module.
- Work with Assette to extract and embed reusable answers.
Step 9: Training and Handoff #
What: Train your internal users and finalize ownership of the module.
Why: Ensures your team can confidently manage content, generate responses, and maintain the system going forward.
Action Items:
- Schedule training sessions with Assette (live or recorded).
- Assign system owners for ongoing content updates and QA.
- Review support contacts and escalation paths.
- Confirm go-live readiness.
Additional Resources #
To support your implementation efforts, please refer to the following resources: