Case Study

Kento

An AI that writes your book as you read it. Guide the story paragraph by paragraph with simple nudges; Kento handles the prose, the pacing, and the plot twists. Every story is personal, every book is yours.

PROJECT SPECS
Icon
Client:
Personal Project
Icon
Year:
January 28, 2026
Icon
Role:
Owner and Designer
Case Study

What is Kento?

Kento is an AI powered co-writing app that writes personalized books with you, one paragraph at a time. Simply set your genre, tone, and mood, then guide the story forward with short nudges while Kento crafts the prose. Whether you're exploring fantasy worlds, unraveling a mystery thriller, or shaping a memoir, Kento turns your imagination into a book that's entirely your own.

The Problem

People with rich story ideas and creative energy struggle to turn them into finished narratives. Existing tools are either too rigid (Scrivener, Notion), too generic (ChatGPT prompts), or too niche (Everweave's DnD-only focus). Readers who want a personalized, immersive story experience have nowhere to go.

The Opportunity

The intersection of AI-generated content and interactive storytelling is growing rapidly, yet no product has claimed the "personalized book for general audiences" space. Kento enters this gap with a reader-first framing, not a writing tool, not a game, but a living book that grows with the reader's choices.

User Personas & Target Audience

Jobs-To-Be-Done

Overcoming the blank page

"When I sit down wanting to read something made for me, I want the app to spin up a premise from a few preferences, so I can dive in without planning anything."

Guiding without fully writing

"When I have ideas about what should happen next but don't want to draft full prose, I want to nudge the story with short instructions so the app does the heavy lifting."

Experiencing a personal book

"When I'm tired of static books and generic AI outputs, I want a single evolving story that remembers my preferences and feels like a long-form book made for me."

Filling short downtime meaningfully

"When I have 10–20 minutes, I want to continue my story from where I left off so those moments feel creative rather than wasted."

Practicing storytelling with low pressure

"When I want to improve at storytelling, I want to experiment with tone and plot decisions one paragraph at a time without starting from scratch."

Core Features & MVP

Aesthetic and Visual Direction

Sleek, modern, typographic — inspired by Notion, Arc, Apple, and editorial book design.

Assumptions & Key Risks

Top assumptions to validate
Users enjoy a conversational, paragraph-by-paragraph guidance loop more than one-click generation.
The "reader-first" framing resonates more broadly than a "writer tool" framing.
Users will return across multiple sessions to build long-form stories.
Romance-driven readers are a strong early adopter segment.

Top risks to mitigate
AI outputs feel repetitive or lose continuity in longer stories (context management critical).
Users feel the AI is "taking over" their story (mitigated by Draft vs Canon mode).
Free AI tools (ChatGPT) feel "good enough," making subscription justification hard.
Addressable market may be narrower than expected if DnD/fantasy readers are the primary early adopters.

Key Learnings

Framing changes everything
The single biggest design decision wasn't a UI choice, it was reframing the product from a "writing tool" to a "reading experience." Positioning Kento as "a book that writes itself as you read it" opened the product to a much broader audience than "AI writing assistant" ever could. This taught me that the mental model you give users before they open the app shapes every interaction inside it.
The best products live in the gap between existing ones
Kento wasn't born from scratch, it came from mapping what Everweave did well (immersive DM-style storytelling loop) against what it couldn't do (serve general book readers, novelists, and non-fiction writers). Studying the competitive landscape revealed a specific, underserved space that no one had claimed yet. I learned that the most valuable design opportunities often live in the intersection of two adjacent products, not in entirely new territory.
The core loop is the product
In an app like Kento, the core interaction loop, Read → Nudge → Draft → Approve → Repeat, is essentially the entire product. Getting that loop right matters more than any individual screen or visual detail. I learned to design from the loop outward rather than from the screen inward: nail the feeling of one turn first, then design the surrounding context (library, onboarding, chapter breaks) to support it.
Differentiation requires saying no
During ideation, Kento could have included character sheets, dice mechanics, branching tree visualizations, social sharing, and multiplayer co-writing. Each feature had a valid use case. But adding them would have diluted the core identity, a sleek, reader-first book experience, and pushed Kento back toward being another RPG tool or writing app. I learned that strong product differentiation requires deliberate restraint, and that saying no to good ideas is as important as generating them.
Starting with strategy makes design faster
Because I invested time upfront in personas, JTBD, assumptions, competitive analysis, design principles, and a product brief before touching any UI, every design decision downstream had a clear reason behind it. There was no "why are we doing this again?" moment. I learned that strategic groundwork doesn't slow design down, it accelerates it by eliminating ambiguity and second-guessing at every screen.