VizTunr ↗: an AI try-on tool for tuning-shop customers to see wheels and colors on their own car, sold by cold email only
- MRR
- $791 Verified 2026-10-21
- Total revenue
- $2,019
- Active subscriptions
- 9
Verified by TrustMRR
In one line: An AI tool that lets tuning shop customers preview wheels and paint on their own car, with one subscription per shop tiered by image volume, plus a pay-per-image personal option.
- Founder
- Piotr ObidowskiX ↗ · Solo
Timeline
- Founded date listed on TrustMRR
- First customer; revenue that month: $219 (TrustMRR)
- Revenue that month: $357 (TrustMRR)
- Founder reports 5 customers, zero cancellations, all from cold email (self-reported)
Compared with similar products
Sources: TrustMRR: Viztunr.com; TrustMRR: Visualizee.ai; X post by @pobidowski.
TrustMRR figures are monthly revenue as shown on 2026-10-23 (read-only sync from the payment provider).
Moves VizTunr made
No public information yet
How to copy it
Build a try-on page: upload your own photo, pick a product, get an image with it installed
Start with one product type (high price, where customers hesitate most before buying). The page has three steps: upload a photo, pick one of a few product images, generate, then show original and result side by side. No signup or payments yet. What the founder did: the product lets shops show customers their own item with a new product before they buy (X post by @pobidowski), built on Next.js, Supabase, Vercel and Stripe (TrustMRR).Expand ▾Collapse ▴
Start with one product type (high price, where customers hesitate most before buying). The page has three steps: upload a photo, pick one of a few product images, generate, then show original and result side by side. No signup or payments yet. What the founder did: the product lets shops show customers their own item with a new product before they buy (X post by @pobidowski ↗), built on Next.js, Supabase, Vercel and Stripe (TrustMRR ↗).
- A working page: upload a photo, pick a product, get a side-by-side result.
- A shop owner sees a result and would show it to their customers.
Build a try-on page for <your target users>: 1) upload a photo; 2) pick one of 5 product images; 3) call an image-editing API to place the product on the photo, keeping everything else unchanged; 4) show original and result side by side. Stack: Next.js + Supabase, secrets in environment variables, API parameters per official docs.
Used in step 1 to build the try-on page; Next.js is in the VizTunr stack listed on TrustMRR.
Used in step 1 to store each shop's wheel images and render history; Supabase is in the stack listed on TrustMRR.
Used in step 1 to put the wheel on the customer's car; the founder uses his own Visualizee engine, so this is our recommended substitute, not tested.
Use Google Maps to list target shops with online product pages and note one featured product each
Search Google Maps city by city for your target shops and keep only those with a website showing clear product images. Record name, website, public contact email, and one featured product's name and image link. What the founder did: every customer came from cold email, with no ads, SEO or launch (X post by @pobidowski, X post by @pobidowski).Expand ▾Collapse ▴
Search Google Maps city by city for your target shops and keep only those with a website showing clear product images. Record name, website, public contact email, and one featured product's name and image link. What the founder did: every customer came from cold email, with no ads, SEO or launch (X post by @pobidowski ↗, X post by @pobidowski ↗).
- A shop table with name, website, public contact email, and one featured product's name and image link.
- Every shop in the table has a product image you can generate with.
Below are <your target users> I found on Google Maps: names and websites. Help me design a tracking sheet: 1) list the fields (name, website, public contact email, featured product name, product image link, city); 2) give me a per-shop checklist: clear product images on the site, contact email public or not; 3) don't guess emails and leave unpublished ones blank. List: <paste>
Used in step 2 to find tuning shops city by city; the founder does not say where his list came from, so this is our recommendation.
Use Claude Code to generate a dedicated page per shop: their product on a few sample images, a try link, price and a claim button
With Claude Code, add a dynamic route to the step 1 project that reads each shop's product from the step 2 table and places it on a few fixed sample images. The page shows those images, a try link with the product preselected, the price and a claim button that generates a try-on link branded with the shop's name and logo. What the founder did: he builds a dedicated page for every prospect so the product is set up before they reply (X post by @pobidowski), and setup is just a link with no plugin (viztunr.com).Expand ▾Collapse ▴
With Claude Code, add a dynamic route to the step 1 project that reads each shop's product from the step 2 table and places it on a few fixed sample images. The page shows those images, a try link with the product preselected, the price and a claim button that generates a try-on link branded with the shop's name and logo. What the founder did: he builds a dedicated page for every prospect so the product is set up before they reply (X post by @pobidowski ↗), and setup is just a link with no plugin (viztunr.com ↗).
- Every shop in the table has a working page with their product results, a try link, price and a claim button.
- Someone who doesn't know you looks at a shop's page and understands what the shop can do with it.
Add a dynamic route /for/<shop> to my Next.js project: 1) read the shop's name, logo and one product image from the table; 2) use the existing image function to place the product on 3 fixed sample images and cache the results; 3) show the 3 images, a try link with the product preselected, the price and a "claim" button; 4) on claim, mark the shop claimed and generate a try-on link branded with its name and logo.
Used in step 3 to add the per-shop dynamic route and the batch render script; the founder built Visualizee with Cursor and Claude Code but has not said what he used for VizTunr, so this is our recommendation.
Used in step 3 to cache each shop's example renders.
Send cold emails from Gmail: two or three sentences plus the shop's dedicated page link, then follow up by reply type
Send one at a time from your own Gmail, naming the shop and product in each, with no mass mailing and no attachments. Keep the body to two or three sentences: what you made, the link, and "reply no and I won't follow up". Sort replies into interested, already have a solution, and do not contact, and stop immediately for the last. Check the recipient country's rules on commercial email first. What the founder did: cold email worked because each email was just a link to something already built for them (X post by @pobidowski).Expand ▾Collapse ▴
Send one at a time from your own Gmail, naming the shop and product in each, with no mass mailing and no attachments. Keep the body to two or three sentences: what you made, the link, and "reply no and I won't follow up". Sort replies into interested, already have a solution, and do not contact, and stop immediately for the last. Check the recipient country's rules on commercial email first. What the founder did: cold email worked because each email was just a link to something already built for them (X post by @pobidowski ↗).
- A batch of sent emails and a reply table with three columns.
- A shop clicks the claim button.
Write a cold email to the shop below, in English, at most 3 sentences: 1) mention their shop name and <product>; 2) say I already placed this product on a few sample images and include <dedicated page link>; 3) say a "no" reply means I won't follow up; 4) no hype, no attachments. Also write a follow-up for "interested" replies. Shop: <paste>
Used in step 4 to send cold emails one by one from your own mailbox; the founder does not say what he sends with, so this is our recommendation.
After a claim, charge a monthly subscription priced by image volume with Stripe and get the first shop's payment
After "claim", connect Stripe Checkout with two or three tiers by images per month at prices you set. On payment, lift the trial limit on the shop's try-on link and give them a button snippet to paste on their product pages. What the founder did: each shop has one subscription tiered by image volume (viztunr.com pricing), with payments through Stripe (TrustMRR).Expand ▾Collapse ▴
After "claim", connect Stripe Checkout with two or three tiers by images per month at prices you set. On payment, lift the trial limit on the shop's try-on link and give them a button snippet to paste on their product pages. What the founder did: each shop has one subscription tiered by image volume (viztunr.com pricing ↗), with payments through Stripe (TrustMRR ↗).
- Claiming leads to Stripe Checkout; a test payment lifts the trial limit and returns the snippet; Stripe shows the first real payment.
- Stripe shows the first shop's real payment and they put the button on their product page.
My try-on tool charges shops monthly after they claim, in tiers: <tier names, prices, images per month>. Write: 1) English checkout copy: tier differences, what happens to unused credits (my rule: <rule>), cancel anytime; 2) backend pseudocode that lifts the trial limit and generates an embed button snippet on Stripe webhook events (event names per official docs); 3) use only my numbers.
Used in step 5 to charge monthly subscriptions priced by render volume; TrustMRR's data comes from the founder's Stripe.
Sources
- TrustMRR
- TrustMRR public Markdown page (sync time, monthly revenue, subscriptions, channels)
- X: "1,000 cold emails. 5 paying customers. $792 MRR." full cold-email playbook (2026-10-15, self-reported)
- X: "VizTunr just hit $792 MRR" (2026-10-14, self-reported)
- X: VizTunr made $634 last month (2026-10-15, self-reported)
- Website viztunr.com ("Powered by Visualizee.ai", setup)
- Pricing page viztunr.com/pricing
- trustmrr.com
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
