Jasper ↗
Brand expressionKeep a consistent voice
Reusable context reduces repeated briefing
X wanted a hook. Xiaohongshu wanted the everyday problem first. LinkedIn wanted the backstory. I rewrote one product update seven times before I could post it everywhere. Finfold started there: AI drafts for each channel, and a person makes the final call.
One product update
seven rewrites
After shipping a product update, I wanted to post it on X, Xiaohongshu, WeChat, LinkedIn, Reddit and Product Hunt. Copying took seconds. Adapting took forever. A chatbot could draft, but every channel meant explaining the product, the audience and the platform’s unwritten rules all over again. One launch turned into seven rounds of prompt roulette, and the time I saved went straight into checking.
Each time I rewrote it, I noted what that pass was actually fixing. Two kinds of work kept showing up. Names, prices, dates and product limits could not change by a single word. Openings, structure, tone and image sizes had to change for every channel. Everything I designed in Finfold afterwards deals with how those two kinds of content live together.
Already in use
September 2026 · Product dataI mapped the core tasks, rebuilt the workspace layout, and designed the bilingual light and dark interface system. With the team, I carried the states nobody draws in a demo, like confirm, cancel and recover, all the way into the product.
Writing got faster
results didn’t follow
First I needed to know whether this was just my problem. A 2026 report from CMI and MarketingProfs put two numbers side by side. Most marketers using AI to write felt more productive. Fewer than four in ten felt their content performed better.
87%
Reported improved productivity
39%
Reported improved content performance
B2B marketers using AI for content creation · CMI / MarketingProfs · 2026 ↗
The gap between 87 and 39 is the work I wanted to do
The report covers 1,015 B2B marketers, primarily in North America, surveyed June 24–August 14, 2025. Percentages are self-reported by the subgroup using AI to create content.
One tool keeps the voice
another keeps the calendar
The best tools in the market each guard one end. Jasper keeps a brand sounding like itself. Buffer puts every channel on one calendar. The stretch in between, from one update to several drafts you can actually post, was still the user’s job to carry by hand.
Two real businesses
one publishing problem
My seven rewrites were a sample of one. In research I interviewed participants and followed two real clients: a bike retailer in Australia and a cross-border medical service. Very different businesses. Almost the same checkpoints between an idea and a published post.
Cycling retail · Australia

Cross-border medical services
Product context and intent
Opening, length, structure
Facts, tone, requirements
Drafts, brand, outcomes
Everyone re-explained their brand
no one wanted to post blind
The same lines kept coming up in interviews. Every session started with re-introducing the brand. Every channel needed its own pass. And at the last step, nobody wanted a machine to press publish for them. Those three remarks became three design principles.
Brand memory and rules come along to every session
Switch channels and edit each draft on its own
Review first, then hand off, with consequences visible
Six scattered chores
three connected steps
Broken down, one launch was six separate chores, bouncing between a chat window, a doc and a spreadsheet. The new structure has three steps, with brand memory running underneath all of them. The layout changed too. The old version split source, channels and results into three columns, leaving the draft, the thing you actually have to read word by word, a narrow strip.
Product update · Brand context
Content shaped for each channel
Human review · Saved content
Earlier layout01
Three equal columns squeezed the draft into a strip
Revised structure02
Inputs share one side; the draft gets the room
Keep the eye
on the draft
Mist and graphite themes share one hierarchy. Glass effects stay in navigation and controls. The writing area stays calm, because this is where people check every word, and any extra shine pulls attention away.
One prompt and three familiar starting points01 / 03
Channel variants and review controls in one view02 / 03
Account trends, goals, and the next action03 / 03
Visual language
Less border weight and fewer competing accents. Space, type, and a restrained green distinguish priorities.
What AI can carry
and the step that stays human
Getting AI to draft is no longer the hard part. The hard part is deciding what to hand over and which step must stay with a person. This chapter is a handful of those calls, including two things I deleted myself.
Early on, the brand check ran last. All eleven drafts were generated before the system warned that the tone might be off. The warning was right, it just came too late: people had already edited, and starting over felt like punishment. So I moved the rules before generation. How the brand is spelled, which numbers can’t change, which words are off-limits all go into context first, then get checked again afterwards.
Clear, credible, without overpromisingJoey Zhao · Person + brand
Context you repeat goes into memory; each task’s source stays on the workbench. Brand information lasts for months while sources change every time, so they live in separate places, and people can always see what the AI was working from.
Two drafts from the same saved content kit, for X and LinkedIn.
Finfold helps solo founders and small teams turn one product update into platform-specific content drafts.
Solo founders don’t hate writing. They hate writing the same update four different ways.
Open directly with the repeated work
02Number the workflow and its limits
Most solo founders publish one platform and quietly abandon the rest.
Not from laziness. From arithmetic.
Start with the founder’s situation
02Explain the workflow and design choices
The structure changes by channel; the facts and review controls stay in view
Neither change shows up in a screenshot, and the demo got slightly worse. I made them anyway. People spend years building an account, and one post with a wrong fact lands on them, not on us.
The first overview screen showed 42 posts queued, 11 in review, 18 scheduled. It made the product look mature. The numbers were demo data, so the whole row went. An honest empty state is better than a borrowed full one.
When the model failed, the system quietly slipped in a template and still showed success. Demos ran smoothly, and users had no way to tell which drafts the model wrote and which were filler. Now a failed card says why, can be retried on its own, and every successful result stays put.
The Agent opens with a prompt and common tasks. Supporting panels appear when needed, so the first screen stays approachable.
Editing and copying stay within reach. Secondary controls step back so the content remains the focus.
Show elapsed time and returned outputs; let people read what is ready
Keep cancellation, retry, and draft recovery within the workflow
Distinguish drafts, review, and publishing handoff so consequences are clear
Running all fourteen channels at once looks impressive, but waiting and failures rise together. Six is closer to a real launch batch, and still something a person can review properly.
Three tasks
aimed at where things break
Testing skipped the smooth path on purpose. Two of the three tasks were about what happens after something goes wrong: fixing a flawed draft, and leaving halfway then coming back. That is where AI products most often lose trust.
Checked first actions and channel selection
Checked editing controls and version understanding
Checked draft retrieval and recovery
A post that went out
and four honors
Once the product was live, Finfold content started going out for real. This Xiaohongshu post comes from an actual account in the project records. I show only the single post’s numbers and don’t credit them to the redesign.
Xiaohongshu · Design education
Aphrodite Design Study Abroad
Why do McDonald’s seats make you want to leave after 40 minutes?
Single-post metrics · September 2026 pitch deck
Inaugural Shanghai “AI + Consumption”
Innovation Competition
HuaQing PuZhi · SoloVerse
FC-OPC × Next iBot
Shanghai Creative Hackathon
X-Agent AI MCP Hackathon
Entry: Finfold Growth Mission
From project presentations and live demos
AI products are easy to design for the demo. The happy path is the easiest thing to draw and the easiest way to fool yourself. This time I spent most of my hours on the moments a demo never shows: the model is slow, a draft fails, someone leaves and comes back. None of that makes it on stage, but it’s exactly where people decide whether to trust the product with their account.
The team

Product direction and experience design

Core systems and implementation

Commercial strategy and growth

AI research and applications
Joey Zhao / AI Product Designer
Open to AI product design roles and project collaborations