howtodistribute
← Back to the index

How Arc got its users

HARDOrganic socialstartupb2cno ads
Visit arc.net

An aesthetic built for the screenshot, relayed heavily on X and TikTok. Distribution worked. Retention did not.

Read from signals. Consistent with what is publicly observable, but nobody confirmed it. Check before you quote it.

Can you run this?
HARD

Reproducible, but it will cost you real money, real months, or a skill you may not have.

Your time
12 months
Your money
Very little
First signal
3 months
Upside
  • Acquisition at near-zero marginal cost once the format is found
  • A content library you can reuse as paid creative
Price of entry
  • A repeatable format, found after 50 to 100 posts
  • A tolerance for failing in public
  • A product that shows itself in 3 seconds

Organic social in 2026

The cheapest channel and the hardest one. Entry cost is zero, the real cost is your consistency.

Everything on this channel →

The play

5 steps, in the order they ran them.

  1. 1

    The format is one gesture on screen, not a feature list. Arc's shareable unit was a single motion: the gradient Spaces sidebar sliding away, or the pinch in Arc Search that folds a page origami-style into a summary. Find the one moment in your product where something visibly changes state in under three seconds. Record it at phone size, no cursor trail, no voiceover, no logo card. That clip is the post. The caption is one plain line under it.

    done whenCan you name the one moment in your product that reads in under three seconds with the sound off? If your best clip needs a voiceover to make sense, you have a demo, not a post.

  2. 2

    Rhythm: Arc's Release Notes went out weekly as a video of the founder talking to a webcam in a room, closer to a vlog than to an ad. Copy the cadence, not the production. Pick one weekday, keep it, and post two lines on what changed plus one clip of it running, shot on the laptop camera you already own. Publish on weeks the change is tiny. People subscribe to the beat, and a skipped week costs more than a boring one.

    done whenLook at your last four weeks. Did a public update go out on a fixed day each time, or only when the change felt big enough? Silent weeks are the failure mode, not small ones.

  3. 3

    Give the artifact a URL that escapes the app. Arc Easels let you drag a live tab onto a canvas, then hand out a public link that opens in any browser while editing stays inside Arc on macOS. Build the cheap version: whatever a user makes in your product gets a public page, readable with no install and no account, carrying your name. The user writes the post for free, the link does the selling.

    done whenOpen something a user made in your product from a private window with no account. If it 404s, asks for a signup, or needs your app installed, it cannot travel.

  4. 4

    Let people vandalize it. Arc shipped Boosts: restyle any site's colors and fonts, Zap out the elements you hate, then browse the community Boosts Gallery and install someone else's in one click. Ship the smallest version of that, one surface users can make theirs and screenshot. Then repost their versions from your own account. With no audience of your own, other people's feeds are the only feed you have.

    done whenCount the screenshots of your product posted in the last month by people who do not work for you. If the answer is zero, nothing in it is worth showing off yet.

  5. 5

    Turn replies into the page. arc.net runs a user quote as its headline and stacks testimonial cards credited to X handles like @beebomco and @markfishman_XYZ. Do the same: screenshot every unprompted post about you, ask the author, put it on your homepage, then send them the live link. Most repost it. One compliment becomes two posts, and your landing page stops sounding like you wrote it.

    done whenSearch your product name on X and TikTok. If there are posts you have never replied to or reused on your own site, your only free distribution is sitting there unused.

The product itself

read from arc.net, live

Arc is the Chrome replacement I've been waiting for.

12 public pages

Run this against your own product

In your chat

Carries the play above, and is written to tell you no when this channel is out of reach for you.

In your editor

The same twelve channels as an agent skill. It reads your repository and eliminates what you cannot run. Open source, MIT.

curl -o ~/.claude/skills/howtodistribute/SKILL.md https://howtodistribute.com/skill.md

Strong adoption, then development wound down

They ran the same play

Want this verdict on your product?

Describe it. You get back the channel I would run in your place, the 30-day plan, and the number at which you stop.