Your content now has a strategy brain behind it.
TomSocial is the content arm of the iS3 family. TomPilot is the strategy brain: vision, mission, goals and OKRs, alive in Slack. Same platform, same sign-in, same governed foundation. Adopt one and the next comes easier.
TomSocial and TomPilot run on a single platform: one Supabase project, one Basejump tenancy, one set of rules. You are not integrating two systems, you are switching on another part of the same one.
A single sign-in across the iS3 family, on one Basejump tenancy. Adopt TomSocial today and switch on TomPilot later, with no new login and no migration.
The same deny-by-default row-level security, the same immutable, append-only audit log, and UK data residency in London. Governance is shared, not re-bought per product.
The same components, the same plain-spoken interface and the same approval-first posture. Moving between content and strategy feels like one product, because it is.
Switch on Align to strategy and TomSocial is designed to read your TomPilot strategy, your vision, mission and goals, as read-only context for every draft. The result is content that pushes the strategy you have already set, not generic posts.
Illustrative. Strategy is read as read-only context, and the approval gate still publishes nothing without you.