Canviq Founder Guide¶

How to set up Canviq, measure your PMF score, identify your High-Expectation Customer, and turn survey data into product decisions.

Before you begin¶

You need:

• A Canviq account (sign up at canviq.app)
• Your API key from Settings > API Keys
• The iOS SDK installed in your app, or the JS snippet added to your web product (see SDK documentation)

Onboarding checklist¶

Complete these five steps to see your first PMF score.

• [ ] Install the SDK. Choose iOS (Swift Package Manager) or web (JS snippet via your CDN)
• [ ] Create your first survey. Use the PMF template in your dashboard
• [ ] Add your API key. Initialize the SDK with your key and user ID at login
• [ ] Trigger the survey. Configure a trigger event (e.g. project_created after a user completes a core action)
• [ ] Collect 40 responses. The PMF score becomes statistically meaningful at this threshold

Tip: Use showSurvey("your-survey-id") in development to force-show the survey without waiting for trigger conditions. See testing your integration.

The PMF score¶

What it measures¶

The PMF score is the percentage of your users who answer "Very disappointed" to the Sean Ellis question:

"How would you feel if you could no longer use [Product]?"

• Very disappointed
• Somewhat disappointed
• Not disappointed

Your PMF score = % of "Very disappointed" responses.

The 40% threshold¶

40% is the threshold Superhuman used to identify Product-Market Fit. Below 40%, most companies cannot scale efficiently. Growth leaks out through churn faster than acquisition can refill it. At or above 40%, word-of-mouth and retention reinforce each other.

Trend chart¶

The trend chart plots your PMF score over time, grouped by response week. Look for:

• Upward trend after a release: a feature you shipped moved the score
• Flat trend despite growth: you may be acquiring users outside your ideal segment
• Drop after a release: you may have broken something your best users rely on

Segment analysis¶

The segment view breaks your responses into two cohorts:

What to look for¶

For each cohort, Canviq shows the distribution of answers to the follow-up open-text question:

"What is the main benefit you receive from [Product]?"

Compare how "Very disappointed" users describe the value vs. "Somewhat disappointed" users. The gap reveals which use cases you've nailed and which are still soft.

Actionable rule: If "Somewhat disappointed" users describe a benefit you already deliver well, there's a messaging or onboarding problem, not a product problem.

HXC Profiler¶

The High-Expectation Customer (HXC) is the most demanding, most engaged user in your target market. Superhuman's insight was to build for this user exclusively. Everyone else follows.

How the profiler works¶

After collecting at least 40 responses, the HXC Profiler uses Claude Sonnet to analyze the open-text answers from your "Very disappointed" cohort and produces:

• Profile summary: the characteristics of your HXC (role, workflow context, what they're trying to accomplish)
• Core value proposition: the specific benefit they articulate most consistently
• Friction themes: what's stopping the "Somewhat disappointed" cohort from becoming "Very disappointed"

Using the profile¶

Take the friction themes and add them to your roadmap as a prioritized backlog. The HXC Profiler does not prescribe solutions. It surfaces the problems your best users want solved.

Survey targeting¶

Trigger rules¶

A trigger rule defines when a survey appears. It has three fields:

The SDK counts events in memory per session. A user who triggers project_created 3 times within a single session will see the survey on the third call. The count resets when the app is terminated.

Best practice: Trigger PMF surveys after users have experienced the core value of your product, not on first launch. Configure a trigger event that fires after a meaningful action (not a session start) and set minCount to reflect how many times within a session that action indicates engagement. For cross-session behavioral thresholds (e.g., active 2+ times in 14 days), use server-side targeting rules in your Canviq dashboard.

Note: To target users who have performed an action across multiple sessions, configure server-side targeting rules in your Canviq dashboard using user attributes or behavioral signals.

Fatigue settings¶

Fatigue prevents the same user from seeing the same survey within the cooldown window. State is stored on the device (iOS) or in a server-side user record (web SDK). reset() clears it.

Set cooldownDays to at least 60–90 days for PMF surveys. Shorter cooldowns produce response volume but increase respondent fatigue, which deflates scores.

Audience segmentation¶

Targeting rules let you narrow which users see a survey. Rules can filter on:

• User attributes: properties passed with the user ID at initialization
• Behavioral signals: event counts and recency
• Device or locale: useful when testing translations before a full rollout

Configure targeting rules in your dashboard under Surveys > [survey name] > Targeting.

Feedback board admin¶

Moderating submissions¶

Submissions from your feedback board arrive in the Triage queue. Each submission can be:

Changing submission status¶

Move a submission through the workflow as you act on it:

When you move a submission to Planned, Shipped, or Declined, all followers receive an email notification. Include a brief comment explaining the decision; it shows users their feedback was read.

Responding officially¶

Any team member can leave an official response on a submission. Official responses are marked with a team badge and appear prominently above user comments.

Use official responses to:

• Explain why a submission was declined
• Share a timeline for a planned feature
• Ask a clarifying question before making a decision

Roadmap¶

The public roadmap shows submissions in Planned and In Progress status. Your users can see what you are working on and vote on upcoming features.

To control which submissions appear on the roadmap, use status changes: move a submission to Planned when you are committed to shipping it. Move it to In Progress when work has started.

The roadmap is automatically ordered by vote count within each column. You cannot manually reorder the roadmap. It reflects your users' stated priorities.

MCP / AI agent integration¶

If you want to automate survey deployment, query PMF scores, or integrate Canviq into an AI workflow, use the MCP server.

Quick start¶

1. Go to Settings > API Keys and create a new key. Select the MCP Agent key type and choose the scopes you need.
2. Copy the key. It is shown exactly once.
3. Configure your agent with the MCP server URL: https://canviq.app/api/mcp
4. Send your first query:

   "What is my current PMF score?"
   

See Guide: MCP and AI Agent Integration for the full tool reference, rate limits, and authentication details.

Account and billing¶

API keys¶

API keys are scoped by permission tier. Go to Settings > API Keys to create, rotate, or revoke keys.

• The full key is shown once at creation. Store it in a secrets manager; it cannot be retrieved from the dashboard.
• Rotate keys on a schedule or immediately if you suspect a leak.
• Each key records its last-used timestamp. Use this to identify unused keys before revoking them.

Notifications¶

You receive email notifications when:

• A new submission receives your admin's attention threshold (configurable)
• A survey reaches your response count target
• A PMF score change exceeds a threshold you configure

Manage these in Settings > Notifications.

Related¶

• API Reference: iOS SDK public methods
• MCP / Agent Guide: AI agent integration and tool reference
• Respondent Guide: What your users see