Genrupt: From AI MVP to Paid Seller Operations
Helped Genrupt move from a working AI demo to dependable paid operations for its first 200 seller customers.
Project overview
Genrupt: From AI MVP to Paid Seller Operations overview
A short overview of the problem, solution, and result.
Starting Point
Genrupt had AI image and video generation working, but the product was not ready for serious customer usage. Paying seller teams needed subscriptions, organization billing, safer credit accounting, and long-running jobs they could trust.What Shipped
Subscriptions, organization billing, and credit-ledger accounting for paid seller teamsWhy It Mattered
Genrupt became commercially operable, with subscriptions, organization billing, credit accounting, automatic payment updates, and safer cost controls for paying seller teams.A working AI demo needed dependable paid operations
Genrupt had a working AI creative product for Amazon sellers, but a working demo was not yet a dependable paid operation.
I worked on the commercial and operational systems required to support the first 200 paying customers: team accounts, billing, cost controls, reliable long-running workflows, and controlled agent access.
Paid seller teams needed more than generation
Genrupt was expanding from AI image and video generation into Amazon seller workflows: market analysis, review scraping, variations, listing builder, A+ content, and experimentation.
That expansion made the product more valuable, but it also exposed the limits of the MVP. Paid seller teams needed subscriptions, organization billing, credit accounting, reliable background work, and clearer recovery paths when long-running AI jobs failed.
As the product grew, app screens became only one way to use it. External agents and internal chat also needed a safe way to run approved operations.
I built the commercial foundation before expanding workflows
Move from demo-stage generation to seller-team operations.
I helped add the foundations that make a product billable: organizations, subscriptions, credits, safer job handling, and clear ownership for each workflow.
Give agents a controlled operating surface.
Instead of exposing the whole product, the agent surface offered a small set of allowed capabilities with clear status and recovery paths.
The product could support paid seller teams
The product moved beyond a demo-stage generator into a more operable seller workflow platform with project, account, billing, and workflow surfaces for paid seller teams.
I helped ship subscriptions, organization billing, credits, and automatic payment updates, then connected that foundation to long-running AI and Amazon seller workflows.
I made paid workflows easier to operate
Turned billing and credits into a commercial foundation.
I helped add subscriptions, organization billing, credit accounting, automatic payment updates, and safer cost controls so paid seller teams could use the product without the business relying on manual cleanup.
Made long-running AI workflows easier to trust.
Image, video, storyboard, and seller-workflow jobs needed to survive retries and show clear progress. Recoverable operations and safer retries made those flows more dependable.
Opened approved workflows to external agents.
Paid users could connect agents and run selected seller workflows through a small list of approved actions instead of exposing the entire product.
The commercial systems supported the next stage
Genrupt became ready for paid seller teams because billing, reliable AI workflows, and agent access shared one product foundation. That foundation helped support the first 200 paying customers.
Seller teams could become paying accounts.
Subscriptions, organization billing, credit accounting, and automatic payment updates gave the product a cleaner path to paid usage.
Agents could run approved workflows safely.
A permissioned tool catalog let agents use product capabilities without exposing the product's internal routes or job mechanics.
Long-running AI work became easier to trust.
Clear status, recoverable operations, and safer retries reduced the need to manually babysit generation and seller workflows.
New seller workflows became easier to add.
Clearer ownership across the product reduced the fragility that had built up around earlier demo-stage features.
Seller workflows connect billing, agents, and production
The clearest result is the shift from isolated generation into seller-facing workflows with the surrounding systems needed for paid usage.
Implementation details
Have something that needs building?
I build customer-facing features, internal tools, and integrations for B2B SaaS teams on contract.