← 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 aligns with the guided dashboard + Worker stack described in-repo.
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 — Workers, Turnstile, R2/D1 posture fits a buyer who wants edge delivery 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 implementation direction — embed widget, capture API, Better Auth, webhooks: the demo and checklist can reflect reality 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 + 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 + Better Auth + 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 + Cloudflare edge + transparent tiers helps; sustained moat 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.html): $29 (Bootstrapper), $99 (Agency), $499 (Scale-Out) per month. Below: simple multiples only — not churn-adjusted, not net of Stripe fees, tax, or support time.
| Scenario (illustrative) | Math | MRR | ARR (×12) |
|---|
| 100 × Tier 1 | 100 × $29 | $2,900 | $34,800 |
| 50 × Tier 2 | 50 × $99 | $4,950 | $59,400 |
| 20 × Tier 3 | 20 × $499 | $9,980 | $119,760 |
| Mixed (60 / 25 / 5) | 60×29 + 25×99 + 5×499 | $7,415 | $88,980 |
To reach $1M ARR at blended ~$80–120k per enterprise-ish customer equivalent, you need hundreds of paying workspaces at low tiers or a thinner count at Tier 3 — 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 on Workers 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 (e.g., “consent evidence vault Cloudflare”) and ship two technical articles.
- Instrument funnel: visits → pricing → sign-in attempts → paid conversion (Stripe events).