Skip to content

Loupe Factory Pricing Documentation Implementation Plan

For agentic workers: REQUIRED SUB-SKILL: Use superpowers:subagent-driven-development (recommended) or superpowers:executing-plans to implement this plan task-by-task. Steps use checkbox (- [ ]) syntax for tracking.

Goal: Synchronize all relevant pricing documentation with the July 17, 2026 public pricing page and add a clear, theme-safe plan comparison.

Architecture: Keep the public pricing page as the commercial source of truth. Put the complete decision guide in pricing-plans.md, keep supporting pages concise, and protect exact commercial facts with a focused content regression test. Add only scoped CSS classes for the pricing strip so the rest of the site remains unchanged.

Tech Stack: MkDocs Material, Markdown with md_in_html, CSS custom properties, Python pytest

Global Constraints

  • Never use em dashes.
  • Do not add radial-gradient background styling to UI components.
  • Use small border-radius values.
  • Support both the default and slate MkDocs color schemes.
  • Do not run browser server tests.
  • Do not run the full test suite.
  • Treat https://www.loupefactory.com/pricing/ as the commercial source of truth.
  • Use direct international English and show self-serve prices in USD.

Task 1: Add Pricing Content Regressions

Files: - Create: tests/test_pricing_docs.py - Test: tests/test_pricing_docs.py

Interfaces: - Consumes: Customer-facing Markdown in docs/ and pricing styles in docs/stylesheets/extra.css - Produces: Focused assertions for exact prices, plan capacities, supporting copy, and theme-safe CSS

  • [x] Step 1: Write focused failing tests

Create tests that assert $990 USD per year, $1,990 USD per year, 25 users included, the four exact monthly AI credit allowances, August 31, 2026, $10 USD per user per month, and the absence of $1,010, $2,028, and Unlimited AI credits from the pricing guide. Add assertions for login-seat language in Users & Access, current onboarding wording in the FAQ, Enterprise availability in Shopify, and the pricing strip's light, dark, responsive, focus, and reduced-motion CSS.

  • [x] Step 2: Run the focused test and verify red

Run: ../.venv/bin/pytest tests/test_pricing_docs.py -q

Expected: FAIL because the current documentation contains stale prices and the pricing strip does not exist.

Task 2: Rewrite the Canonical Pricing Guide and Add Scoped Styling

Files: - Modify: docs/account-billing/pricing-plans.md - Modify: docs/stylesheets/extra.css - Test: tests/test_pricing_docs.py

Interfaces: - Consumes: Exact live pricing facts protected by Task 1 - Produces: A responsive .lf-plan-strip comparison and complete customer decision guide

  • [x] Step 1: Replace stale pricing and packaging copy

Write the launch notice, four-plan overview, plan-selection guidance, current capability tables, and billing notes described in the approved design. Use $99 USD per month, $990 USD per year, $199 USD per month, $1,990 USD per year, 25 users included, and exact credit allowances of 500, 3,000, 9,000, and 25,000 per month.

  • [x] Step 2: Add scoped comparison styles

Add light, dark, and fallback variables for the strip. Implement a four-column grid with one shared border, column dividers, a Business highlight, link hover and focus states, a stacked mobile layout below 800px, and a prefers-reduced-motion: reduce rule. Do not use radial gradients.

  • [x] Step 3: Run the focused test

Run: ../.venv/bin/pytest tests/test_pricing_docs.py -q

Expected: Supporting-page assertions may still fail, while canonical pricing and CSS assertions pass.

Task 3: Synchronize Supporting Pages

Files: - Modify: docs/account-billing/index.md - Modify: docs/account-billing/ai-credits-billing.md - Modify: docs/faq.md - Modify: docs/admin-settings/users-access.md - Modify: docs/admin-settings/organization-settings.md - Modify: docs/integrations/shopify.md - Test: tests/test_pricing_docs.py

Interfaces: - Consumes: Canonical plan facts from the updated pricing guide - Produces: Concise, consistent plan references at each point of customer need

  • [x] Step 1: Add exact AI allowances and subscription terms

Add the four monthly credit allowances to AI Credits & Billing and link back to the canonical pricing guide for prices and feature comparisons. State that annual billing is paid upfront and that Enterprise contract terms control when they differ.

  • [x] Step 2: Correct decision and onboarding copy

Update the FAQ and account overview with current plan-selection language, Enterprise migration support, guided onboarding across plans, and no stale live-training prices.

  • [x] Step 3: Correct seats, locations, and Shopify availability

Explain that only login users consume seats, list 1, 10, 25, and unlimited included seats, document $10 USD add-on seats for Professional and Business, list the 1, 3, unlimited, and unlimited location limits, and include Enterprise where Shopify availability is stated.

  • [x] Step 4: Run the focused test and verify green

Run: ../.venv/bin/pytest tests/test_pricing_docs.py -q

Expected: all tests in tests/test_pricing_docs.py pass.

Task 4: Validate the Documentation Build and Diff

Files: - Verify: all modified files

Interfaces: - Consumes: Completed customer-facing documentation and scoped CSS - Produces: Build evidence and a reviewed final diff

  • [x] Step 1: Run the strict docs build

Run: mkdocs build --strict

Expected: exit code 0 with no documentation errors.

  • [x] Step 2: Scan for stale pricing and forbidden punctuation

Run: rg -n '1,010|2,028|Unlimited AI credits|unlimited AI capacity' docs/account-billing docs/faq.md docs/admin-settings/users-access.md docs/admin-settings/organization-settings.md docs/integrations/shopify.md

Run: rg -n '\x{2014}' docs/account-billing docs/faq.md docs/admin-settings/users-access.md docs/admin-settings/organization-settings.md docs/integrations/shopify.md tests/test_pricing_docs.py

Expected: no matches.

  • [x] Step 3: Review the final diff

Run: git diff --check and git diff --stat

Expected: no whitespace errors and changes limited to the approved pricing documentation, scoped styling, tests, design record, and implementation plan.