The shared-list problem is a creator problem in disguise
Every social media operator I know runs at least three “lists” that were never meant to be lists: a content calendar in a spreadsheet, a shot list in Notes, a sponsor deliverables checklist in a DM thread. They get shared the same way the grocery list in Psst’s launch story gets shared — as a screenshot, one version behind, pasted into a group chat that nobody owns. If you have ever watched a Reels draft get approved in a comment thread while the actual edit sat in a different app, you already understand the thesis of this essay: the collaboration layer is the product, and most tools still treat it as an upsell. That is the lens I want to use to look at Psst, a shared-list app from maker Ibrahim Hajjaj, and what it signals for the rest of us who ship content across Instagram, TikTok, YouTube, X, LinkedIn, Facebook, Threads, and Pinterest.
What Psst actually is, and what problem it claims to solve
Let me be precise about the source material, because the Product Hunt page is thin and I am not going to pretend otherwise. The maker’s own framing is that this started with a shared grocery list that was really a screenshot of a notes app, sent back and forth, “always one version behind.” His complaint about the category is specific: “every to-do app I tried was built for one person and had sharing added later, so the moment two people touched the same list it fell apart or turned into a paid team plan.” Psst is positioned as the inverse — “a list is an invite.”
The feature set, as described by the maker, includes:
- Add the people a list concerns, and they see every change as it happens
- Roles, so “the wrong edit cannot happen”
- Comments on any item, so decisions live next to the task
- An activity feed
- Presence, so you can see who else is on the list
- All of the above in the free tier — explicitly not a crippled demo with collaboration paywalled
- Full offline operation with sync when you are back online
- iOS, Android, and web
- No ads, no tracking, no selling data
That is the whole disclosure. Review count is described as early and reflective of that; specific numbers are not disclosed. Pricing beyond “the free tier” is not disclosed. Team size, funding, and roadmap are not disclosed. I am flagging that up front because the rest of this piece is going to be my read on what this pattern means, not a review of benchmarks I do not have.
Why the “collaboration is the free tier” line matters more than the feature list
Here is the part I keep coming back to as someone who has paid for a lot of software on behalf of content teams. The standard SaaS playbook for the last decade has been: single-player is free, multiplayer is a per-seat upgrade. Notion does it. Airtable does it. Asana and Trello do it. Even Buffer and Later gate multi-user approvals and client permissions behind higher tiers, which is reasonable for them but means a two-person creative operation often pays an agency-tier bill for agency-tier features it barely uses. The maker’s argument — that collaboration is “the entire point of the app,” so paywalling it would be self-defeating — is a positioning choice, not a technical one. My take: it is also a distribution strategy. If the collaboration is free, every shared list is a viral loop, and every new collaborator is a warm install. That is the same mechanic that made Google Docs unstoppable inside companies and Figma unstoppable inside design teams, and it is worth studying if you run any kind of shared editorial workflow.
How this compares to the tools creators already use
I want to be fair to the incumbents here, because “shared list app” is a crowded shelf and Psst is not obviously better at everything.
Against general-purpose docs and wikis. Notion, Coda, and Google Docs can absolutely hold a shared list. I have run content calendars in all three. The failure mode the maker describes is real: the moment two people edit the same doc, you get suggestion mode, comment threads that drift away from the line they refer to, and a version history nobody reads. Psst’s bet is that item-level comments and roles beat document-level comments and permissions. I think that is right for checklists and wrong for anything with prose.
Against task managers. Todoist, Things, TickTick, and Microsoft To Do all support shared lists. The maker’s critique — that sharing was bolted on — is a fair characterization of some of them and unfair to others. Todoist’s shared projects work fine for two people. Where they tend to break is exactly where content workflows break: when the “list” is really a sequence of decisions, not a sequence of checkboxes, and the decision context lives in a chat thread somewhere else.
Against chat. The most honest comparison in the comment thread is from Adam Nurbol, who says this is “basically what my partner and I use WhatsApp for when we’re shopping.” He is right, and that is the real competitor — not Notion. WhatsApp, iMessage, Slack, and Discord are where most small-team coordination actually happens, and they are terrible at state. A message is a moment; a list is a state. The reason people screenshot lists into chats is that chats are where the other person already is.
Against the spreadsheet. Google Sheets remains the default content calendar for a huge share of creators I talk to, and it is genuinely good at the tabular parts — dates, platforms, status columns, links. It is bad at the “who is doing what right now” part, which is what presence and roles are for.
Why TikTok creators should care more than LinkedIn ones
This is a judgment call, so flag it as mine. Short-form workflows are more volatile than long-form or B2B ones. A TikTok or Reels shoot generates a pile of clips that need to be triaged, captioned, approved, and scheduled inside a 24-to-72-hour window, often by two or three people who are not in the same room. LinkedIn content, by contrast, is usually one person writing in a doc. The more hands touch a piece of content before it ships, the more a shared-state tool earns its place. If you are a solo creator posting to one platform, you do not need this category at all — a Notes app is fine. If you are running a two-to-five person content operation across three or more platforms, the coordination tax is real and it compounds.
What creators and social teams can borrow from this launch
I am less interested in whether you adopt Psst than in the design principles it makes legible. Four of them are worth stealing regardless of your stack.
1. Put decisions next to the thing they are about
The comment from James Sanders — “keeping little decisions on the item itself instead of losing them in chat” — is the whole thesis in one sentence. In my own content workflows, the single biggest source of rework is a decision made in Slack or a DM that never makes it back to the asset. “Use the second take.” “Swap the hook.” “Legal says drop the claim.” If your approval process lives in chat, your approval process is lossy. Whatever tool you use, the rule should be: the decision lives where the work lives, and the chat links to it, not the other way around.
2. Roles are a feature, not bureaucracy
The maker mentions roles “so the wrong edit cannot happen.” In content terms: the person who schedules should not be the person who rewrites the caption at 11pm, and the client should be able to comment without being able to publish. Most creator stacks handle this with trust and screenshots. That works until it does not. If you are running paid social for a client, an approval role is not optional — it is the thing that keeps you out of a very bad morning.
3. Offline-first is underrated in field production
Filipe Braiman Carvalho and the maker both flag offline mode, and I want to underline it for a different reason than groceries. If you shoot on location — a market, a venue, a warehouse, a trail — you will lose signal. Any production tool that assumes connectivity will fail you at exactly the moment you need it most. Check whether your shot list, call sheet, and approval flow survive airplane mode before you commit to them.
4. Free collaboration is a growth loop, not charity
If you are building anything — a newsletter, a community, a template pack — think about which part of your product is the invite. The maker’s framing (“a list is an invite”) is a growth mechanic disguised as a UX principle. The thing you want shared should be free, frictionless, and useful to the person receiving it before they ever pay you anything.
Where the math breaks
I have to be honest about the limits of this comparison, because a grocery list and a content pipeline are not the same object. A grocery list has one decision axis (buy / do not buy) and a short lifecycle. A content pipeline has at least four axes — platform, format, status, and owner — plus a publishing schedule that has to survive algorithm changes and API rate limits on the platforms themselves. A tool that nails shared state for a two-person checklist may not extend to a five-platform, three-approver publishing calendar. I would not assume it does without testing it.
Where my judgment says this falls short
The maker invites exactly this, so let me take him up on it. These are my opinions, not sourced facts.
The category is brutal and the differentiation is thin. “Shared list” is one of the most crowded software categories in existence, and the incumbents are free, mature, and pre-installed on most phones. Apple Reminders and Google Keep already do shared lists with real-time sync, and they are already on the device. Psst’s answer — item comments, roles, presence, price history — is a real answer, but it is a features answer, not a platform answer. The comment from Vriddhi Mittal and Zarnappa Earnoor about price history and unit-price comparison is interesting, and Andrea Zanon is right that unit price beats total price for actual shopping decisions. But price history is a grocery-specific feature, and grocery-specific features do not obviously transfer to content work. If the app’s wedge is shopping, the creator-market read of this launch is mostly metaphorical. If the wedge is general shared lists, price history is a distraction.
“No tracking, no ads, no selling data” is a promise, not a business model. I believe the maker means it. I also note that the source does not disclose how the company makes money, what the paid tier looks like, or what happens when the free tier’s storage or collaborator count becomes expensive. That is not an accusation — it is a question any operator should ask before moving a workflow onto a free product. Free collaboration is a great growth loop and a hard P&L.
Early review count is a real signal, and the maker says so. He is unusually candid about it: “it is early, and the review count reflects that.” I would take him at his word. Do not migrate a client-facing approval flow onto a product in this stage without a fallback.
Who this is not for. Solo creators posting to one platform. Teams already happy inside Notion or Airtable with a working approval process. Anyone who needs deep integration with scheduling tools like Buffer, Hootsuite, Later, Metricool, or Sprout Social — the source says nothing about integrations, and for a content operator, integrations are often the whole decision. If your workflow depends on a UTM-tagged link, a CapCut export, or a Canva template handoff, verify those paths exist before you commit.
What I’d watch / test next
Three concrete things I would do this week, whether or not you install anything.
First, run a state audit on your current content operation. Pick one recurring workflow — a weekly Reels batch, a client approval loop, a newsletter issue — and trace every decision that got made about it in the last two weeks. Count how many of those decisions live in a chat thread rather than on the asset itself. That number is your coordination tax, and it is the number any shared-state tool has to beat.
Second, test offline behavior on whatever tool you already use. Open your shot list or calendar in airplane mode and try to work. If it fails, you have found a real gap, and Psst’s offline-first claim is worth a closer look — but verify it yourself rather than trusting a launch page.
Third, watch the pricing disclosure. The maker’s “collaboration is free” stance is the most interesting thing about this launch, and the most fragile. If a paid tier appears later that gates roles or presence, the entire positioning collapses. That is the thing I would check back on in 90 days. And if you do try Psst, answer the maker’s actual question in the comments — “if you share lists with someone today, what breaks first?” — because that thread is where the roadmap is being written.
