Set up team scoring

Configure your org, onboard members, and run a collaborative scoring practice.

Orgs are auto-created from your email domain. Onboard members, assign roles, add products, and start scoring as a team. Lead role and above unlocks portfolio analytics.

Set up team scoring

As a leader, you want your org set up for collaborative scoring so your team can score together, track trajectory, and hold a consistent evaluation standard.

How orgs work

Orgs are provisioned automatically by email domain. When anyone on your team signs up with a company email, they join the same org.

1. Sign up with your work email

   We pull the email domain and match you to an existing org (or create a new one).

2. Name the org

   The first user from a domain becomes admin. Set the org display name under Settings > Account.

3. Share the sign-up link

   Tell team members to sign up at app.dacard.ai/sign-up with their work email. They join your org automatically.

Configure roles

Roles control what each team member can see and do. Assign roles from Settings > Members.

Role	Score	Create products	Manage members	Billing	Suite analytics
Member	Yes	No	No	No	No
Lead	Yes	Yes	No	No	Yes
Executive	Yes	Yes	No	Yes	Yes
Admin	Yes	Yes	Yes	Yes	Yes

Roles follow a hierarchy. You can’t assign a role higher than your own or modify users who outrank you. Promote senior PMs and engineering leads to Lead so they unlock portfolio analytics.

Recommended role assignment

Team member	Suggested role	Why
VP Product / Director	Executive or Admin	Needs billing access and full portfolio visibility
Senior PM / Tech Lead	Lead	Needs to create products and read suite analytics
PM / Designer / Engineer	Member	Can score products and read individual reports
Finance / Operations	Executive	Needs billing without member management

Add products to your portfolio

1. Open the dashboard

   Head to your main dashboard.

2. Hit Add Product

   Drop the product URL and display name. Products are visible to all team members.

3. Score the product

   Run an initial score to set a baseline. The portfolio view populates from this data.

Establish a scoring cadence

Consistent scoring matters more than frequent scoring. A cadence we recommend:

Cadence	When to use	What it captures
Monthly	Standard rhythm	Steady-state trajectory
Before/after milestones	Major releases, reorgs, new tool adoption	Impact measurement for specific initiatives
Quarterly deep dive	Strategic planning cycles	Cross-product comparison for resource allocation

Composite team scores

When your team scores multiple products, we compute composite analytics.

• Portfolio average: mean score across all products. Track it as your top-level read.
• Dimension heatmap: all 27 dimensions across all products.
• Systemic patterns: dimensions consistently strong or weak across your org.
• Score deltas: the move per product between scoring runs.

Practice

Use adapters for accuracy

Connected tools (GitHub, Linear, Slack) provide operational ground truth. Scores based on URL crawl plus adapter signal land materially closer to truth than URL-only scores.

Score competitors too

Drop competitor URLs to benchmark against the market. Competitor scores run on public signal only (no adapter data), so comparison is fair.

Review scores as a team

Share suite analytics in product reviews. Discuss patterns, not just individual scores. “Our whole org is weak on feedback loop quality” is a more actionable read than “Product X scored 48.”

Each URL score costs 10 credits. Monitor your usage under Settings > Usage and consider the Pro plan if you’re scoring more than 20 products per month.

What’s next

Track your portfolio

Read cross-product analytics and suite intelligence.

Benchmark against peers

Compare scores to peers at your stage and size.

Connect adapters

Tighten scoring accuracy with operational ground truth.

Plans and billing

Compare plans and manage team subscriptions.