Jimi Jackson · YouTube creator, 1.34M+ subscribers · Advisory
A plan for better research.
Jimi Jackson runs a YouTube operation with more than 1.34 million subscribers. Hours of every day were going into manual research — hunting ideas, scanning trends, validating topics, and trying to forecast what would perform — instead of into making videos. This was an advisory engagement: I mapped where the research hours were actually going, worked out which parts were rules-based enough to hand to software, and designed a daily AI research and trend-forecasting engine that feeds ready-made briefs to the team.
No tech knowledge needed · 15 minutes · you keep the map either way.
- Best for
- Creators and teams with a heavy daily research load.
- Problem
- Hours of manual research ate the creative time the channel runs on.
- Changed
- Advisory: a mapped research-ops path plus a designed daily AI research engine. The map is the deliverable.
The problem
What was breaking?
The research load grew with the channel. Finding ideas, scanning what was trending, validating topics and guessing what would perform were all being done by hand, every day. Creative time — the thing a 1.34M-subscriber channel actually runs on — was being eaten by busywork that a system should be doing.
The system
What did the engagement cover?
This was advisory, not a build. We walked the research and trend workflow end to end: where the hours were going, which steps were rules-based enough to hand to software, and where human judgement has to stay. The output was the design for a daily AI research engine — trend scanning, topic validation and performance forecasting running on a schedule, delivering briefs the team can act on.
- The research ops map: where the daily hours were actually going
- The split between rules-based research work and human creative judgement
- The design for a daily AI research and trend-forecasting engine
- Briefs delivered to the team on a schedule, instead of research on demand
- A plan the operation can run with, in-house or with any builder
The outcome
What did the team leave with?
A clear, sequenced plan: what the research engine watches, how topics get validated, how forecasts are made, and what lands in the team’s hands each day as a ready-made brief. The map is the deliverable — the operation can act on it at its own pace.
| Before / After | Before | After |
|---|---|---|
| Engagement | Hours of manual research daily | One mapped research-ops path |
| Idea hunting & trend scanning | By hand, every day | Designed to run on a schedule |
| Topic validation & forecasting | Gut feel | A defined, repeatable process |
| The team’s mornings | Start from zero | Start from a daily brief |
Human control built in
How does the plan keep the team in control?
The proposed engine researches; people decide. The advisory design keeps publishing decisions human and calls for source links to travel with each brief so the team can verify a recommendation. Those controls describe the plan, not a claim that the engine was implemented in this engagement.
- Human approval points
- Sensitive actions wait for a person to sign off before anything sends or triggers.
- Escalation rules
- When something falls outside the rules, the system hands it to a person instead of guessing.
- Logs and visibility
- In-scope actions are recorded where connected tools expose the required events.
Bring me yours
Bring me the workflow that keeps breaking.
Book the free 15-minute build review. You leave with your 3 biggest time leaks mapped and a concrete recommendation — whether or not we ever work together.
No tech knowledge needed · 15 minutes · you keep the map either way.
One focused workflow. A clear scope in writing. Commonly targeted in 7 to 14 days after the required access and inputs are confirmed.