Marlowe spent nine years running editorial operations for content agencies before starting Voyepi Tawano. Much of the platform's Kanban structure and review queue logic came directly from processes tested across several client teams with very different publishing cadences. Marlowe still spends time each quarter sitting in on customer workflow reviews to see where the board gets stretched or ignored.
Behind the Platform
Built by someone who has sat in the editor's chair
Voyepi Tawano started as an internal tool for a mid-sized content team that was tired of losing track of drafts between a spreadsheet, a shared doc, and a group chat.
Origin
A workflow problem, not a software idea, came first
Before Voyepi Tawano existed, its founder managed editorial operations for a content agency handling several client publications at once. The recurring problem wasn't a lack of talented writers. It was that no single view showed where a story actually stood: whether the brief was done, who owned the draft, whether an editor had already looked at it, or whether social posts were ready to go out alongside it.
The first version of the board was a set of shared spreadsheets stitched together with color-coded tabs. It worked, barely, for a few months. Then a client asked for weekly SEO gap reports, another wanted a formal review step before anything published, and the spreadsheet system stopped scaling.
What followed was a slow rebuild: first a simple Kanban board, then a brief template that pulled in competitor headings automatically, then a review queue so editors stopped hunting through email for the next draft. Publishing and social scheduling were the last pieces added, once it became clear that an article's promotion plan kept getting separated from the article itself.
Voyepi Tawano is that internal tool, refined and made available to other editorial teams facing the same coordination problem, whether they are a two-person newsletter operation or a twenty-writer content department.
The Team
The people shaping how the platform works
Click any card to read more about each person's background and what part of the platform they focus on.
Priya worked as a managing editor for a regional news outlet for over a decade before joining the team. She designed the review queue's inline-comment system after years of watching feedback get lost across scattered email threads. Priya focuses on how the review and revision-request features hold up under tight daily deadlines rather than slower long-form cycles.
Desmond spent several years building content briefs by hand for freelance writer teams, a process that could take an hour or more per article. He now oversees how the brief builder gathers competitor headings and subtopics, and is careful that the tool presents gaps as reference points for writers rather than instructions to follow automatically.
Renata previously managed social calendars for a network of lifestyle publications, coordinating launch posts across several accounts by hand. She built the calendar's link between article publish times and staggered social post scheduling, and continues to refine how the platform handles time zone differences across distributed teams.
Approach
What guides how the platform gets built
New features generally come from a workflow gap someone on the team observed directly, rather than from a general industry trend. The dashboard reports what has happened; it does not tell a team what to publish next or promise a particular result from any workflow change.
Small teams and larger departments use the platform differently, and that shapes how columns, briefs, and the review queue can be configured. The goal is flexibility around a process a team already has, not a rigid structure everyone must adopt exactly as built.