How ASI:One Ships On-Brand Launches With Flockx
A sibling team in the Fetch.ai ecosystem launched Spheres with a founder announcement, a hub-and-spoke blog cluster, and one-shot on-brand imagery. They produced all of it on Flockx. Here's what that looked like from the inside.
Product launches break brands. Not on purpose. Every channel wants its own piece, every piece wants its own revision, and somewhere in the shuffle the voice drifts. A launch is the moment your brand meets the most people at once. It's also the moment consistency is hardest to hold.
The ASI:One team knows this pressure well. Spheres, their new community feature, gives every community its own AI partner that works alongside the people in it. Launching it meant a founder announcement on X and LinkedIn, a coordinated set of blog posts, and fresh imagery for all of it. Under a tight timeline. With a feature name that was still moving.
They ran the whole content push on Flockx. The launch went out on brand, in one voice, across every channel, and the rename didn't break a thing. Here's what that looked like.
Why This Case Study Is Different
ASI:One and Flockx are siblings in the Fetch.ai ecosystem. When a team inside your own ecosystem chooses your platform for their launch, that's the real test. They know every alternative. They still picked Flockx.
A Hub-and-Spoke Blog Cluster
Launches used to mean one big post and hope. The ASI:One team built a cluster instead. A hub post, "Spheres: A Home for Your Community, With a Partner Built In," anchors the launch. Around it sit companion posts for the two audiences the feature launches with first: university clubs and sports fanbases. A six-post thought-leadership series on why community platforms break down gives the launch its editorial spine.
Every post links back to the hub. The hub links out to every spoke. A reader who lands on the series from a search finds the launch. A reader who starts at the launch finds the series. Each piece feeds the others.
What the cluster holds together
- • One launch hub that tells the full story of what Spheres is and why it exists.
- • Two companion posts that translate the launch for the first audiences who will actually use it.
- • A six-post series that earns attention on its own merits while pointing back to the launch.
- • Cross-links in every direction, so any entry point leads a reader to the whole story.
Building a cluster like that by hand means a dozen open tabs, three tools, and a spreadsheet to track which post links where. With the whole cluster in one place, the structure held itself. Each post was drafted, reviewed, and published from the same seat, with the same voice rules applied to every one.
One-Shot, On-Brand Imagery
Every blog post needed a hero image. That's normally where launches quietly fall apart. The visual brief gets written once and then forgotten, the images drift from the brand, and someone burns an afternoon regenerating them.
The ASI:One team wrote their visual brand guidelines down first: 3D cartoon characters, mint green glow, navy accents, people at the center with the AI as a quiet partner. Then they generated every hero image through Flockx with their brand profile applied. The images came out on brand the first time. No iteration loop. No regenerating until midnight until the glow looks right.
Why the First Shot Landed
The images weren't lucky. The brand profile held the visual identity, and the written guidelines pinned the style. When both are in place before you generate, the first output is the right output.
The Announcement Came From the Founder
The launch didn't open with a blog post. It opened with Humayun Sheikh, Founder of Fetch.ai, announcing Spheres on X and LinkedIn. The posts were drafted in his voice, reviewed by the team, and published. The blog cluster followed.
What's easy to miss is why the announcement and every blog post said the same thing the same way. The naming and messaging rules were written down before any content was generated. The announcement, the hub, the companions, and the series all drew from the same source, so they all sounded like one launch, not five documents that happened to ship the same week.
The Real Test: A Rename Mid-Flight
Here's the part of the story that would have sunk a normal launch. The feature's name moved. It started as an internal working name, went through two candidate names in review, and landed on Spheres.
Done by hand, that rename means reopening every draft, every announcement, every image brief, and hunting the old name out of each one. Something always gets missed. A stale name ships to the wrong channel and becomes the screenshot everyone shares.
Because the naming and messaging guidelines lived in versioned files rather than in people's heads, the rename propagated across all in-flight content in one pass. The old name left every draft. The new name arrived everywhere at once. The voice stayed consistent through the change, which is the hardest moment to keep a voice consistent.
The Lesson From the Rename
Brand rules only work when they're written down and versioned. When the name moves, the rules move with it, and everything downstream inherits the change. The alternative is institutional memory, which is another way of saying someone forgets.
What the Team Accomplished
Step back and look at what the ASI:One team shipped. A founder announcement on two channels, in the founder's voice. A hub-and-spoke blog cluster that reaches the first audiences and earns search traffic along the way. A full set of hero images, on brand, generated on the first pass. And a rename that rolled through all of it without a single stale reference.
The team didn't manage tools. They didn't herd freelancers. They wrote down how they wanted to sound, described what they needed, and reviewed what came back. Flockx handled the production. That's the whole trade: write the rules once, then publish instead of iterate.
The next time your launch date lands before your feature name does, that's the launch you want.
Run your launch on Flockx
Write your brand rules once. Describe what you need. Ship an announcement, a blog cluster, and imagery that all sound like one launch.