Native Viral Loop
This is a loop-design teardown, not a growth story. WheelSheet is a new, small product with no published growth figures, so we will not pretend it has any. What we can do is examine why the loop baked into its core artifact is unusually well targeted — and where it leaks.
The mechanic in one line: a private seller makes a single page for the car they are selling, then blasts that link into the places where car people gather — local groups, forums, chats, and a QR code taped to the window. One person buys the car. Dozens see the page. And here is the part that makes the whole thing turn: almost everyone shopping for a car is about to have one to sell. Buying and selling are two halves of the same swap, usually days apart.
WheelSheet is deliberately narrow: one page for one car. A private seller decodes the VIN, adds up to ten full-screen photos, an equipment checklist and honest condition disclosures, and gets a single clean URL — plus a printable QR sign for the window. Their phone number stays hidden until a buyer actually acts. There is a free period, then a small flat fee per listing, and no commission on the sale. Setup takes about five minutes and needs no account.
What it pointedly is not is a marketplace. There is no public browsing, no search, no wall of strangers' cars. The seller decides who sees the listing. That decision has large consequences for growth, and we come back to it below.
Here is the part that matters for the loop: a car listing is an artifact whose entire purpose is to be distributed as widely as possible. The seller is not being asked to share anything on WheelSheet's behalf — spreading that link is the whole job. They post it in local Facebook groups, marque forums, WhatsApp threads, and they park the car with a QR code in the window. Every one of those surfaces carries the page, and the page is the product.
For the underlying theory first, start with what a viral loop is and how the viral coefficient (k-factor) is calculated. This page is the applied, WheelSheet-specific version.
The seller's own incentive is maximum distribution. A loop where the user wants to spread the artifact further than you do is a rare thing.
A note on numbers: WheelSheet is early and has published no metrics, so there is no k-factor to quote and we will not invent one. The mechanics, not the metrics, are the point — measure your own loop against your real numbers.
A viral loop needs a trigger — a moment in the natural use of the product that starts the cycle. WheelSheet's trigger is unusually forceful: you cannot sell a car without showing it to as many plausible buyers as you can find. Distribution is not a favor to the tool; it is the entire point of the exercise.
The default is a cramped listing on a marketplace, sandwiched between dealers, with compressed photos and a phone number harvested by resellers within the hour. The seller has no control over presentation and no control over who calls.
Instead, the seller sends a link to a full-screen, VIN-verified page that makes their car look like it belongs in a showroom. The share is selfish: a better-presented car sells faster and for more. Nobody is doing WheelSheet a favor.
Why this trigger beats most of them. In the loops we have studied, the user shares because it is convenient — a Calendly link saves them email tennis, a Loom video saves them a meeting. Here the user's incentive is stronger than convenience: they have thousands of dollars riding on how widely and how well that page circulates. They will push it into more places than any growth team would dare to ask.
Five minutes from a VIN to a finished page. Then the seller does what every private seller does: posts the link in local buy-and-sell groups, in the marque forum, in the classifieds group for their city, in WhatsApp threads with friends who know someone looking. And they print the QR sign for the rear window.
This is the step where the loop gets its power. One creation event produces many distribution events, and the user chooses the surfaces themselves — usually the highest-intent places they know.
This is the step it is easy to model wrongly. It is tempting to think of the recipient as "the buyer" — one person, who wants to buy rather than sell, and therefore has no use for the tool. That would make for a very weak loop.
But a car listing is not sent to one person. It is broadcast to a group, scrolled past by everyone in that group, and seen by everyone who walks past the parked car. One person buys; the rest are the audience. Modelling the reach as one is the difference between concluding this loop is hopeless and seeing why it works.
It is tempting to file these viewers under "buyers, not sellers" and move on. That would be a mistake, because hardly anyone buys a car without having one to get rid of. Replacing a car is a swap: you buy the new one, and within days you are photographing the old one for sale. The purchase is not the end of that person's involvement — it is the trigger for their own listing.
So the viewer is not a bystander who might need the product in five years. They are a seller whose moment arrives in a fortnight. And they encounter WheelSheet at the ideal instant: mid-transaction, actively comparing listings, seeing exactly what a good one looks like right before they have to make their own.
That is remarkable targeting, and it costs nothing. No ad platform sells "people who will list a car within the month" — a car group approximates it for free, and the seller delivers the product there while chasing their own sale.
Those future sellers are not reading a pitch. They are looking at a listing that is conspicuously better than the ones around it — full-screen photos, decoded specifications, a clean layout, no dealer clutter. Next to a blurry marketplace ad, the contrast does the arguing.
This is the same property that powers Typeform: the artifact is good enough to be noticed, so using it doubles as the advertisement. The thought is not "what a nice tool" but "when I sell mine, I want it to look like that."
The buyer completes the purchase, and now the old car is sitting on the drive. They remember the page that stood out while they were shopping, and they make their own. It goes into the same groups, plus the ones only they know. The loop restarts, one community wider.
Note what this does to the pace. It is easy to assume the cycle must be slow because people keep cars for years — but the loop is coupled to the transaction cycle, not the ownership cycle. The original seller will not be back for years, and it does not matter: their buyer is listing within weeks. Measured properly, this loop turns in days, not seasons.
Four properties, and the second one is the one most people miss when they look at a marketplace-adjacent product.
With real money on the line, the seller pushes the link into more groups, forums and chats than any growth team would request. You are not persuading anyone to share — you are supplying an artifact to someone already highly motivated to broadcast it.
Replacing a car means selling a car. The people reading listings are days away from writing one, so the audience converts not because it was targeted but because the purchase itself creates the need. The loop is coupled to the transaction, not to ownership.
Anyone can open the page and browse the car with no account, no signup, nothing gated. The viewer gets the full experience of the product as a reader before they are ever asked to become a seller.
A serious-looking page sitting beside ordinary classified ads makes its own argument. No copy is needed: the comparison happens in the viewer's head, in the feed, next to the alternative.
Put together: a motivated broadcaster, an audience of future users, no barrier to viewing, and an artifact that outshines its neighbors. That is a genuine native loop, and it costs the company nothing per turn.
Every native loop needs a surface where the brand travels with the value. WheelSheet has two, and the second is unlike anything else in this collection.
The page. The link carries a preview card into every chat and group it is pasted into, and the page itself is the product performing its job. Standard, and strong.
The QR code in the car window. This one is genuinely unusual: an offline distribution surface. A car parked on a street with a sign in the window is a billboard that works while the seller sleeps, seen by neighbors, passers-by, and everyone in the supermarket car park. Scanning it costs nothing and requires no account. Every other loop we have studied lives entirely inside a screen; this one puts the artifact on a curb.
A QR code on a car window is a distribution surface with a physical address. Most products never look for one.
The obvious product here would have been a classifieds site: let everyone browse, accumulate demand, take a cut. WheelSheet refuses that, and the refusal is the most consequential strategic choice in the whole design.
A marketplace gets more valuable to sellers as buyers accumulate, and vice versa. WheelSheet banks none of that: every seller must bring their own audience, every time. The platform never becomes the reason buyers show up.
Marketplaces are brutal to launch — useless to sellers until buyers arrive and vice versa. WheelSheet is fully useful to its very first user on day one, because the seller supplies the demand. No chicken and egg.
The trade in one sentence. A marketplace compounds value on the platform; a tool like this compounds reach through its users and nothing else. That is a worse long-term moat and a far better short-term launch — and for a bootstrapped product with no ability to subsidise a cold start, it is close to the only workable choice. Read it as a considered trade rather than a missing feature. For the distinction between loops and network effects, we have a whole piece on it.
All three are native loops with no incentive, where the artifact reaches non-users. What separates WheelSheet is who the audience is and how often the individual user comes back.
| WheelSheet | Typeform | Calendly | |
|---|---|---|---|
| Reach per share | One-to-a-community, plus the street | One-to-a-crowd | One-to-one |
| Who the audience is | People mid-swap — sellers within weeks | Anyone answering a form | A non-user who needs to book |
| Why the user shares | Money depends on it | They need answers | It saves them time |
| Surfaces | Link, preview card, QR in a window | Link and embeds | The booking page |
| Does the user return? | Rarely — one car, then years | Often — forms are routine | Constantly — meetings recur |
| What converts the viewer | The gap vs ordinary listings | The experience itself | The relief of no email tennis |
Read the second-to-last row carefully, because it is where WheelSheet genuinely differs. Typeform and Calendly users come back weekly; a car seller finishes and leaves. The loop still turns — the audience supplies the next user — but the business cannot rely on the same person twice. That shapes everything about pricing and retention. For more patterns, see our viral loop examples and the Native Viral Loop method.
WheelSheet is a working example of the mechanic this teardown describes: one page for one car, built to be broadcast — and good enough that the people who see it remember how it looked when their own turn comes.
Visit WheelSheet →Disclosure: WheelSheet and Native Viral Loop are built by the same team.