Abhishek Raj: We focus on tools that enhance the creative thinking process rather than automating it away

How the tech leader behind One Stop for Writers turned a creative platform into a global benchmark without spending on advertising 

The global creative software market presents a compelling growth trajectory, with industry data from Horizon Databook projecting expansion from USD 9.4 billion in 2023 to USD 15.0 billion by 2030. This surge reflects a fundamental shift in how creative professionals approach their craft, increasingly leveraging sophisticated digital tools to accelerate workflows, enhance output quality, and unlock new creative possibilities. Yet in this rapidly expanding ecosystem, success belongs not merely to the fastest or most feature-rich platforms, but to those that master the delicate balance between technological innovation and genuine understanding of creator needs.

Building a platform that serves writers globally while maintaining technical excellence requires precisely this blend of engineering leadership and deep creative workflow understanding. Writers need stability, trust, and tools that amplify their voice, without unnecessary complexity or intrusive automation.

Meet Abhishek Raj—who has held key engineering roles at Apple and India’s leading audio streaming service JioSaavn — and has applied that mindset to One Stop for Writers. As the CTO, he led the technical transformation of bestselling authors Angela Ackerman and Becca Puglisi’s story support platform into a global powerhouse serving 70,000 users across 170+ countries —all without spending a dollar on advertising.

One Stop for Writers stands apart in the crowded writing tools market. While many platforms focus on generic templates or automated content generation, this platform was designed as a comprehensive creative library and suite of interactive tools. It offers unique solutions for planning, writing, and editing stories—from the acclaimed Character Builder to interactive Story Maps, guided Storyteller’s Roadmap, Scene Maps, and Timelines. Writing communities consistently highlight these tools as unmatched by competitors in functionality and depth.

Under Raj’s technical leadership, this bootstrapped startup has achieved what many venture-funded companies struggle with: organic growth, profitability, 100% uptime, and a loyal global user base. His approach? Focus relentlessly on value over features, and let engineering excellence drive business results.

We spoke with Abhishek Raj about how he bridged the gap between modern technology and creative writing, the engineering principles that enabled global scale without advertising spend, and why he believes the future belongs to tools that amplify rather than replace human creativity.

“Support, not substitution, of creative thinking.” 

You led the development of signature tools like Character Builder and Storyteller’s Roadmap. How do these differ from typical writing software? 

Character Builder isn’t a template—it’s a system that leverages psychology and human experience to help authors deeply flesh out their characters. It’s built on a sophisticated engine that analyzes user inputs and provides intelligent insights, combined with visual cues and proprietary content that enriches the character creation process. Storyteller’s Roadmap acts as a compass, guiding authors through story development without dictating their path. Both tools increase engagement and let writers focus on creativity rather than getting lost in complex software interfaces.

Story Map and Timeline features are one of your platform’s key innovations. What philosophy guided their development? 

Story Map helps writers visualize their narrative and structure their timeline interactively—it enhances story control without overwhelming them with unnecessary complexity. Built on Ruby on Rails with cutting-edge JavaScript frameworks, it transforms user inputs about story acts and events into interactive, visually compelling maps. These tools set the tone for the entire platform: support, not substitution, of creative thinking.

“The key was listening to our writing community.” 

Your background spans Apple and JioSaavn, yet you’ve also transformed One Stop for Writers into a global platform serving 70,000 users. How did your big tech experience influence your approach to building a tool for the creative community? 

Working in big tech teaches you to think at scale—designing systems that are resilient, modular, and ready for long-term growth. At One Stop, I established a culture of code reviews, strong security practices, version control discipline, and high standards for quality from the very beginning. However, startups also require speed, so I focused on solutions that could be implemented quickly without becoming bottlenecks down the line.

But there’s something unique about building for writers—they’re entrusting you with their most personal creative work. Every technical flaw doesn’t just create user frustration; it erodes the trust that’s fundamental to the creative process. This is why I prioritized engineering discipline from day one, implementing full CI/CD automation with comprehensive test coverage. For authors, platform stability isn’t a nice-to-have—it’s foundational to their creative flow.

You’ve achieved what many consider the holy grail of SaaS: sustainable growth without any ad spend. What was your strategy? 

We bet everything on the product. Instead of paying for traffic, we invested in unique features, user experience, and SEO optimization. We studied real author workflows and systematically improved them. The key was listening to our writing community—through embedded feedback mechanisms, testimonials, and feature requests—and building exactly what they needed next.

We also implemented a transparent subscription model with a friction-free trial that lets users explore the platform without pressure. When writers experience tools like our Character Builder or Story Maps firsthand, the value is instantly clear. That led to strong conversions and organic word-of-mouth growth through writing communities and forums.

“Reliability isn’t a feature—it’s part of our user promise.” 

Despite serving users across 170+ countries with enterprise-grade stability, your team remains compact. How do you maintain such high technical standards with limited resources? 

I designed our engineering processes for a small, tight-knit team. And the hiring bar was set incredibly high, focused on finding the best people, even if it took months. I built a team of engineers who not only held themselves to high engineering standards but also cared deeply about the product and embraced ownership.

We avoided bloated frameworks and focused on modularity—each feature is a microservice that can scale independently. All static assets are served via CDN, and dynamic workloads are processed regionally. To ensure security and reliability, we utilize automated tools: rate limiting, alerting, and self-healing scripts. This setup provides enterprise-grade stability without a large DevOps team.

The platform is renowned for its exceptional stability and security, essential for writers working on sensitive creative projects. What specific practices enabled that level of reliability? 

We embedded redundancy and fault tolerance at the architectural level. All user data is encrypted, backups are daily, and the core infrastructure is replicated across the globe, ensuring high availability of the platform. We have captchas to secure all entry points against bots, caching our thesaurus content helps reduce load and accelerate response times, and we have an in-house rate-limiting system protecting against denial-of-service attacks. Because our entire infrastructure is covered by automated testing and monitoring, we can roll out updates without risk. Our sophisticated workflow ensures that every change is vetted by multiple people in the team in staging environments before it makes it to our users. Reliability isn’t a feature—it’s part of our user promise, especially for creative projects that hold deep personal value for authors.

Without an advertising budget, SEO became crucial for discovery. How did you approach organic growth technically? 

We optimized the entire public-facing layer for search engines: server-side rendering, semantic markup, schema.org support, and automatic sitemap updates. Every tool, article, and tutorial is SEO-optimized and indexed right after publishing. Our system automatically generates educational content based on real user scenarios. Requiring no manual input, it consistently brings in over 80% of new traffic.

You developed your own checkout system rather than using third-party solutions. What drove that decision? 

The user journey has to feel seamless, and that was a core principle from the start. Every external redirect, especially during checkout, increases friction and risk. So we built our PCI-certified checkout experience embedded within the single-page app. This lets us control the interface, run A/B tests, and tailor flows to user behavior—all while maintaining security. By using smart payment retries, we also reduced payment collection failures by over 40% and significantly improved retention rates.

“We don’t just look for engineers—we look for product thinkers.” 

How do you systematize feedback from such a diverse global user base? 

User feedback became more than a source of ideas—it’s now part of our product cycle. We embedded feedback mechanisms directly into the platform, from widgets to ticket analysis. All data is aggregated, automatically labeled, and scored by relevance. Only the features that show true user value make it into development. This approach eliminates guesswork and makes our roadmap more accurate and predictable. For example, prioritised feedback flagged friction in organising creative work, so we revamped the entire writer workspace and shipped better organisation features, such as folders and projects with an intuitive and smooth navigation.

You built your own analytics platform rather than using existing tools. Why? 

Data is the backbone of our platform, and I embedded a data-driven decision-making culture across the team. We began with Google Analytics but quickly realised we needed deeper application-layer insight that off-the-shelf tools couldn’t provide, so I invested in building an in-house analytics system. Given we’re bootstrapped, I kept the build lean—reusing existing instrumentation, avoiding reinvention, and implementing only the metrics that mattered. The result was an analytics system that tracks interface behavior, subscription triggers and churn points, and friction areas. This gives us fact-based clarity.

How do you define your engineering culture, especially when building for creative professionals? 

We don’t just look for engineers—we look for product thinkers. In a small team, everyone needs to be autonomous and understand how their work impacts users. We automated everything from ticketing to deployment to reduce friction and focus on value. Our core principle is simple: every new feature must empower the user, not overwhelm them. That sometimes means saying no to corporate integrations or aggressive monetization, but that restraint keeps us affordable for new writers and builds trust.

Looking ahead, how do you see the relationship between technology and human creativity evolving? 

The future isn’t about technology replacing writers—it’s about creating more sophisticated creative partnerships. Writers will always be the source of a unique voice, emotional truth, and meaningful stories. Technology should amplify those strengths, not replace them. That’s why we focus on tools that enhance the creative thinking process rather than automating it away.

Our success without any advertising spend already proves something important: when you build technology that truly serves your users’ creative process, they become your best advocates. The writing community can tell when a product is built in their interest, and that trust directly translates to sustainable growth.

Have you read?
The Citizenship by Investment (CBI) Index evaluates the performance of the 11 nations currently offering operational Citizenship By Investment (CBI) programs: St Kitts and Nevis (Saint Kitts and Nevis), Dominica, Grenada, Saint Lucia (St. Lucia), Antigua & Barbuda, Nauru, Vanuatu, Türkiye (Turkey), São Tomé and Príncipe, Jordan, and Egypt.