UserClimb

How to market a SaaS or developer tool on TikTok and Instagram

By Thomas, founder of UserClimbUpdated 14 min read

The short answer

Show it working and show the real number; the second it sounds like an ad, a builder is gone. Talk to the viewer's situation, not a demographic. Lead with the builder's pain, named, opinions and 'stop doing X' and demos and changelog clips, and keep most posts about the viewer's problem rather than your app. Bring the app in as the way they get the result, usually late in the video or in the caption, and ask for the download in only about 20% of posts.

Who you're actually talking to

A builder or operator who has been sold to all day. A solo developer whose side project has users but no revenue, a vibe coder who shipped their first app last month, a two-person team selling to agencies, or an agency owner trying to automate outreach. They watch between tasks, often on X or YouTube on a desktop, and they can smell marketing in the first second.

What they want

  • show me it working, not a slide about it
  • what's your stack and what does it cost a month
  • how you got your first 100 users without ads
  • a repeatable way to get customers that isn't cold outreach all day
  • real numbers I can compare mine to
  • to ship faster and stop fiddling with tooling
  • one honest take from someone a step ahead, not a guru

What frustrates them before they find an app like yours

  • shipped and nobody came
  • every tool is per-seat, bloated and wants a sales call
  • marketing feels like lying and I'd rather code
  • cold emails land in spam and nobody replies
  • I have visitors but no signups and no idea why
  • another AI wrapper with a landing page and no product
  • my only audience is other founders who never buy
  • paid SEO and ads burned money and brought nothing

Words they actually use

Use their words in your hooks and captions, not yours: "just ship it", "build in public", "what's the stack?", "is this open source?", "can I self-host it?", "link?", "is this an ad?", "it's a wrapper", "any developer could have done this", "please make another one open-sourced", "I'd pay for this", "vibe coded it in a weekend", "MRR", "first product of the day", "aha moment".

What makes them stop scrolling

The one rule for SaaS and developer tools: show it working and show the real number; the second it sounds like an ad, a builder is gone.

They stop for

  • a real UI doing one thing in the first second, with the cursor visible
  • a number that looks real: odd, specific, with a date, not a round 10k
  • a founder saying something they half disagree with
  • 'here's my exact...' anything: stack, workflow, prompt, pricing
  • a pain they had this week, said in the words they'd use
  • a before and after of a workflow they actually do
  • 'I shipped this today' with the thing on screen

They scroll past

  • a logo intro or anything that opens with 'introducing'
  • an AI narrator reading '5 tools every founder needs' over stock footage
  • 'game-changing', 'seamless', 'enterprise-grade', '10x' with no demo
  • round numbers, '7 figures' and 'passive income'
  • a face reading a script in a corporate room
  • a full-screen dashboard they cannot read on a phone
  • 'comment X for the link' and 'limited spots'

What to post: the content mix

Split your posts roughly like this: the builder's pain, named (25%), opinions and 'stop doing X' (20%), demos and changelog clips (20%), build in public with real numbers (20%), exact stack and workflow (15%). Each kind of post has a different job, so you're not asking for the download in every video.

The builder's pain, named (about 25% of posts)

Names one problem a founder, developer or operator has this week (nobody came after launch, emails in spam, visitors but no signups, an hour lost to a manual job) and gives a real fix. Worth watching if the app never existed. Brings in new people and marks the account as someone who has been there.

  • Hook: You shipped. Nobody came. Here's the bit nobody told you.
  • Hook: Your cold emails aren't bad. They're landing in the wrong folder.
  • Hook: [fill-in] visitors, zero signups. The leak is never where you think.
  • Hook: Every founder loses [fill-in: hours] a week to [task]. Here's how I got mine back.

Example: "You shipped. Nobody came.". Camera. 0 to 2s: the hook, words on screen. 2 to 8s: 'Launch day I posted everywhere. [fill-in] visitors. [fill-in] signups.' Two-number counter. 8 to 25s: three cards, one per mistake: the headline said what it was, not who it was for; no demo above the fold; no reason to come back on day two. 25 to 35s: 'Fix the headline first. Then a six-second demo above the fold.' Soft close. It ends on: i post what I change and what happens next; follow if you're pre-launch.

Opinions and 'stop doing X' (about 20% of posts)

A strong, defensible opinion about how to build, price, launch or market software, backed by something the founder did. Gets shares and arguments, which is how this audience spreads things, and gives the founder a point of view people follow.

  • Hook: Stop building features. Nobody asked for the last three.
  • Hook: Your startup doesn't need a Discord. It needs ten paying users.
  • Hook: Unpopular opinion: your free plan is why you're broke.
  • Hook: I deleted [fill-in: feature] and revenue went up.

Example: "Stop building features". Camera. 0 to 3s: hook. 3 to 10s: 'I shipped [fill-in] features in [fill-in] months. Users asked for two.' Bar graphic: built vs asked. 10 to 25s: what moved the number instead, one card each: the headline, the onboarding, replying to every comment. 25 to 32s: the caveat: 'the exception is the feature your top complaint is about; build that tomorrow.' It ends on: disagree in the comments; I read all of them.

Demos and changelog clips (about 20% of posts)

The product doing one thing in 6 to 15 seconds, or three things shipped this week in 20. The brand account's main engine and the only pillar where the app is the subject. Each clip opens on the pain the feature removes, then shows it, then asks.

  • Hook: Watch [task] take six seconds.
  • Hook: This used to take me [fill-in: time]. Now:
  • Hook: Shipped today: [feature]. Here's why.
  • Hook: [Pain] was the top complaint in our reviews. Fixed.

Example: "Watch it take six seconds". Screen. 0 to 1s: caption 'Watch [task] take six seconds', the UI already up, cursor at the start. 1 to 7s: one action: paste, click, result. Zoom on the click, out on the result. 7 to 9s: result held, caption becomes the ask. Under ten seconds. Same clip goes on X as native video, link in the first reply. It ends on: free to try at [app].com. Link in bio.

Build in public with real numbers (about 20% of posts)

The founder's own numbers and decisions: signups, revenue, churn, the launch that flopped, the price change, and what moved them. Real numbers only, left as [fill-in]. People follow the person who shows the work, then find the tool.

  • Hook: [fill-in] users in [fill-in] weeks. Here's the only thing that worked.
  • Hook: I built [app] in a weekend. [fill-in] months later, here's the real number.
  • Hook: Month [fill-in] of building [app]: [fill-in] revenue, and one mistake.
  • Hook: I lost [fill-in] users in a week. This is why.

Example: "I built it in a weekend. Here's the real number.". Camera. 0 to 3s: hook. 3 to 10s: 'Weekend build, [fill-in] months ago. Today: [fill-in] users, [fill-in] paying.' Counter with the date. 10 to 28s: three cards for what got it there: replying to people with the problem, the headline rewrite, the six-second demo clip. 28 to 38s: 'what didn't work: [fill-in: the launch, the paid SEO].' Soft close. It ends on: i post the number every month; follow for the next one.

Exact stack and workflow (about 15% of posts)

How the founder actually works: the tools, the order, the shortcuts, with timings and monthly costs. Builders want to copy a working setup. The app is one piece of the workflow, the most native placement this audience accepts.

  • Hook: Here's my exact stack for [app], and what it costs a month.
  • Hook: How I [task] in [fill-in] minutes every morning.
  • Hook: The [fill-in]-tool setup that replaced my [agency / spreadsheet / second hire].
  • Hook: I run [app] alone. This is the whole system.

Example: "My exact stack and what it costs". Screen. 0 to 3s: caption 'My exact stack for [app]: [fill-in] a month', the browser tabs visible. 3 to 30s: click through each tab, two to three seconds each, the tool and its one job top-left, the real cost adding up bottom-right. The founder's own app is one tab, same weight. 30 to 36s: the total, and the one thing I'd cut. It ends on: copy the stack; swap my app for whatever you use. Full list in the caption.

Hooks that work, and hooks that flop

The first second decides everything. These are the patterns that hold this audience, and the ones that lose them.

Works

  • Stop [doing X] in your startup.: builders lean contrarian; a direct instruction they half disagree with gets the argument, and arguments get reach.
  • I built [thing] in [time] and [real result].: time plus outcome is the native currency of this audience, as long as the number is the founder's own.
  • Here's my exact [stack / workflow / prompt / pricing].: 'Exact' promises something to copy; vague advice gets scrolled, a working setup gets saved.
  • You shipped. Nobody came.: the most shared pain in the niche, said in four words; everyone has had that launch day.
  • Watch [task] take six seconds.: a demo promise with a time limit; the viewer stays to check you kept it.
  • [fill-in] users and [one surprising detail].: a specific number with a twist reads as real; a round number with no twist reads as a pitch.
  • I was wrong about [X].: admitting a mistake reads as honesty in a feed full of wins, and the lesson gets saved.
  • The top complaint in our reviews. Fixed.: shows you read the complaints and shipped; the hardest trust signal to fake.
  • What [big company] does that you can copy for free.: borrowed authority plus a free takeaway; the app appears as how you copied it.

Flops

  • Introducing [feature] / Excited to announce: the press-release voice; the audience's whole identity is not falling for it.
  • This AI tool will replace developers: bait that invites a pile-on; the comments argue about you instead of trying the tool.
  • Make passive income with [X]: course-funnel language; builders assume the product is the audience.
  • Game-changing / revolutionary / 10x your [X]: adjectives with no demo; the viewer wants to see it, not be told.
  • 5 tools every founder needs: faceless listicle slop; thousands exist and none convert.
  • Comment [word] for the link: reads as engagement farming; builders would rather search the name and judge the landing page.
  • Only [N] spots left / price goes up Friday: fake scarcity on a self-serve tool; it is the fastest way to lose a developer's trust.

Where the app shows up

Most posts shouldn't sell. A good split is about 45% for reaching new people, 35% for building trust and 20% that ask for the download.

Founder accounts: the app appears mid-reel as 'the thing I'm building' (a screen clip or a mockup for three to five seconds), never pitched, with a soft close like 'it's on my profile'. Brand accounts: pain first, the demo in the middle, the direct ask in the last three seconds and again in the caption. On X the link goes in the first reply, never the post. Every convert reel still opens on the pain the feature removes.

Calls to action that fit

  • Free to try at [app].com; link in bio.
  • If [pain] is your week, [app] is in my bio.
  • Search [app] on the App Store; the free plan does this.
  • Try it on your own [data / inbox / repo] before you believe me.
  • Open source: the repo is on my profile. Star it if it saves you a weekend.
  • Steal the workflow; the tool is optional.

Asks that backfire

  • 'Comment X for the link' or 'DM me for a demo' on a self-serve tool.
  • 'Limited spots', 'price goes up Friday', countdown timers.
  • 'Like and follow for part two' on every reel.
  • 'Book a call' as the only path when the product has a free plan.
  • An ask before the viewer has seen anything work.

TikTok, Instagram, YouTube and X

  • TikTok: Vibe-coding and 'I built this in a weekend' clips reach non-developers here too, so hooks must work for someone who has never shipped. Founder face plus a phone-recorded screen demo, under 30 seconds, a pointer or finger on the screen lifts retention. Comments ask 'what tool' and 'link'; answer with the name, not a sales line.
  • Instagram: Reels for the founder story and clean design-led demo clips; the audience is smaller for developers but strong for design, no-code and agency tools. Big captions, the lesson in the caption text, no watermarks from other apps. Keep Reels under 90 seconds or they are not shown to new people.
  • YouTube Shorts: Shorts are the search-led platform for this audience: the title is the hook ('I built X with Y', 'my exact stack for Z') and stack or workflow clips keep getting found for months. Expect more sceptical comments than on X; answer them plainly. Point to a longer build log or tutorial on the same channel.
  • X: The home of this audience. Native video of six to fifteen second demos, build-in-public numbers with the why, dry one-line hot takes, memes about founder life. Link in the first reply. Memes and feature clips can share the same post. The tone is a developer talking to developers: jargon is fine, hype is not.

Accounts that grew this way

Real accounts worth studying for SaaS and developer tools, and what they did that worked.

  • Jack Friks (Post Bridge, Curiosity Quench) on X: Grew his apps with six-second clips posted to every platform at once, kept a working format running daily until it stopped working, and documented challenges, rejections and revenue in public; Post Bridge grew out of his own posting routine. x.com/jackfriks
  • Nevo David (Postiz) on X: Open-sourced the product and launched it again every month on Reddit and developer communities with what was new; outcome-led clips about going viral with slideshows, with Postiz appearing only inside the workflow, drove trials. x.com/nevodavid
  • Adam Pietrasiak (Screen Studio) on X: The screen demo is the whole marketing: every polished recording users share doubles as an advert, and the founder's own account, not the brand, carries the launches and the daily build-in-public posts. x.com/pie6k
  • Marc Lou (ShipFast, DataFast) on X: Every launch gets a short skit video and a headline that challenges the status quo; titles pair a time with a money figure; the X audience was warm while the YouTube audience was sceptical, which he addressed openly. x.com/marclou
  • Tony Dinh (TypingMind, Xnapper, DevUtils) on X: Built a feature in the morning, posted a demo clip in the afternoon, messaged beta users in the evening; every shipped feature became a post, with revenue screenshots and failures shared alongside. x.com/tdinh_me
  • Riley Brown (Vibe Code) on TikTok: Screen-share builds with a plain hook that names the value up front, phone-recorded demos with a pointer prop for short-form, big tool names on screen instead of fancy intros; he says sounding like AI is suicide for a creator. tiktok.com/@rileybrown.ai
  • Supabase on X: Memes as the native language: a meme in nearly every feature announcement, code snippet images, technical terms with no fluff, few posts, launch weeks that batch releases into an event, and sales that looks like support. x.com/supabase
  • Pieter Levels (Nomad List, Photo AI) on X: The open-startup model: live public revenue and blunt progress posts across many launches, so each new product starts with the distribution the last one built. x.com/levelsio
  • Daniel Fazio (ListKit, Client Ascension) on X: Built ListKit's audience from an agency community and long cold-email masterclasses where the founder teaches and the tool appears inside the lesson, not as the subject. x.com/danielfazio

If you're the founder

The founder is the distribution: people follow the person who ships, then find the tool. Their reels are what I shipped today with a six-second clip, the real number this month and what moved it, the mistake, the exact stack, the opinion they will defend in the comments. The app is always the thing being built, shown for a few seconds inside the story, never pitched; the close is 'it's on my profile', never 'download now'.

Lines not to cross

  • Only the founder's real numbers, left as [fill-in]: never a mocked-up Stripe or analytics screenshot, never an estimate presented as a result. Fake MRR screenshots are a known trope here and get called out in the comments.
  • No 'passive income', 'while you sleep' or 'make $X in 30 days' framing; it reads as a course funnel and the audience assumes they are the product.
  • Never disparage a named competitor. Compare practices ('most tools charge per seat') not companies, and only state facts you can point to on their public pricing or docs page.
  • Be careful with 'AI replaces developers' takes: frame as what you personally do faster, shown on screen, not as a prediction about other people's jobs.
  • Say what the tool cannot do, in the reel, when it matters ('it won't do X yet'); one honest limit buys more trust than ten features.
  • No fake scarcity or urgency on a self-serve product: no spots, no countdowns, no 'price goes up Friday' unless it is true and dated.
  • Cold email and lead tools: never promise inbox placement or reply rates; teach consent-aware outreach (CAN-SPAM in the US, GDPR and PECR in the UK and EU) and never show scraping personal emails as a trick.
  • Blur customer names, emails, keys and billing details in every screen recording; never show a customer's inbox or workspace without permission.
  • Only call it open source if the licence is a real open-source licence; 'source available' is different and this audience checks the repo.
  • Only claim security or compliance you have ('SOC 2', 'end-to-end encrypted', 'enterprise-grade') if it is true; security bugs in a popular indie product become the story for months.

Making these without a marketing team

You can film these yourself on your phone, record your screen, or build them without filming at all. Demos, changelog clips, workflows, stack breakdowns, showing the real dashboard.

If you'd rather not start from a blank page, UserClimb turns your SaaS or developer tool's link into motion graphic videos built on hooks like these: a hook on your viewer's problem, a quick lesson, then your app as the answer, voiced, captioned and set to music. It posts them to TikTok, Instagram and YouTube for you. Your first video is free, plus 6 free posts, no card.

Questions

What should I post to market a SaaS or developer tool?
A mix of the builder's pain, named (25%), opinions and 'stop doing X' (20%), demos and changelog clips (20%), build in public with real numbers (20%), exact stack and workflow (15%). Most posts should help or entertain the viewer; only a few should ask for the download.
What hooks work for SaaS and developer tools?
Stop [doing X] in your startup.. I built [thing] in [time] and [real result].. Here's my exact [stack / workflow / prompt / pricing]..
Should I show the app in every video?
No. Founder accounts: the app appears mid-reel as 'the thing I'm building' (a screen clip or a mockup for three to five seconds), never pitched, with a soft close like 'it's on my profile'. Brand accounts: pain first, the demo in the middle, the direct ask in the last three seconds and again in the caption.
Is TikTok or Instagram better for SaaS and developer tools?
Both work, differently. Vibe-coding and 'I built this in a weekend' clips reach non-developers here too, so hooks must work for someone who has never shipped. Reels for the founder story and clean design-led demo clips; the audience is smaller for developers but strong for design, no-code and agency tools.
UserClimb

Rather not work out what to post? Paste your app's link.

UserClimb makes motion graphic videos for your app: a hook on your customer's problem, a quick lesson, then your app as the answer, voiced, captioned and set to music. Then it posts them to TikTok, Instagram and YouTube. Your first video is free, plus 6 free posts, no card.