Shared rooms, not private AI tabs.
People and AI teammates work from the same room context so decisions, updates, and contributions stay visible.
What I'm building
Sociail.
Think better, together.
A shared workspace where people and AI teammates work together in the same context. This is the founder-side bridge - why I'm building it, how it connects to Shared Intelligence, and where the practical product story belongs. For the company, team, and product proof, go to Sociail.com/about.
Request-led Early Access opens June 1, 2026. Building toward a small, opinionated first cohort.
Why this exists here
The work is fragmented. The AI is private.
AI collaboration is broken when every person has their own AI tab, their own context, and their own conversation history. Nobody is really working together. Not the people. Not the AIs.
Sociail exists to make AI part of shared work instead of a solo side channel. The practical version starts with rooms where people, AI teammates, context, artifacts, and next steps can stay together.
The deeper claim - the one the essays defend - is that most of the value of AI at work is not faster solo prompting. It's whether your team's context, judgment, and follow-through compound across the people and AI teammates doing the work. That's the category I keep calling Shared Intelligence, and Sociail is its product implementation.
What belongs on this page
Four claims, in this, not that form.
Shared Intelligence is the broader pattern. Early Access is the focused proof surface. Four sharp distinctions define what Sociail is - and what it deliberately isn't.
Room-aware AI teammates, not isolated assistants.
AI teammates participate with the work in view - helping compare, draft, summarize, and prepare next steps.
Durable outputs, not disposable chats.
Briefs, plans, and decisions stay attached to the room that shaped them instead of disappearing into prompt history.
Bounded follow-through, not runaway autonomy.
Sociail is designed around visible trust boundaries, review, and approval-aware next steps.
The company About page can carry the team story and product proof. This founder page should carry the thesis, the tradeoffs, and the route into the deeper writing.
Founder view
Why I keep writing about rooms.
The operator lesson behind Sociail is simple: when work gets complex, coordination becomes the product. AEFIS taught me that durable teams need shared context, visible ownership, and accountable follow-through long before AI enters the picture.
AI makes that lesson sharper. If the intelligence is private, the team keeps reconstructing the work. If the intelligence belongs in the room, the work can compound.
That is why this site spends more time on the thesis than on the feature list. For team culture, company story, and product examples, the better destination is Sociail.com/about.
Team culture
Are you a Sociail Transformer or Regenerate?
The Sociail team is distributed, practical, and still very human. Building AI-native collaboration is serious work; it also needs enough team culture to keep the humans recognizably human.
Where we are
Request-led Early Access opens June 1, 2026.
The infrastructure is running. The first collaboration architecture is in place. The product surface is being polished through active Design Partner projects with teams already doing serious AI-heavy work.
Stage
Request-led Early Access opens June 1Design Partners
Active Design Partner projectsInfrastructure
Self-operated on-prem GPU clusterOfficial Early Access signup is handled on Sociail.com/early-access when you are ready to request access - that's the one door for the first cohort.
Where to go next
Two sites, two jobs.
Founder view / sualp.com
This site.
The thinking behind Sociail - the thesis, the essays, the arguments about why shared context matters, and the operator path that led here.
Read the essaysProduct view / sociail.com
Sociail.com
The company and product view - how Sociail works, why the team is building it, what's in Early Access, and how to request access.
See the company page