Vertical Landing Pages Implementation Plan

For Claude: REQUIRED SUB-SKILL: Use superpowers:executing-plans to implement this plan task-by-task.

Goal: Build 8 consistent, SEO-optimized vertical landing pages for SQUR's website using a shared template.

Architecture: Static HTML pages in squr-website/verticals/, sharing CSS via styles-verticals.css, using the existing loadIncludes() mechanism for header/footer. Each page follows an identical section structure with industry-specific content. No framework migration needed.

Tech Stack: HTML5, CSS3, vanilla JavaScript, JSON-LD structured data

Design doc: docs/plans/2026-02-25-vertical-landing-pages-design.md

---

Task 1: Merge Remote Changes

Context: Local main and origin/main have diverged. Remote has commit 25d9a83 (vertical pages). Local has 3 Human Deep-Dive commits. We need to merge to get both.

Step 1: Merge origin/main into local

git merge origin/main -m "Merge remote vertical landing pages into local"

Expected: Clean merge (no overlapping files — remote changed squr-website/verticals/ and includes/footer.html, local changed strategy/ docs).

Step 2: Verify merge succeeded

git log --oneline -5

Expected: Merge commit on top, both branches' commits visible.

Step 3: Verify the remote files are now local

ls -la squr-website/verticals/

Expected: fintech.html, healthtech.html, industrial.html all present.

---

Task 2: Create Shared Vertical Stylesheet

Files: - Create: squr-website/styles-verticals.css

Context: Currently the fintech page has ~250 lines of inline <style>. We extract and unify this into a shared stylesheet that all vertical pages will reference. The design uses the main site's dark theme, #0066FF blue accent, and existing patterns from styles.css.

Step 1: Create squr-website/styles-verticals.css

This CSS file should contain all styles needed by vertical pages, organized by section:

/* ==========================================================================
   SQUR Vertical Landing Pages - Shared Styles
   All vertical pages share this stylesheet on top of styles.css
   ========================================================================== */

/* ---------- Hero Section ---------- */
.vertical-hero {
    padding: 140px 0 80px;
    text-align: center;
    background: linear-gradient(180deg, #0a0a0a 0%, #121212 100%);
    position: relative;
    overflow: hidden;
}

.vertical-hero::before {
    content: '';
    position: absolute;
    top: 0;
    left: 50%;
    transform: translateX(-50%);
    width: 800px;
    height: 800px;
    background: radial-gradient(circle, rgba(0, 102, 255, 0.08) 0%, transparent 70%);
    pointer-events: none;
}

.vertical-hero h1 {
    font-size: 3rem;
    font-weight: 800;
    color: #FFFFFF;
    margin-bottom: 16px;
    line-height: 1.2;
}

.vertical-hero .hero-subtitle {
    font-size: 1.25rem;
    color: #9CA3AF;
    max-width: 600px;
    margin: 0 auto 12px;
    line-height: 1.6;
}

.vertical-hero .hero-tagline {
    font-size: 0.95rem;
    color: #0066FF;
    font-weight: 600;
    margin-bottom: 32px;
}

.vertical-hero .hero-ctas {
    display: flex;
    gap: 16px;
    justify-content: center;
    flex-wrap: wrap;
}

.vertical-hero .hero-ctas .btn-primary {
    background: #0066FF;
    color: #FFFFFF;
    padding: 14px 32px;
    border-radius: 8px;
    font-size: 1rem;
    font-weight: 600;
    text-decoration: none;
    transition: all 0.3s ease;
    border: 2px solid #0066FF;
}

.vertical-hero .hero-ctas .btn-primary:hover {
    background: #0052CC;
    border-color: #0052CC;
    transform: translateY(-2px);
    box-shadow: 0 4px 12px rgba(0, 102, 255, 0.3);
}

.vertical-hero .hero-ctas .btn-secondary {
    background: transparent;
    color: #FFFFFF;
    padding: 14px 32px;
    border-radius: 8px;
    font-size: 1rem;
    font-weight: 600;
    text-decoration: none;
    transition: all 0.3s ease;
    border: 2px solid rgba(255, 255, 255, 0.3);
}

.vertical-hero .hero-ctas .btn-secondary:hover {
    border-color: #FFFFFF;
    transform: translateY(-2px);
}

/* ---------- Challenges Section ---------- */
.vertical-challenges {
    padding: 80px 0;
    background: #121212;
}

.vertical-challenges h2 {
    text-align: center;
    color: #FFFFFF;
    font-size: 2rem;
    font-weight: 700;
    margin-bottom: 48px;
}

.challenges-grid {
    display: grid;
    grid-template-columns: repeat(3, 1fr);
    gap: 24px;
    max-width: 1100px;
    margin: 0 auto;
}

.challenge-card {
    background: #1A1A1A;
    border-radius: 12px;
    padding: 32px 28px;
    border: 1px solid rgba(255, 255, 255, 0.06);
    transition: transform 0.3s ease, border-color 0.3s ease;
}

.challenge-card:hover {
    transform: translateY(-4px);
    border-color: rgba(0, 102, 255, 0.3);
}

.challenge-card .card-icon {
    font-size: 2rem;
    margin-bottom: 16px;
    display: block;
}

.challenge-card h3 {
    color: #FFFFFF;
    font-size: 1.2rem;
    font-weight: 700;
    margin-bottom: 12px;
}

.challenge-card p {
    color: #9CA3AF;
    font-size: 0.95rem;
    line-height: 1.6;
    margin: 0;
}

/* ---------- How SQUR Helps Section ---------- */
.vertical-solution {
    padding: 80px 0;
    background: #0F0F0F;
}

.vertical-solution h2 {
    text-align: center;
    color: #FFFFFF;
    font-size: 2rem;
    font-weight: 700;
    margin-bottom: 48px;
}

.solution-grid {
    display: grid;
    grid-template-columns: repeat(2, 1fr);
    gap: 24px;
    max-width: 900px;
    margin: 0 auto;
}

.solution-item {
    display: flex;
    gap: 16px;
    padding: 24px;
    background: rgba(0, 102, 255, 0.04);
    border-radius: 12px;
    border: 1px solid rgba(0, 102, 255, 0.1);
}

.solution-item .item-icon {
    flex-shrink: 0;
    width: 40px;
    height: 40px;
    display: flex;
    align-items: center;
    justify-content: center;
    font-size: 1.5rem;
}

.solution-item h3 {
    color: #0066FF;
    font-size: 1.05rem;
    font-weight: 700;
    margin-bottom: 8px;
}

.solution-item p {
    color: #9CA3AF;
    font-size: 0.9rem;
    line-height: 1.5;
    margin: 0;
}

/* ---------- Compliance Section ---------- */
.vertical-compliance {
    padding: 80px 0;
    background: #121212;
}

.vertical-compliance h2 {
    text-align: center;
    color: #FFFFFF;
    font-size: 2rem;
    font-weight: 700;
    margin-bottom: 16px;
}

.vertical-compliance .compliance-subtitle {
    text-align: center;
    color: #9CA3AF;
    font-size: 0.95rem;
    max-width: 650px;
    margin: 0 auto 48px;
    line-height: 1.6;
}

.compliance-grid {
    display: grid;
    grid-template-columns: repeat(auto-fit, minmax(250px, 1fr));
    gap: 24px;
    max-width: 1100px;
    margin: 0 auto;
}

.compliance-card {
    background: #1A1A1A;
    border-radius: 12px;
    padding: 28px 24px;
    border-left: 3px solid #0066FF;
}

.compliance-card h3 {
    color: #FFFFFF;
    font-size: 1.1rem;
    font-weight: 700;
    margin-bottom: 10px;
}

.compliance-card p {
    color: #9CA3AF;
    font-size: 0.9rem;
    line-height: 1.6;
    margin: 0;
}

/* ---------- Stats Banner ---------- */
.vertical-stats {
    padding: 60px 0;
    background: linear-gradient(135deg, #0a1628 0%, #0F172A 100%);
    border-top: 1px solid rgba(0, 102, 255, 0.15);
    border-bottom: 1px solid rgba(0, 102, 255, 0.15);
}

.stats-grid {
    display: grid;
    grid-template-columns: repeat(4, 1fr);
    gap: 32px;
    max-width: 1000px;
    margin: 0 auto;
    text-align: center;
}

.stat-item .stat-value {
    font-size: 2.5rem;
    font-weight: 800;
    color: #0066FF;
    line-height: 1;
    margin-bottom: 8px;
}

.stat-item .stat-label {
    font-size: 0.85rem;
    color: #9CA3AF;
    line-height: 1.4;
}

/* ---------- FAQ Section ---------- */
.vertical-faq {
    padding: 80px 0;
    background: #0F0F0F;
}

.vertical-faq h2 {
    text-align: center;
    color: #FFFFFF;
    font-size: 2rem;
    font-weight: 700;
    margin-bottom: 48px;
}

.faq-list {
    max-width: 800px;
    margin: 0 auto;
    display: flex;
    flex-direction: column;
    gap: 12px;
}

.faq-item {
    background: #1A1A1A;
    border-radius: 10px;
    border: 1px solid rgba(255, 255, 255, 0.06);
    overflow: hidden;
}

.faq-question {
    width: 100%;
    background: none;
    border: none;
    padding: 20px 24px;
    display: flex;
    justify-content: space-between;
    align-items: center;
    cursor: pointer;
    color: #FFFFFF;
    font-size: 1rem;
    font-weight: 600;
    text-align: left;
    transition: color 0.3s ease;
}

.faq-question:hover {
    color: #0066FF;
}

.faq-question .faq-toggle {
    font-size: 1.2rem;
    color: #0066FF;
    transition: transform 0.3s ease;
    flex-shrink: 0;
    margin-left: 16px;
}

.faq-item.active .faq-question .faq-toggle {
    transform: rotate(45deg);
}

.faq-answer {
    max-height: 0;
    overflow: hidden;
    transition: max-height 0.3s ease;
}

.faq-answer-inner {
    padding: 0 24px 20px;
    color: #9CA3AF;
    font-size: 0.95rem;
    line-height: 1.7;
}

.faq-item.active .faq-answer {
    max-height: 300px;
}

/* ---------- Bottom CTA Section ---------- */
.vertical-cta {
    padding: 80px 0;
    background: linear-gradient(135deg, #001a4d 0%, #0066FF 100%);
    text-align: center;
}

.vertical-cta h2 {
    color: #FFFFFF;
    font-size: 2rem;
    font-weight: 700;
    margin-bottom: 16px;
}

.vertical-cta p {
    color: rgba(255, 255, 255, 0.85);
    font-size: 1.1rem;
    max-width: 500px;
    margin: 0 auto 32px;
    line-height: 1.6;
}

.vertical-cta .hero-ctas {
    display: flex;
    gap: 16px;
    justify-content: center;
    flex-wrap: wrap;
}

.vertical-cta .btn-start {
    background: #FFFFFF;
    color: #0066FF;
    padding: 14px 32px;
    border-radius: 8px;
    font-size: 1rem;
    font-weight: 600;
    text-decoration: none;
    transition: all 0.3s ease;
    border: 2px solid #FFFFFF;
}

.vertical-cta .btn-start:hover {
    background: rgba(255, 255, 255, 0.9);
    transform: translateY(-2px);
    box-shadow: 0 4px 12px rgba(0, 0, 0, 0.2);
}

.vertical-cta .btn-demo {
    background: transparent;
    color: #FFFFFF;
    padding: 14px 32px;
    border-radius: 8px;
    font-size: 1rem;
    font-weight: 600;
    text-decoration: none;
    transition: all 0.3s ease;
    border: 2px solid rgba(255, 255, 255, 0.5);
}

.vertical-cta .btn-demo:hover {
    border-color: #FFFFFF;
    transform: translateY(-2px);
}

/* ---------- Responsive ---------- */
@media (max-width: 1024px) {
    .challenges-grid {
        grid-template-columns: repeat(2, 1fr);
    }
    .stats-grid {
        grid-template-columns: repeat(2, 1fr);
        gap: 24px;
    }
}

@media (max-width: 768px) {
    .vertical-hero {
        padding: 120px 20px 60px;
    }
    .vertical-hero h1 {
        font-size: 2rem;
    }
    .challenges-grid,
    .solution-grid {
        grid-template-columns: 1fr;
    }
    .stats-grid {
        grid-template-columns: repeat(2, 1fr);
        gap: 20px;
    }
    .stat-item .stat-value {
        font-size: 2rem;
    }
    .vertical-hero .hero-ctas,
    .vertical-cta .hero-ctas {
        flex-direction: column;
        align-items: center;
    }
}

Step 2: Verify the file is accessible from verticals/

The file lives at squr-website/styles-verticals.css. Vertical pages at squr-website/verticals/*.html reference it as ../styles-verticals.css.

Step 3: Commit

git add squr-website/styles-verticals.css
git commit -m "Add shared stylesheet for vertical landing pages"

---

Task 3: Create the B2B SaaS Vertical Page

Files: - Create: squr-website/verticals/saas.html

Context: This is the first vertical built with the new template. All subsequent verticals follow this exact structure. B2B SaaS is SQUR's primary GTM track (2,200+ target companies in Germany).

Step 1: Create squr-website/verticals/saas.html

The complete page follows this structure (provide the full HTML):

1. Head: Title "Autonomous Pentesting for B2B SaaS | SQUR", meta description, OG/Twitter tags, canonical URL, link to ../styles.css, ../styles-enhancements.css, ../styles-verticals.css, FAQ JSON-LD schema with 5-6 SaaS-specific questions, WebPage schema, consent-check.js, GTM script (copy exact pattern from existing fintech.html head)

2. Body: class="dark-theme", GTM noscript, #header-placeholder div, then <main> containing:

3. Hero section (section.vertical-hero):

4. H1: "Autonomous Pentesting for B2B SaaS"
5. Subtitle: "Ship faster without security bottlenecks. Get the pentest reports your customers and auditors demand — in 24 hours, not weeks."
6. Tagline: "SOC 2 Evidence · ISO 27001 Support · CI/CD Friendly"

7. Two CTAs: "Start Pentest" → https://app.squr.ai, "Book a Demo" → /book-a-demo.html

8. Challenges section (section.vertical-challenges):

9. H2: "Why SaaS Companies Need Autonomous Pentesting"

10. 3 cards:

    • "Vendor Security Questionnaires" — "Enterprise customers require pentest reports before signing. Traditional pentests take weeks and cost thousands — creating bottlenecks in your sales pipeline."
    • "Compliance Pressure" — "SOC 2 and ISO 27001 audits require evidence of regular security testing. Annual manual pentests leave gaps that auditors notice."
    • "Rapid Release Cycles" — "You deploy daily but test security quarterly. Every release is a potential window of exposure that goes unvalidated."

11. Solution section (section.vertical-solution):

12. H2: "How SQUR Helps SaaS Teams"

13. 4 items:

    • "24-Hour Results" — "Complete pentest of your web app and APIs in 24 hours. Send the report to enterprise prospects the same week they ask for it."
    • "Continuous Testing" — "Run pentests with every major release. Stop relying on a single annual snapshot to demonstrate your security posture."
    • "No Expertise Needed" — "No security team required. Point SQUR at your application and get a comprehensive assessment with clear remediation guidance."
    • "Developer-Friendly Reports" — "Findings include evidence, severity ratings, and step-by-step remediation. Your dev team can act on results without a security translator."

14. Compliance section (section.vertical-compliance):

15. H2: "Security Testing Evidence for Your Audits"
16. Subtitle: "SQUR provides pentesting reports that support the security testing requirements within common compliance frameworks."

17. Cards:

    • "SOC 2" — "SOC 2 audits assess whether you perform regular security testing. SQUR's pentest reports provide dated, evidence-based documentation of your testing practices."
    • "ISO 27001" — "Annex A of ISO 27001 references technical vulnerability management. Regular pentesting demonstrates proactive security assessment to auditors."
    • "Vendor Questionnaires" — "Most enterprise security questionnaires ask 'When was your last pentest?' SQUR lets you answer 'this week' instead of 'last year.'"

18. Stats banner (section.vertical-stats):

19. 4 stats: "24h" / "Full pentest results", "87.5%" / "CTF benchmark score", "AI-Verified" / "Every finding validated", "Retest" / "Included at no extra cost"

20. FAQ section (section.vertical-faq):

21. H2: "Frequently Asked Questions"
22. 5-6 questions with answers, e.g.:
    • "Can I use SQUR's report for SOC 2 audits?" → "SQUR provides comprehensive pentest reports with evidence-based findings, severity ratings, and timestamps. Many auditors accept third-party pentest reports as evidence of security testing practices. We recommend confirming with your specific auditor."
    • "What does SQUR actually test?" → "SQUR performs autonomous penetration testing of web applications and APIs. Our AI agents conduct reconnaissance, identify attack surfaces, and attempt exploitation — similar to what a human pentester would do, but in 24 hours."
    • "Do I need a security team to use SQUR?" → "No. SQUR is designed for teams without dedicated security expertise. You provide the URL of your application, and SQUR handles the rest. Results include clear, developer-friendly remediation guidance."
    • "How often should I run pentests for compliance?" → "Most compliance frameworks expect regular security testing. With SQUR's speed and pricing, many customers run pentests monthly or with every major release, rather than the traditional once-per-year approach."
    • "What happens after SQUR finds vulnerabilities?" → "You receive a detailed report with each finding's evidence, severity, and remediation steps. After fixing issues, you can retest for free to verify the vulnerabilities are resolved."

23. Each Q in JSON-LD FAQ schema in the <head>

24. CTA section (section.vertical-cta):

25. H2: "Secure Your SaaS Platform Today"
26. P: "Get your first pentest report in 24 hours."

27. Two CTAs: "Start Pentest" → https://app.squr.ai, "Book a Demo" → /book-a-demo.html

28. Footer: #footer-placeholder div, then <script src="../scripts.js"></script>

FAQ toggle JS: Add a small inline script at the bottom (before </body>) to handle FAQ expand/collapse:

<script>
document.querySelectorAll('.faq-question').forEach(btn => {
    btn.addEventListener('click', () => {
        btn.closest('.faq-item').classList.toggle('active');
    });
});
</script>

Step 2: Verify the page loads

Open in browser or serve locally:

cd squr-website && python3 -m http.server 8000

Check http://localhost:8000/verticals/saas.html — verify header/footer load, all sections render, FAQ toggles work.

Step 3: Commit

git add squr-website/verticals/saas.html
git commit -m "Add B2B SaaS vertical landing page"

---

Task 4: Create Fintech Vertical Page (Rebuild)

Files: - Overwrite: squr-website/verticals/fintech.html

Context: Replace the existing 725-line page with the new template. Key content differences from SaaS: DORA Article 24 (cite specifically), BaFin context, API-heavy architectures, PCI DSS mentioned as context only.

Step 1: Create squr-website/verticals/fintech.html

Same template structure as SaaS page. Content specifics: - Hero: "Autonomous Pentesting for Fintech" / "Security testing that keeps pace with your release cycles. Meet regulatory expectations with evidence-based pentest reports — delivered in 24 hours." - Tagline: "DORA Article 24 · API Security · 24h Reports" - Challenges: "Regulatory Pressure" (DORA, BaFin oversight, annual testing mandates), "API-Heavy Architectures" (REST, GraphQL, payment endpoints), "Speed vs. Security" (daily deploys but quarterly security checks) - Solution: "DORA Article 24 Support" (pentesting evidence for DORA's annual TLPT requirements), "Deep API Testing" (REST and GraphQL endpoints tested thoroughly), "24-Hour Turnaround" (report in hand before the compliance deadline), "Retest After Fixes" (verify remediations are effective at no extra cost) - Compliance cards: "DORA Article 24" (specifically: "DORA requires annual threat-led penetration testing of critical ICT systems. SQUR provides the autonomous pentesting evidence to support this requirement."), "BaFin Oversight" ("Financial institutions under BaFin supervision face increasing scrutiny on IT security practices. Regular pentesting demonstrates proactive risk management."), "ISO 27001" (same general framing as SaaS page) - FAQ: Fintech-specific questions about DORA, payment security, API testing, BaFin requirements - CTA: "Secure Your Fintech Platform Today"

Step 2: Verify visually

Check http://localhost:8000/verticals/fintech.html

Step 3: Commit

git add squr-website/verticals/fintech.html
git commit -m "Rebuild fintech vertical with new consistent template"

---

Task 5: Create HealthTech Vertical Page (Rebuild)

Files: - Overwrite: squr-website/verticals/healthtech.html

Content specifics: - Hero: "Autonomous Pentesting for HealthTech" / "Protect patient data with continuous security validation. GDPR-supporting pentest evidence in 24 hours." - Tagline: "GDPR Art. 32 · Patient Data · API Security" - Challenges: "Patient Data Exposure" (healthcare breaches have severe consequences), "GDPR Compliance Pressure" (Art. 32 requires testing effectiveness of security measures), "API-First Health Platforms" (FHIR APIs, telehealth endpoints, EHR integrations) - Solution: Speed, API security, no expertise needed, evidence-based reports - Compliance cards: "GDPR Article 32" ("GDPR Article 32 requires 'a process for regularly testing, assessing and evaluating the effectiveness of technical and organisational measures.' SQUR's regular pentesting provides dated evidence of this testing."), "Patient Data Protection" ("Healthcare applications handle sensitive PII. Regular pentesting helps identify vulnerabilities before they become breaches."), general security best practices - FAQ: HealthTech-specific (GDPR, patient data, FHIR APIs, no-expertise-needed) - CTA: "Secure Your HealthTech Platform Today"

Step 1: Create full HTML file Step 2: Verify visually Step 3: Commit

git add squr-website/verticals/healthtech.html
git commit -m "Rebuild healthtech vertical with new consistent template"

---

Task 6: Create E-Commerce Vertical Page

Files: - Create: squr-website/verticals/ecommerce.html

Content specifics: - Hero: "Autonomous Pentesting for E-Commerce" / "Don't let security slow down your next launch. Validate your store's security before peak season — in 24 hours." - Tagline: "Payment Security · Customer Data · Pre-Launch Testing" - Challenges: "Payment Data at Risk" (checkout flows, payment integrations), "Customer Trust" (one breach destroys brand confidence), "Seasonal Pressure" (launches, sales events, no time for month-long pentests) - Solution: Pre-launch validation, payment flow testing, 24h results, retest after fixes - Compliance cards: "PCI DSS Context" ("PCI DSS requires regular security testing for systems handling payment data. SQUR's pentest reports provide evidence of your security testing practices for payment-related systems."), "GDPR" (customer data protection), "Customer Trust" ("Regular security testing demonstrates to customers that you take their data protection seriously.") - FAQ: E-commerce-specific - CTA: "Secure Your E-Commerce Platform Today"

Step 1: Create full HTML file Step 2: Verify visually Step 3: Commit

git add squr-website/verticals/ecommerce.html
git commit -m "Add e-commerce vertical landing page"

---

Task 7: Create Industrial/DeepTech Vertical Page (Rebuild)

Files: - Overwrite: squr-website/verticals/industrial.html

Content specifics: - Hero: "Autonomous Pentesting for Industrial & DeepTech" / "Secure the web interfaces protecting your intellectual property and operational technology." - Tagline: "IP Protection · NIS2 · Supply Chain Security" - Challenges: "Web Portal Exposure" (OT management interfaces, customer portals), "IP Theft Risk" (proprietary APIs and data endpoints), "Supply Chain Vulnerabilities" (partner integrations, data exchanges) - Solution: Web and API testing, IP protection validation, supply chain partner security, 24h turnaround - Compliance cards: "NIS2" ("NIS2 requires operators of essential services to conduct regular security assessments. SQUR provides autonomous pentesting evidence for your web-facing systems."), "ISO 27001" (general), "Supply Chain Due Diligence" ("Demonstrate to partners and customers that your web systems undergo regular security testing.") - FAQ: Industrial/DeepTech-specific (what SQUR tests, web vs OT systems, NIS2) - Important: Be clear SQUR tests web apps/APIs, NOT OT/SCADA systems directly - CTA: "Secure Your Digital Infrastructure Today"

Step 1: Create full HTML file Step 2: Verify visually Step 3: Commit

git add squr-website/verticals/industrial.html
git commit -m "Rebuild industrial/deeptech vertical with new consistent template"

---

Task 8: Create Legal Tech Vertical Page

Files: - Create: squr-website/verticals/legaltech.html

Content specifics: - Hero: "Autonomous Pentesting for Legal Tech" / "Security your clients expect from their legal technology partners." - Tagline: "Client Confidentiality · GDPR · Professional Trust" - Challenges: "Client Confidentiality at Stake" (legal data is extremely sensitive), "Professional Obligations" (bar associations and regulators expect security diligence), "Enterprise Client Requirements" (law firms and corporate legal teams demand vendor security evidence) - Solution: Confidential data protection testing, professional credibility evidence, no security team needed, developer-friendly remediation - Compliance cards: "GDPR" (client data handling), "Professional Due Diligence" ("Legal tech vendors are expected to demonstrate security best practices. Regular pentest reports provide the evidence your clients require."), "Enterprise Requirements" ("Corporate legal departments increasingly require vendors to show evidence of security testing as part of procurement processes.") - FAQ: Legal tech-specific - CTA: "Secure Your Legal Tech Platform Today"

Step 1: Create full HTML file Step 2: Verify visually Step 3: Commit

git add squr-website/verticals/legaltech.html
git commit -m "Add legal tech vertical landing page"

---

Task 9: Create Startups Vertical Page

Files: - Create: squr-website/verticals/startups.html

Content specifics: - Hero: "Autonomous Pentesting for Startups" / "Investor-grade security without a security team. Get your first pentest report before your next board meeting." - Tagline: "Due Diligence Ready · 80% Cost Reduction · No Expertise Needed" - Challenges: "Investor Due Diligence" (VCs and acquirers ask about security posture), "Resource Constraints" (no budget for expensive consultants, no security hire yet), "SOC 2 Pressure" (enterprise customers won't sign without it) - Solution: Affordable first pentest, same-week report for due diligence, no security expertise needed, retest as you grow - Compliance cards: "Investor Expectations" ("VCs increasingly assess security posture during due diligence. A current pentest report demonstrates maturity and risk awareness."), "SOC 2 Readiness" ("Starting security testing early makes your SOC 2 journey easier. SQUR gives you the pentesting component from day one."), "Enterprise Sales" ("Enterprise customers require vendor security evidence. SQUR gets you the pentest report that unblocks the deal.") - FAQ: Startup-specific (cost, speed, when to start pentesting, what investors look for) - CTA: "Get Your First Pentest Report Today"

Step 1: Create full HTML file Step 2: Verify visually Step 3: Commit

git add squr-website/verticals/startups.html
git commit -m "Add startups vertical landing page"

---

Task 10: Create Government/Public Sector Vertical Page

Files: - Create: squr-website/verticals/government.html

Content specifics: - Hero: "Autonomous Pentesting for Government & Public Sector" / "Meet public sector security standards with autonomous testing. EU-hosted, GDPR-compliant, from a German security company." - Tagline: "EU Data Sovereignty · BSI Standards · NIS2 Support" - Challenges: "Strict Security Standards" (BSI IT-Grundschutz, procurement requirements), "Data Sovereignty" (data must stay in EU, vendor must be trustworthy), "Resource Limitations" (public sector IT budgets are constrained, security talent is scarce) - Solution: EU-hosted platform, German company with EU data residency, no security expertise needed, affordable compared to traditional consultants - Compliance cards: "BSI IT-Grundschutz" ("BSI IT-Grundschutz recommends regular penetration testing as part of its security baseline. SQUR provides autonomous pentesting evidence for your web-facing systems."), "NIS2" ("NIS2 requires operators of essential services to conduct regular security assessments. SQUR supports this testing requirement for web applications and APIs."), "EU Data Sovereignty" ("SQUR is a German company with EU-hosted infrastructure. Your data stays in Europe.") - FAQ: Government-specific (data sovereignty, BSI, procurement, EU hosting) - CTA: "Secure Your Public Sector Systems Today"

Step 1: Create full HTML file Step 2: Verify visually Step 3: Commit

git add squr-website/verticals/government.html
git commit -m "Add government/public sector vertical landing page"

---

Task 11: Update Footer with All 8 Verticals

Files: - Modify: squr-website/includes/footer.html

Step 1: Update the Verticals column in footer

The remote footer already has a "Verticals" column with 3 links. Update it to include all 8:

<div class="links-column">
  <h4>Verticals</h4>
  <ul>
    <li><a href="/verticals/saas.html">B2B SaaS</a></li>
    <li><a href="/verticals/fintech.html">Fintech</a></li>
    <li><a href="/verticals/healthtech.html">HealthTech</a></li>
    <li><a href="/verticals/ecommerce.html">E-Commerce</a></li>
    <li><a href="/verticals/industrial.html">Industrial</a></li>
    <li><a href="/verticals/legaltech.html">Legal Tech</a></li>
    <li><a href="/verticals/startups.html">Startups</a></li>
    <li><a href="/verticals/government.html">Government</a></li>
  </ul>
</div>

Note: The footer grid may need to accommodate 5 link columns now. Check the existing grid-template-columns: repeat(4, 1fr) in footer CSS and update to repeat(5, 1fr) if the Verticals column was added as a 5th column. Review and adjust the responsive breakpoints too.

Step 2: Commit

git add squr-website/includes/footer.html
git commit -m "Update footer with all 8 vertical landing page links"

---

Task 12: Update Sitemap

Files: - Modify: squr-website/sitemap-main.xml

Step 1: Add all 8 vertical pages to sitemap

Add entries for each vertical page with priority 0.8 and monthly changefreq:

<url>
  <loc>https://squr.ai/verticals/saas.html</loc>
  <lastmod>2026-02-25</lastmod>
  <changefreq>monthly</changefreq>
  <priority>0.8</priority>
</url>
<url>
  <loc>https://squr.ai/verticals/fintech.html</loc>
  <lastmod>2026-02-25</lastmod>
  <changefreq>monthly</changefreq>
  <priority>0.8</priority>
</url>
<!-- ... etc for all 8 -->

Remove the old fintech-only entry (priority 0.9) and replace with the new set.

Step 2: Commit

git add squr-website/sitemap-main.xml
git commit -m "Add all vertical landing pages to sitemap"

---

Task 13: Visual Verification and Polish

Step 1: Serve the site and check all 8 pages

cd squr-website && python3 -m http.server 8000

Verify each page at: - http://localhost:8000/verticals/saas.html - http://localhost:8000/verticals/fintech.html - http://localhost:8000/verticals/healthtech.html - http://localhost:8000/verticals/ecommerce.html - http://localhost:8000/verticals/industrial.html - http://localhost:8000/verticals/legaltech.html - http://localhost:8000/verticals/startups.html - http://localhost:8000/verticals/government.html

Check for each page: - [ ] Header loads with navigation - [ ] Hero section renders with correct H1 and subtitle - [ ] Challenge cards display in 3-column grid - [ ] Solution items display in 2-column grid - [ ] Compliance section renders with left-border cards - [ ] Stats banner shows 4 stats in a row - [ ] FAQ items expand/collapse on click - [ ] Bottom CTA section renders with blue gradient - [ ] Footer loads with all 8 vertical links - [ ] Mobile responsive (check at 375px width) - [ ] No console errors

Step 2: Fix any visual issues found

Address CSS inconsistencies, spacing problems, or broken elements.

Step 3: Final commit

git add -A squr-website/
git commit -m "Polish vertical landing pages after visual review"

---

Summary

Task	Description	New/Modified Files
1	Merge remote changes	git merge
2	Create shared CSS	styles-verticals.css
3	B2B SaaS page	verticals/saas.html
4	Fintech page (rebuild)	verticals/fintech.html
5	HealthTech page (rebuild)	verticals/healthtech.html
6	E-Commerce page	verticals/ecommerce.html
7	Industrial page (rebuild)	verticals/industrial.html
8	Legal Tech page	verticals/legaltech.html
9	Startups page	verticals/startups.html
10	Government page	verticals/government.html
11	Update footer	includes/footer.html
12	Update sitemap	sitemap-main.xml
13	Visual verification	any fixes