Based on the text below on CCS:

Compliance Content
S ervices
Business Line: NA
Product: NA
Title: Compliance Content                             Date:     March
Services                                              2024
Challenge                Solution                                          Key Metrics (Progress &              Target Customer &                   Anchors / Constraints
                                                                           Success)                             Segments
Challenge: Disparate content          Solution: Formally establish         •   Phase 1 (FY24): Inception        CCS will support customers in       Possible constraints:
products and content teams            Compliance Content Services as a          1. Content Library POC.         all Business Lines
with no centralised                   transversal support centre and            2. Central CMS POC.             and products.                       •   Failure to create
coordination or contribution          product function.                         3. Expansion lead-gen.                                                  cost centre and
toward Ideagen goals.                                                           4. Central resources hub        Particular focus::                      allocate P&L.
                                      The Vision: The leading                      created.
Evidence:                             Compliance Content as a Service                                           •   Phase 2 (FY25):                 •   Failure to clarify cost-to-
                                      Solution.                            •   Phase 2 (FY25): Foundations           o Existing content products        serve alignment and metrics
•   Content products: x 4                                                       1. Establish CCS Core                  – WorkRite/Q-Pulse Law           within global R&D spend.
    (CompliSpace; Workrite; Q-        The world’s largest and most                  team.                              supporting expansion/new
    Pulse Law; Audit Analytics)       valuable library of best-practice,        2. Content Playbook.                   logo revenue.                •   Failure to clarify alignment
                                      real-time compliant risk,                 3. Content transversal.                                                 of CCS within organisational
•   FTE:   ~ 90                       regulatory, compliance content and        4. Artificial                   •   Phase 3:                            structure (eg. transversal;
                                      information, immediately usable,              intelligence.                    o The above,                       product; BL)
•   Content volumes:    > 10,000      accessible via the cloud,                 5. Content Library.                    PLUS
    items                             developed and maintained for mass                                              o New content - Developing
                                                                                6. Central CMS.
                                      distribution, by the world’s                                                     new content products to
                                                                                7. Central LMS.
                                      leading and most efficient
•   Content maintenance                                                         8. Revenue generation.                 support expansion/new
                                      distributed team of risk
    backlogs: Significant.                                                      9. Cost-to-serve model.                logo
                                      and compliance content experts.
                                                                                10. Right-shoring projects.          o M&A – Content
•   M&A: More content products        Goal: 50,000 customers x +1 item          11. M&A (NORAM/APAC                    acquired.
    anticipated.                      Alternatives                                  content).                   Adoption Strategy                   Risks
                                      of content each @ £1,000 p/item
                                      = £50m ARR                                12. Offshore content services
•   Strong demand: High level         • No coordination of global                   centre.                     •   Dedicated PM and UX             •   Failure to establish CCS
    of enquiry and interest in           content                                                                    Consultant to drive adoption        leads to a lack of
    content available.                   opportunities/expansion.              Refer to plan-on-a-page              of Ideagen Content                  coordination and
                                                                               (below)                              Marketplace.                        contribution from content
                                       •   No internal efficiencies                                             •   CCS leaders to drive                teams and products toward
                                           realised relating to content    •   Phase 3/4                            commercial opportunities            Ideagen goals.
                                           teams.                          (FY26/27): Expansion                     (expansion/new).
Return on Investment - the Outcome                                         Key1.Activities
                                                                                  Content Marketplace           Notes:
                                                                                  expansion.
•   Costs (3 years): £1.1m                                                 • Confirm   ELT expansion
                                                                               2. Revenue   commitment– to      •   Potential cost-savings/efficiencies not scoped in this
      o Product Manager x 1                                                   establishment   of CCS.and new
                                                                                  Existing product                  Business Case.
      o User Experience x 1                                                • Confirm   commitment
                                                                                  product  revenue to Phase 2
      o Tech Developers x 3                                                • Create   and deploy MVP Content
                                                                                  (expansion/new).
      o Content Developers x 5                                                Marketplace
      Total = £385K pa (£1.1m 3 years)                                     • Secure and leverage Damstra
                                                                              for LMS capabilities
•   Revenue (3    years):   £7.4m (ROI 543%)                               • Create/acquire
      o FY25:     £350K                                                       NORAM learning content
      o FY26:     £1.05m                                                   • Execute operational
      o FY27:     £6.0m                                                       efficiency activities
     Business Case                Estimated Cost                                                               Resource Cost Breakdown
     The Financials (3 years)                  Impact                        Amount                         Dev Resources                                                   10
                                  FY24                                         £0                           Duration Months                                                 36
                                  FY25                                        £385K                         % US                                                            0%
                                                                                                            % KL                                                           20%
                                  FY26                                        £385K                         % IN                                                            0%
 Revenue
                                  FY27                                        £385K                         % UK                                                           80%
        Impact        Amount      Assumptions – What needs to be true.
3 Year Revenue       £7,400,000
                                  COSTS:
Payback Period       13 months    Role                                     Units       FTE          Period (Yr)       Cost              Total (pa)           Total (3yr)

3 Year ROI             543%       Product Manager                                  1            1                 3           £60,000          £60,000             £180,000
                                  User Experience                                  1            1                 3           £50,000          £50,000             £150,000
Cost                 £1,155,000
                                  Tech Developers (KL)                             3            1                 3           £25,000          £75,000             £225,000
                                  Content Developers                               5            1                 3           £40,000         £200,000             £600,000
                                                                                                                                              £385,000           £1,155,000
 Revenue Levers
                                  REVENUE:
          Lever     Improvement                                                         FY24            FY25                   FY26                   FY27                 Total
% New Logo ARR         0.00%      Total Ideagen customers (approx)                 10,000             20,000                 35,000              50,000
% Expansion            0.00%      New content sales (% of all customers)                               0.25%                  2.00%                  4.00%
% Contraction          0.00%      New content sales (units)                                               50                   700                   2,000             2,750
% Churned              0.00%      Unit price                                                          £7,000                 £1,500              £3,000
Starting QTR          Q2FY25      New ARR                                                           £350,000           £1,050,000           £6,000,000           £7,400,000
Weighted (Ramp)           4
                                  •   FY25: New content sales include WorkRite into US (25 units @ £7000) and QPL into EHS market (25 units @ £7000).
                                  •   FY26: Estimated new content sales 'attached' to a target of 2% of overall customers (@ £1500 unit price).
                                  •   FY27: Estimated new content sales 'attached' to a target of 4% of overall customers (@ £3000 unit price).

                                  Notes:
                                  • New content sales in FY26+ will include different content types: learning items; regulatory summaries; policies; risk resources; other.
                                  • The revenue forecasts above do not include content sold directly by BLs (eg. CompliSpace) or other content growth opportunities (eg. M&A;
                                     licensing of third-party content).
CCS: Phase 2 (FY25)

      VISION                                                                            'THE LEADING COMPLIANCE CONTENT AS A SERVICE SOLUTION'

       GOAL                                                                       50,000 CUSTOMERS x +1 ITEM OF CONTENT EACH @ £1,000 P/ITEM = £50m

                                                                                                                                                                     KEY ELEMENTS

    OBJECTIVES                                                          FY 25 KEY RESULTS                                                                     #2                                      #5
                                                                                                                                                   #1                     #3             #4
                                                                                                                                                           CONTENT                                   NEW
                                                                                                                                                CCS CORE               LEARNING     EFFICIENCIES
                                                                                                                                                           LIBRARY                                 CONTENT

                      1. Establish CCS Core team: New CCS team to drive Phase 2 (1 x PM; 1 x UX; 3 x Tech Devs; 5 x Content Devs).
     CONTENT
                      2. Content methodology: V1 of the Global Content Playbook that supports 'write once; use many' principles.
     QUALITY
                      3. Content transversal: Centralise content teams and central hub of support/resources, etc.
 Consistent quality
                      4. Artificial intelligence: 3 x new tools/solutions implemented to enhance efficiency/productivity or product features.

                      5. Content Library/Marketplace: Launch V1 of the Ideagen Content Library/Marketplace.
     CONTENT
    SURFACING         6. Content Management System (CMS): MVP CMS to support cross-surfacing of content.

     Revenue          7. Learning Management System (LMS): Acquire an LMS and integrate it into the Ideagen CMS model.
    generation
                      8. Revenue: Identify and support the development of new content and revenue initiatives (expansion/new).

                      9. Cost-to-serve model: Develop a benchmark content cost-to-serve model.
 CONTENT RIGHT-
   SHORING            10. Right-shoring projects: Lead right-shoring of existing and new content teams as required.

        Cost          11. M&A: Acquisition(s) of new content businesses in NORAM/APAC.
  rationalisation
                      12. Offshore content shared service: Establish a first squad of content team members in a low-cost centre.
         Charter
         Project Overview
Summary                                                                                        Objectives
Solution: Formally establish Compliance Content Services as a transversal support centre and
product function.                                                                              Objective 1         Content quality – Consistent quality

The Vision: The leading Compliance Content as a Service Solution.
                                                                                               Objective 2         ​Content surfacing – Revenue generation
Goal: 50,000 customers x 1 item of content each @ £1,000 p/item = £50m ARR
                                                                                               Objective 3         ​Content right-shoring – Revenue generation



Strategic Alignment                                                                                                                          High    Medium     Low   None



         New Logo                           Cross Sell                         Expansion              EDITDA                      NPS                         CHURN


 Scope (Key Deliverables)                                                                      Milestones (Name and Description)
 In                                                 Out                                        Name                      Date                       Description
 Establish CCS Core team                            ​Marketing                                 Establish team         ​May 2025     Establish new central CCS Core team
 Content Library/Marketplace                        ​Sales                                     Launch V1 Library      ​Nov 2025     New content library/marketplace
 Central LMS                                        ​Cost savings                              Central LMS            ​TBC          New central LMS (Damstra – TBC)
 New content / M&A                                  ​M&A                                       New Content / M&A      ​TBC          New content/revenue + content M&A
                                                                                                                              Guide (Dev months/weeks)
                                                                                                                              • High = Month+
        Business Case                                                                                                         • Medium = less than Month
                                                                                                                              • Low less than 1 week
        The External Resource Impact

Effort required                                                                                                                           High   Medium    Low   None



          Cloud Ops                                Architecture                                Platform                  AI                               UX
           Marketing                            Customer Success                                 Sales                 Finance                            HR
                                                                                                                                                     Content


Schedule Intentions – Resource Timings


    •   Create GraphQL and/or Protobuf schemas for each document type to be ingested
    •   Register and manage those in HyGraph CMS
    •   Create and deploy AWS components for the ingestion pipeline, specifically:
              • Kafka message queue and topics
               AWS Lambda
               Step Functions
               AWS API Gateways
    •   Work with the other tech teams involved (presumably initially that would be CompliSpace, QPL and/or
        WorkRite) to implement webhooks and API calls seamlessly
    •   Work with the QA/test team to devise ways of testing the ingestion pipelines, given that most of it does not
        have a frontend
    •   Start to (re)design the frontend concept for the library/marketplace
    •   Scope out how a CCS subscription model would work from a monetization point of view - this might involve:
               Google Subscriptions
               Other subscription-management platforms (such as Zuora)
            Prospective Timeline [Update]
                         May   Feb   Mar   Apr   May   Jun   Jul   Aug   Sep   Oct   Nov   Dec

1. Establish CCS team



2. Content Playbook



3. Content community



4. AI




5. Content Marketplace




6. NORAM content


7. LMS



8. Operational
efficiencies
     Business Case                Estimated Cost                                                 Resource Cost Breakdown
     The Financials [Update]              Impact                      Amount                   Dev Resources                       10
                                  FY24                                  £0                     Duration Months                     24
                                  FY25                                 £495K                   % US                               20%
                                                                                               % KL                               30%
                                  FY26                                 £495K                   % IN                                0%
 Revenue
                                                                                               % UK                               30%
        Impact        Amount                                                                   % AUS                              20%
3 Year Revenue      £17,780,000
Payback Period      18 months
3 Year ROI            1,364%      Assumptions – What needs to be true.
Cost                  £900K
                                  PHASE 2 (FY25)
                                  - Costs:
                                        o 1 x PM = £60K
                                        o 1 x UX = £50K
 Revenue Levers                         o 3 x Tech Devs = 3 x £25K = £75K
                                        o 5x Content Devs = 5 x £40K = £310K
          Lever    Improvement             Total = £495K
                                  - Revenue:
% New Logo ARR        1.50%
                                        o Existing content products:
% Expansion           0.00%                      Legal summaries into new market: ~ 20 new sales @ £7,000 = £140,000
% Contraction         0.00%                      Learning courses into new market: ~ 20 new sales @ £7,000 = £140,000
% Churned             0.00%             o New content products / new logo:
Starting QTR         Q2FY25                      5 new logos acquired, purchasing primary BL product and CCS content (£££ TBC)
Weighted (Ramp)          4
                                  PHASE 3 (FY26)
                                  -  Goal: 25% of circa 30,000 customers x 1 item of content each @ £1,000 p/item = £7,5M ARR

                                  PHASE 4 (FY27)
                                  - Goal: 35% of circa 50,000 customers x 1 item of content each @ £1,000 p/item = £17.5M ARR
     Business Case                Estimated Cost                                    Resource Cost Breakdown
     The Financials [Update]             Impact                        Amount   Dev Resources                          10
                                  FY24                                   £0     Duration Months                        24
                                  FY25                                  £495K   % US                                  20%
                                                                                % KL                                  30%
                                  FY26                                  £495K   % IN                                   0%
 Revenue
                                                                                % UK                                  30%
        Impact        Amount                                                    % AUS                                 20%
3 Year Revenue      £17,780,000
Payback Period      18 months
3 Year ROI            1,364%      Assumptions – What needs to be true.
Cost                  £900K



                                         BUSINESS CASE             COSTS        REVENUE                   ROI
 Revenue Levers
                                         #1 CS CORE                £495K        -                         TBC
          Lever    Improvement
                                         #2 CONTENT LIBRARY        -            + TBC                     TBC
% New Logo ARR        1.50%
% Expansion           0.00%              #3 LEARNING               -            TBC                       TBC
% Contraction         0.00%
% Churned             0.00%              #4 EFFICIENCIES           -            (Savings)                 TBC
Starting QTR         Q2FY25
                                         #5 NEW CONTENT            -            TBC – Hard to model now   TBC
Weighted (Ramp)          4

                                                           TOTAL   £495K        Total TBC                 Total TBC
     Business Case                Estimated Cost                                                   Resource Cost Breakdown
     The Financials [Update]             Impact                      Amount                       Dev Resources                     10
                                  FY24                                 £0                         Duration Months                   24
                                  FY25                                £495K                       % US                             20%
                                                                                                  % KL                             30%
                                  FY26                                £495K                       % IN                              0%
 Revenue
                                                                                                  % UK                             30%
        Impact        Amount                                                                      % AUS                            20%
3 Year Revenue      £17,780,000
Payback Period      18 months
3 Year ROI            1,364%      Assumptions – What needs to be true.
Cost                  £900K



                                                                                          UNITS
 Revenue Levers                             BUSINESS CASE                                                             UNIT PRICE
                                                                                                                                     TOTAL
                                                                                                                                      ARR
                                                                     FY25          FY26            FY27       TOTAL
          Lever    Improvement
                                         #2 CONTENT LIBRARY     10            50             100            160       1000         160,000
% New Logo ARR        1.50%
% Expansion           0.00%              #3 LEARNING            50            100            200            350       1000         350,000
% Contraction         0.00%
% Churned             0.00%              #4 EFFICIENCIES        10% savings
Starting QTR         Q2FY25
                                         #5 NEW CONTENT         50            100            200            350       1000         350,000
Weighted (Ramp)          4               (see list of opps)
                                                        TOTAL                                                                      860,000
       Charter
       Project Overview
Summary                                                        Objectives
Content Marketplace (see separate Business Case)               Objective 1     Build POC, surfacing summaries of content from multiple
                                                                               content solutions
                                                               Objective 2     ​Surface content marketplace to all IHome customers with
                                                                                the ability to purchase content solutions via Revenue team
                                                                                interactions
                                                               Objective 3     ​Automate the purchase of content solutions, through a fully
                                                                                ecommerce model
Strategic Alignment                                                                                      High      Medium     Low   None



       New Logo                    Cross Sell      Expansion          EDITDA                 NPS                            CHURN


Scope (Key Deliverables)                                       Milestones (Name and Description)
In                                          Out                Name              Date                           Description
                                                               Dev Complete
                                                               Go To Market
                                                               Milestone
                                                               Milestone
                                                               Milestone
       Charter
       Project Overview
Summary                                                     Objectives
Learning (see separate Business Case)                       Objective 1     Deliver New Capability to increase X by Y on this date

                                                            Objective 2

                                                            Objective 3



Strategic Alignment                                                                                 High      Medium     Low   None



       New Logo                    Cross Sell   Expansion          EDITDA                NPS                           CHURN


Scope (Key Deliverables)                                    Milestones (Name and Description)
In                                        Out               Name              Date                         Description
Initiative 1                                                Dev Complete

Initiative 2                                                Go To Market
                                                            Milestone
                                                            Milestone
                                                            Milestone
       Charter
       Project Overview
Summary                                                        Objectives
NORAM content (see separate business case)                     Objective 1     Deliver New Capability to increase X by Y on this date

                                                               Objective 2

                                                               Objective 3



Strategic Alignment                                                                                    High      Medium     Low   None



       New Logo                   Cross Sell       Expansion          EDITDA                NPS                           CHURN


Scope (Key Deliverables)                                       Milestones (Name and Description)
In                                           Out               Name              Date                         Description
Initiative 1                                                   Dev Complete

Initiative 2                                                   Go To Market
                                                               Milestone
                                                               Milestone
                                                               Milestone
       Charter
       Project Overview
Summary                                                                 Objectives
CCS Operational efficiencies (see separate Business Case)               Objective 1     Deliver New Capability to increase X by Y on this date

                                                                        Objective 2

                                                                        Objective 3



Strategic Alignment                                                                                             High      Medium     Low   None



       New Logo                     Cross Sell              Expansion          EDITDA                NPS                           CHURN


Scope (Key Deliverables)                                                Milestones (Name and Description)
In                                           Out                        Name              Date                         Description
Initiative 1                                                            Dev Complete

Initiative 2                                                            Go To Market
                                                                        Milestone
                                                                        Milestone
                                                                        Milestone
Assumptions Guide


Revenue
• Pricing Model
• Churn rate

Marketing & Sales
• CAC

Competitive Landscape
Sales
Marketing
PS
CCS: The vision

  The leading Compliance Content as a Service (CCaaS)
  solution
   The world’s largest and most valuable library of best-practice,
   real-time compliant risk, regulatory, compliance content and
   information, immediately usable, accessible via the cloud,
   developed and maintained for mass distribution, by the world’s
   leading and most efficient distributed team of risk and
   compliance content experts.

   50,000 customers x 1 content item @ £1,000 p/item = £50m ARR


and the USer Stories of Ihome, as below:

iHome User Stories

Suggested MVP – highlighted light blue
Setting/User Management:
User Set Up & Profile Management: As a tenant admin   , I want to set up new users within my organization and manage my profile settings, including updating personal information  , changing passwords, and managing notification preferences.
As a user, I want to manage my profile settings, including updating personal information, changing passwords , and managing notification preferences   (Global on/off button).
As an Ideagen Tenant Admin, I want to set up and provision new tenant admin, be able to all what a Tenant Admin and a User can do. 
Definition: 
* Ideagen Tenant Admin – This is a role that can provision instances of an application, can assign licenses to the tenant. And can perform any action a Customer Tenant Admin can do (see below)

* Customer Tenant Admin       – Can modify tenant settings (e.g., name of company, etc.), can add/deactivate users, can assign licenses to users (from the pool of licenses available), can modify users, can send password resets for users 


Dashboard and BI:
Beyond the Aha! link to personas, here’s also info at a high level from Stephanie:

 
Customizable Dashboard: As a finance manager, I want to customize my dashboard with widgets and shortcuts to quickly access the features and functionalities that are relevant to  my role and responsibilities, such as incident trends, compliance status, and operational performance metrics. 
Integration with BI Tools:  As an analyst , I want seamless integration with BI tools within the dashboard interface to visualize and analyze data directly from the dashboard. Preferably using click and drag  functionality to create interactive visualizations and dashboards tailored to my specific analysis needs.
As an auditor, I want seamless integration with BI tools within the dashboard interface of IHOME to access and analyze audit data. The integration should enable me to gather and analyze audit data effectively, maintain independence, and collaborate with internal teams while ensuring transparency and accountability in audit processes.
Interactive Data Visualization & Predictive Modeling: As a  data scientist, I want access to advanced data visualization tools and predictive modeling capabilities within the BI section/Dashboard of IHOME.
As an executive manager, I want access to advanced data visualization and predictive modeling capabilities within the BI section/Dashboard of IHOME to address challenges related to uncertainty, talent retention, stakeholder expectations, and technology adoption. I want to analyze market trends, identify talent gaps, and anticipate future challenges to develop agile strategies and foster innovation within the organization. The BI section should provide John with actionable insights and recommendations derived from predictive modeling.
Customizable Reports: As a  compliance officer, I want the ability to create and customize reports within the BI section to track      key compliance indicators and measure the effectiveness of products in ensuring regulatory compliance and mitigating risks.
As an auditor, I require the ability to create and customize reports within the BI section of IHOME to communicate audit findings, recommendations, and insights effectively. I need customizable reporting functionalities that allow me to generate comprehensive audit reports quickly, ensure proper distribution, and track report engagement.


Product Page:
Access to Licensed Products: As a user, I want access to all the products that I have access to (and that my organization has licenses for). 
Access to Different Instances: As a user, I want to access all the different instances that I have access to.
Demo and Trial Access: As a user (manager), I want the ability to request demos and trials for new Ideagen products to evaluate their suitability for my organization before making a purchase decision.

Tasks, Calendar and Notification:
Status Updates & Integration with Calendar: As a manager, I want to view the status of tasks and projects across my team in real-time and have tasks and deadlines automatically synced with my iHome calendar for better organization and time management. 
As a user, I want to view the status of my tasks and projects, with tasks and deadlines automatically synced with my iHome calendar.
Reminders and Notifications: As a user, I want to receive reminders and notifications for upcoming events to ensure I stay on track and meet my commitments. I want to have them automatically reflected in the calendar. I want to have the ability to customize my notification preferences (email, SMS, Push Notification).
Real-time Alerts: As a  Support, I want to receive real-time alerts for critical issues and escalations within Ideagen products to take immediate action and minimize downtime .
As a Tenant Admin, I want to receive real-time alerts for business issues within the products which my organization has licenses to.

Activity Feed:
Real-time Updates & Filtering: As a user, I want to view a real-time activity feed that highlights recent actions, events, and interactions within Ideagen products, with the ability to filter and search for relevant information and conversations.

Support Ticketing System & Community Engagement:
Integrated Support Portal & Self-Service Troubleshooting (Zendesk Integration): As a user, I want to access the support ticketing system within IHOME to submit and track support requests, access knowledge base articles, and engage with support agents for assistance with Ideagen products, along with self-service troubleshooting resources.  
As a manager, I would like to see tickets raised by my reports and the corresponding updates on the tickets.
Interactive Discussion Forums & Knowledge Sharing (Community Integration): As a user, I want to participate in interactive discussion forums and user groups within IHOME, connecting with peers, sharing insights, and seeking advice on best practices and product usage.

Learning Management System (LMS) Integration:
Training: As a user, I want to access training and certification courses within IHOME through integration with the LMS, enabling continuous learning and skill development, along with tracking learner progress and performance.

Unified Identity Management:
Single Sign-On (SSO) Integration & Centralized Notification Inbox: As a user, I want to log in to IHOME with my organization’s credentials, seamlessly access all connected Ideagen products, and receive notifications in a centralized inbox with customizable preferences. 
As a tenant admin, I would like to have the ability to set up the password policies for my users (follows Cognito/Auth0’s password policy – choose password length and password character/number/special character requirement)

Common Licensing Framework:
Unified License Management: As an admin, I want to manage licenses for all connected Ideagen products from a common service within IHOME.

Common Reporting & Comprehensive Change Log:
Cross-Product Reporting & Unified Change Log: As a manager, I want to have a cross-product reporting within IHOME, identifying key reporting requirements, and access a unified change log repository.
As a Risk Manager, I want to access cross-product reporting within IHOME (for products that I have access to) to identify key risk indicators and trends across all connected Ideagen products. Additionally, I need access to a unified change log repository to track changes and updates across these products.
As an Audit Manager, I want access to cross-product reporting within IHOME to identify key audit findings and trends across all connected Ideagen products (for products that I have access to). Additionally, I need access to a unified change log repository to track changes and updates across these products.

Automated Provisioning Process:
Automated Tenant Provisioning: As an tenant admin, I want to automate the provisioning process for new tenants and users within IHOME from onboarding to completion.   

Artificial Intelligence (Virtual Assistance):
AI-Powered Insights & Search: As a user, I want to receive personalized insights and recommendations from an AI assistant embedded within IHOME, with the ability to interact using natural language commands and queries, and intelligent search capabilities.
Other items that need to be added
•	Change Log
•	Data sharing between products
•	Access to content (compliance content marketplace, etc.)

Change Log:
Unified Change Log Repository: As a user, I want access to a comprehensive change log within IHOME, providing visibility into all changes and updates across connected Ideagen products that I have access to.
Granular Change Tracking: As a manager, I want the ability to track and audit changes at a granular level within IHOME, including user actions, configuration changes, and system events.
Change Log Setting: As an admin, I want to control access to the change log within IHOME based on user roles and permissions, ensuring that only authorized users can view and manage change log settings and data.

Data Sharing Between Products:
Seamless Data Exchange: As a user, I want seamless data sharing and integration between connected Ideagen products within IHOME that I have access to, allowing for the exchange of information and insights across different functionalities and domains.
Secure Data Transmission: As a security admin, I want to ensure that data sharing between products within IHOME adheres to robust security protocols and encryption standards, safeguarding sensitive information and ensuring compliance with data privacy regulations.

Access to Content:
Content Marketplace: As a user, I want access to content marketplace within IHOME, offering a collection of regulatory documents, standards, and best practices relevant to my industry and jurisdiction, enabling me to stay updated and compliant with legal regulatory requirements.


Assumptions based on Megan’s Concept    
https://www.figma.com/proto/KqWCvcUjY0KlmGgOTRZR2Y/Future-Of%3A-Home?page-id=344%3A143103&type=design&node-id=344-143104&viewport=-331%2C335%2C0.49&t=3zaa7TE3kQv5eVXf-1&scaling=min-zoom&starting-point-node-id=344%3A143104
Base Assumptions (Must be handled  )   
•	All users accessing IHOME are authenticated through platform authentication services and thus are uniquely identified   and their identity is the same in any product connected to IHOME 
•	There is a central database that stores IHOME related information about each identity that logs into it (e.g., for widget configuration)
•	There are some UI elements that are applicable to users based on their role within their organization (NOTE: This is assumed, but not explicitly demonstrated within the concept UI)
•	There exists a user profile page where users may perform basic actions such as changing their demographics, and if applicable (not federated) email address and password
•	There exists a provisioning page where users may be provisioned to licenses a tenant owns by a tenant administrator
Main Screen    
•	We know the name of the user
•	We know the time zone of the user
•	We know the user’s location
•	We have the ability to query weather data from their location
•	Apps have the ability to surface actions required of the user  
•	Apps must specify which instance of the app is surfacing the action
•	We have the ability to know what actions are overdue (presumably via due date information and user’s current date/time)
•	Apps have the ability to surface alerts to the  user  
•	Apps must specify which instance of the app is surfacing the alert
•	We have the ability to know what alerts are new (presumably since the user last looked?)
•	The user has a calendar maintained in IHOME  
•	Apps have the ability to put events on the user’s calendar
•	Apps must specify which instance of the app is surfacing the event
•	There is the concept of widgets that exist on this screen  
•	Widgets may be resized to half or full size (width)  
•	Some widgets may be removed   (TBD on how to enforce, but it’s clear that you shouldn’t be able to remove “My Apps” for instance)
•	Widgets may be repositioned / reordered
My Apps Widget  
•	We know what apps    the user has access to
•	We know what instances of a product the user has access to (NOTE: This is not pictured in Megan’s prototype, but we know from Home Marketing and just general usage that this is required)
•	We know what business line each app corresponds to  
•	We know the current version of each app
•	There is a “More Apps” button or equivalent that takes the user to the More Apps screen
•	NOTE: ignoring Megan’s “Update” concept for now     

•	My Quick Actions Widget   
•	Apps have the ability to surface “quick actions” to IHOME
•	Apps must provide information about which instance of the app is surfacing the quick action
•	Users have the ability to add or remove quick actions from this widget

•	Learn Widget 
•	We know what training modules a user has access to
•	We know what training the user must complete and by when 
•	We know when new training modules are made available to the user
•	We know the categorization  of all training modules available to the user
•	We know the approximate time to complete of each training module
•	We know user can try certain training modules via Demos 

•	Compliments  Your Business Widget 
•	We know what products might compliment a user based on their business 
•	For each product that might compliment a user’s business, we know what action the user can take to interact with it (e.g., Add to Cart,  Book a demo, Learn More, Get in Touch)
•	For some apps that might compliment the user’s business, we will provide the ability to learn more about the app 
•	For some apps that might compliment the user’s business, we will provide the ability to book a demo with sales 
•	For apps that users wishes to book a demo for, we know the dates and times that demos can be booked and upon booking we will send a notification to the appropriate sales resources  
Discover Widget
•	There exists other content that the user might want to discover such as reports and news 
•	We will display that content to the users
•	We know the categorization for each bit of content that the user might want to discover
Recents Widget
•	Apps have the ability to surface recently viewed documents
•	Apps must provide information about which instance of the app is surfacing the recent document
Community Widget
	
•	We have the ability to retrieve community posts and display them
Customization
•	The user has access to a customization UI
•	The user can customize the background color of all other UIs
•	The customization UI allows users to add widgets to the main screen  
Actions Required Slideout 
•	We know the title, status, due date, and completion status of all actions apps have surfaced to us
•	We need to be able to filter     the actions list
•	We need to be able to search the actions list
Needs Your Attention Slideout
•	TBD – Assumed based on Actions Required slideout, but not yet in prototype
Upcoming Events Slideout
•	TBD – Assumed based on Actions Required slideout, but not yet in prototype
More Apps Screen  
•	All assumptions from My Apps Widget & Compliments Your Apps Widget
•	We know what products are available to a user’s organization even if the user themselves does not have access to it
•	For apps that are available to the organization but not the specific user, the ability to request access to the app exists
•	Requesting access allows the user to specify the reason they need access to the app and send the request to their company’s administrator to approve or deny access  
•	We know all products that are available including their keywords, industry, regulation, and standards information for purposes of filtering  
•	We know all products that are available including their keywords, industry, regulation, and standards information for purpose of searching
•	We know about apps that integrate with Ideagen apps (e.g., APIs, Add-ons, etc.)   
•	NOTE: Ignoring “something exciting” banner for now
Learn Screen  
•	All assumptions from the Learn widget
•	We know what courses each user has started, completed, or needs to complete
•	We know what training to suggest to a user based on their characteristics   
•	We know all learning modules that exist including their keywords, tutorial type, skill level, and duration for the purposes of filtering 
•	We know all learning modules that exist including their keywords, tutorial type, skill level, and duration for the purposes of searching
•	We will be able to either keep a leaderboard of people’s training completion or integrate with a leaderboard provided by an LMS
•	We will be able to determine achievements and a user’s progress to them that a user may complete to earn points on the leaderboard
•	We will be able to integrate with common social media sites to allow users to share their learning leaderboard progress
•	We will be able to filter and search on Leaderboard and Achievement 
Discover Screen
•	All assumptions from the Discover widget
•	We know content that exists in an Ideagen content library
•	We know how to suggest content to a user based on their characteristics
•	There is a news feed that can be displayed to users  
•	We can integrate with Community such as to display relevant   posts
•	There is a feed of upcoming   events
•	Users may add an event to their calendar
Insight  Screen   
•	There is a concept of visualization widgets that are displayed on this screen
•	Apps have the ability to define entities that we will show visualizations of (e.g., tasks, audits, incidents, risks)  
•	Visualizations will have a permissions structure that we can leverage so as to know who has access to which visualizations
•	Within the entities that an app defines, apps have the ability to tell us when these entities change state (e.g., complete, in progress, overdue)
•	We will store entity state details for the purposes of visualization by date and app  
•	We will be able to display trend analysis of metrics surfaced by some or all visualizations
•	Where apps report on entities of the same category we will be able to aggregate that data
•	We will know all possible widgets that could be displayed on this page as defined somewhere
•	We will provide a customization screen similar to that available for the main screen that allows for the addition, removal, reordering, and resizing of insight widgets  
•	A tasks widget will be available to show outstanding tasks (NOTE: I’m not sure the insights screen is the right spot for this, but probably has same implications if it’s elsewhere)
•	We will be able to filter a task (in Task Widget). 
•	We will be able to search for tasks (in Task Widget). 
Task Widget
•	As discussed in the main screen, apps have the ability to surface tasks to us including their due date
•	Users may take an action directly on a task in this widget in order to complete the task (see below as example)
Task Update Slideout
•	Some or all tasks have the ability to be acted upon in IHOME directly (e.g., document approvals)
•	Apps may surface additional details about tasks based on the type of task
•	For example, a document approval task can surface the document title, manager, number of revisions, summary of changes, and approval history
•	Each  
Insights Widgets 
•	Widgets can filter by app and by date (e.g., weekly, monthly, daily)
•	Widgets will enable a user to see the raw data that contributes to the visualization (e.g., list of risks, tasks, etc. corresponding to the displayed graph)
Content Cloud Screen
•	TBD
Community Screen
•	TBD
Support Screen      (NOTE: Megan’s UI does not have this yet so these are assumptions)
•	We have the ability to integrate with Zendesk at a user identity level
•	We have the ability to query Zendesk for tickets related to identities
•	We will show the user all tickets they have raised
•	We will show some users (e.g., managers) all tickets raised for their organization

Questions for UI/UX Team
•	Define maximum numbers of things like apps, links, actions that should be displayed in a single UI as well as default “recency” ranges


pls suggest how I can integrate CCS into iHome.