Sample report — fictional channel

Northstar Fieldworks is invented. Every figure on this page is illustrative sample data, not a submitted or measured channel.

Channel Opportunity Audit — sample report

Subject: Northstar Fieldworks (fictional B2B field-service software channel). This is the shape and depth of a reviewed audit, filled with invented data so nothing here can be mistaken for a measured result.

01 / Channel snapshot

Public facts, before any grade

Lifetime figures are shown separately from the recent sample. Lifetime totals cover the channel's whole life; sample statistics cover 12 recorded uploads only.

Lifetime (whole channel)

Subscribers

4,820

Publicly rounded by the provider.

Public uploads

84

Public videos only.

Lifetime views

386,400

youtube.statistics.viewCount (demo definition v1)

Channel created

12 Apr 2021

Latest upload

12 Sep 2026

YouTube topic categories

Technology · Business

Reported by YouTube, not our hypothesis.

Recent sample — 12 recorded uploads, 2026-05-04 to 2026-09-12

Average runtime

13m 16s

Runtime, not watch time.

Median runtime

12m 59s

Average views

3,662

Per recorded upload in the sample.

Median views

3,350

2 live-stream items were excluded from runtime statistics. Shorts are never classified by duration alone — only a provider-declared flag counts.

Sample dataset behind these figures

Fourteen fictional items: twelve recorded uploads and two excluded broadcasts
PublishedTitleRuntimeViewsType
2026-05-04Dispatch board setup for a 6-truck plumbing crew12m 22s3,180recorded
2026-05-18Why your job photos never make it to the invoice8m 31s2,460recorded
2026-06-01Scheduling software teardown: three tools, one service week18m 04s5,120recorded
2026-06-15First-time-fix rate: what operations managers actually track10m 33s4,015recorded
2026-06-29Quoting on site without slowing the technician down7m 38s1,890recorded
2026-07-09Route density explained for small service fleets15m 02s6,340recorded
2026-07-23Recurring maintenance contracts: the ops setup20m 10s2,705recorded
2026-08-03Parts van inventory audit in 40 minutes11m 28s3,520recorded
2026-08-14Dispatcher handoff checklist we use with clients6m 35s2,260recorded
2026-08-27Service agreements that survive a price increase13m 35s4,890recorded
2026-09-04Technician onboarding: week one in the field app16m 07s3,105recorded
2026-09-12Reading a service P&L without an accountant19m 03s4,460recorded
2026-09-10Live: field ops Q&A (excluded from runtime stats)90m 00s610live (excluded)
2026-09-20Upcoming: dispatch automation workshop (excluded)Not reportedupcoming (excluded)

Computed from sampleComputed from the 12 recorded uploads below — fictionalas of 2026-09-15

02 / Readiness

62/100 — developing

An illustrative rubric score. Missing evidence is recorded as unknown, never as zero, and there is no penalty for a small or new channel.

Positioning clarity

15/20

developing

The subject matter is consistent, but the channel does not state who it is for in a place a first-time viewer will see.

4/4 checks answered

Titles & thumbnails

10/20

early

Titles vary in structure and thumbnails have no repeatable system, so the catalogue does not read as one product.

4/4 checks answered

Catalogue structure

12/20

developing

Strong individual explainers, few sequences a viewer can follow in order.

4/4 checks answered

Next step for the viewer

9/20

early

Most uploads end without a specific next step; descriptions carry a generic link only.

4/4 checks answered

Production consistency

16/20

established

Audio, pacing and cadence are steady enough to build on.

4/4 checks answered

A normalised total is only published when at least 16 of 20 checks are answered and every category has at least 3. This sample answered 20, so a total is shown. Unanswered checks stay null and are excluded from the normalisation.

Priority 1

A repeatable thumbnail and title system

Each upload currently competes on its own; a system lets the catalogue compound.

First step Define three title patterns and one thumbnail grid, then apply them to the next six uploads.

Priority 2

One clear next step per video

Attention is reaching the end of videos with nowhere specific to go.

First step Write one sentence and one link per video, matched to that video's topic.

Priority 3

A repeatable series

A named series gives returning viewers a reason to come back on a schedule.

First step Pick one recurring operations problem and commit to a four-part run.

Suggested 30-day sequence

  1. Week 1Lock positioning line, title patterns and thumbnail grid.
  2. Week 2Re-package the three strongest existing uploads.
  3. Week 3Publish part one of the named series with a specific next step.
  4. Week 4Review what the packaging change did, then set the next four-week run.

No performance outcome is predicted here. If you want this walked through with a human: book a session.

Reviewer interpretationReviewer rubric — sampleas of 2026-09-15

03 / Niche hypothesis

What we think this channel is for

This is a reviewer interpretation of public titles and descriptions — not an automated classification, and not private audience demographics.

Reviewer selection (a human confirms this)

Selecting an option only records the reviewer's working interpretation in this demo. Nothing is submitted and no model is run.

Likely buyer

Operations managers and service-business owners (5–50 field technicians)

Confidence

moderate

Titles and described workflows point consistently at service operations, but a reviewer has not yet confirmed the commercial offer behind the channel.

YouTube's own categories (separate from our view)

Technology · Business

Evidence — fictional upload

Dispatch board setup for a 6-truck plumbing crew

Names a specific operational artefact (the dispatch board) and a fleet size, which reads as software-adjacent operations teaching rather than consumer content.

Evidence — fictional upload

First-time-fix rate: what operations managers actually track

Uses a field-service KPI and addresses operations managers directly — the buyer role we would expect to convert.

Reviewer interpretationReviewer hypothesis — sampleas of 2026-09-15

04 / Similar channels

Context, not a ranking

Three invented peers with a similar business model, audience and language. This is not a percentile and not a sales-fit grade.

Three fictional peer channels with invented metrics
Channel (fictional)Public uploadsSubscribersSample avg. runtime
Northstar Fieldworks (subject)844,82013m 16s
Ridgeline Service Ops @ridgeline-sample1217,31014m 05s
Toolbelt Systems @toolbeltsystems-sample633,94010m 12s
Dispatch & Dime @dispatchanddime-sample965,48012m 13s

Why comparable — fictional

Ridgeline Service Ops

Same buyer role (operations managers), same long-form teaching format, English-language, sells an operations product rather than sponsorships.

Runtime from a 12-video sample

Why comparable — fictional

Toolbelt Systems

Comparable catalogue depth and a near-identical product-led business model: software walkthroughs that end in a demo request.

Runtime from a 12-video sample

Why comparable — fictional

Dispatch & Dime

Covers the same operational subject matter for the same trades audience, with a similar upload cadence and language.

Runtime from a 12-video sample

In a real audit, discovery selects three to five peers only after a reviewer confirms the niche. Subscriber or view size alone is not enough to call a channel comparable — business model, buyer and language have to match.

Fictional sample dataFictional peeras of 2026-09-15

05 / Growth over time

Dated snapshots, not a single pull

Growth can only be stated where dated snapshots exist. Current catalogue views grouped by publish date are shown separately — they describe the catalogue today, not history.

Last 30 days

Views: +13,700

Subscribers: +130

2026-08-13 → 2026-09-12. Public subscriber counts are rounded, so small subscriber changes are imprecise.

Last 90 days

Views: +36,600

Subscribers: +420

2026-06-14 → 2026-09-12. Public subscriber counts are rounded, so small subscriber changes are imprecise.

Snapshot table (accessible fallback)

Fictional dated snapshots with the provider view-count definition at capture time
CapturedViewsSubscribersView-count definition
2026-03-12312,5003,960demo-synthetic viewCount (single comparable definition)
2026-04-12325,9004,120demo-synthetic viewCount (single comparable definition)
2026-05-12338,2004,270demo-synthetic viewCount (single comparable definition)
2026-06-14349,8004,400demo-synthetic viewCount (single comparable definition)
2026-07-12361,1004,560demo-synthetic viewCount (single comparable definition)
2026-08-13372,7004,690demo-synthetic viewCount (single comparable definition)
2026-09-12386,4004,820demo-synthetic viewCount (single comparable definition)

Catalogue views by publish month — not growth history

  • 2026-05: 5,640
  • 2026-06: 11,025
  • 2026-07: 9,045
  • 2026-08: 10,670
  • 2026-09: 7,565

These are today's lifetime view totals of videos grouped by their publish date. They cannot be read as month-by-month growth.

Public subscriber counts are rounded by the provider, so small movements are imprecise. For real channels, a view delta spanning the 24 Aug 2026 view-count definition change is withheld rather than presented as a comparable growth rate.

Fictional sample dataSample history — fictionaldef: demo-synthetic viewCount (single comparable definition)as of 2026-09-15

06 / What this sample is not

Honest limits

  • No live channel lookup runs on this site today.
  • No prediction of views, revenue or subscribers is made anywhere in the report.
  • Private audience demographics are never used or inferred.
  • A new or dormant channel is a valid subject — there is no small-channel penalty.

For a reviewed audit of your own channel, the existing intake is at hyper-brand.com/channel-audit.