TomSocial is the content module of the same operating system as TomPilot. It researches, writes and schedules on-brand content for your blog and social channels every week, and a person approves everything before it publishes. Same login, same governed platform, same standards.
TomPilot and TomSocial are separate products that share a single foundation. One secure sign-in, one database, one set of standards. Your data stays yours, scoped to your account, with the same audit trail and GDPR tooling behind both.
Add TomSocial to your existing TomPilot sign-in. No second login, no re-entering your business details.
Row-level isolation, an immutable audit log and UK data residency sit under both products, not bolted on per app.
The same considered, board-ready interface, so moving between strategy and content feels like one tool.
This is the heart of the link. With your opt-in, TomSocial is designed to read your TomPilot strategy, your vision, mission and goals, and use it as context when it drafts content. So what you publish stays on message with where the business is heading.
It is read-only and off by default. Your strategy can shape the content. The content can never change your strategy.
TomPilot already does part of this today. A Claude-powered operator lives in your Slack and creates and updates tasks and OKRs across seventeen tools, from a message or a voice note.
The direction is to extend that across the family, so you can shape both your strategy and your content by talking to an Ai assistant in plain English, whether that is Claude or the tools your team already uses. Every action would stay inside the same permissions, the same human approval gate and the same audit log that govern the rest of the platform.
Run a pilot on TomPilot, and bring TomSocial in on the same account when the time is right.