From score to action: how the five DAC layers work

A maturity score by itself is a number. A number without context is a ranking. A ranking without action is just status anxiety. The five DAC layers exist because each step in the progression answers a question the previous one raises: you scored 67, now what?

That question is why DAC-score is the starting point, not the deliverable. The score opens the diagnostic. What comes next is the work that makes the number useful.

Why layers, not features

Most diagnostics stop at the score. Some add recommendations. Very few close the loop from measurement all the way through action and back to re-measurement. The five DAC layers are a deliberate progression, not a feature list.

Each layer is only possible because the previous one exists. The coaching actions in DAC-coach are specific because DAC-intelligence has already isolated the structural tensions. The intelligence is useful because DAC-score provides the evidence foundation. The score is trustworthy because DAC-framework gives it a rigorous, consistent rubric. The full diagnostic experience in DAC-diagnostics is only coherent because all four preceding layers are in place.

Remove any layer and the one above it degrades. Generic recommendations with no score foundation are just advice. A score with no framework is an opinion. This is why the architecture is sequential and why each layer has a distinct definition.

1. DAC-framework: Three scoring frameworks. 54 dimensions. The shared language that makes scores mean something.
2. DAC-score: Your position across 54 dimensions, scored to stage. Evidence-based, not self-report. (Free)
3. DAC-intelligence: Tensions, gaps, and the Translation Gap. The structural problems you can't see from the score alone.
4. DAC-coach: Priority-ordered prescriptions. 90-day plans grounded in your actual score data. Synced to Linear. (Leader)
5. DAC-diagnostics: The complete experience. Board-ready narrative. Quarterly cadence. Portfolio view. The full loop. (Org+)

Layer 01: DAC-framework

The framework layer is not something you interact with directly in the UI. It's the invisible foundation. Without it, scores are arbitrary. With it, a "72" on Delivery Velocity means something specific: it's evidence-based against a rubric that has been consistent across every company scored, every cycle, every time.

The three frameworks (F1, F2, F3) create the shared language that makes cross-company and cross-cycle comparison possible. A score without a framework is a diagnostic without grounding. A score with a rigorous framework is a benchmark.

• F1 (People): AI-Native Team Maturity. 27 dimensions across Strategy, Design, Development, Operations, GTM, and Intelligence.
• F2 (Process): AI-Native Product Lifecycle. 34 tasks across Specify, Build Context, Orchestrate, Validate, Ship Economics, and Learn.
• F3 (Product): AI-Native Product Intelligence. 27 dimensions across Architecture, Intelligence, Data, Economics, Trust, and Moat.

F1 and F3 share 54 combined unique dimensions that form the DAC-diagnostics composite. F2 operates on the process layer separately, measuring whether the operational practices and lifecycle management are mature enough to support consistent AI-native delivery.

Layer 02: DAC-score

The score is evidence-based, not self-report. It's extracted from public signals (product surfaces, changelog history, documentation, job postings, technical artifacts) and evaluated against the rubric by a Claude-powered scoring engine. Same schema, same rubric, every time.

This matters for two reasons. First, your score at cycle 1 and cycle 4 are directly comparable. Second, your score is directly comparable to every other company scored in the same framework. Self-report diagnostics measure confidence. Evidence-based diagnostics measure capability. These are not the same thing.

The number is the starting point, not the conclusion. Available at the free tier, the score gives you position. The layers above give you direction.

The spread between your highest and lowest dimensions is often more informative than the composite. A score of 72 with a range of 31 to 82 is a fundamentally different situation than a score of 72 with a range of 65 to 79. The first has critical gaps. The second has an investment pattern problem.

Layer 03: DAC-intelligence

This is where the score becomes a diagnosis. DAC-intelligence has three outputs.

Dimension tensions are pairs of dimensions where high performance in one and low performance in another reveals a structural misalignment. These are not random. A team that scores well on Delivery Velocity but poorly on Customer Signal Synthesis is shipping fast in the wrong direction, a pattern that surfaces repeatedly in companies with strong engineering culture and weak feedback loops.

Function gaps are whole functions (Strategy, Design, Development, Operations, GTM, Intelligence) lagging behind the rest, indicating sustained investment imbalance. A function that consistently underperforms suggests organizational structure or resourcing constraints, not just execution gaps.

The Translation Gap is the scored distance between F1 (team maturity) and F3 (product AI-nativeness). A company that scores well on Development capability (F1) but poorly on Core Integration Depth (F3) has a translation problem: the team has the capability, but it's not showing up in the product. This is one of the highest-leverage findings in the diagnostic because it reveals a capability constraint the team often can't see internally.

For example, a team with Delivery Velocity at 82 and Customer Signal Synthesis at 31 has a 51-point spread. Shipping velocity is high, but feedback loop infrastructure is weak. The team is likely building fast without the signal infrastructure to evaluate whether what's shipping is working. This spread is a structural risk, not a prioritization lag.

A Translation Gap of 23 points (F1: 72, F3: 49) means team maturity leads product AI-nativeness. The team is capable of more than the product currently reflects. This is typically a roadmap or resourcing constraint, but if unaddressed, the gap tends to widen as the team's capability compounds faster than the product catches up.

Layer 04: DAC-coach

The coaching layer turns intelligence into action. Each DAC-coach prescription is ordered by expected impact-per-effort for your specific score profile. Not generic advice. The prescriptions are generated from the evidence gaps in your lowest-scoring dimensions, with enough specificity to translate directly into planning decisions, hiring criteria, or architectural choices.

A team with weak Customer Signal Synthesis (F1) and a high Translation Gap gets different coaching than a team with strong Intelligence functions but weak GTM. The coaching is contextual because the score data is contextual. That specificity is what separates a coaching plan from a best-practices checklist.

Each coaching action syncs to Linear as an issue. The first comment on every issue is a DAC coaching tip, which means every team member who opens the issue in Linear gets the diagnostic context alongside the task. The diagnostic loop and the delivery loop stay connected.

Layer 05: DAC-diagnostics

The diagnostics layer is what the complete experience looks like assembled. It includes the full score report across all three frameworks, the cross-framework intelligence analysis, 90-day coaching plans from DAC-coach, trend tracking across scoring cycles, and the portfolio view for teams managing multiple products.

This is the layer that makes Dacard useful for board presentations, QPR preparation, and investment decisions, not just team retrospectives. The quarterly re-scoring cadence (monthly for high-velocity teams) is built in. The narrative layer is structured for executives who need context without the full diagnostic depth.

DAC-diagnostics is available at Org tier and above. It's the full loop: score, understand, act, track, compound.

Pricing tiers and included layers:

• Free ($0): DAC-framework + DAC-score. Full 54-dimension score report (once), stage classification, signal bars by function.
• Individual ($49/mo): Adds DAC-intelligence. Unlimited scoring cycles, dimension tension analysis, Translation Gap calculation.
• Lead ($149/mo): Adds DAC-coach. Priority-ordered coaching actions, 90-day improvement plans.
• Leader ($299/mo): Full DAC-intelligence + DAC-coach. Trend tracking across cycles, Linear sync for coaching actions.
• Org ($599/mo): Adds DAC-diagnostics. Multi-seat, board-ready narrative output, portfolio view.
• Enterprise ($2,500+/mo): Everything in Org plus SSO and advanced access controls, custom playbooks and rubrics, dedicated CSM.

The loop

The five layers only create compounding value when they cycle. Score. Understand. Act. Re-score. The teams that improve fastest aren't the ones with the highest first score. They're the ones with the tightest feedback loop between action and measurement.

The diagnostic cadence matters: quarterly for most teams, monthly for high-velocity organizations running tight 90-day coaching cycles. Each re-score validates whether the actions from the previous cycle produced measurable evidence changes. If the score improves, the evidence changed. If the score doesn't move, the action didn't produce observable output, which is itself a signal worth examining.

The five layers are the architecture. The loop is the mechanism. The compound effect, scores that improve faster over time as teams develop the practices to act on intelligence systematically, is the outcome.

> "A score without a plan is a judgment. A plan without a score is a guess. The five DAC layers exist to close the gap between measurement and action, and then measure whether the action worked."