Intempt Handbook

The product and community health score

One 100-point weekly scorecard for the Product & Community team: a product worth wanting, a community that stays, and the loop that turns a visitor into a paying workspace.

Product and community health is one number out of 100, graded every week across the whole Product & Community team. The team does two things, and this score grades both: build it (a product people want, kept and evangelized by the community that uses it) and convert it (turn a visitor on the surface into an activated, paying workspace). It is the counterpart to the engineering, marketing and growth, and sales health scores.

This replaces the earlier split between a product-build score and a growth score. Product & Community is one team with one number: the product it builds, the community that uses it, and the loop to paid it owns. Acquisition, the channels that bring a stranger to the surface, is Marketing & Growth's and is graded there.

Claude computes it from what the team already produces: the specs and mockup-gap files, the scenario coverage and test results, the docs tracker and academy audit, the research, the community feedback and advocate numbers, and the activation and revenue behind the surfaces. It posts the score and the deltas every week, with a source and a pull date beside every number, because the live numbers sit in dashboards this repo cannot read. It is a measurement, not a target invented on the spot.

Web, mobile, and desktop development all sit with Product & Community, built in-house with Claude Code. We do not use Lovable or Cursor for production. Developer experience (DX) stays with engineering.

The rubric: 100 points, build and convert

BucketCategoryPoints
BuildDifferentiated AI product16
BuildQA14
BuildCustomer communication12
BuildCommunity: feedback and evangelism18
ConvertInstall to signup8
ConvertSignup to activation10
ConvertActivation to paid12
The numberRevenue our agents generate10

A week starts at 100 and loses points against the thresholds below.

Market research is mandatory for a 100. The competitive landscape must be current and complete. If a competitor turns up that the team had not already found, the week cannot score 100, whatever else looks good: finding rivals late is a failure, not a nicety.

Build: a product worth wanting, and a community that stays (60 points)

Differentiated AI product, 16 points

SignalPointsFull marks whenSource
Spec coverage and freshness5Every shipped area has a current spec with requirement IDs and scenarios; nothing shipped ahead of its specThe product specs, the drift scan
CX built and shipped3Customer-facing UI across web, mobile and desktop prototyped, gap-analyzed, then built in-house; coverage classifiedThe mockup-gap files
AI output quality5Every AI feature has a scoring rubric; outputs inside their quality bar; no unflagged degradationThe AI quality evaluations
Differentiation and market research3Competitive set complete, with no rival not already identified; comparison pages current and honestThe comparison pages, the positioning doc, the market research

QA, 14 points

SignalPointsFull marks whenSource
Scenario coverage and traceability5Every shipped area has scenarios, each naming the requirement IDs it coversThe specs and scenario docs
Test execution5Automated regression green; the manual end-to-end pass run on its cadence and recordedCI history, the test-owner results
Escaped defects4No production bug a scenario should have caught; no shipped feature drifting from its specBug board, the drift scan

Customer communication, 12 points

SignalPointsFull marks whenSource
Docs freshness5Every shipped feature documented; the backlog shrinking; every article at the Grade A bar; only public surface documentedThe docs tracker
Academy3Scripts current against the live product; filming progressing against the baselineThe academy audit and curriculum
Support SLA and voice4SLA first response met: every support case answered inside its severity window across the community channels (Slack, Discord) and email; ICP evidence refreshed with real customer input; incident and status communication on time; escalations handledSupport records, the research docs, the incident reviews

Community: feedback and evangelism, 18 points

The Slack, Discord, YouTube, and Reddit communities run as the product's feedback loop and its evangelism engine, covered in how we run Product & Community.

SignalPointsFull marks whenSource
Feedback into the roadmap7Bugs, confusion, and requests surfaced from the community with signal, and the loop closed back to the user who raised themThe community channels, the roadmap
Community health5Active members growing; questions answered; the rooms worth being in, not noiseThe community channels, Intempt analytics
Advocates grown6Unpaid advocates identified and growing; users answering each other and recommending Intempt without being askedThe community channels, referral data

Convert: turn a visitor into paid (30 points)

The conversion rate on our surfaces, stage by stage. Acquisition brings the visitor; Product & Community converts them.

SignalPointsFull marks whenSource
Install to signup8Installs (plugin, MCP, CLI) and surface visits turning into signupsIntempt analytics
Signup to activation10Source connected and first play seen, climbing; recipes run per new workspaceIntempt analytics
Activation to paid12Free seats crossing the wall (metered product or gated feature) to paid; retention holdingPayments, Intempt analytics

The one number: 10 points

The game is the revenue the product's agents generate for customers. Activation and paid conversion are the leading inputs; this is the number they feed.

SignalPointsFull marks whenSource
Revenue our agents generate10The revenue the product's agents generate for customers, attributed to the agent and to Intempt, growing, each carrying a source and a dateIntempt analytics, the attribution model

The bands

ScoreGradeWhat it means
90 to 100AHealthy. Keep building.
80 to 89BMinor slippage. Named owner, fixed this week.
70 to 79CA category is failing. It leads the next week's priorities.
60 to 69DTwo or more categories failing. Slow new scope until it recovers.
Below 60FStop and fix. The product is not worth wanting or not converting.

How a week runs

  • The score posts once a week, with the category breakdown, every number's source and pull date, and the change from last week.
  • A drop names an owner, with a date, not a general concern.
  • The weakest category sets priorities. It leads the next week's priorities.
  • The rubric is honest about gaps. A docs backlog, an unfilmed academy, a quiet community, or a conversion rate nobody is pulling shows up as a low category rather than being dropped.

This is the weekly read on how we run Product & Community and product operations, next to the marketing and growth and sales health scores.

On this page