Get Your First 100 Users With a Curiosity Artifact
Stop asking strangers to sign up before they understand value; give them one surprising, shareable output that makes the product worth remembering.
Most first-user attempts die in the same place: the signup form. You have built something that feels useful, strange, or quietly necessary, but the first thing a stranger sees is a request. Create an account. Connect a tool. Invite a teammate. Try the beta. The product is still a rumor, and you are asking for a commitment. That is the wrong order. The first hundred users are usually won before any commitment, by giving a stranger one experience that makes the product feel real.
The move is not a growth tactic. It is a curiosity loop: a small, zero-friction experience that returns a personal, surprising output, then lets the person share it without becoming a user. The artifact does the selling. The follow-up does the rest.
What the artifact looks like
A good artifact is not a demo. A demo explains. An artifact performs. It should take one input, or no input at all, and return something that feels like it was made for that person. It should be a shareable output: easy to understand in a few seconds, easy to screenshot, and easy to send to a friend with a one-line caption. If the value only appears after a tour, a tutorial, or a sales call, you have not built the artifact yet.
Any Human Ever describes its core experience as drawing a random year, place, and life from real data. The page can carry a big idea: over 100 billion people have ever lived. The explanation is the hook: a random birth is more likely to be near the present because population growth was exponential. The details make it feel handmade: the site says its AI images were generated locally on the author's laptop rather than in data centers, and brighter clusters represented larger populations. The value is visible, strange, and shareable before the product asks for anything.
That is the shape you want. The output should be personal enough to feel selected, surprising enough to be remembered, and simple enough to be retold. A random result is not enough. A result with a reason is better. A result with a reason and a visual is even better. The artifact should make the visitor think, 'I need to show someone this,' not 'I should maybe try this later.'
Build the loop in four moves
- Build one zero-friction experience. Pick the smallest slice of your product that can return a personal output. If your idea is data-driven, make the data do the talking. If it is utility, make the utility produce a result the user can keep. If it is novelty, make the novelty generate a reaction. The experience should work without an account, without a password, without a phone number, and without a promise.
- Make the output shareable without an account. The output should be the share. A clean image, a short sentence, a result card, a link that renders well in a chat window. Do not make the user explain the product. Let the artifact explain itself. If someone can send it to a friend and the friend can understand it in one glance, you have a loop.
- Add one optional email capture after the output. Ask after the value, not before. The request should be small and specific: get the next result, get the explanation, get the version that is better for your case. Do not ask for a newsletter, a profile, or a commitment. Ask for one follow-up. The email is not the product. The email is the hand you extend after the stranger has already felt the pull.
- Manually follow up with the first hundred people who engage. This is the unscalable part, and it is the part that matters. Read the replies. Ask what surprised them. Send the next thing by hand. Fix the confusing step. Make the output better because of what they said. The first hundred are not a list. They are a room you can walk around.
The loop is simple, but the discipline is not. You will be tempted to add analytics, funnels, paid tests, and automation before you have enough signal. Resist. The first users are not a market. They are a set of conversations. If you cannot explain why someone shared the artifact, you do not understand the product yet. If you cannot follow up personally, you are too early to scale.
Keep the hand-holding visible
Small products fail when they try to look like platforms before they have users. The first hundred do not need a polished onboarding sequence. They need a person who notices when they arrive, answers when they are confused, and remembers what they shared. Manual outreach is not a failure mode. It is the product. Your product is the artifact plus your attention. The artifact brings them in. Your attention turns a stranger into someone who comes back.
Do not wait for the product to be ready. The product is ready when a stranger can experience the core value without being asked for anything. Then the work becomes human: watch what they share, ask why it mattered, and make the next version for the people who actually showed up. That is how a small idea stops feeling too small to market. It becomes something people want to pass along.
