What stayed with the owner
Account access, passwords, store publishing, and public identity stayed under human control. The agent arrived at each approval point with the work and evidence ready.
Live build log · results still being measured
One growth goal became a store, search, and distribution system.
We ran this project with VibeGrow's growth workflow. The agent clarified each product's job, prepared store releases, built search pages, drafted distribution, and kept review monitoring active. A person approved the store submissions and public posts.
Work shipped
The output is public and inspectable.
The workflow produced pages, releases, posts, and monitoring. It also preserved one clear job for each extension.
Separated the products
Chat Downloader owns one-conversation export. Instagrow owns publishing, scheduling, media downloads, story music, and hashtags.
Open the extension chooserBuilt the search paths
Each extension now has a focused product page, a problem-specific guide, comparison copy, and measured internal links.
Open the growth guidesPrepared the releases
The next store versions have clearer names and tighter scope. Chat v2.4.0 also has a private release draft waiting for store approval.
See the public discovery updateKept the job running
A scheduled monitor checks both public listings. It will update the site and release state when Google publishes the reviewed versions.
View the current evidenceEvidence ledger
Follow the work, source by source.
Instagrow v1.0.7 is public. Google is still reviewing Chat v2.4.0; this page will update when it becomes public.
What the workflow removed
Repeated research, disconnected drafts, manual status checks, and lost context moved into one running growth job. The owner reviewed decisions instead of rebuilding the plan every morning.
Run the same process
Give VibeGrow one product and one growth goal.
Start with a bounded job. Review the sources, files, and next actions. Keep publishing behind your approval.