Tellshift

Your work. Consistent profiles and content.

Explore the studio with several projects, their sources, profiles and history.

A concrete starting point

Start with the job in front of you.

Three connected examples, each with its own saved progress. A real decision, a draft you can change, and a next step to keep.

I’m taking part

Make the working demo easy to understand.

Set the brief, respond to a build setback, prepare the story and choose the test you want after the event.

Try this journey

I’m organizing

Bring the event together through its teams.

Set the event brief, inspect what teams allow you to use, prepare an official story and give the next step an owner.

Try this journey

I’m building in public

Turn progress into a better conversation.

Choose one real question, inspect a work signal, edit a useful update and turn the response into a next decision.

Try this journey

Try the workspace

Your context. A working studio.

Choose a starting point, then configure projects, prepare profiles, create content and inspect its history in one workspace.

Interactive example · no account required

This workspace is saved in this browser. Imported files remain on this device. No social account is connected.

Choose a context and workstyle inside the studio. Each combination keeps a separate local workspace. Examples are fictional; your own workspace starts empty.

The workspace interface is currently in English. Content can be prepared in English or French.

Also explore an illustrated campaign

From project to content

One project. More than one way to explain it.

The message and format change with the people you want to reach. Choose the channels that serve your goal.

Choose a format

LinkedInXInstagramEmail

From the same project experience

Explore the content

Fictional example · Short preview; the full format is in the explorer.

Fictional example. No content is published.

Explore the full example

The example in detail

Fictional example · A consultancy uses what it learned from a project involving customer orders to prepare a campaign.

ContributorFormat

#explorer .explorer-interactive { display: none !important; }

Read the complete example

Sources, full drafts, account scenarios, and results are available in this reading view. Open the part you want to inspect.

Fictional consultancy, sources, account, and activity. This example publishes nothing and sends no messages.

Sources and channel formats

Founder

The customer wanted to keep the ERP. Their concern was who would check the orders that needed review. We discussed that responsibility before agreeing on the automation scope. The buying decision included a decision about how the team would work.

Fictional remarks, created for this example.

LinkedIn post

X thread

Draft title for review: The question before the software

Instagram carousel

Email outreach

Technical lead

The model read the order correctly. It matched the wrong catalog item. We added review for uncertain matches. Reading the document and choosing the correct reference were separate steps in this project.

Fictional remarks, created for this example.

LinkedIn post

X thread

Draft title for review: Correct reading. Wrong reference.

Instagram carousel

Email outreach

Delivery lead

An order flagged for review only moved when somebody knew they owned it. We defined who checks it and what happens while it waits. We also agreed how ownership passes to the next shift. The review step needed a practical handover.

Fictional remarks, created for this example.

LinkedIn post

X thread

Draft title for review: A review flag needs a next owner

Instagram carousel

Email outreach

Account plan and responses

Fictional account, people and activity. Changing this example sends no messages.

Awaiting response

A distributor has announced a second warehouse. Its order-handling needs have not been confirmed.

Conversation owner: Consultancy founder

Example day 1
Sent · Example
Channel: Email
Sending identity: Founder
Recipient: Operations lead
Ask how uncertain orders will be reviewed during the warehouse rollout.
Example day 4
Scheduled · Example
Channel: LinkedIn · Manual task
Sending identity: Founder
Recipient: Operations lead
Review whether a relevant, appropriate LinkedIn follow-up would add anything useful.
Example day 7
Owner review required
Channel: Email
Sending identity: Technical lead
Recipient: Technical / IT lead
Review whether to involve a technical contact, using the catalog-matching example.

The timing illustrates a plan; it is not a recommended universal cadence.

This is an illustrative plan. The LinkedIn step is a task for a person; no platform connection or automated message is demonstrated.

A contact replies

A distributor has announced a second warehouse. Its order-handling needs have not been confirmed.

Conversation owner: Consultancy founder

Example day 1
Reply received · Example
Channel: Email
Sending identity: Founder
Recipient: Operations lead
Ask how uncertain orders will be reviewed during the warehouse rollout.
Example day 4
Paused for the conversation
Channel: LinkedIn · Manual task
Sending identity: Founder
Recipient: Operations lead
Review whether a relevant, appropriate LinkedIn follow-up would add anything useful.
Example day 7
Paused for the conversation
Channel: Email
Sending identity: Technical lead
Recipient: Technical / IT lead
Review whether to involve a technical contact, using the catalog-matching example.

The timing illustrates a plan; it is not a recommended universal cadence.

This is an illustrative plan. The LinkedIn step is a task for a person; no platform connection or automated message is demonstrated.

The company asks to stop

A distributor has announced a second warehouse. Its order-handling needs have not been confirmed.

Conversation owner: Consultancy founder

Example day 1
Company-wide stop request · Example
Channel: Email
Sending identity: Founder
Recipient: Operations lead
Ask how uncertain orders will be reviewed during the warehouse rollout.
Example day 4
Stopped
Channel: LinkedIn · Manual task
Sending identity: Founder
Recipient: Operations lead
Review whether a relevant, appropriate LinkedIn follow-up would add anything useful.
Example day 7
Stopped
Channel: Email
Sending identity: Technical lead
Recipient: Technical / IT lead
Review whether to involve a technical contact, using the catalog-matching example.

The timing illustrates a plan; it is not a recommended universal cadence.

This is an illustrative plan. The LinkedIn step is a task for a person; no platform connection or automated message is demonstrated.

Observations and the next draft

All figures, comments and activity below are fictional examples, not customer results.

Back to the observations

LinkedIn · Technical contributor · First 72 hours · Illustrative snapshot

Impressions: 1,200
Reactions: 24
Comments: 4

Illustrative aggregate counts. Comments are not unique people; reactions do not identify buyers or establish buying intent.

One example audience question

How do you hand a flagged order over when the next shift starts?

Observed response

The displayed question asks how responsibility passes to the next shift. It gives the team a specific topic to examine.

Hypothesis to test

A practical handover example may answer this reader’s question. The team can review a draft before deciding whether to test that angle.

Next draft for review

Use the delivery contributor’s source to prepare a handover example. Review it before any publication, then decide what response to observe.

These observations suggest a next test. They do not establish buying intent or prove a sales effect.

Inspect the next draft

LinkedIn · Technical contributor · First 72 hours · Illustrative snapshot

Next draft for review · For editorial review

One example audience question

How do you hand a flagged order over when the next shift starts?

Observed response

The displayed question asks how responsibility passes to the next shift. It gives the team a specific topic to examine.

Hypothesis to test

A practical handover example may answer this reader’s question. The team can review a draft before deciding whether to test that angle.

These observations suggest a next test. They do not establish buying intent or prove a sales effect.

Example: data unavailable

LinkedIn · Technical contributor · First 72 hours · Illustrative snapshot

Impressions: Not available
Reactions: Not available
Comments: Not available

Illustrative aggregate counts. Comments are not unique people; reactions do not identify buyers or establish buying intent.

Results have not been collected for this example.

Add observed results and responses before making a recommendation from them.