Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.dacard.ai/llms.txt

Use this file to discover all available pages before exploring further.

We score every product across 27 dimensions in 6 functions. Each dimension lands 1-5. The composite (27-135) places you on a 5-stage maturity ladder. Connect integrations to ground the score in operational data.

How scoring works

We score products by reading observable signals across 27 dimensions in 6 functions. Each dimension scores 1-5. Your composite (27-135) places you on a 5-stage ladder. Five-step scoring process: Crawl, Analyze, Score, Classify, Recommend

The five steps

1

Crawl

We visit the URL and pull up to 6 pages, extracting signal from your product’s public surface, docs, pricing, and UX patterns.
2

Analyze

We score each of the 27 dimensions against the rubric for each stage. Signal includes architecture tells, business model, UX patterns, and operational indicators.
3

Score

Every dimension lands a score from 1 (Foundation) to 5 (Compounding). The 27 scores sum to a composite total of 27-135.
4

Classify

The composite places you on the maturity ladder (Foundation through Compounding).
5

Recommend

We surface dimension-level reads, your strengths, your gaps, and the next move we’d take. The receipts live at /r/{id}.

Five maturity stages

Maturity ladder from Foundation (27-48) through Compounding (114-135)
StageScoreRead
Foundation27-48Basics missing or absent. Capability is not yet part of the product’s core.
Building49-70Emerging practice, applied unevenly. Features exist; advantage doesn’t.
Scaling71-91Systematic, measured, repeatable. Capability is a real lever.
Leading92-113Deeply integrated. Pull it out and the product breaks.
Compounding114-135Capability compounds across product, data, ops, and business model. The flywheel runs itself.

27 dimensions across 6 functions

Market intelligence - how well the team collects and synthesizes market signalDecision quality - evidence behind product and strategic decisionsRoadmap discipline - how well the roadmap reflects strategic priorities and tracks outcomesCompetitive positioning - clarity and defensibility of market position
Research and discovery - depth and consistency of user researchPrototyping speed - how fast the team goes from idea to testable artifactExperience design - quality of interaction patterns and UX craftDesign-dev handoff - efficiency and fidelity of the design-to-build handoff
Architecture and systems - depth of technical integrationSpec and context quality - quality of PRDs, tickets, and context handed to buildersBuild vs buy - decision rigor on model and infrastructure choicesDelivery velocity - speed and consistency of shipping improvements
Customer signal synthesis - quality of customer feedback collection and synthesisProduct analytics - depth and use of product usage dataData flywheel - whether data creates a defensible compounding advantageFeedback loop quality - whether usage data flows back to improve the productKnowledge management - how well institutional knowledge is captured, organized, and surfaced
Positioning and messaging - clarity and resonance of market messagingLaunch execution - consistency and quality of launchesAdoption and expansion - how the product drives usage growth and expansionPricing and packaging - whether pricing reflects value and supports growth
Quality and experimentation - rigor of testing, evaluation, and quality processesTeam orchestration - how the team coordinates work across people and systemsProcess iteration - how fast the team improves its own ways of workingCost and token economics - how the team manages inference and infrastructure costsSecurity and compliance - how the team manages security and compliance riskReliability and resilience - how features handle failure and maintain availability

Signal bars

We surface scores as signal bars in a traffic-light system. They appear throughout the dashboard, reports, and portfolio views.
Dimension scoreColorRead
1 (Foundation)RedGap. This dimension is capping your composite.
2 (Building)AmberDeveloping. Targeted move pays off fast.
3 (Scaling)GreenStrong. Maintain and extend.
4-5 (Leading / Compounding)GreenExceptional. Defensible capability.

Signal-score blending

Surface assessment and integration signals blend into composite dimension scores When you connect integrations (GitHub, Linear, PostHog, others), your scores get signal-grounded. We blend two sources:
  1. Surface assessment - our read of your public surface
  2. Adapter signals - operational ground truth from connected tools (deploy frequency, PR cycle time, sprint velocity, others)

How we blend

Each integration produces metrics mapped to specific dimensions. We convert those metrics into 1-5 signal scores using calibrated thresholds, then blend with the surface read.
FactorEffect
Signal countMore signals, higher blending weight (5 minimum to activate, up to 0.4 weight at 20+)
ConfidenceHigh-confidence signals (from well-established adapters) carry more weight
Weight capAdapter signal never exceeds 60% weight; surface read stays the primary input
The result: connected teams get measurably tighter scores because dimensions reflect both observable surface quality and live operational data.
Wire up GitHub and Linear first. They cover the most dimensions and produce the highest-confidence adapter signal.

Scoring practice

Start with your own URL to calibrate. Then score 2-3 competitors to see where you sit. Each URL score costs 10 credits.
Click Add context before you score to drop a brief read on what your product does and who it serves. We use that to ground products with thin public surface.
Scores are point-in-time. Re-score after a major ship or quarterly to trace trajectory. We preserve score history automatically.
URL-only scoring leans on the public surface. Wiring GitHub, Linear, and PostHog adds operational ground truth that materially improves both accuracy and confidence.
Every score has a shareable URL at /r/{id}. Send it to leadership, investors, or your team without making them sign in.

Anonymous scoring

Anyone can score at app.dacard.ai/try without an account. Anonymous scores are rate-limited (1 per hour per IP) and don’t unlock the full report.
When you sign up after an anonymous score, we can link the anonymous score to your new account. Your history travels with you.

Read your report

Walk through the report section by section.

Team Operations deep dive

Full 27-dimension definitions and scoring rubric.

Connect integrations

Pull live operational signal into scoring.

Score your first product

Step-by-step walkthrough for first-time users.