Built for Devs - See how developers really experience your product
by•
Three tools. One platform. Complete developer adoption intelligence. Time-to-value tracking, screen-recorded evaluations with real ICP-matched devs, and an AI engine that tells you exactly what's broken and how to fix it. The intelligence compounds.
You've watched the dashboards. Developers still drop off. Now you'll know why.
Replies
jared.so
Do you track where developers get stuck during onboarding or is it more focused on the overall experience? Congrats on the launch!
Tabstack
@mcarmonas It tracks the entire journey. But you have to include the script in every platform the developers touch. We bring the pieces together and show you the entire developer journey from first visit to when they leave across your site, docs, blog, product, etc. As long as the script loads.
Thank you so much!!!
This looks really useful. The screen-recorded evaluations with real devs are a great idea, getting unfiltered first impressions before launch sounds way better than guessing. Curious about the time-to-value tracking too, how do you define 'conversion'? Is it something I configure or does it detect it automatically? I'm building a desktop app with Electron so also wondering if this would work for that or if it's web-only.
Tabstack
@ray_artlas You configure it by setting your "value points" because there can be multiple points per product. In the configuration you also set which pages/endpoints go in which part of the developer journey, too. This helps you see a clear view of your developer user journey and then the events and human data are layered over top of that to provide rich recommendations on what to improve. Its web only unfortunately.
@tessak22 That makes sense. Being able to map specific pages to journey stages sounds really useful for finding where developers drop off. Web only is fine for us. Thanks for the detailed answer!
Mobil uygulamar için böyle bir analiz programına ihtiyaç var aslında bu sadece website mi inceliyor?
Tabstack
@yafurkan The events script logging does only work on browser-based web apps. However, the real developer feedback could be catered to mobile apps. We just wouldn't have the same level of tracking. I've considered expanding to mobile but haven't pursued that to deeply just yet.
Snyk
Congrats on the launch Tessa!
Tabstack
Tabstack
Drop one script tag into your site. That's it.
bfd.js tracks how developers actually move through your docs and product—pageviews, clicks, scroll depth, time on page, rage clicks, copy events, JS errors, and form interactions. No fluff. No PII. Sensitive fields and params are automatically redacted.
Pair it with screen-recorded evaluations from ICP-matched developers in our 6k+ network, and you stop guessing what's broken. You see it.
Three products. One goal: turn drop-offs into adoption.
→ JS tracking script — measures TTV and the full developer journey
→ Screen-recorded evaluations — real developers, your exact ICP, paid to do a thorough job
→ AI recommendations engine — tells you what's broken and what to fix. Gets smarter over time.
Built for dev tool teams who are tired of shipping docs into a void.
Tabstack
Here's an example of a developer adoption score!
Developer experience testing is such a blind spot for most SaaS companies. Do you record the actual terminal/IDE session or is it more survey-based? The raw session recordings would be gold for debugging onboarding friction.
Tabstack
@greythegyutae they are gold for debugging onboarding friction! Developers doing the evaluations share their screen and commentate the entire time. So if your tool is a terminal or IDE too, then yes, that would be included in the recording. So you would have event logs and full recordings of the entire experience. Event logs are for the browser experience only, of course. We are currently building an agent-driven evaluation that should be out soon!