SDK Developer Tools: 60k MRR Cold Start Retrospective

Editor’s Take · AI Serial Entrepreneur Perspective (The following content is distilled by AI; opinions belong to the original author. You can skip the source article after reading this.)

Anton noticed the B2C design tool market had become a bloodbath, so he pivoted to build Polotno SDK, a B2B product for developers that solves the headache of embedding design editors into enterprise apps. Key numbers: $60k MRR in six years (A·Verified), 200+ paying customers, 2 million monthly loads (A·Verified). The takeaway for makers who want to make money: stay out of the cutthroat C-end market, and use the technical moat built from open-source projects to sell shovels. This model suits small teams with deep expertise in frontend and Canvas technology. Next step: audit the open-source libraries you maintain or the pain points in your niche, and figure out whether they can be wrapped into a developer SDK.

• Stay out of the B2C red ocean; wrap general-purpose tools into B2B SDKs and sell them
• Lower startup risk by leveraging technical depth accumulated from long-term open-source maintenance
• Build early go-to-market channels through open-source communities and documentation
• A three-person core team proved that high-margin, tech-driven small teams are viable

1. What kind of opportunity is this

Anton Lavrenov founded Polotno to offer B-end developers a “white-label design editor SDK” and batch image/video generation APIs. By embedding its component, Polotno helps companies integrate complex canvas interactions into their own apps, charging via SaaS subscriptions. The core logic is simple: package the repetitive, low-level heavy lifting into a standardized product and sell it to B2B customers desperate to ship design features quickly.

2. Independent judgment

Worth doing, but the bar is punishingly high. This is not your average CRUD project. It is foundational infrastructure built on Canvas graphics, which creates a natural technical moat. We believe this only makes sense for geeky teams with three to five years of deep frontend graphics experience and solid intuition for WebGL and Canvas rendering. Generalist full-stack or mobile developers will struggle. The real test is whether you can solve those long-tail, stubborn bugs around text editing, transforms, and export quality, not just slap a UI wrapper on top.

3. Cold-start path

Start by maintaining an active open-source base library, like Konva.js. Let the pain points surface from high-frequency questions on GitHub and Discord. Costs are tiny: just a domain and hosting fee early on, built in spare time while a day job covers living expenses. You can ship an MVP and get initial validation within six to nine months without needing a fat marketing budget.

4. Biggest risks and how to avoid them

The fatal risk is a moat too shallow to defend against big players like Figma’s API or free open-source alternatives like Fabric.js. The counterplay is to dig into enterprise-grade pain: large-scale node performance, high-precision export compatibility, and multi-language or multi-timezone support. These are the dirty, unglamorous jobs big tech won’t bother with and open-source communities can’t easily solve. Don’t fall for the fantasy of chasing both B2C traffic and B2B stability at once. Pick the B2B subscription lane and stay in it.

5. Postmortem from someone who did it

• Product positioning: Skip the C-end design tool space (and the Canva red ocean) and build a B2B SDK that lets companies embed a design editor into their own apps.
• Technical reuse: Built on the long-maintained open-source library Konva.js. Reused code logic accumulated from earlier editor projects for multiple clients, which cut R&D trial-and-error costs.
• Customer acquisition: Zero-cost cold start. Relied on the Konva.js GitHub/Discord community to surface demand. The first order came from a community user exposing the pain that “building an editor from scratch is too hard.”
• Product iteration: Kicked off in February 2020; launched the Docusaurus docs site in September. A co-founder joined in 2023 to own marketing, the site migrated to Framer, and server-side rendering was added with Node.js, Puppeteer, and Supabase to strengthen core capabilities.
• Key data: $60k MRR in six years, 200+ paying customers, 2 million monthly loads, three-person team, bootstrapped to profitability.

6. Dual-track feasibility

Global: feasible. Sell USD subscriptions to SaaS customers worldwide and siphon traffic from GitHub communities. China: not feasible. B-end willingness to pay is low, and the Canvas tool market is brutally competitive. You would need to pivot toward high-ticket, custom non-standard services like on-premises deployment plus bespoke development, but you lose the ability to scale along a SaaS trajectory.

Original · Indie Hackers · Postmortem: Read the original →