SuperbulletAI ↗: a Roblox AI game-creation platform
- MRR
- $11,896 Verified 2026-10-18
- Total revenue
- $116,657
- Active subscriptions
- 601
Verified by TrustMRR
In one line: An AI platform for Roblox developers to build games, with a creator marketplace, sold as a subscription.
- Founder
- FroredionX ↗
Timeline
- Founded date listed on TrustMRR
- First monthly revenue on TrustMRR: $5,088 (TrustMRR)
- Revenue that month: $12,083 (TrustMRR)
- Revenue that month: $15,408 (TrustMRR)
- Latest full month of revenue: $18,044 (TrustMRR)
Sources: TrustMRR: Superbullet, LLC.
TrustMRR figures are monthly revenue as shown on 2026-10-23 (read-only sync from the payment provider).
Compared with similar products
No public information yet
Moves SuperbulletAI made
No public information yet
How to copy it
Gather reusable modules from your team's shipped projects and document interfaces and dependencies
From projects your team has shipped, pick the modules rewritten most often, export each as a standalone file, and write one page per module: where it lives, its public interface and its dependencies. What the founder did: the product is built on the team's own proven work (superbullet.ai).Expand ▾Collapse ▴
From projects your team has shipped, pick the modules rewritten most often, export each as a standalone file, and write one page per module: where it lives, its public interface and its dependencies. What the founder did: the product is built on the team's own proven work (superbullet.ai ↗).
- A module library where each module imports and runs in an empty project on its own, each with a one-page interface and dependency doc.
- A developer who never worked on the original project wires one module into an empty project from the doc alone.
I'm building an AI tool for developers in <your niche>, based on reusable modules from my team's shipped projects. Below are one module's code and the project structure. Write a one-page doc: 1) where it belongs in a project; 2) its public interface (event names, function signatures, parameters and returns); 3) the other modules it depends on; 4) the names and config usually changed in a new project. Base it only on my code and mark anything unclear "to confirm". Code: <paste>
Build the product: understand the user's current project and wire a library module in from one sentence
Have the product read the current project's structure and naming. The user types a one-line request, the product picks a module from the step 1 library, uses an LLM to rename it to the project's conventions and connect it to existing interfaces, then puts it in place so the user can run it immediately. Build only on library modules; don't let the model write logic from scratch. What the founder did: the homepage says its AI knows your project and codebase and will code for you (superbullet.ai).Expand ▾Collapse ▴
Have the product read the current project's structure and naming. The user types a one-line request, the product picks a module from the step 1 library, uses an LLM to rename it to the project's conventions and connect it to existing interfaces, then puts it in place so the user can run it immediately. Build only on library modules; don't let the model write logic from scratch. What the founder did: the homepage says its AI knows your project and codebase and will code for you (superbullet.ai ↗).
- In a real project, a one-line request wires a module in that runs without errors and matches the project's naming.
- A developer outside the team completes a request with it and the result runs without hand edits.
Write the core logic of a developer tool for developers in <your niche>: 1) read the current project's folder structure and existing script names; 2) take a one-line request and pick the best module from the library docs below, with reasons; 3) call an LLM API to adapt the module to the project's naming and connect it to existing interfaces, changing only names and wiring, no new logic; 4) output where it goes and a change list. Read secrets from environment variables; follow official docs and flag anything uncertain. Library docs: <paste>
Step 2: only renames to the project's naming and wires up existing interfaces, never writing logic from scratch.
Use it on your own team first: build a few modules in a live project and record time saved
Have your team's developers use the step 2 product to build a few modules in a live project, recording two times per module: how long with the product until it runs, and how long a similar module took by hand before (note whether logged or estimated). Log every error and hand edit and fix them until they stop recurring. What the founder did: he had his own team's developers use it first before pushing it to others (X post by @froredion).Expand ▾Collapse ▴
Have your team's developers use the step 2 product to build a few modules in a live project, recording two times per module: how long with the product until it runs, and how long a similar module took by hand before (note whether logged or estimated). Log every error and hand edit and fix them until they stop recurring. What the founder did: he had his own team's developers use it first before pushing it to others (X post by @froredion ↗).
- A table with one row per module showing both times and the error log; every issue in it is fixed.
- Team developers reach for it on the next module instead of writing it by hand.
Below are my team's records from building a few modules in a live project with our own AI developer tool: time with the tool, time by hand before (logged or estimated), errors and hand edits. Please: 1) group errors by cause and give each group a concrete fix direction; 2) compute time saved per module, listing estimates separately; 3) pick the best module for a public demo and say why; 4) use only my data. Records: <paste>
Record a one-take screen demo from one-line request to running result, and post it where your target users gather
Record a short screen capture: type one sentence, the product wires a module into the project, and it runs, in one take without cutting the waits. Post it where your target users gather with one line on how long this module used to take by hand (from step 3). What the founder did: his launch post introduced the product with a demo video (X post by @froredion), followed later by a YouTube video (YouTube video).Expand ▾Collapse ▴
Record a short screen capture: type one sentence, the product wires a module into the project, and it runs, in one take without cutting the waits. Post it where your target users gather with one line on how long this module used to take by hand (from step 3). What the founder did: his launch post introduced the product with a demo video (X post by @froredion ↗), followed later by a YouTube video (YouTube video ↗).
- The video is posted, one take from input to running; the time in the caption matches the step 3 table.
- The video brings signups from strangers.
I built an AI developer tool: <your target users> type a one-line request and it wires a proven module from my team's shipped work into their project using its naming. I'll record a one-take short screen demo with <module picked in step 3>, which took <time> by hand. Write: 1) a shot list: what's on screen in each shot and the exact sentence I type; 2) a short English caption whose first line is the by-hand time; 3) one English call to action with <signup link>. Use only my numbers.
Step 4: post the demo video and a few versions with different opening lines; the founder's launch post was a demo video on X.
Step 4: upload the same demo with the trial link in the description; the founder linked his own YouTube video in an X post on 2025-11-26.
Offer a free tier plus two Stripe payment links: a monthly subscription and a one-time top-up
Give the free tier a small monthly allowance and create two links on Stripe's Payment Links page: a monthly subscription and a one-time top-up, crediting the account when payment succeeds. You set the prices. What the founder did: the pricing page has a free tier, a monthly plan and usage top-ups (superbullet.ai pricing), and the terms name Tebex as merchant of record (superbullet.ai terms of service).Expand ▾Collapse ▴
Give the free tier a small monthly allowance and create two links on Stripe's Payment Links page: a monthly subscription and a one-time top-up, crediting the account when payment succeeds. You set the prices. What the founder did: the pricing page has a free tier, a monthly plan and usage top-ups (superbullet.ai pricing ↗), and the terms name Tebex as merchant of record (superbullet.ai terms of service ↗).
- Both payment links open; one test payment on each credits the account accordingly.
- One test subscription and one test top-up both credit the account.
My AI developer tool has three tiers: free with <allowance>/month; subscription at $<price>/month with <allowance>/month; top-ups from $<price> at $<unit price> per <unit>. Write: 1) English product names and one-line descriptions for the two Stripe links, stating allowances; 2) under 80 words for the pricing page explaining the tiers and what happens when the allowance runs out; 3) backend pseudocode crediting the account on Stripe webhook events, with event names per the official docs. Use only my numbers.
Step 5: on the Payment Links page, create a $20/month Pro subscription link and a $20 one-time top-up link; TrustMRR shows SuperbulletAI's revenue verified through the Stripe API.
Step 5: alternative payment provider; the superbullet.ai Terms of Service name Tebex as merchant of record for its checkout. How much goes through Tebex versus Stripe is not disclosed.
Get your first revenue: the first subscription lands and the user spends their first allowance
Confirm the first payment in your Stripe payments list, then check backend logs for whether this user sent requests after paying, how much allowance they used and whether the wired-in modules run. If they paid but didn't get going, DM them the same day asking where they got stuck. What the founder did: his Stripe-verified revenue is public on TrustMRR (TrustMRR).Expand ▾Collapse ▴
Confirm the first payment in your Stripe payments list, then check backend logs for whether this user sent requests after paying, how much allowance they used and whether the wired-in modules run. If they paid but didn't get going, DM them the same day asking where they got stuck. What the founder did: his Stripe-verified revenue is public on TrustMRR (TrustMRR ↗).
- Stripe shows the first real subscription payment (not test mode) and logs show the user spending allowance after paying.
- The user pays again in the second billing cycle.
My AI developer tool just got its first paying user. Below is their usage log after paying: requests sent, allowance used, modules wired in and run results. Please: 1) judge whether they actually got going; 2) if any request failed, write an English DM under 80 words asking where they got stuck, with a one-line request that would solve it; 3) base it only on the log. Log: <paste>
Step 6: check the first real $20 Pro subscription payment in the payments list; TrustMRR shows SuperbulletAI's revenue verified through the Stripe API.
Sources
Next case
One-click AI YouTube documentary generator, founded July 2026
Business model: Three subscription tiers; prices in the comparison table.
Data source: TrustMRR, checked 2026-10-26