Storyline was a Y Combinator-backed startup (Winter 2018) founded in September 2017 by Vasili Shynkarenka and Maksim Abramchuk, two Belarusian entrepreneurs who had previously run Botcube, a software agency building chatbots and voice ap…
Storyline was a Y Combinator-backed startup (Winter 2018) founded in September 2017 by Vasili Shynkarenka and Maksim Abramchuk, two Belarusian entrepreneurs who had previously run Botcube, a software agency building chatbots and voice apps for clients. The company built a drag-and-drop, browser-based tool that let non-technical users create and publish Amazon Alexa skills without writing a single line of code — positioning itself as the "Weebly for voice apps."[1]
Storyline failed because it built a tooling business on top of a platform whose end-user adoption never materialized. The Alexa Skills ecosystem attracted hobbyists but not sustained consumer engagement, leaving Storyline with a large, enthusiastic user base that was structurally unwilling to pay. A November 2018 pivot to Invocable — a voice UX prototyping tool for professional designers — solved the monetization problem in theory but introduced a fatal retention problem: prototyping is episodic, not recurring.
Invocable shut down on April 15, 2019, roughly 18 months after Storyline's founding and five months after the pivot. The company raised a total of $770,000 and transitioned its remaining users to Voiceflow, a Canadian competitor that survived by securing additional venture capital and waiting out the market's slow maturation. Shynkarenka later described the aftermath as years of processing "sneaky trauma from a failed startup" before re-emerging in 2023 to found AI Study Camp, a course teaching YC founders about large language models.[2]
Vasili Shynkarenka and Maksim Abramchuk came to Storyline not from academic research or a consumer frustration, but from the trenches of client services. Before founding Storyline, the two ran Botcube, a Belarusian software development agency that built chatbots and voice applications for paying clients.[3] That agency work gave them an unusually direct view of a recurring production bottleneck: the people with the best ideas for voice content — journalists, educators, marketers — couldn't code, and the engineers who could code weren't skilled at crafting engaging conversational content.
Shynkarenka articulated the founding thesis with unusual precision: "Our hypothesis was that good content creators aren't always technical, and technical people aren't great at content."[4] The insight was real. The question was whether the market it pointed to was large enough and willing enough to pay.
The founders incorporated Storyline in September 2017 and shipped a first product version in October 2017 — a remarkably fast timeline that reflected the relative simplicity of the initial product scope.[5] In late 2017, Shynkarenka and Abramchuk relocated from Belarus to the Bay Area, a move that signaled their intent to pursue venture-scale growth rather than a lifestyle business.[6]
Y Combinator accepted Storyline into its Winter 2018 class, providing the standard YC deal, network access, and the Demo Day platform that would generate Storyline's first significant press coverage.[7] The YC acceptance also validated the "Weebly for voice apps" framing — a clean, legible analogy that positioned Storyline within a proven no-code category and made the pitch immediately comprehensible to investors and press alike.
The analogy was also the company's most dangerous assumption. Weebly succeeded because the web had hundreds of millions of active users and a proven advertising and e-commerce economy. The Alexa Skills ecosystem in 2017–2018 was a platform in search of a use case — Amazon had shipped the hardware, but consumer behavior on smart speakers remained stubbornly narrow. The founding insight about content creators and coders was correct. The implicit assumption that Alexa would grow into a platform resembling the web was not.
Shynkarenka later reflected: "We realized there was this big struggle with creating conversational apps. We learned that creative people and content creators are not really good at writing code. That was the major insight."[8] The insight was sound. The platform it was applied to was not.
Storyline's core product was a browser-based, drag-and-drop visual editor for building and publishing Amazon Alexa skills — no programming knowledge required. The founders claimed a non-technical user could go from zero to a published skill in five to seven minutes.[25]
The Three Skill Types
The platform supported three categories of Alexa skills, each with a distinct use case and builder interface:[26]
Flash Briefings — Short audio or text news updates that Alexa reads aloud when a user asks for their daily briefing. This was the most popular use case for media companies, podcasters, and content creators who wanted a presence on Alexa without building a full application.
Games and Trivia — Multiple-choice and question-and-answer formats that Alexa could deliver interactively. These were the most common hobbyist skills and the easiest to build.
Custom Skills — More open-ended conversational flows that could handle branching dialogue, user inputs, and multi-turn interactions. These were the most complex to design well, even with Storyline's visual interface.
The User Experience
A user would log into Storyline's web interface, select a skill type, and build the conversational flow using a visual node editor — connecting dialogue blocks, response options, and branching paths without touching code. The platform included a built-in preview mode that simulated how the skill would sound on an Alexa device, allowing iteration before publishing. When the skill was ready, a single click submitted it to Amazon's Skill Store for review and publication.[27]
Built-in analytics tracked how users interacted with published skills — session counts, drop-off points, and engagement metrics — giving non-technical creators data they would otherwise need a developer to instrument.[28]
Pricing
The basic tier was free. The Pro tier was priced at $49/month and added technical support and the ability to schedule flash briefing posts — a feature primarily useful for media organizations publishing on a regular cadence.[29]
Platform Scope
At launch, Storyline was exclusively Amazon Alexa-focused. The founders publicly planned to expand to Google Home and Google Assistant, but this expansion was never executed before the pivot.[30] This single-platform dependency meant Storyline's fate was entirely tied to Alexa's ecosystem growth.
What Made It Different
Relative to building Alexa skills natively through Amazon's developer console — which required familiarity with JSON, AWS Lambda, and Alexa's intent/slot model — Storyline was genuinely easier. The visual node editor abstracted away the underlying architecture. The one-click publishing pipeline removed the need to configure AWS infrastructure. The built-in analytics replaced the need for custom logging.
The limitation was the ceiling. Storyline's tree-based design model worked well for simple, predictable conversational flows but struggled with the open-ended, context-aware interactions that would have made Alexa skills genuinely useful. A third-party analyst noted that the tree-based approach "forced users to think about voice apps as decision trees," which constrained the quality of experiences for anything beyond scripted exchanges.[31]
Storyline's initial target was non-technical content creators: journalists, podcasters, educators, marketers, and hobbyists who wanted a presence on Alexa but lacked the engineering skills to build natively. The Kids Court win — a skill built by Adva Levin, a non-developer, that won Amazon's $25,000 Alexa Skills Challenge: Kids — was the clearest demonstration of this thesis in action.[32]
In practice, the user base skewed heavily toward hobbyists: individuals building skills for personal projects, small media outlets experimenting with flash briefings, and educators creating trivia games. This was a community, not a professional market. The free tier dominated adoption. The $49/month Pro tier found limited uptake — the number of paying subscribers was never disclosed, which is itself a signal that the figure was not a selling point.[33]
After the November 2018 pivot to Invocable, the target shifted to professional voice UX designers — a smaller, more specialized audience that Storyline hoped would pay $99/month for a prototyping tool. This was a deliberate narrowing: Invocable launched invite-only and paid-only, explicitly designed to filter out the hobbyist community that had dominated Storyline's user base.
The addressable market for Alexa skill-building tools in 2018 was structurally constrained by the size of the Alexa developer ecosystem. Amazon reported approximately 80,000 skills in the Alexa Skills Store by mid-2018 — a large absolute number, but one that masked a critical problem: the vast majority of those skills had negligible user engagement. Consumer behavior on smart speakers was concentrated in a handful of native functions (music, timers, weather, news), not third-party skills.
The no-code tool market itself was real and growing — Weebly, Squarespace, and Wix had demonstrated that non-technical users would pay for website builders. But the analogy broke down at the demand side: websites had a clear, proven value proposition for small businesses and individuals. Alexa skills did not. There was no equivalent of "I need a website for my business" driving demand for skill creation.
The professional voice UX designer market that Invocable targeted was even smaller. Voice design as a distinct professional discipline was nascent in 2018 — most companies building voice experiences were using internal developers, not specialized designers. The total addressable market for a $99/month prototyping tool for voice designers was, at best, in the tens of thousands of potential users globally.
The competitive landscape for no-code Alexa skill builders in 2018 was fragmented but consolidating rapidly. Storyline's key competitors included:
Voiceflow (formerly Storyflow) — A Canadian startup that began as a direct competitor to Storyline, targeting a similar non-technical audience with a visual skill builder. Voiceflow's key strategic difference was its willingness to raise more capital and wait out the market's slow development. When Storyline pivoted to Invocable in November 2018, the flood of displaced Storyline users overwhelmed Voiceflow's beta program and forced an early general availability launch.[34] Voiceflow subsequently raised $3.5 million CAD in April 2019 — the same month Invocable shut down — and eventually pivoted toward enterprise conversational AI design, surviving long enough to find a more durable market.[35]
Sayspring — A code-free voice prototyping tool that was acquired by Adobe in April 2018.[36] The Adobe acquisition was initially read as validation of the category. In retrospect, it was a consolidation signal: a large incumbent absorbing a small tool into a design suite, not a sign of standalone market viability.
Amazon's Native Developer Console — The most important "competitor" was Amazon itself. Amazon's own developer tools improved over the 2017–2019 period, and Amazon had no incentive to make third-party skill builders succeed at the expense of its own developer ecosystem. Storyline was building on a platform controlled by a company that could — and did — improve its own tooling.
The structural competitive dynamic was unfavorable along two axes. On distribution, Amazon had a natural advantage: every Alexa developer already had an Amazon account and access to the native console. On data, Voiceflow had more runway to accumulate user behavior data and iterate. Storyline competed on product simplicity — a real advantage, but one that Amazon could erode by improving its own tools, and one that Voiceflow could match with sufficient investment.
Storyline operated a freemium SaaS model. The free tier provided full access to the skill builder with no usage limits. The Pro tier at $49/month added technical support and flash briefing scheduling — features primarily useful for media organizations and power users.[37]
The company never disclosed revenue figures. The absence of any revenue data in press coverage — across TechCrunch, Voicebot.ai, and the founders' own blog posts — is consistent with a business where revenue was not a compelling part of the story. The 3,000-user email list cited at the November 2018 pivot was described as "an amazing community," not as a revenue base.[38]
Inferred unit economics (labeled as estimates): With $770,000 in total funding and a three-person team (per the YC profile), annual burn was likely in the range of $300,000–$450,000, assuming Bay Area salaries and minimal infrastructure costs. At $49/month per Pro subscriber, Storyline would have needed approximately 500–750 paying users to approach breakeven — a figure that appears inconsistent with the hobbyist-dominated user base described in coverage. If even 5% of the 3,000-user base converted to Pro, that would represent 150 subscribers and roughly $88,000 in annualized revenue — well short of sustainability. These are inferences from indirect evidence, not confirmed figures.
After the pivot, Invocable launched at $99/month with no free tier — a deliberate attempt to force revenue validation. The product shut down five months later, suggesting the paid-only model did not find sufficient demand at that price point.
Storyline's growth in published skills was rapid and real. The company went from approximately 200 live skills in February 2018 to 500 by April 2018, 3,500 by mid-2018, and over 5,000 by November 2018 — representing more than 8% of the entire Alexa Skills Store at the time of the pivot.[39] For a product that had been live for roughly 13 months, this was a meaningful share of a major platform's content ecosystem.
The Kids Court win in March 2018 was Storyline's highest-profile validation moment. Adva Levin, a non-developer, built the skill entirely on Storyline and won the $25,000 Grand Prize in Amazon's Alexa Skills Challenge: Kids — a concrete proof point that the platform could produce competition-quality output.[40]
However, the user growth data tells a more cautious story. The 3,000-signup figure cited at YC Demo Day in February 2018 and the "3,000+ users" cited in the November 2018 pivot announcement span a nine-month period — suggesting user growth had plateaued well before the pivot decision. The ratio of total signups to published skills (roughly 1:1 at launch, then diverging sharply as the skill count grew to 5,000 while the user base remained at 3,000) suggests a core group of power users publishing multiple skills, not broad market adoption.
The most telling traction signal was the user response to the pivot: when Storyline shut down in November 2018, so many users migrated to Voiceflow that Voiceflow had to end its restricted beta early and open to general availability.[41] This confirmed genuine demand for the category — but also confirmed that Storyline had failed to convert that demand into a sustainable business.
Storyline's failure was, at its core, a platform bet that lost. The company's entire business model depended on the Alexa Skills ecosystem becoming a meaningful consumer platform — one where users regularly discovered, enabled, and returned to third-party skills. That ecosystem never developed.
Shynkarenka identified this with unusual directness in the Invocable shutdown post: "The market of a tool for creating voice applications relies on the success of voice applications, which is not there yet."[42] Consumer behavior on smart speakers remained concentrated in native functions — music, news, timers, reminders, and simple commands — that required no third-party skills at all.[43]
This was not a failure of execution. Storyline published over 5,000 skills — more than 8% of the entire Alexa Skills Store — in 13 months. The product worked. The platform didn't grow into the use case. A tooling business cannot outrun the adoption curve of the platform it serves.
The structural lesson is broader: no-code tooling businesses are derivative bets. Their ceiling is set by the ceiling of the underlying platform. Weebly succeeded because the web had a billion users and a proven commercial economy. Storyline failed because Alexa had tens of millions of devices but a consumer behavior pattern that didn't require third-party skills.
Storyline's founding thesis — that content creators needed a no-code voice tool — was correct about the technical barrier but wrong about the product management barrier. Shynkarenka acknowledged this explicitly in the shutdown post: "Non-tech creative folks are actually able to create good content, but the app is not just content. A skill is like a huge product on itself, rather than just a content piece. And most content creators are not good at product management."[44]
Storyline lowered the technical barrier to zero. It did not lower the product thinking barrier. Building an engaging Alexa skill required decisions about conversational flow, error handling, user intent modeling, and re-engagement mechanics — decisions that required product management skills, not coding skills. Content creators who could write excellent flash briefing copy struggled to design multi-turn conversational experiences that users would return to.
The Kids Court win was the exception that proved the rule. Adva Levin succeeded because she was building a structured, rules-based game — a use case that mapped well to Storyline's tree-based interface. Open-ended conversational skills, which would have driven the most valuable user engagement, required a level of product sophistication that the target user base didn't have.
Storyline's response was to pivot to professional designers — users who did have product thinking skills. But this was a smaller market, and it introduced the next failure mode.
The November 2018 pivot to Invocable was logically coherent: professional designers would pay more, and the prototyping use case was adjacent to Storyline's existing capability. But Shynkarenka later identified the fatal flaw in the pivot's logic: "Prototyping tools are great to play with and explain ideas, but it's super hard to retain users by being a prototyping tool — because they use the tool to prototype and then that's it."[45]
Prototyping is episodic. A designer uses a prototyping tool to validate a concept, presents it to a client or stakeholder, and then moves to implementation — at which point the prototyping tool is no longer needed. This is the opposite of the recurring, habitual usage that SaaS businesses require. Invocable's $99/month price point assumed monthly retention that the use case structurally couldn't support.
The pivot also damaged user trust in a way that accelerated churn. The two-hour "maintenance window" that ended with Storyline replaced by Invocable — and getstoryline.com redirecting to Invocable.com — surprised thousands of users who had built live skills on the platform.[46] Users had until December 2018 to make final edits; after that, their skills were frozen. The abruptness of the transition was a reputational cost that made it harder to build the professional community Invocable needed.
Even if Storyline had solved its monetization and retention problems, a technical ceiling imposed by Alexa itself would have constrained the quality of skills that could be built. Invocable's farewell post noted that NLP and NLU quality were not good enough to support the growth of complex voice apps.[47]
This was an Amazon problem, not a Storyline problem — but it was a problem Storyline had no ability to fix. Alexa's intent recognition in 2018 was reliable for simple, scripted commands but degraded rapidly for open-ended, context-dependent conversations. A skill built on Storyline could only be as good as Alexa's ability to understand what users said. When users encountered misrecognitions and dead ends, they abandoned skills — not because the skill was poorly designed, but because the underlying NLP couldn't handle natural speech variation.
This technical ceiling meant that even the best Storyline-built skills delivered experiences that felt brittle compared to native Alexa functions. The platform was asking users to adopt a new behavior (using third-party skills) while delivering an experience that was demonstrably worse than the native behavior (asking Alexa directly). That gap was not closeable with better tooling.
Voiceflow's survival — and Invocable's failure — was not primarily a product quality story. Both companies built similar tools for similar markets. The difference was capital. Voiceflow raised $3.5 million CAD in April 2019, the same month Invocable shut down, giving it the runway to survive the market's slow maturation and eventually pivot toward enterprise conversational AI design.[48] Invocable, with $770,000 in total funding and a five-month runway after the pivot, did not have the same option.
Whether Storyline/Invocable attempted to raise additional capital after the $770,000 round is not confirmed in the public record. The absence of any fundraising announcement between July 2018 and the April 2019 shutdown suggests either that the attempt failed or was not made.
Tooling businesses are derivative bets on platform adoption, and the platform's consumer behavior ceiling sets the tooling business's revenue ceiling. Storyline published over 5,000 Alexa skills — more than 8% of the entire Skills Store — and still failed, because the underlying platform never developed the consumer engagement that would have made skill creation commercially valuable. The lesson is not "pick the right platform" in the abstract; it is that a no-code tooling business requires evidence that end-users are already engaging with the platform's third-party ecosystem before the tooling market can sustain a SaaS business. Storyline launched in 2017 when Alexa skill engagement data was already showing that consumers used smart speakers for native functions, not third-party skills. Voiceflow survived by raising enough capital to wait for the market to mature into enterprise conversational AI — a different market entirely.
Lowering the technical barrier does not automatically lower the product thinking barrier, and conflating the two leads to a user base that is enthusiastic but unable to produce the outcomes that would justify paying. Storyline's content creator hypothesis was correct that non-technical users couldn't code. It was incorrect that removing the coding requirement was sufficient to enable good skill design. Shynkarenka's own post-mortem identified that "most content creators are not good at product management" — a gap that no amount of UX simplification could close. The implication for no-code tools is that the target user's skill gap must be precisely identified: Storyline solved the wrong gap.
Freemium community metrics and revenue metrics diverge sharply when the free tier attracts users who are structurally unable to pay. Storyline's 3,000-user community was described as "truly supportive" and generated impressive skill-store penetration. But the same community characteristics — hobbyists, content creators, bedroom builders — that made it enthusiastic made it resistant to the $49/month Pro tier. The pivot to Invocable's paid-only $99/month model was a correct diagnosis of this problem, but it was applied to a use case (prototyping) that had a structural retention problem. The lesson is that community size is not a leading indicator of revenue potential; the willingness and ability of the specific user persona to pay must be validated before the community is built.
Abrupt product pivots that strand existing users destroy the trust capital needed to build the next product. The two-hour maintenance window that replaced Storyline with Invocable — surprising thousands of users who had live skills on the platform — was a reputational cost that Invocable could not afford given its five-month runway. A more gradual transition, or a longer deprecation timeline, might have preserved enough goodwill to generate referrals and early adopters for the new product. Instead, the pivot generated user frustration that was publicly documented and contributed to the mass migration to Voiceflow.
The prototyping tool category has a structural retention problem that makes it a poor fit for subscription SaaS pricing. Invocable's pivot to voice UX prototyping was a logical response to the monetization failure of Storyline's hobbyist model. But Shynkarenka himself identified the flaw: prototyping is episodic. Users prototype, present, and move on. This pattern is incompatible with monthly recurring revenue. The lesson is specific to Invocable's situation: the pivot solved the "willingness to pay" problem by targeting professionals, but introduced a "reason to keep paying" problem that the use case couldn't resolve. A usage-based or per-project pricing model might have been more appropriate for the prototyping use case than a monthly subscription.