Yuba Analytics Metrics Manual
This manual explains the analytics terms used in Yuba. It is written for program teams, partners, and clients who may not know the technical details behind the platform.
The goal is to help someone answer: What is happening in this cohort? Who is making progress? Who may need support? Where are founders spending their time and credits?
Quick Orientation
Yuba Analytics shows how founders, teams, cohorts, and projects are moving through the venture-building journey. The numbers are meant to support program decisions, not to replace human judgment.
Most analytics numbers depend on the filters selected at the top of the page:
- Date range: The period being reviewed. Example: Last 7 days, Last 30 days, or a custom range.
- Cohort: The group being reviewed. Example: ET Cohort or Yuba Ventures Pitch Demo Cohort.
- Member type: Whether the view is showing solo founders, teams, or both.
- Feature: A specific Yuba tool. Example: GTM, BMC, Market Research, or Pitch Deck.
- Risk status: A health filter. Example: Healthy, At Risk, Stalled, or Inactive.
If a metric is zero, it usually means Yuba did not find tracked activity for the selected filters. It does not always mean the founder did no work outside the platform.
Main Objects
Organization: The full client or partner workspace in Yuba. Example: Yuba Ventures is the organization that owns cohorts, members, teams, projects, credits, and analytics.
Cohort: A group of founders or teams managed together. Example: A grant program may create one cohort for the May 2026 founder group.
Member: A founder, solo participant, or team workspace inside the organization. A member is the person or group being monitored in analytics.
Solo Founder: An individual member working on their own project. Example: Amina has one venture project and is not part of a team workspace.
Team: A group workspace where multiple people work together on one or more projects.
Project: A venture idea, business concept, or startup project created by a founder or team. Example: "SafiSolar Cold Chain" may be one project owned by a founder.
Scope: The level the analytics row applies to. Example: A report can be scoped to a whole cohort, a single founder, a team, or a project.
Health And Risk Terms
Healthy: The member or project does not currently show major warning signals. Example: A founder with recent activity, steady progress, and normal credit usage may be marked Healthy.
At Risk: The member or project shows signals that may need follow-up. Example: A founder has used many credits but has completed only a few journey stages.
Stalled: The member or project appears stuck in a stage or module longer than expected. Example: A venture has stayed in Market Research for many days without completing the next milestone.
Inactive: There has been little or no recent tracked activity. Example: A member has not used monitored Yuba pages or completed tracked actions for several days.
Current Risk / Risk Status: The current health label for a member, team, project, or cohort. These labels are decision-support signals, not final judgments about founder quality.
Reason Codes: Short explanations for why Yuba flagged a risk or intervention. Example: "no_activity_14d" may mean the member has had no recent tracked activity for about two weeks.
Owner Message: A suggested follow-up message or summary for the program owner. Example: "Claire needs follow-up because persona work has not started and there was no activity in the selected window."
Priority: A score used to rank which intervention items should be reviewed first. Higher priority usually means the issue is more urgent or has more warning signals.
Urgent Action Queue: The highest-priority items that may need attention now. Example: founders with no activity, stalled progress, or high burn may appear here.
Operational Signals: System-generated notes that summarize important patterns. Example: "No activity recorded in the selected report window" is an operational signal.
Intervention Summary: A summary of people or projects that may need admin follow-up.
Open Interventions: Follow-up items that are still visible and unresolved.
Member Issues: Intervention items attached to members.
Project Issues: Intervention items attached to projects.
Activity Terms
Event: A tracked action inside Yuba. Examples include generating content, editing content, saving selected content, or deleting content.
Events In Window / Events In Range: The number of tracked actions that happened during the selected date range. Example: If the report runs from May 19 to May 25, only events during those dates are counted.
Total Events: All tracked actions in the selected view. Example: If a cohort has 150 total events, members in that cohort performed 150 tracked actions during the selected period.
Activity Days: The number of days in the selected range where activity was tracked. Example: If a founder worked on May 19, May 21, and May 24, they have 3 activity days.
Active Members: Members with tracked platform activity in the selected view.
Active Members 7d: Members who used the platform during the last seven days. Example: If 6 out of 15 members used Yuba this week, Active Members 7d is 6.
Active Subjects: Members or teams active on the busiest day in the selected window. This helps show the peak level of participation.
Last Activity: The most recent tracked platform action or engagement event. Example: "1 day ago" means the latest tracked activity happened one day before the report was generated.
Peak Event Day: The day with the highest number of tracked actions.
Activity Trend: A day-by-day chart of events and engagement. Use it to see whether activity is rising, falling, or concentrated on one day.
Activity Breakdown: A summary of action types, such as generates, regenerates, edits, adds, deletes, and failed actions.
Feature Activity: Activity grouped by Yuba feature. Example: GTM may show 20 events, Market Research may show 15, and BMC may show 10.
Feature Activity Breakdown: A chart or table showing which features received the most tracked actions.
Top Feature: The feature with the strongest activity or engagement in the selected view. Example: If members spent the most effort in GTM, GTM appears as the top feature.
Top Features: A ranked list of features where users spent the most active platform time.
Workflow Engagement: Activity across major venture-building workflows, such as customer discovery, business model design, or commercialization.
Action Terms
Generates: Times a user asked Yuba to create new content. Example: generating a Business Model Canvas, GTM strategy, or pitch deck.
Regenerates: Times a user asked Yuba to create a new version of content. A high number of regenerates can mean the founder is iterating, but it can also suggest they are not satisfied with the output.
Edits: Times a user changed generated or saved content. Edits are usually a good signal because they show the founder is refining the work rather than only accepting AI output.
Adds: Times a user added generated content into their project workspace or saved work.
Deletes: Times a user removed generated or saved content.
Saves / Save Selection Events: Times a user saved a selected output or useful generated option.
Fails / Failed Events: Actions that did not complete successfully. Example: a generation request failed or a feature action could not finish.
Words Added: Words added by users during editing activity. This can show how much a founder expanded or improved generated content.
Words Removed: Words removed by users during editing activity. This can show pruning, cleanup, or rewriting.
Engagement Terms
Engaged Minutes: Active time spent on monitored Yuba pages. It counts active platform time, not all time a founder spent thinking or working offline.
Engaged 7d: Active platform time during the last seven days.
Engaged 30d: Active platform time during the last 30 days.
Screen Engagement: Visible, active time collected from monitored Yuba pages. Example: time on an analytics, project, or feature page while the user is actively interacting.
Sessions: Active visits to monitored Yuba pages. Example: If a founder opens Yuba three separate times during a week, that may appear as three sessions.
Average Session: The average length of active monitored sessions. Example: if sessions are 5, 10, and 15 minutes, the average session is 10 minutes.
Median Session: The middle session length when sessions are ordered from shortest to longest. Example: if sessions are 2, 4, 30, and 60 minutes, the median is between 4 and 30, while the average is pulled higher by the long sessions.
Distinct Pages: How many different monitored pages were visited. Example: a founder who visited Dashboard, GTM, and Pitch Deck has 3 distinct pages.
Distinct Features: How many different tracked features were used. Example: using Market Research, BMC, and Pitch Deck means 3 distinct features.
Top Engaged Pages: Pages where users spent the most active time.
Top Engaged Features: Features where users spent the most active time.
Engagement Trend: A daily chart of active platform time and active members. It helps show whether founders are consistently engaged or only active on a few days.
Platform Time: How a member's active time compares with the cohort average.
Platform Time Ratio: A comparison of one member's active time to the cohort average. Example: a ratio of 1.0 means the member is around the cohort average. A ratio of 0.5 means about half the cohort average. A ratio of 2.0 means about twice the cohort average.
Platform Time Benchmark: The cohort comparison used to decide whether platform time looks high, normal, or low.
Credit Terms
Credits Charged: Credits used by tracked work during the selected date range. Example: if members generated reports, pitch content, and research outputs, each may charge credits.
Credit Consumption: Credit usage across members, teams, projects, and features.
Total Spend: Total credits used in the selected view.
Top Consumer: The member or team with the highest tracked credit usage.
Credit Burn: How much of the available credit allocation has been used. Example: if a founder has 200 credits and has used 120, their credit burn is 60%.
Consumed Credits: Credits already used.
Allocated Credits: Credits assigned or available to the member, team, or project.
Credits Burned In Module: Credits used while a venture was in a specific journey module. Example: a founder may use 40 credits while working through Market Research.
Credit Gap / Progress-Credit Gap: The difference between journey progress and credit usage. Example: if a founder has used 70% of their credits but has completed only 25% of the journey, the gap is large and may need follow-up.
Low Progress / High Burn: Members or projects that have used many credits but have not made much journey progress. This can signal that a founder is spending credits without reaching milestones.
Journey Progress Terms
Journey Progress: How far a venture has moved through Yuba's venture-building journey. It is based on completed journey stages, not just time spent on the platform.
Venture Progress: Another name for journey progress at the project or member level.
Median Progress: The middle progress value when all selected ventures are ordered from lowest to highest. Example: if five ventures are at 10%, 20%, 40%, 80%, and 90%, the median progress is 40%. Median is useful because one very advanced or very delayed venture does not distort the picture.
Average Progress: The total progress divided by the number of ventures. Using the same example, 10% + 20% + 40% + 80% + 90% = 240%, and 240% divided by 5 is 48%. Average is useful for the overall performance level, but it can be pulled up or down by extreme cases.
Difference Between Median And Average Progress: Median answers, "What does the middle venture look like?" Average answers, "What is the overall progress level if everyone is blended together?" Example: if one venture is at 100% and nine ventures are at 10%, the average is 19%, but the median is 10%. The median shows most ventures are still early, while the average is slightly lifted by the one advanced venture.
Average Median Progress: The average of each cohort's median progress. This is useful when comparing several cohorts because each cohort contributes one middle value.
Ventures Above 50%: The share of ventures that have passed the halfway point in the journey. Example: if 5 out of 15 ventures are above 50%, the value is 33%.
Current Stage: The latest venture-building step reached by a member or project. Example: a project may currently be at GTM Strategy.
Stage: A specific step in the venture-building journey, such as Persona Defining, Market Findings Analysis, or Pitch Deck Generation.
Stage Distribution: Where members or projects currently sit across journey stages. Example: 4 projects may be in Market Research, 3 in Business Model Design, and 2 in GTM Strategy.
Journey Stage Distribution: Another name for stage distribution.
Report Stage Distribution: Stage distribution within the selected report window and filters.
Current Module: The larger journey area where the member or project is currently focused. Example: Commercialization is a module that includes Pricing Strategy and GTM Strategy.
Module: A larger part of the venture journey that contains several stages. Example: Customer Discovery contains Persona Defining and Customer Profiling.
Days In Module: How long a member or project has been in the current module. Example: 18 days in Market Research may suggest the founder is taking time to complete that phase.
Days Inactive: How long it has been since the last tracked activity.
Module Bottlenecks: Modules where members are taking longer, stopping, or failing to complete expected steps. Example: if many founders stay in Market Research for a long time, Market Research may be a bottleneck.
Module Time Breakdown: A view of how long members or projects spend in each journey module.
Completion Rate: The share of members or projects that completed a stage or module. Example: if 6 out of 10 started a module and 3 completed it, the completion rate is 50% of those started.
Current Distribution: The share of members or projects currently sitting in a stage or module. Example: if 30% of the cohort is currently in GTM, GTM has a 30% current distribution.
Stalled Count: Members or projects that appear stuck in a module.
Median Days: The middle number of days spent in a stage or module. Like median progress, this avoids being overly affected by one very slow or very fast founder.
P75 Completed Days: The time by which 75% of completed members or projects finished. Example: if P75 is 14 days, most completed ventures finished within 14 days, while the remaining 25% took longer.
Active Incomplete Days: How long active members or projects have been in a module without completing it.
Average Progress Entering Module: The average journey progress members or projects had when they entered a module.
Journey Milestone Timeline: The completed journey stages shown in time order. This helps explain how the venture moved through the journey.
Journey Progress Detail: A detailed view of stage completion, module timing, credit burn, and engagement.
Venture Progress Diagnostics: Progress and productivity signals for a member, project, cohort, or organization.
Venture Journey Stages
Problem Validation Report: The founder has completed the first structured problem validation work. Example: they have evidence that the problem exists and is worth exploring.
Persona Defining: The founder has created a target customer persona. Example: "smallholder farmer managing post-harvest storage" could be a persona.
Customer Profiling: The first customer profile has been created. This describes the target customer, their pains, and their needs.
Value Proposition Canvas: The venture has worked through the value proposition canvas, connecting customer pains and gains to the proposed solution.
Assumptions Framing: Key assumptions have been defined. Example: "farmers will pay monthly for cold storage access."
Hypothesis Framing: Testable hypotheses have been defined. Example: "If we offer pickup within 24 hours, farmers will reduce spoilage by 20%."
Market Research Questions Generation: Research questions have been generated to guide customer or market learning.
Market Findings Analysis: Market research findings have been analyzed and summarized.
Customer Profiling V2: The customer profile has been refined after more learning.
Value Map Design: The value map has been created or refined to show how the solution creates value for customers.
Value Proposition Statement Design: A first value proposition statement has been created.
BMC Building: A first Business Model Canvas has been created.
Solution Critique: The proposed solution has been reviewed or critiqued to find weaknesses and improvement areas.
Value Proposition Statement Design V2: The value proposition statement has been refined.
BMC Building V2: The Business Model Canvas has been refined.
Business Model: A fuller business model has been developed.
Product Requirement Details Document: MVP requirements have been defined. Example: the founder has listed what the first usable product must include.
Validation Metrics: Metrics for validating the venture have been defined. Example: activation rate, repeat usage, conversion rate, or willingness to pay.
Pricing Strategy: Pricing assumptions or strategy have been developed.
GTM Strategy: Go-to-market strategy has been developed. GTM means go-to-market.
Pitch Deck Generation: A pitch deck has been generated.
Team Versus Solo Founder Terms
Team Projects: Projects owned by teams.
Solo Projects: Projects owned by individual founders.
Team Median Progress: The middle journey progress value for team-owned projects. This helps show the typical team project's progress.
Solo Median Progress: The middle journey progress value for solo-founder projects. This helps show the typical solo founder project's progress.
Median Progress Gap: The difference between team median progress and solo median progress. Example: if team median progress is 60% and solo median progress is 40%, the gap is +20 percentage points for teams.
Teams Versus Solo Founders: A cohort-level comparison of team projects and solo founder projects. Use this to understand program design and support needs, not to rank founders.
Research Terms
Research Coverage: The industries and geographies represented in tracked research activity. It shows whether the cohort is exploring a narrow or broad set of markets.
Industries Researched: The number of industries found in project research or activity. Example: agriculture, health, education, and fintech would count as four industries.
Geographies Researched: The number of geographies found in project research or activity. Example: Nigeria, Kenya, Rwanda, or West Africa.
Top Researched Industries: The industries most represented in the selected view.
Top Researched Geographies: The geographies most represented in the selected view.
Industry: A sector or market area, such as agriculture, health, education, fintech, logistics, or energy.
Geography: A country, region, or market location connected to the research.
Cohort And Member Table Terms
Cohort Health: A cohort-level view of activity, progress, risk, and intervention needs. It helps program teams see whether the cohort as a whole is moving well.
Member Table: A detailed member list for the selected cohort and filters. It usually includes progress, module, risk, engagement, projects, and last activity.
Member Type: Whether the row is an individual member or a team.
Members In Scope: Members included in the selected filters. Example: if the filter is set to Solo Founders in one cohort, only those solo founders are in scope.
Projects: Projects connected to the selected members, teams, or cohort.
Project Count: The number of projects connected to the selected member, team, or cohort.
Member Type Breakdown: A split of cohort activity between individual members and teams.
Display Name: The member, team, or project name shown in analytics.
Generated: The time the report or analytics view was created.
Report Terms
Operational Report: A detailed report for a member, team, or cohort over a selected date range. It brings together progress, activity, engagement, risk, evidence, and suggested follow-up.
Date Presets: Quick date options such as Day, Week, Month, or Custom.
Start Date: The first day included in the report.
End Date: The last day included in the report.
Previous Period: The same length of time immediately before the selected date range. Example: if the report covers May 19 to May 25, the previous period is the seven days before May 19.
Yesterday: The day before the report end date. It is used as a short-term comparison point.
Change Summary: A comparison of the selected period against the previous period and yesterday.
Current Value: The number for the selected date range.
Previous Value: The number for the previous period.
Delta / Change: The difference between the current value and the previous value. Example: if events increased from 40 to 50, the delta is +10.
Delta Percent: The percentage increase or decrease compared with the previous period. Example: moving from 40 to 50 events is a 25% increase.
Evidence Tables: Tables that show supporting detail behind the report, such as completed milestones, project evidence, or recent activity. They help explain why the report shows a certain status.
Project Evidence: Projects linked to the selected member, team, or cohort. Example: a founder detail report may show one or two project rows with stage, risk, events, and last activity.
Recent Activity Evidence: Recent tracked actions that support the report.
Context Blocks: Extra summary sections that give context for the report.
Download PDF: Exports the current operational report as a PDF.
Data Freshness Terms
Freshness: How recently analytics data was updated. Fresh data means the system has recently processed activity into the analytics views.
Generated At: The time the visible report was created.
Last Engagement At: The most recent tracked engagement event.
Stale Data: A warning that the latest activity may not have fully appeared in analytics yet. If data is stale, the report may not include the most recent actions.
Snapshot: A saved analytics summary used to make pages load faster.
Rollup: A daily summary of many smaller activity records. Example: instead of reading every action one by one, Yuba can summarize all of a member's actions for a day.
Raw Event: The original tracked action before it is summarized. Example: one generate click or one edit action.
Important Reading Notes
Analytics only reflects activity Yuba can track inside the platform.
Engaged time means active time on monitored pages, not total time a founder spent working offline.
Risk labels are decision-support signals, not final judgments about a founder or project.
Team versus solo founder metrics are for understanding cohort patterns, not ranking people.
Credit usage should be read together with journey progress. High credit usage is not automatically bad if progress is also high.
Median and average answer different questions. Median shows the typical middle case. Average shows the overall blended value.
Reports are affected by filters. Always check the cohort, member type, feature, and date range before interpreting results.