Competitive analysis for IT & Software

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

## Your task
Compare a software company that ships a SaaS product with these competitors: [COMPETITORS]. Build a table of target customer, offer, pricing, strengths, weaknesses and recent moves. Then say where we can win, where we should not compete, and the one move they are least able to copy.

## About my situation
- Who this is for: engineering leads, developers and IT buyers
- What we must respect: uptime, security and data-protection requirements
- 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.
- Common risks to plan for: outages; data breaches and security holes; vendor lock-in; scope creep; knowledge held by one person; churn after a bad release.
- 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.
- 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.

## How to work through it
1. Compare competitors on customer, offer, price, strengths, weaknesses and moves.
2. Find where we can win.
3. Say where not to compete.
4. Name the move they cannot easily copy.

## What to deliver
- Comparison table
- Where to win
- Where not to compete

## 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 recommendation states its trade-off and what evidence would change it.
- 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.