← Dashboard · Pricing · Trust Center
Website & product scorecard
Internal-style assessment of capchacloud.com as shipped — positioning, trust artifacts, technical readiness, and conversion clarity. Scores are qualitative (not automated Lighthouse). Last reviewed against the live marketing site and operator dashboard.
Not financial advice. Revenue tables are illustrative arithmetic on published list prices — not forecasts, run-rate commitments, or guarantees. Real outcomes depend on sales execution, churn, support load, infra overages, disputes, and competition.
Executive summary
Strengths
- Coherent Cloudflare-native story — Edge delivery plus Turnstile fits buyers who want low-latency auth and evidence-oriented consent capture.
- Trust surface area — Trust Center, compliance hub, and policy depth punch above typical early-stage B2B SaaS.
- Transparent pricing posture — No-Gate tiers ($29 / $99 / $499) reduce “call us” friction vs opaque CIAM quotes.
- Product narrative matches what ships — embed, capture path, OAuth, webhooks: marketing and the setup checklist should match what is deployed when secrets exist.
Gaps / risks
- Category crowding — Clerk, Auth0, Cognito, Stytch, and DIY stacks set baseline expectations; differentiation must stay crisp (consent evidence + edge + pricing ethics).
- SEO for the SPA shell — Primary dashboard is app-like; marketing lift depends on static pages (pricing, policies, this scorecard) and outbound motion.
- Operator burden — OAuth, Turnstile, and Stripe must be configured; until then, live pages show honest “not configured” states — good for integrity, a conversion tax until green.
Dimensional scores (0–10 each)
| Dimension | Score | Notes |
|---|
| Positioning clarity |
7 |
Auth + consent evidence + fair pricing is clear; tighten one-line differentiation vs “CIAM suite” in hero tests. |
| Trust & compliance UX |
8 |
Deep policy library and Trust Center — strong for procurement-minded buyers (not legal advice). |
| Technical credibility |
8 |
Turnstile + OAuth + capture path is credible; public checklist surfaces misconfiguration honestly. |
| Conversion path |
7 |
Pricing & sign-in visible; dependency on OAuth secrets means first-run needs operator focus. |
| SEO / discoverability (static pages) |
6 |
Good static footprint; competitive keywords (auth, CIAM) are expensive — content & backlinks still needed. |
| Differentiation vs incumbents |
6 |
Evidence posture + edge delivery + transparent tiers helps; sustained differentiation requires workflow lock-in and proof points. |
Rough weighted read: ~7.0 / 10 — solid foundation; biggest lever is distribution + case studies, not more features.
Illustrative revenue math (published list prices)
Pricing reference (from Pricing): $9 (Starter), $29 (Pro), $99 (Business) per month. Enterprise is custom (from $499/mo on the pricing page). Below: simple multiples only — not churn-adjusted, not net of Stripe fees, tax, or support time.
| Scenario (illustrative) | Math | MRR | ARR (×12) |
|---|
| 100 × Starter | 100 × $9 | $900 | $10,800 |
| 50 × Pro | 50 × $29 | $1,450 | $17,400 |
| 20 × Business | 20 × $99 | $1,980 | $23,760 |
| Mixed (60 Starter / 25 Pro / 5 Business) | 60×9 + 25×29 + 5×99 | $1,760 | $21,120 |
To reach $1M ARR at blended ~$80–120k per enterprise-ish customer equivalent, you need hundreds of paying workspaces at Starter/Pro or a thinner count at Business and custom Enterprise — both require repeatable acquisition and low churn. Many SaaS products never reach $1M ARR; many stall near five figures MRR. Treat tables as possibilities, not targets.
Reality check on “how much can I earn?”
- Value is real where buyers must prove consent & integrity — regulated-adjacent SaaS, agencies with liability exposure, and teams allergic to opaque CIAM pricing are plausible ICPs.
- Earnings follow distribution — product completeness alone does not create ARR; outbound, partnerships, integrations marketplace presence, and founder-led sales cycles dominate early revenue.
- Margins vs responsibilities — Low infra variable cost at the edge helps; human support, incident response, and contractual commitments compress operating margin as you scale logos.
- Honest baseline — Treat early revenue as experimental until you have repeatable onboarding (OAuth, Turnstile, Stripe green), reference customers, and a support rhythm.
Suggested next moves (90 days)
- Publish two concise case-style narratives (even if anonymized): before/after evidence posture.
- Reduce time-to-green checklist friction — docs links from dashboard errors are already aligned; add video walkthrough optional.
- Pick one wedge keyword cluster around consent evidence and edge delivery, then ship two credible technical articles.
- Instrument funnel: visits → pricing → sign-in attempts → paid conversion (Stripe events).