RICE prioritisation for IT & Software

You are an expert in this kind of work, and you know the IT & Software sector from the inside.

## Your task
Prioritise these feature ideas for a software company that ships a SaaS product using RICE (reach, impact, confidence, effort). Explain the estimate behind each score, rank the list, and point out where the ranking conflicts with uptime, security and data-protection requirements.

## About my situation
- Who this is for: engineering leads, developers and IT buyers
- How we measure success: deployment frequency and uptime

## What matters in IT & Software
- How customers decide: technical evaluators and budget owners decide together; they judge security, integrations, total cost and support quality; free trials and proofs of concept are common; contracts are usually annual and renew.
- Numbers that matter: deployment frequency; lead time for changes; change failure rate; mean time to recovery; uptime against SLA; MRR/ARR; net revenue retention; logo churn.
- Rules and standards that usually apply: data-protection law (GDPR in the EU, the DPDP Act 2023 in India, CCPA in California); SOC 2 or ISO 27001 security audits; OWASP secure-coding practice; open-source licence terms; the uptime and support promises in customer SLAs.
- Tools commonly used: GitHub or GitLab; Jira; Slack; AWS, Azure or GCP; Datadog or Grafana; PostgreSQL or MySQL.
- Rules differ by country. If I have not said where I work, ask me, and do not present one country's law as if it applied everywhere.

## What I will give you
Ideas: [PASTE IDEAS]

## How to work through it
1. Estimate reach, impact, confidence and effort.
2. Explain each estimate.
3. Rank the list.
4. Point out conflicts with constraints.

## What to deliver
- RICE table
- Ranked list
- Conflicts

## Rules
- Make every point specific to my situation and my industry; replace generic advice with detail that fits.
- Use plain language, short sentences, and tables where they make the answer easier to scan.
- Use only the facts I give you. Do not invent figures, laws, sources or quotes. Mark anything you had to assume with "Assumption:".
- If something important is missing, ask me up to 3 short questions before you start.

## Before you answer
Check your draft against this list and fix anything that fails:
- Each feature is tied to a user problem and a measurable outcome.
- It is written for a software company that ships a SaaS product; nothing in it would read the same for any other business.
- Nothing in it breaks uptime, security and data-protection requirements.
- Every item under "What to deliver" is included.