After one month, the account crossed 100K views. One reel drew 319 comments, and the public run was 100% handled by Claude. That is the honest result. The less flattering part is that I did not preserve per-reel counts or record a time baseline, and the visual system was still too repetitive.

I built Ootto, so I did not want its first serious test to happen on a friendly demo account. I connected my own account, @jayantcreates.ai, and made the product do the work in public.

This is what happened, what I can prove, and what I cannot.

What did I actually hand over?

The assignment was narrower than "grow my Instagram." I gave the system the recurring production work: script the reels, build them, and post them to the connected account.

That distinction matters. A machine can complete a workflow. It cannot make every creative decision good merely because the workflow ran. I still owned the product, the account, and the decision to publish this review.

If you want the nuts and bolts, the Instagram reel autopilot guide shows the pipeline. This post is about the result of using it on ourselves.

If you want to remove the manual production loop rather than rebuild my setup, this is the product I used.

Live product preview

Hyper-power your Instagram growth

Claude made my reel go viral

Ootto

Your 24/7 Instagram Growth Operator

Skip the manual setup

Finds winning content opportunities
Creates on-brand Reels and captions
Replies to comments instantly
Starts personalized DM conversations
Qualifies leads automatically
Runs up to 50 Instagram accounts
Helps book calls and drive sales
Learns and improves with every interaction

One AI. Every Post. Every Comment. More Leads. More Sales.

Made by Ootto

Real reels, rendered by the engine

Six demonstration brands, six finished reels - the same engine that studies a niche and builds the reel actually made these, start to finish. No shot lists, no editors.

What did it actually make?

The current public showcase contains six posted reels. They are not stock examples or speculative mockups. That body of work was real enough to judge, which is more useful than saying the pipeline completed. It also made the weakness obvious: the output could feel like the same clean layout wearing different words. Shipping repeatedly exposed that faster than another round of internal demos would have.

What actually worked?

The clearest result was reach. The account recorded more than 100K views in the month. One reel generated 319 comments. The production run was 100% handled by Claude.

Those figures tell me the system could produce work people stopped for and responded to. They do not tell me that every reel worked, that every comment became a lead, or that the same result will happen on another account.

The creative method behind the reels is in the guide to making Instagram reels with Claude. The thinking behind the hooks and audience fit is in how to reach your peak audience on Instagram.

Which reel performed best?

I cannot show that responsibly from the evidence preserved in this repository.

The public page keeps an account-level monthly view total and the comment result from one reel. The current reel records keep the Instagram link, title, cover, and video, but not a current view count for each post. So I cannot publish a neat winner-versus-loser table without fetching a new snapshot and pretending it was the month-end record.

That is a measurement failure. The next run needs a dated performance snapshot for every reel, not just the strongest account-level outcomes.

Did it actually save me time?

Probably, but I did not measure it, so I will not attach a number to it.

I did not record a manual-production baseline before the run, and I did not log my review time during it. Any claim about hours saved would now be memory dressed up as data. What I can say is that the system handled the scripting, building, and posting loop. What I cannot say is exactly how many hours that removed from my month.

What did not work?

Three things stayed unresolved.

First, repeatability was ahead of visual range. The engine could keep producing, but its default look was too narrow. Future styles are not shown here as if they were shipped work.

Second, the reporting was not rigorous enough. We kept the headline result but not a dated metric for every reel. That limits what I can learn about hooks, topics, and formats after the fact.

Third, this was not a controlled growth experiment. There was no untreated account running beside it, and many things changed while I was building the product. The result proves the system operated my account and produced the published outcome. It does not prove that AI alone caused every view.

So should you let AI run your Instagram?

Let it run the repetitive production loop if you want consistency and you are willing to review the work. Do not hand it your expectations and assume automation makes every idea good.

My conclusion after the month is narrower than a sales claim: an AI system can script, build, and post real reels on a real account, and those reels can earn meaningful reach and conversation. The system still needs better creative range, better per-post measurement, and a human who will admit when the evidence stops.

That is what happened on my account. It is also the standard I want Ootto judged by.

Route A: do it yourself

Start with the exact free skill for this outcome

MIT, no account, no email. Install first, then run the command for your account.

For this outcome: Content Factory

Prompt

git clone --depth 1 https://github.com/Ootto-AI/claude-content-skills.git && bash claude-content-skills/install.sh

Installs the free MIT Content Skills bundle into ~/.claude/skills in one shot.

Prompt

/content-factory - my niche is [niche], model this reel: [reel URL], my handle @..., CTA keyword GUIDE

Runs the full pipeline order for the post: research, hook, script, build, caption, and comment-to-DM lead setup.

Route B: let Ootto run it

Ootto replicates this on autopilot

Open the dashboard, connect once, then let the pipeline handle research, production, and lead replies.

1Sign in

Open the connector dashboard

Go to /content/login, sign in, and open your Ootto content dashboard.

Ootto content dashboard landing screen after sign in

2Connect

Add Ootto to Claude

Use the one-button Add flow so Ootto appears in Claude's Connectors panel.

3Verify

Claude shows the connector

The connector lands in Claude's Connectors settings, confirming Ootto is wired.

Claude Connectors screen showing Ootto connector setup

4Auto onboarding

Board reads back your context

Your audience, pillars, voice, and creator signals are filled from account context.

Dashboard board-ready state with audience, voice, and niche fields

5Research

What is actually working now

Ootto pulls what is moving in your niche and loads ranked examples in board.

Idea Studio showing niche winners and ranked creator reels

6Loop

Reel + comment-to-DM lead loop

Reels move to ready state and comments are answered with public replies plus DM follow-ups.

Unattended reel pipeline with production and lead capture continuing overnight

What Happened When AI Ran My Instagram?