Graduation, Not Leaving — Why Tasukiba, an AI Operations Secretary, Chose Discord
Why Discord, not Slack
For a business-leaning service, the obvious community platform is Slack.
Tasukiba deliberately chose Discord.
The reason is one line. Tasukiba’s community is for community formation, not for business updates.
If you’re doing business updates, Slack is fine. But the temperature Tasukiba wants to gather isn’t the tidy business-meeting temperature.
A half-step over the business line, flat conversation, peers across organizations.
For that, Discord’s “per-server cultures,” “casual voice channels,” and “flexible role-based permissions” fit better than Slack.
This is Chapter A’s closing post. The topic is community design and “graduation culture.”
What I want talked about
The conversations I want to host on Discord look like:
- Development behind-the-scenes — “I’m building this feature right now”
- Use-case sharing — “we use this feature in this unusual way”
- Feature requests — “we’d love a feature that does X”
- Casual talk — “had a wild project this month”
- Personal context — “family stuff, might be quiet for a while”
Roles flattened, hierarchy off the table. And if the conversation grows into actual friendship offline, that’s the dream. That’s the honest version.
A “third place” — not home, not work
Tasukiba wants to become a third place, beyond home and work.
Calling a business-SaaS community a “place to settle” is a minority framing. The mainstream framing is “support overflow” or “feedback collection.”
Tasukiba deliberately stands half a step away from that.
Support and feature requests will eventually live in a dedicated channel separate from Discord. If support fills the Discord, the community temperature gets diluted.
| Platform | Role |
|---|---|
| Discord | Community, conversation |
| Dedicated support (mid-term TODO) | Inquiries, support, feature requests |
That’s the eventual split.
”Graduation,” not “leaving”
Here’s the part I care most about.
At Tasukiba, when a member moves on, I want to call it “graduation,” not “leaving.”
When a member who’s been with the project moves toward independent development, founding their own company, or another challenge, that should be celebrated as a successful graduation.
The culture isn’t “leaving = failure.” It’s “you got something here, and you’re going somewhere with it.”
Why I’m so attached to the word “graduation”
In business-SaaS communities, I’ve watched a lot of people feel pressure to “stay here forever, or else.”
The community is supposed to have nothing to do with work obligations, and yet leaving it ends up labeling someone as “the one who walked away.” I want to remove that structure.
Replacing one word — “leaving” with “graduating” — lowers the exit barrier dramatically. And paradoxically, a community with a low exit barrier becomes more comfortable to stay in.
This sounds contradictory. It isn’t. It’s the same shape as the “anxiety zone” vs. “learning zone” distinction in Psychological safety isn’t reached by “knowing it”. Only a place you believe you can leave can really hold you.
The reason to stay shifts from obligation to genuine preference. That’s what a graduation-culture community is.
A place to meet what you want to do
I also want the people around Tasukiba to find something they want to do.
I myself only got to “I could build a SaaS” because of my previous product-development job. I want the next people, too, to discover what they want to try.
Through Tasukiba you might:
- Start your own indie project
- Found a company
- Keep building Tasukiba with us long-term
Any of those is a “next step” Tasukiba can be the catalyst for. That’s a place I want to be.
Keep the face of the operator visible
On Discord, I plan to post as a fellow member, not as a remote authority.
I won’t say things like “this is the operator account — please direct inquiries elsewhere.” I’ll share development progress, design dilemmas, post-release impressions. As much as possible.
This is my way of respecting the people who use the service.
Business SaaS often turns the operator into a faceless organization. Because Tasukiba starts as indie development, I want to keep the operator’s face visible for as long as I can.
Three lines for the community
Compressing Chapter A’s closing post:
- Choose Discord — for community, not for business updates
- Don’t mix in support — that’s a separate channel
- Build a graduation culture — lower the exit barrier, raise the comfort of staying
There are business SaaS with communities attached. There are very few business SaaS that frame the community as “a place unrelated to work.”
That, too, is part of what makes Tasukiba shaped differently.
Chapter A (origin and philosophy) is now done — six posts. Chapter B starts next, switching to product, screen-by-screen. The next post is the June 1, 2026 release announcement — the service in full.
Related posts
- Meet the Tasuki Owl — why Tasukiba’s mascot is an owl — series part 5, mascot
- Psychological safety isn’t reached by “knowing it” — “anxiety zone” vs. “graduation culture”
- Reteal Organizations — what stops “self-managing teams” in the first place — designing communities that run themselves
About Tasukiba
Public release: June 1, 2026. The product page covers the service overview and the Discord invite plan.
