Skibidi Toilet’s 35M+
subscriber growth year.
INVIZ’s reporting systems.

Onboarding and reporting for the merchandise business behind major YouTube creators, including the creator behind Skibidi Toilet. Noah built these systems in 2023, the year that channel added 35.2 million subscribers.

Explore the four systems

01 / Business context

Behind the channel.
Inside the business.

INVIZ.tv produces, fulfills and markets merchandise for major YouTube creators. Noah built onboarding and reporting systems for INVIZ and its clients in 2023, including the business serving the creator behind Skibidi Toilet. Its 2023 creator terms describe merchandise production, fulfillment and marketing services.

According to HypeAuditor’s 2024 report, the YouTube channel behind Skibidi Toilet added 35.2 million subscribers in 2023. That growth shows the scale of the creator business INVIZ served; it is not attributed to Noah’s onboarding and reporting work.

The work spanned two connected operating needs: help the team and its creator clients understand onboarding progress, and organize the source data used for creator reporting. Those needs produced distinct systems rather than a single all-purpose dashboard.

The work covered client checklists, the sales-to-service handoff and the data behind creator reports. The detailed studies distinguish an earlier onboarding setup from the later reporting work.

02 / Inside the systems

Explore the systems.
Follow the handoffs.

Choose a system to see what starts the work, where decisions happen and what the team receives.

Select a system, then select any step for the detail.

Client-board template test
Create the client-facing checklist from a template; the test used a static company name.
Client-facing onboarding board
Expose the onboarding tasks and statuses for the invited client.
Central client register
Retain the associated board ID and the onboarding summary for each client.
Guest-account access check
Inspect the invited board and task interactions from a separate account.
Client task-status event
A changed task on the external board supplies the progress update.
Find client by board ID
Use the stored association to locate the matching register record.
Update central progress
Reflect the matching status fields and progress in the client register, one way only.

Each system has its own history. Alternative versions are identified in the detail.

03 / System directory

Explore the four
system studies.

Open a study for the business process, Noah’s contribution and the implementation detail.

Client operations

System 01Client operations

Client-facing boards and onboarding progress

Give each client an onboarding checklist and reflect its progress in the team’s central view, one way only.

Historical scoping, configured board-creation/status tests and guest-view check; later internal-board redesign remained a change brief.Explore the system System 02Client operations

Lead-to-client handoff and reporting workspace provisioning

When a lead becomes a client, prepare the onboarding state, reporting workspace and links the team needs.

Historical build session with narrated test folders, template sheets and client-field population.Explore the system

Reporting sources

System 03Reporting sources

QuickBooks uploads and creator reporting data

Keep the original accounting export, prepare its transactions for reporting and show when the client last uploaded data.

Configured historical reporting handoff and sample-data population; creator statements remained discovery/proposed work.Explore the system System 04Reporting sources

Shopify order collection for creator reporting

Test whether store orders are available before designing how to separate creators’ sales in the reports.

Narrated successful order-fetch test for one store; broader source mapping and rollout pending.Explore the system

04 / Contribution & scope

The role behind
the system work.

Noah designed the workflows, directed parts of the implementation and repaired integrations built with the team. He prepared reporting resources, corrected client handoffs and tested access to store orders.

Recorded tests created a client-facing board and reflected its task changes in a central client register. A guest-account check showed the invited board and available task interactions.

The ClickUp build produced test client folders and reporting sheets, then narrated successful form-data population. A separate Shopify test returned orders from one store.

The project covered onboarding, reporting preparation and commerce-data collection. Client-account rollout and financial reconciliation were outside the tested scope of these workflows.