BobaAI

BobaAI is a storytelling tool. Boba is a Thoughtworks experiment that combines web research, future scenario building, Playing to Win strategy prompts and illustrated storyboards in one ideation workflow for strategists and product teams.

Boba is a generative ideation co-pilot built as an experiment by Thoughtworks. It is aimed at strategists, researchers, product teams and consultants who need to turn early signals into a coherent story about what could happen next. The product is organized into four connected modes: research, scenarios, strategies and storyboards. Each mode takes a prompt and produces material you can push further, so the workflow feels less like a single answer machine and more like a sequence of drafting sessions with a well read colleague. Research is the entry point. Boba searches the web for articles and news to answer qualitative questions, then analyzes and summarizes what it finds, including longer items such as earnings call takeaways. From there you can dig deeper on a specific signal or discuss an article before moving on. The scenarios mode takes a strategic prompt and brainstorms plausible futures, then explores the opportunities, threats, probability and plausibility attached to each one. Strategies applies the Playing to Win framework, generating where to play and how to win choices and the key questions a team should weigh against a given scenario. Storyboarding closes the loop. Boba can build illustrated narratives for current or future state scenarios, brainstorm story driven points of view and pitches, and generate scenes that describe a customer journey. The script and visual style can be edited, and storyboards can be generated directly from scenarios you have already produced. The tool suits innovation and foresight work, early product discovery and workshop preparation, where the value is in breadth of options rather than finished deliverables. The positioning is worth noting. Boba is explicitly labeled an experiment, it gates access through a login and a waitlist, and the homepage does not publish pricing, integrations or a support program. Teams that need procurement guarantees or documented service levels should treat those gaps as open questions before committing. Against general purpose chat assistants, the difference is the structured pipeline from evidence to scenario to strategy to visual narrative.