Log inStart free

Use case

upTake for indie hackers

You build in public: launch threads, milestone posts, replies, a Show HN. Each one takes an evening, and you have no way to tell which evening paid.

Likes and upvotes are loud. Revenue is quiet, and it usually comes from somewhere else.

What upTake measures for you

  • Visits, signups and payments behind each tagged link, one tag per post.
  • Payments from Stripe, Lemon Squeezy, Gumroad or Polar, matched to the visit that led to them.
  • Posts you log by hand when you could not add a link: upTake estimates their effect from the traffic their channel sent in the following 72 hours, and says it is an estimate.
  • A weekly report that ranks what you did by what it brought.

What it does not measure

  • Likes, upvotes and comments on Indie Hackers or Reddit: these sites give upTake no way to read your posts, so a tagged link does the measuring.
  • Followers gained.

See the workflow before adding your site

Use the weekly report to choose what to repeat, stop or try. The example shows how those decisions are presented, rather than a promise of the same results.

Weekly report · Read what worked, what did not, and the next moves suggested from your numbers.Actual interface · fictional IndiePDF data · captured October 30, 2026Explore this view →

Connectors that help

See every integration, and what upTake reads from each.

What a week can look like Example

Example figures, invented to illustrate. Not a real customer.
PostVisitsSignupsPaying customersRevenue
Indie Hackers launch thread640414$210
Build-in-public post on X380222$96
Milestone screenshot on LinkedIn9600$0

Two posts brought every customer. The third only brought reactions.

These figures are an example, invented to show what the table looks like. They are not a customer's results. Open the live demo to see a full example project.

See which of your posts bring customers

Free plan · No card · 5-minute setup

Create your projectSee a live demo