One brief. A different LinkedIn post for every employee, in their own voice.
Postfox writes each person's post from the brief and from what they told it about their own work. They approve it, edit it or decline it, and nothing goes out until they approve it.
This month we publish The Handoff Report. Over the last quarter we sat in on 40 handoffs from sales to customer success at companies that use Acme, and read the notes each one produced.
What we found: most handoff notes are written for the person sending them. They record what was sold, not what the customer needs to happen in their first week. The customers who reached their first result fastest had one thing in common: before the kickoff call, someone asked what the customer expected to see working by the end of week one.
We don't want anyone to summarise the report. We want each person to talk about handoffs as they see them in their own job.
Acme · by Jordan Lee
LM
Lou Martin
Product Manager
Booked
I watched recordings of six onboarding sessions recently to decide what we build next quarter. I expected to hear feature requests. Mostly I heard customers explaining their own goals again to someone new, because those goals had gone missing somewhere between the contract and the first call.
MT
Mei Tanaka
Staff Engineer
Waiting for Mei
I was building the part of the product that turns a sales call summary into the first checklist a new customer sees.
One detail to check before Mei approves
Detail: The information was simply absent,
You told us the notes never say what the customer is trying to get done, not that the information was simply absent.
AD
Ana Duarte
Head of Sales
Published
I spent most of last week on two renewals. In both cases the thing they were unhappy about was something we promised during the sale and never wrote down for the customer success team.
One brief
The handoff report
This month we publish The Handoff Report. Over the last quarter we sat in on 40 handoffs from sales to customer success at companies that use Acme, and read the notes each one produced.
What we found: most handoff notes are written for the person sending them. They record what was sold, not what the customer needs to happen in their first week. The customers who reached their first result fastest had one thing in common: before the kickoff call, someone asked what the customer expected to see working by the end of week one.
We don't want anyone to summarise the report. We want each person to talk about handoffs as they see them in their own job.
Acme · by Jordan Lee
becomes a different post for each person
LM
Lou Martin
Product Manager
Booked
I watched recordings of six onboarding sessions recently to decide what we build next quarter. I expected to hear feature requests. Mostly I heard customers explaining their own goals again to someone new, because those goals had gone missing somewhere between the contract and the first call.
MT
Mei Tanaka
Staff Engineer
Waiting for Mei
I was building the part of the product that turns a sales call summary into the first checklist a new customer sees.
One detail to check before Mei approves
Detail: The information was simply absent,
You told us the notes never say what the customer is trying to get done, not that the information was simply absent.
AD
Ana Duarte
Head of Sales
Published
I spent most of last week on two renewals. In both cases the thing they were unhappy about was something we promised during the sale and never wrote down for the customer success team.
Same caption, ten profiles. Their network reads it as spam.
You end up chasing people in Slack to share the company page's posts.
By month two, it's the same three people posting.
Employee advocacy without the copy-paste.
The usual way
10 people, 1 post
AD
Ana Duarte
Head of Sales
Excited to share The Handoff Report! We sat in on 40 sales-to-CS handoffs to find out what makes onboarding work. Read it here: acme.example/handoff-report #CustomerSuccess #Onboarding
MT
Mei Tanaka
Staff Engineer
Excited to share The Handoff Report! We sat in on 40 sales-to-CS handoffs to find out what makes onboarding work. Read it here: acme.example/handoff-report #CustomerSuccess #Onboarding
×10
SR
Sam Rivera
Customer Success Manager
Excited to share The Handoff Report! We sat in on 40 sales-to-CS handoffs to find out what makes onboarding work. Read it here: acme.example/handoff-report #CustomerSuccess #Onboarding
LM
Lou Martin
Product Manager
Excited to share The Handoff Report! We sat in on 40 sales-to-CS handoffs to find out what makes onboarding work. Read it here: acme.example/handoff-report #CustomerSuccess #Onboarding
Everyone is handed the same words.
With Postfox
1 brief, a post each
AD
Ana Duarte
Head of Sales
I spent most of last week on two renewals. In both cases the thing they were unhappy about was something we promised during the sale and never wrote down for the customer success team.
MT
Mei Tanaka
Staff Engineer
I was building the part of the product that turns a sales call summary into the first checklist a new customer sees.
+8 more
SR
Sam Rivera
Customer Success Manager
I ran four kickoff calls recently. On three of them, the customer opened with a question I should have known from the handoff and didn't.
LM
Lou Martin
Product Manager
I watched recordings of six onboarding sessions recently to decide what we build next quarter. I expected to hear feature requests. Mostly I heard customers explaining their own goals again to someone new, because those goals had gone missing somewhere between the contract and the first call.
Each person gets a post of their own, from the same brief, in their own voice.
What Postfox wrote
One brief, three people, three posts.
A sample brief from a fictional company, and the post Postfox wrote from it for each of three people on its team. Nothing was edited by hand.
The brief
The handoff report
This month we publish The Handoff Report. Over the last quarter we sat in on 40 handoffs from sales to customer success at companies that use Acme, and read the notes each one produced.
What we found: most handoff notes are written for the person sending them. They record what was sold, not what the customer needs to happen in their first week. The customers who reached their first result fastest had one thing in common: before the kickoff call, someone asked what the customer expected to see working by the end of week one.
We don't want anyone to summarise the report. We want each person to talk about handoffs as they see them in their own job.
Written by Jordan Lee, Acme
A different post for each person, built from what they told Postfox about their own work.
AD
Ana Duarte
Head of Sales, Acme
I spent most of last week on two renewals. In both cases the thing they were unhappy about was something we promised during the sale and never wrote down for the customer success team.
I went back through my notes from those deals. The promises were there, in my handwriting, in a notebook nobody else can read.
We are changing how my team documents a deal before it moves over.
At Acme, we sat in on handoffs and read the notes they produced. What we found is in The Handoff Report. It is worth reading if you have ever gone back through your own records and found something that should have travelled further than it did.
https://acme.example/handoff-report?utm_source=linkedin&utm_medium=social&utm_campaign=the-handoff-report&utm_content=ays43s
Angle: Promises made but never written down
MT
Mei Tanaka
Staff Engineer, Acme
I was building the part of the product that turns a sales call summary into the first checklist a new customer sees.
My assumption was that parsing would be the hard part. It wasn't.
The hard part was that half the notes never said what the customer was trying to get done. The information was simply absent, which meant there was nothing to turn into a checklist.
At Acme, we published a report this month on handoffs from sales to customer success, and what we found in the notes people actually write.
We added one required field to the deal form instead of writing more code.
If you work anywhere near this problem, it is worth reading: https://acme.example/handoff-report?utm_source=linkedin&utm_medium=social&utm_campaign=the-handoff-report&utm_content=h6r8q4
One detail to check before Mei approves
Postfox could not trace these to the brief or to anything Mei told it, so it asks Mei first.
Detail: “The information was simply absent,”You told us the notes never say what the customer is trying to get done, not that the information was simply absent.
Angle: When the notes have nothing to parse
SR
Sam Rivera
Customer Success Manager, Acme
I ran four kickoff calls recently. On three of them, the customer opened with a question I should have known from the handoff and didn't.
The fourth was different. Before the call, the account executive had written one line at the top of the handoff notes: what the customer's VP needed to see working by Friday. The whole call ran differently because of it.
At Acme, we spent a quarter sitting in on handoffs and reading the notes they produced. The report is linked below.
I've added one step before I book any kickoff now.
https://acme.example/handoff-report?utm_source=linkedin&utm_medium=social&utm_campaign=the-handoff-report&utm_content=ph7jk5
Invite people by email, and connect your company's Slack if you use it. Each person answers one question about their work in their own words, taps a few choices and picks their posting times. A few minutes.
2
Write one brief.
Say what the campaign is about, add any documents or link it should draw on, and choose who it goes to. What your company must never claim is set once in its settings, and holds for every campaign. No content library to keep stocked.
3
Postfox writes a different post for each person.
Postfox gives each person their own angle on the brief, and writes their post in their voice from what they told it about their work. When a brief is too narrow for everyone to have their own angle, the campaign page says so. Anything it can't trace is marked for them to check.
4
Each person approves their own.
Their post reaches them in Slack or by email. In Slack, approving is one click. They can also edit it in Postfox first, or say Not this time.
Postfox
PostfoxApp9:30 AM
Hi Mei. Here is a post written for you at Acme, for the campaign The handoff report. What you told us about yourself stays yours: your company cannot read it.
I was building the part of the product that turns a sales call summary into the first checklist a new customer sees.
My assumption was that parsing would be the hard part. It wasn't.
The hard part was that half the notes never said what the customer was trying to get done. The information was simply absent, which meant there was nothing to turn into a checklist.
At Acme, we published a report this month on handoffs from sales to customer success, and what we found in the notes people actually write.
We added one required field to the deal form instead of writing more code.
If you work anywhere near this problem, it is worth reading: https://acme.example/handoff-report?utm_source=linkedin&utm_medium=social&utm_campaign=the-handoff-report&utm_content=h6r8q4
Drafted with AI, subject to our privacy policy. Check it, and edit anything before it goes out.
⚠️ One detail to check before this goes out
• Detail: "The information was simply absent," (You told us the notes never say what the customer is trying to get done, not that the information was simply absent.)
Check the details and approveEdit it firstNot this time
Nothing goes out until you approve it. Ignoring this is a real answer, and the post simply does not run.
5
It goes out at their time.
Approved posts publish through LinkedIn's official API, from each person's own account, at the times they chose, and appear on the company calendar in Postfox.
Between campaigns, each person can add a short update about their work, in Postfox or Slack, and Postfox asks every two weeks if they want. Their next posts draw on what they shared.
For everyone on the team
Works even for the person who has never posted on LinkedIn.
Your first worry is that people won't take part. So Postfox asks almost nothing of them.
The post is already written, in their voice, from what they told Postfox about their own work.
To start, they describe something they worked on recently, in their own words, tap a few choices about their work and style, pick their posting times and connect LinkedIn. A few minutes, and nothing to install.
Approving is one click in Slack.
It's their name: they approve it, edit it first, or say Not this time. Nobody asks why, and the admin never sees who passed.
If they haven't answered after two days, Postfox reminds them once by email. Never more, so nobody has to chase anyone.
Their LinkedIn connection lasts 60 days, which is LinkedIn's limit, and Postfox reminds them before it runs out.
People who already post can paste in past posts, so their drafts start from how they already write.
‹Postfox
PostfoxApp9:30 AM
Hi Mei. Here is a post written for you at Acme, for the campaign The handoff report. What you told us about yourself stays yours: your company cannot read it.
I was building the part of the product that turns a sales call summary into the first checklist a new customer sees.
My assumption was that parsing would be the hard part. It wasn't.
The hard part was that half the notes never said what the customer was trying to get done. The information was simply absent, which meant there was nothing to turn into a checklist.
At Acme, we published a report this month on handoffs from sales to customer success, and what we found in the notes people actually write.
We added one required field to the deal form instead of writing more code.
If you work anywhere near this problem, it is worth reading: https://acme.example/handoff-report?utm_source=linkedin&utm_medium=social&utm_campaign=the-handoff-report&utm_content=h6r8q4
Drafted with AI, subject to our privacy policy. Check it, and edit anything before it goes out.
⚠️ One detail to check before this goes out
• Detail: "The information was simply absent," (You told us the notes never say what the customer is trying to get done, not that the information was simply absent.)
Check the details and approveEdit it firstNot this time
Nothing goes out until you approve it. Ignoring this is a real answer, and the post simply does not run.
Message Postfox
Why it can be trusted
Nothing goes out under someone's name that they didn't approve.
Only the author can publish.
Each post goes out from its author's own LinkedIn account, and only once they approve it. Admins can't approve, edit or publish it for them.
Details are flagged.
Before anyone approves, Postfox checks every sentence against the brief and the author's own words, and flags anything it can't trace: a figure, a name, a date, a reaction they never had. The author has the final word.
Your company's rules hold.
Every draft is written with your list of what the company must never claim, and every version Postfox writes is checked against it.
Official LinkedIn API only.
No browser extension, no scraping, and never anyone's LinkedIn password.
Your data is never used to train AI models, by Postfox or by its model provider. Data processing agreement on request. Write to hello@postfox.ai.
Dashboard
Every campaign at a glance
123
1
What is not approved yet
Posts still waiting for their authors. Who passed stays private: once the campaign ends, you see how many passed, whenever that number can't point at anyone.
2
What is booked
Approved posts, with the time each one goes out.
3
What is published
Live on LinkedIn, with a link to each post.
The Adoption view shows who is set up and how many people approve their posts, and each person's link code shows their clicks in your own analytics.
What you don't see: drafts, or what each person told Postfox about their work.
More than 10 people? Each extra person is $19 a month, or $15 a month on the yearly plan.
Every plan also includes
A unique post for each team member
Posts that can use their own updates
A fact check on every AI draft
Approval in Slack or by email
No publishing without approval
Each member's own posting schedule
Calendar and kanban views
The official LinkedIn API, no extension
FAQ
Do people have to take part?
No. Under Postfox's terms, your company agrees not to require anyone to join, approve or publish, and not to treat anyone differently for saying Not this time.
Can we see who said Not this time?
No. Once a campaign ends, you see how many people passed, whenever that number can't point at anyone.
Can the AI make things up?
It can. Before the author sees the draft, every detail Postfox can't trace is sent back to be taken out, and anything left is flagged.
Won't the posts sound like AI?
Postfox looks for the habits readers take for AI, like a stock opening line, “it's not X, it's Y” or a closing lesson. It rewrites what it finds, so the author doesn't have to.
Does Postfox read our people's LinkedIn?
No. It asks LinkedIn only for who the person is (name, photo, email) and for permission to publish the posts they approve, which can write but not read.
Can we set rules for what posts must never say?
Yes. Every draft is written and checked against your list of what the company must never claim, and Postfox flags a post that recommends what you sell without saying its author works for you. If your posts must be approved by compliance or archived, as in financial services, Postfox isn't a fit yet.
Which tools does it work with?
Slack for approvals, by direct message, and email for anyone Postfox can't match to a Slack account, including everyone on Slack Enterprise Grid. There's no Microsoft Teams connection: on Teams, people approve by email.
How does billing work?
Your first campaign is free for up to 10 people; on a plan, everyone who has joined counts toward the price, admins included, from the day they accept their invitation. You can cancel at any time, effective at the end of the month or year already begun, which isn't refunded.
Can we measure results?
Clicks, yes: each person's link carries a UTM code, so visits show up in your own analytics, and the campaign page shows whose code is whose. Postfox doesn't show impressions or reactions, because LinkedIn hasn't given it access: each author sees their own on LinkedIn.
What happens after the first campaign?
Each person keeps adding short updates about their work, and the next campaign's posts draw on them. When you create a campaign, Postfox suggests three ideas from your company's context.
Run your first campaign free
One brief, a different LinkedIn post for each person on your team. Your first campaign is free. No card to start.
Postfox
