01 Market sizing
Three numbers anchor the market shape and stay locked across the memo, this document, and the Series A pitch. SAM is $1.23B. TAM is $3.5B+. Near-term SOM is $30-50M ARR by 2028. The conservative posture is intentional. The product is a diagnostic with an outcome-calibrated pattern library underneath, not a horizontal productivity tool. The market it sells into is specific, and the bottom-up math reflects that specificity.
Bottom-up SAM math
The serviceable addressable market is post-Series A B2B SaaS in the United States and the European Union. Roughly 12,000 to 15,000 companies fit that filter. Three additional cuts narrow the set to the buying unit Dacard sells to. First, headcount band: 50 to 200 employees, the window where cross-functional product teams have formed but a Head of Product Operations is not yet a justified hire. Second, software-led category: the product is the company, and the product organization is the operating leverage. Third, modern stack: Linear, GitHub, and at least one of Slack, Jira, PostHog, Figma already in production use. Both mid-market and enterprise have legacy stacks; the Linear filter pre-qualifies the buyer for the activation event Dacard depends on.
Modeling penetration at a Pro / Business blended ACV (weighted toward $299 Pro at the early-cohort stage, climbing toward $1,200 Business as products multiply within an account) and applying a conservative 30 to 40 percent eventual penetration of the qualified SAM produces $1.23B. The number is not aspirational. It is the floor on a category that already buys assessments (compliance via Vanta, engineering via DX, Jellyfish, LinearB) but has no instrument for the layer above engineering.
TAM expansion logic
The total addressable market expands once the diagnostic surface ships into adjacent buyer-job counts. Three expansions sit in the model. First, all software companies with cross-functional product teams (not just B2B SaaS), which adds consumer software, developer tools, and embedded-software product orgs. Second, non-software companies that have stood up cross-functional product teams to ship AI-native customer experiences (financial services, healthcare, logistics, retail). Third, venture-capital portfolios that need a single instrument across 20-50 portfolio companies; this is the platform-contract motion, not the seat motion. Stacked, these expansions push TAM north of $3.5B with a credible path to $5B by 2030.
Near-term SOM
The 2028 SOM lands at $30-50M ARR. The math is bottom-up off the design-partner cohort plus the Pro-tier conversion curve. With 100 paying customers by Q4 2026 (the seed-extension milestone) and 300 by Q2-Q3 2027 (the Series A milestone), the trajectory implies 1,500 to 2,500 paying logos by end of 2028 at a $200 to $220 ARR-per-logo blended figure. The Business-tier expansion is the upside lever. Three Business-tier accounts contribute the same ARR as fifty Pro accounts, and the design-partner cohort is shaped to seed those expansions.
The macro reference
Menlo Ventures' 2025 State of Generative AI in the Enterprise report measured $4B in enterprise AI coding spend, growing 4.1x year over year. That number is the wave. It is measured at the developer-productivity layer (Cursor, Vercel, Replit, the AI-native dev stack). Dacard sells the layer above. The same buyers paying for Cursor seats are getting questions from their boards on whether the developer-productivity spend is producing product-organizational outcomes. Dacard answers that question. The sizing argument is therefore not "Dacard is a slice of the AI coding spend." It is "Dacard is the instrument the AI coding spend is being measured by, one tier up the stack."
02 Comparable companies
The comparable set is deliberately not a list of dashboards. It is a list of category-shape comparables. Vanta is the dominant analog. The developer-experience precedent (Atlassian + DX) sets the floor on what the adjacent category is worth. Jellyfish and LinearB anchor the engineering-effectiveness ARR ladder, which sits one tier below Dacard. The AI-native dev wave (Cursor, Vercel, Replit, Figma, Supabase) is the macro reference for what valuation looks like when a category catches the agentic-era updraft.
| Company | Metric | Why it matters |
|---|---|---|
| Vanta | $4.15B valuation | The assessment-as-a-service comparable. Continuous monitoring of an organizational property, packaged as software, sold to a buyer with no other path to the answer. Dacard is the same shape, applied to AI maturity. |
| Atlassian + DX | ~$1B acquisition (Sept 2025) | Developer-experience category precedent. Adjacent to Dacard, narrower (engineering only). Sets the floor on what cross-function maturity is worth. |
| Jellyfish | $31.9M ARR | Engineering effectiveness. Covers one of six functions in the Dacard frame. Useful as an ARR ladder comparable, not a competitive comparable. |
| LinearB | ~$16M ARR | Dev workflow analytics. Single substrate (engineering). Validates that buyers will pay for the read. |
| Cursor | $29.3B | The AI-native dev wave. Macro reference for the agentic-era updraft. |
| Vercel | $9.3B | Same wave, deployment substrate. |
| Replit | $9B | Same wave, agent-native dev environment. |
| Figma | $15.3B | Cross-function design substrate. Adjacent buyer to Dacard's. |
| Supabase | $5B | Open-source data substrate. Reference for the agent-native distribution motion. |
The pattern across the comparable set is consistent: categories that combine continuous data capture with named insight surfaces, sold to a buyer with board-level accountability, command outsized multiples. Dacard sits at that intersection.
03 Beachhead ICP
The beachhead is sharp on purpose. VP Product, Head of Product, or CPO at post-Series A B2B SaaS, 50-200 employees, Linear in production use, three or more cross-functional squads. The primary trigger is a new VP Product hire inside the first 90 days. Secondary triggers are the pre-board cycle, the post-fundraise hiring sprint, and the post-pivot reset. Each trigger produces the same buyer state: a senior leader with a board-level accountability, no instrument for the answer, and a 90-day window before they are no longer "new."
The ICP is operationalized as a weighted scorecard. A prospect scoring above a threshold qualifies for design-partner outreach; below the threshold the prospect goes to the PLG self-serve funnel and is allowed to disqualify itself. The scorecard is not a marketing artifact. It is the routing rule.
ICP scorecard
Pre-qualifies the activation event. Linear is the primary signal substrate; without it, sources_connected lags and Day 1 read degrades.
The window where cross-functional teams exist but a Head of Product Operations is not yet a justified hire. Below 50, no cross-function moat. Above 200, enterprise procurement.
Has a board, has product-organizational accountability, has venture pressure on revenue per employee. Pre-Series A is too early; the role does not yet have the diagnostic mandate.
The seat that owns cross-function product outcomes. The buyer-job is "show the board the team is working." The diagnostic answers it.
Below three, the surface area is too small for the framework to find tension. Three or more is where the Translation Gap and Fragility Signal patterns start firing.
The 30-60-90 onboarding ritual was designed for this window. Probability of activation is highest here. Outside the window, the ritual still works but the urgency drops.
The board pack needs an evidence read. Dacard becomes the source. The Day 30 check-in artifact is shaped to drop into a board update directly.
Hiring a VP Product or three new PMs forces the question of whether the operating model scales. Dacard answers it before the bad hire is made.
A pivot resets the operating model. The new model needs a baseline. Dacard provides the baseline plus the first 90 days of coaching cadence.
Multi-substrate fusion is the moat. A Linear-only customer activates but does not light up the full pattern library. The richer the stack, the deeper the read.
A prospect hitting all five high-weight criteria plus two or more medium-weight criteria is a design-partner candidate. A prospect hitting the high-weights only is a Pro-tier self-serve candidate. The scorecard is the funnel.
04 Anti-ICP
Anti-ICP is as load-bearing as ICP. Each category below is excluded for a specific reason that ties back to the moat or the activation curve. The point is not to be polite; the point is to keep the funnel clean so the design-partner cohort produces calibration data that compounds. A noisy funnel produces noisy calibration.
05 Buyer journey under the 30-60-90 onboarding ritual
The onboarding ritual is not a marketing asset. It is the product motion. Day 0 to Day 90 is the Free tier, and the ritual drives every state transition: signup to activation, activation to Pro, Pro to Business, Business to Enterprise. The ritual also produces shareable artifacts (the Day 1 read, the Week 1 deliverables, the Day 30 check-in, the Day 60 pushback, the Day 90 graduation) that travel on LinkedIn and seed the next signups. The ritual is the funnel and the loop simultaneously.
sources_connected >= 2 within 7 days of signup. The product nudges the user toward the second connection (GitHub, Slack, Jira, PostHog, Figma, Attio, depending on context). Once two sources are live, Week 1 deliverables generate: the first cross-function pattern read (Translation Gap, Fragility Signal, or Compound Ready), the ranked-actions list, and the agent-context push. Activation rate is the North Star.06 Distribution motions, ranked
Six distribution motions, ranked by leverage. The top two are the structural bets: agent-skill distribution and MCP. Both are live today. The bottom four are the supporting scaffold: REST API, founder-led LinkedIn, content and SEO, and VC portfolio partnerships. Each is described with current state, mechanism, and a target metric so the motion can be evaluated honestly at the next round.
Agent-skill distribution
The Battery thesis ("Agent Skills Are the New SDK," April 2026) is the structural bet. Neon hit 80 percent agent-originated provisioning inside 24 months and was acquired by Databricks for $1B. Dacard's agent skill teaches Claude Code, Cursor, and other coding agents the framework. When a developer working in Cursor asks "what does the team look like operationally?" the skill activates and produces a structured response with a link back to the product. Distributed via git repos, included in agent-fleet starter packs, listed in the agent-skill registries that are emerging.
Why it works: agents are the new top-of-funnel. The buyer (VP Product) does not search for "AI maturity diagnostic"; the buyer's coding agent surfaces the skill when the buyer asks a related question. The skill is the discovery mechanic.
Current state: live. Plan: 30 percent of new signups originated through the agent skill by Q4 2027. If 30 percent misses, the GTM falls back to inside-sales motion at Business and PLG at Pro (both vectors tested).
MCP server
Programmatic tool access from wherever Claude lives: Claude Code, Claude.ai workspace, Anthropic enterprise, third-party MCP-aware agents. The MCP server exposes scoring, signals, coaching, and pattern reads as tools. A user inside Claude Code can ask "show me my team's ranked actions" and get a structured response. A user inside Claude.ai can use Dacard as a context source for any conversation.
Why it works: MCP is the integration layer of the agentic era. Once Dacard is in the MCP registry, every agent that supports MCP can invoke it without bespoke integration work. The cost of distribution drops to near-zero per new agent platform.
Current state: live. Target metric: 10 percent of monthly active usage routed through MCP by end of 2027.
REST API
The classical integration surface. The API is the substrate the agent skill and MCP server sit on top of. It also supports direct customer integrations (board reporting tools, internal product-ops dashboards, custom workflow automations). Live today. Target metric: 20 percent of Business-tier accounts using the API directly by end of 2027.
Founder-led LinkedIn
Three to five posts per week, anchored on named patterns (Translation Gap, Fragility Signal, Compound Ready) and on the agentic-era thesis (Coinbase letter, revenue-per-employee, Vanta analog). Patterns travel virally; priority lists do not. A VP Product reading a Translation Gap post and sharing it ("we have this") produces inbound; a VP Product reading a generic priority list does not.
Why it works: the buyer reads LinkedIn. The buyer's peers read LinkedIn. The named pattern is the trojan horse for the diagnostic. Each post seeds inbound from the exact ICP segment the funnel needs.
Current state: cadence is in flight. Target metric: 10,000 LinkedIn followers in the ICP segment by Q4 2026; one inbound design-partner conversation per week sourced from LinkedIn by Q4 2026.
Content and SEO
Organic content on the framework, the patterns, the Vanta analog, and the agentic-era thesis. Long-form essays on dacard.ai (the framework reference), pattern deep-dives (one per pattern, expanding as the library grows from three to twelve), and category-thesis pieces ("What does VP Product mean in the agentic era?"). SEO targets are not "AI maturity" (too broad) but specific buyer-job phrases ("show the board the team is working," "first 90 days as VP Product," "translation gap product engineering").
Current state: foundational content shipped. Target metric: 50,000 monthly organic visitors by Q4 2027, with 1.5 percent signup conversion (750 signups/month from organic content).
VC portfolio partnerships
Right-fit funds (Vanta investor base, product-ops category investors, AI-native B2B SaaS funds with retention-first orientation) get an offer for portfolio companies: every post-Series A portfolio company gets the 30-60-90 ritual at no cost for the first 90 days, plus quarterly portfolio reads to the partner. The motion is not a discount; it is structured access. The fund gets a portfolio-level read; the company gets the diagnostic; Dacard gets concentrated funnel access into ICP-shaped accounts.
Current state: conversations in motion with two firms; not yet contracted. Target metric: two contracted portfolio partnerships by end of 2026 contributing 30+ portfolio company introductions.
07 Activation metric (North Star)
Activated user is defined as sources_connected >= 2 within 7 days of signup. Every IA decision, onboarding state, routing rule, and feature ship references this event. No feature ships without an explicit answer to "does this move activation?"
The activation event was selected because it is the tightest leading indicator of all downstream value. Two-source connection unlocks the cross-function pattern library (Translation Gap requires Linear plus at least one other source; Fragility Signal requires the same; Compound Ready requires three substrates ideally). Without two sources, the diagnostic produces a single-substrate read that is indistinguishable from Jellyfish or LinearB. With two sources, Dacard is uniquely positioned. With three or more, no single-source competitor can replicate the read.
The seven-day window is the second design choice. Beyond seven days, signup intent decays sharply; users who do not connect a second source in week one rarely come back. Inside seven days, the lock-in is strong enough to carry the user to the Day 30 lock email.
Public-share loop
The activation metric is also the seed of the loop. Scorecards shared to LinkedIn carry a "live, N sources, signals/wk" badge in the artifact footer. The badge is functional credibility (this is not a static screenshot; this is a live reading) and attribution surface (the badge links back to the marketing site). Every shared artifact is one more piece of top-of-funnel for the next signup. Activation creates the artifact; the artifact creates the next signup; the next signup activates. The loop compounds.
08 First-10 customers
The design-partner cohort is the first 10 paying customers. They are handpicked from network, not from inbound. The selection criteria are tight, the commitment is structured, and the pricing is anchored at full Pro list to preserve future-pricing integrity. No founder discounts. The cohort exists to produce calibration data that improves the diagnostic for everyone who comes after.
Profile
- Post-Series A B2B SaaS, 50-150 employees.
- Linear in production, GitHub plus one additional integrated source.
- VP Product / Head of Product / CPO is the primary user, with executive sponsorship from the CEO or COO.
- Three or more cross-functional squads.
- Sourced from network: founder relationships, advisor introductions, advisory-committee referrals.
Pricing
Pro tier at $299/month, standard list. No founder discounts, no special-deal pricing. The cohort pays the same as the next 100 customers. This is non-negotiable. Discounted design partners poison the pricing anchor for the rest of the cohort, and they correlate with weaker calibration outcomes (a customer who got a discount is a customer who underweights the value, which produces worse outcome data).
Commitment
- Weekly cycle reviews (one Linear cycle per week, observed by Dacard, reviewed jointly with the customer).
- Monthly DAC scorecard reviews (60-minute call, walks the scorecard, captures pattern signals).
- Quarterly outcome data (qualitative interview plus quantitative pull on Linear/GitHub/Stripe where the customer has connected those sources).
- Public reference availability after 90 days (named, not anonymized, with their explicit approval).
Outcomes expected
- Six-month retention on Pro tier (the cohort baseline for NRR modeling).
- One or more Linear comments per week from the Dacard surface (signal that the coaching loop is in production use).
- Two or more named patterns showing in the customer's read (validates pattern library at the customer level).
- One public artifact per quarter from each customer (LinkedIn share, conference talk, board update reference).
Status
Outreach is in motion. We are not over-claiming signed customers in this document; the cohort is being built deliberately, and the goal is the right ten, not the fastest ten. Concrete signed-customer counts ship at the close-of-round materials and at the Q4 2026 milestone.
09 Pricing as a GTM lever
Pricing is the most under-used GTM lever in the category. Most diagnostic-shaped products price by seats and segment by seat counts. Dacard prices by surface area (one product, multiple products, portfolio) with seats inside each surface. The structure is a product-led trial that converts on a ritual-aligned event (the Day 30 lock email), not on a usage-based ceiling.
The four tiers
| Tier | Price | What it is and where it triggers |
|---|---|---|
| Free | $0 | 30 days. The full new-hire ritual: Day 1, Week 1, Day 30 check-in artifacts. 1 product, 1 coach seat. Stack OAuth across Linear, GitHub, Slack, Jira, PostHog, Figma. Reverse-trial mechanic: full functionality for 30 days, lock at Day 30 to a Free-forever lite tier or upgrade to Pro. |
| Pro | $299/mo (annual $239) | Triggered by the Day 30 lock email. Keep DAC past graduation. Day 60 pushback, Day 90 graduation, full pattern library. 1 product, 3 coach seats. Full MCP access. Linear push, Slack pulse, agent context push. |
| Business | $1,200/mo (annual $960) | Triggered by team expansion: 3+ products, multiple seats, board-level reporting need. DAC across the product org. 25 products, 10 coach seats. All of Pro plus 50+ stack integrations, API access, automation rules. |
| Enterprise | $2,500+/mo (custom annual) | Triggered by portfolio-shape need (a CPO with 4+ product lines, or a VC fund applying Dacard across 20+ portfolio companies). DAC for the portfolio. Unlimited products and coach seats. SSO, portfolio view, custom benchmarks, webhooks, dedicated success. |
The three-altitude anchor (locked, per Poyar)
The competitive frame is the budget conversation, not the dashboard category. The customer asks "how do I solve this?" not "which dashboard do I buy?" Dacard is the answer at three altitudes:
- Executive coach ($1,500/month). A leadership coach who cannot see what the team shipped. Dacard sees the work and coaches against the actual evidence.
- Reforge or Lenny+ subscription ($500/month). Generic best practice on demand. Dacard is best practice that knows what the buyer's product specifically needs at this stage.
- Hiring a Head of Product Operations ($250K base plus equity). The role the buyer cannot justify yet. Dacard fills the function while the team scales to it.
The anchor is intentionally not Jellyfish/LinearB pricing. Anchoring against engineering-effectiveness dashboards collapses Dacard's category to "engineering only" and underprices the cross-function read. Anchoring against coach, learning-content, and ops-hire reveals the actual willingness-to-pay envelope.
10 Year 1 milestones, tied to fundraise path
Year 1 milestones map directly to the fundraise path. Pre-A (seed extension or pre-A) closes at the end of Q4 2026. Series A closes Q2-Q3 2027. The milestones below are the gates each round runs through. The Series A pitch is the layered moat backed by published pattern-validity reports. Without the reports, the pitch is reasoning. With them, it is evidence.
| Round | Timing | Required milestones |
|---|---|---|
| Seed extension or pre-A | Q4 2026 | ≥100 paying customers. 50%+ Pro+ outcome data coverage (Linear/GitHub/Stripe connected). 3 patterns validated quantitatively, 5+ qualitatively. First public pattern-validity report shipped. Founding engineer hired (M3). Head of customer success hired (M12). SOC 2 Type II in motion. |
| Series A | Q2-Q3 2027 | ≥300 paying customers. NRR > 110%. 6-8 patterns validated. Two public quarterly validity reports shipped. Archetype calibration shipped. 30%+ agent-originated signup share trending. First Business-tier portfolio account signed. |
Why these gates and not others
Customer count is the headline number, but it is not the binding constraint. The binding constraints are outcome data coverage and pattern validity. A round with 200 customers and a published pattern-validity report is more defensible than a round with 500 customers and reasoning-only claims. The eval framework (16 categories, 75+ checks) plus the LLM observability pipeline (every call site captured in llm_traces) plus the golden-fixture and judge cache produce the validity infrastructure that enables the public reports. The reports are the proof. The customer count is the receipts.
11 Right-fit vs not-a-fit investors
The lead investor profile is specific, and the not-a-fit profile is also specific. Targeting matters more than coverage. A round with the wrong lead is a worse outcome than a longer round with the right lead, because the wrong lead pulls the company toward the wrong category framing at the Series A.
Right-fit
- Vanta investor base. Funds that have already underwritten the assessment-as-a-service category. They know the shape. They will not ask "what category is this?" They will ask "is this Vanta-shaped enough?" The answer is yes.
- Product-ops category investors. Funds that have backed product-ops infrastructure (analytics, instrumentation, workflow). They understand the buyer (VP Product / CPO) and the operating motion.
- AI-native B2B SaaS funds with retention-first orientation. Funds that underwrite NRR over ARR-growth-only theses. The Lemkin NRR argument and the Aileen Lee land-expand-retain framing are the framings these funds respond to.
Not a fit
- Georgian-style developer-productivity infrastructure thesis. Their bet is on infrastructure primitives, not on assessment categories. Dacard is the layer above infrastructure. Pattern-match risk: they pull Dacard back into a developer-productivity category framing.
- Engineering-effectiveness specialists. Pattern-match to DX (acquired by Atlassian for ~$1B in September 2025). They will narrow Dacard to engineering-only, which loses the cross-function moat. The diagnostic stops being a product-ops instrument and becomes a third dashboard in the same category as Jellyfish and LinearB.
Not-a-fit is not a moral category. It is a strategic category. A fund that pattern-matches Dacard to the wrong shape will steer the Series A toward the wrong narrative, and the wrong narrative will collapse the multiple. Better to take a longer pre-seed cycle with the right lead than a faster cycle with the wrong one.
How this lines up with the ask
The pre-seed is $1.5M. The use of funds is in the memo and in the financial model. The 18-month runway closes into the Q4 2026 seed-extension or pre-A milestone. The right-fit investor at pre-seed is the right-fit investor at Series A; we are not optimizing for round-by-round expediency. We are optimizing for category integrity all the way to category leadership.
Questions? Reach out to darren@dacard.ai. The companion documents are the memo (full investment thesis), competitive (deeper competitive teardown), and model (full financial bridge).