Dopt’s Onboarding SDK Is Quietly Cornering Appcues’ PLG Base

The SDK Bet That Appcues Didn’t See Coming

Product-led growth was supposed to simplify software adoption – fewer sales reps, more self-serve, and onboarding flows that converted users before anyone had to pick up a phone. Appcues built a strong business on that premise, offering no-code tools that let non-technical teams drop tooltips and modals into their products without writing a line of code. For years, that was enough. Now a startup called Dopt is quietly making the case that it was never really enough at all.

Dopt’s approach is almost the opposite of Appcues in orientation. Instead of putting onboarding in the hands of marketers and product managers through a visual editor, Dopt offers a developer-first SDK that lets engineering teams build onboarding flows directly into their product’s codebase. It’s a smaller, more precise surface area – but for a growing slice of PLG-native software companies, that precision is exactly what they’ve been waiting for.

What Appcues Built and Where It Shows Seams

Appcues became the default choice for SaaS companies that wanted to add user onboarding without involving engineering. The pitch was fast deployment: marketing or growth teams could launch product tours, checklists, and in-app messages through a Chrome extension and a visual builder. For early-stage companies without dedicated engineering bandwidth to spare on onboarding infrastructure, it made obvious sense.

But that convenience comes with trade-offs that compound as a product matures. No-code overlay tools work by injecting UI elements on top of existing interfaces, which means they can break when underlying components change, behave inconsistently across browsers, and create accessibility problems that engineering teams have to hunt down after the fact. More fundamentally, they separate the onboarding experience from the product itself – treating activation flows as something that happens to the product rather than inside it.

For companies with serious product engineering cultures, that separation has always felt like a compromise. Onboarding built outside the component tree is onboarding that product designers can’t fully control, that A/B testing frameworks can’t cleanly instrument, and that design systems teams can’t enforce consistency on. The workarounds exist, but they accumulate into technical debt that nobody budgeted for.

How Dopt Is Cutting Into That Gap

Dopt is structured around the idea that onboarding state should live where product state lives – in code. Its SDK gives engineers the building blocks to define flows, track user progress, and trigger UI components natively, without a separate overlay system running in parallel. The product ships with React components and a flow management interface that lets non-technical teammates configure the logic of a flow – which steps, in what order, under what conditions – while engineers control how each step actually renders.

That division of responsibility is the real pitch. Dopt isn’t asking growth teams to give up control; it’s asking engineering teams to own the implementation layer so growth teams can iterate on logic without creating frontend debt. It’s a workflow model that maps more cleanly onto how modern PLG companies actually operate, where growth and engineering sit closer together and deployment cycles are faster than the tools were designed for.

The startup is targeting a specific type of customer: companies that have outgrown the no-code approach but don’t want to build onboarding infrastructure from scratch. Building custom flow management, state persistence, and analytics on top of product engineering is expensive and distracting. Dopt packages that infrastructure so product teams can stop rebuilding it and start using it. The closest analogy isn’t replacing Appcues feature-for-feature – it’s replacing the category assumption that onboarding tooling should be a layer on top of software rather than a layer inside it.

That reframing has real competitive weight. A developer-first SDK doesn’t just appeal to engineers on aesthetic grounds; it fits the procurement path of companies where engineering signs off on tooling decisions. Appcues typically sells through growth or product roles. Dopt routes the conversation through engineering, which in PLG-native companies tends to have more budget authority and longer vendor relationships. Once an SDK is integrated into a codebase and a team has built flows on top of it, switching costs are substantially higher than canceling a SaaS subscription tied to a Chrome extension.

The PLG Infrastructure Moment

What Dopt is doing sits inside a broader pattern: the tooling layer for product-led growth is getting rebuilt by developer-first startups who think the first generation of PLG tools prioritized speed-to-launch over long-term product quality. The same tension showed up in analytics, where Amplitude and Mixpanel built no-code-friendly products before Segment made the case that the data layer itself needed to be owned by engineers. Infrastructure tends to follow the same arc – convenient abstractions win early, then precise primitives win at scale.

Appcues isn’t standing still. The company has expanded its feature set, added integrations, and continued to invest in the product. But its core architecture – overlay-based, visual-editor-first, non-technical-buyer-facing – is difficult to restructure without rebuilding from scratch. That’s the strategic moat Dopt is betting against.

The honest risk for Dopt is that developer-first doesn’t automatically mean developer-preferred. Engineering teams at growth-stage companies are often under more deadline pressure than anyone, and a tool that requires integration work before it ships value faces a real activation problem. Dopt’s onboarding for its own customers is, in a way, the first test of whether its onboarding philosophy actually works in practice.

Whether the PLG market is large enough to sustain a meaningful competitor to Appcues on the developer-first side is genuinely unclear – but the companies Dopt is signing aren’t fringe cases. They’re exactly the kind of high-growth, engineering-led SaaS businesses that Appcues originally built its roadmap around.