The onboarding gap nobody puts on a content calendar
Here’s the thing I keep running into with creators and social teams: we obsess over the top of the funnel — hooks, thumbnails, watch time, the algorithm — and then we lose the person the second they actually show up. A new subscriber lands on your link-in-bio, or a trial user signs up for your template pack, or someone clicks through to your Discord, and there’s nothing waiting for them except a wall of options and a “figure it out” shrug. I’ve watched creators spend six figures of effort on acquisition and zero on the first ninety seconds of a relationship. So when I saw TourKit — a developer-first product tour platform from maker Raj Chavan — my instinct wasn’t “oh, another SaaS onboarding tool.” It was: this is the mechanic creators keep ignoring, dressed up in developer clothing. The launch post is refreshingly honest about its own traction, which is rare enough that it’s worth paying attention to. Let me explain why a product tour SDK belongs on a social media operator’s radar, and where I think it falls flat.
What TourKit actually solves — and why it’s not just a dev tool
Strip away the framework names and TourKit is a simple idea: guide a user through your product with in-app steps (tooltips, highlights, walkthroughs) without making your engineering team hardcode every step and redeploy every time a button moves. The maker’s pitch is that adding a tour “should take minutes” instead of hours spent configuring libraries, maintaining tours in code, or paying for “an entire enterprise onboarding platform” just to point at a feature.
The mechanics matter here, so let me be precise. TourKit is a lightweight SDK you add with a single script tag, and it works with React, Next.js, Vue, WordPress, and plain HTML. Once it’s installed, you manage the tours from a dashboard — so changing a step doesn’t require touching application code or shipping a new build. The SDK itself is open source under the MIT license, which you can inspect on the project’s GitHub repo. The maker also made a deliberate bet on mobile: instead of a desktop tooltip crammed onto a phone screen, TourKit adapts to a bottom-sheet interaction while keeping the relevant element highlighted.
Now, why should a creator care about any of this? Because the same primitive solves a problem you have every single day. When you sell a course, a Notion template, a preset pack, or a paid community, your onboarding is your retention. A customer who can’t find the first win churns, and churn is the silent killer of creator businesses that look healthy on the surface. The tooling to fix that — guided, editable, no-redeploy walkthroughs — has historically been locked behind enterprise onboarding platforms priced for companies with a sales team, not a solo operator with a Gumroad page.
The incumbents you’d actually compare this to
If you’ve ever shopped for this category, you’ve probably run into Appcues, Userpilot, Pendo, or Intercom’s product tours. These are mature, well-funded platforms with deep analytics, segmentation, A/B testing on tours, and integrations into your CRM and data warehouse. They’re also, in my experience, overkill and overpriced for anyone whose “product” is a 40-page PDF and a Slack community. On the other end you have open-source libraries like Shepherd.js or Intro.js, which are free and flexible but require you to maintain the tour logic in your own codebase — which is exactly the pain the maker is describing.
TourKit sits in the middle: lighter than Appcues, more managed than a raw library, open source at the SDK layer. That’s a genuinely useful position, and I’d argue it’s the position most creator-tooling should occupy.
What creators and social teams can steal from this launch
Even if you never install TourKit, the launch is a masterclass in a few things operators get wrong constantly. Let me pull out the transferable lessons.
Onboarding is a content problem, not a code problem
The single most important line in the maker’s post is this: once integrated, “changing a step doesn’t require changing your application code and redeploying.” Read that again but substitute your own stack. How many of your welcome sequences, link-in-bio flows, or pinned “start here” posts are effectively hardcoded — baked into a design you’re scared to touch because rebuilding it means a whole production cycle? The lesson is to separate the content of your onboarding from the delivery of it. If your welcome email, your first Discord message, and your first-week drip are all editable in one place without a redesign, you’ll actually iterate on them. Most creators never iterate on onboarding because the friction of changing it is higher than the friction of ignoring it.
Mobile-first isn’t a buzzword, it’s a bottom sheet
I love that the maker specifically called out that “a desktop tooltip doesn’t always translate well to a phone.” This is the same mistake creators make when they design a carousel for desktop and then wonder why it dies on Instagram. The platform-native pattern for a small screen is not a shrunken version of the big-screen pattern — it’s a different interaction entirely. TourKit’s answer is the bottom sheet, which is the same pattern TikTok uses for comments and Instagram uses for share sheets. If you’re building any guided experience — a story sequence, a “swipe up to learn more,” a tutorial reel — ask whether you’re porting a desktop pattern or designing a native one. In my experience, the native pattern wins almost every time.
Open source as a trust signal
The SDK is MIT-licensed and publicly inspectable. For a tool that runs on your users’ websites, that transparency matters — you can “see exactly what runs on your users’ websites,” as the maker puts it. Creators should internalize this as a buying heuristic: when you’re evaluating any tool that touches your audience (email platforms, link shorteners, analytics, scheduling tools), ask whether you can verify what it does with your data. It’s not always possible, but “you can read the code” is a meaningfully stronger trust posture than “trust our privacy page.”
The part where the math gets uncomfortable
Here’s where I have to be honest, because the maker was honest first, and that deserves to be met in kind. In the launch post, the maker shares that a prior push on daily.dev reached 116K impressions, 801 clicks, 38 signups, and 0 paying customers. He explicitly says he’s “not coming here pretending I’ve already figured out distribution or product-market fit.”
That’s a remarkable thing to publish. Most launch posts bury the zero. But it also tells you something important about the product’s current stage, and I want to walk through what those numbers actually mean, because the conversion math here is the whole story.
Where the math breaks
Let’s do the arithmetic the maker is implicitly inviting us to do. 801 clicks from 116K impressions is roughly a 0.7% click-through rate — which, for a developer-audience feed, is not catastrophic, but it’s not great either. Then 38 signups from 801 clicks is about a 4.7% signup rate, which is actually decent for a cold developer audience. The problem is the last step: 0 paying customers from 38 signups. You can’t compute a conversion rate from zero, but you can compute the sample size problem. Thirty-eight signups is not enough to conclude anything about willingness to pay. It’s enough to conclude that the funnel isn’t yet producing enough volume to learn from.
This is the classic indie-founder trap, and it’s the same trap creators fall into with a new offer. You get a spike of attention, a trickle of signups, and then you stare at a zero and conclude the product is broken. Usually the product isn’t broken — the sample is just too small to say anything. My take: the honest read of those numbers isn’t “TourKit doesn’t work,” it’s “TourKit hasn’t been in front of enough of the right people yet to know.”
Why TikTok creators should care more than LinkedIn ones
Here’s a sidebar worth dwelling on. If you’re a TikTok creator, your entire business model is built on the assumption that a viewer will take an action after a single piece of content — follow, click the link, buy the thing. That’s a one-touch funnel, and it lives or dies on whether the next screen makes sense. A product tour is the same discipline: make the next screen make sense. Creators who understand “the hook has to earn the next three seconds” already think like onboarding designers.
LinkedIn creators, by contrast, often operate on a multi-touch, relationship-driven model where the “onboarding” is a DM conversation. That’s a different skill. It’s not that LinkedIn creators can’t use this — it’s that the urgency is lower, because the human on the other end will forgive a confusing next step in a way an anonymous TikTok viewer never will. If you’re optimizing for cold, high-volume, low-patience traffic, onboarding quality is existential. If you’re optimizing for warm, low-volume, high-patience traffic, it’s a nice-to-have. Know which one you are.
What I’d actually borrow — and what I’d flag before you buy
Let me separate the transferable principle from the specific product decision, because I don’t want to be accused of shilling a tool I haven’t run in production.
What I’d borrow, regardless of tool: the separation of onboarding content from delivery, the mobile-native interaction pattern, and the discipline of publishing your real numbers even when they’re ugly. That last one is underrated. The maker’s candor is itself a growth asset — it invites the exact feedback he asked for (“What’s confusing? What’s missing? What would stop you from using it in your own product?”), and it builds trust with an audience that’s allergic to hype.
What I’d flag as open questions: the source doesn’t disclose pricing, so I can’t tell you whether this beats Appcues or Userpilot on cost for a solo operator — that’s the single most important unknown. The source also doesn’t disclose how the dashboard handles analytics, A/B testing on tours, or segmentation, which are the features that justify the enterprise incumbents’ price tags. And “0 paying customers” means there’s no public evidence yet of retention or willingness to pay at scale. None of that is a knock on the product; it’s just what the launch post does and doesn’t tell us.
Who this is NOT for
If you’re a creator whose “product” is content itself — you monetize via ad revenue, brand deals, or a Patreon where the value is the content stream — you probably don’t need a product tour SDK. Your onboarding is your content. Similarly, if you’re running a large SaaS with a dedicated growth team, the enterprise platforms’ analytics and segmentation will likely be worth the premium. TourKit looks best suited to the middle: indie founders, small SaaS, and creators who ship a tool (a template, an app, a course platform) and need to guide users through it without hiring an engineer to maintain the walkthrough.
What I’d watch / test next
If you’re an operator reading this, here’s what I’d actually do this week — not buy anything, just test the principle.
Audit your first ninety seconds. Pick one funnel — a link-in-bio, a welcome email, a post-purchase page — and screen-record yourself going through it as a brand-new user. Count the moments of confusion. My bet is you’ll find at least three, and you’ll fix two of them without any new tool.
Separate content from delivery in one place. Take your welcome sequence and move it into something editable without a redesign — a Notion doc, a ConvertKit sequence, whatever you already pay for. The goal is to make iteration cheap, not to adopt a new platform.
Watch the TourKit launch thread. It’s on Product Hunt, and the maker is actively answering questions. If you build SaaS, ask him directly about pricing and analytics — those are the gaps in the public record, and the answers will tell you whether it’s worth a trial.
If you do try it, instrument the funnel. Install the SDK, then track signup-to-activation with UTM parameters and a simple event. The whole point of a tour is that it should move a number. If it doesn’t move a number, it’s decoration.
The bigger lesson here isn’t about TourKit at all. It’s that the creator economy has spent a decade getting very good at acquisition and almost no time getting good at activation — and the tools are finally catching up to that gap. Whether this particular product wins or not, the category is about to matter a lot more to people who currently think of “onboarding” as somebody else’s job. It isn’t. It’s the most under-optimized surface in your entire business, and it’s sitting there waiting.
