TomSocial
Strategy + content

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.

Explore TomPilot →See how they link
One platform
Two products on one platform, not two tools bolted together

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.

One account

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.

One governed foundation

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.

One design language

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.

Where they meet
Opt-in · read-only
Content that follows the plan.

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.

Opt-in and off by default. Nothing is shared between the products until you turn it on.
Read-only by design. TomSocial reads the strategy as context and never writes back to TomPilot.
The approval gate is untouched. A person still approves every post, and nothing publishes without that yes.
app.tomsocial.co.uk/create
Create a post · LinkedIn
Five questions to ask before you commission a bespoke kitchen. Number three protects your budget and your timeline.
Align to strategy
Pulling pillars & goals from TomPilot
PillarDirect retail growth
Goal22 kitchens / month
From TomPilot · read-only

Illustrative. Strategy is read as read-only context, and the approval gate still publishes nothing without you.

On the roadmap
One operating system, driven in plain English.

The direction is a single estate you can run by asking. TomPilot is already part of the way there, and TomSocial follows the same path.

Live in TomPilot
A Claude operator in Slack

TomPilot's Claude operator already lives in Slack, creating and updating strategy, tasks and OKRs across seventeen tools. Real natural-language control, working now.

On the roadmap
That control, across the family

The vision is to extend natural-language control across the iS3 family, through Claude or the tools your team already uses, always inside the same permissions, the same approval gate and the same audit log.

Where TomSocial stands today: it uses Ai to draft content, with no conversational agent and no automated publishing. Those are on the roadmap, and the approval gate is mandatory and stays. We describe what is built as built, and what is planned as planned.

Adopt one. The next comes easier.

Start with content that always ships, then switch on the strategy brain when you are ready. One platform, one login, one governed estate.

Explore TomPilot →Start a trial