About Content Pulse
Content Pulse is a distribution layer for teams who already publish a lot. It reads what you produce, decides what is worth sending out, shapes it for each channel, keeps a person in charge of it, publishes it, and tells you what it did.
Where we are
Media is live in private beta. Marketplaces are enterprise. Ecommerce is in development.
Our point of view
In most teams, publishing is the finish line. The story goes live, the listing goes up, the product page ships — and then reaching an audience becomes somebody's spare-time job.
Articles, listings, products, photography, categories, and a real understanding of who your audience is. None of that needs to be created again. It is sitting in a system you already run, and most of it is only ever seen by the people who came looking for it.
Something dependable that takes what you made and keeps working on it: every day, across every channel you own, without adding a job to anyone's morning. Not a bigger content team. A system that runs the last mile.
Somebody has to decide which of today's hundred articles, or ten thousand listings, is worth a post right now. Done by hand, that decision gets made for the first few and skipped for the rest.
Every destination wants a different size, a different caption and a different rhythm. One post pasted into four places is the cheapest way to do it and the least effective.
Teams will not hand their brand to a machine, and they should not have to. The work should be prepared automatically and still be approvable, editable and stoppable.
The numbers usually land in a different tool, days later, in front of a different person. So nothing anyone learns ever reaches the next decision.
Every one of those four is doable by hand. That is exactly the problem. Doable by hand means done for the first few things each day and quietly abandoned for the rest. A team publishing at volume needs it to happen on its own, and needs to stay in charge of it.
How it works
This is the same shape whether the source is a newsroom, a listings platform or a product catalogue. Only the source and the rules change.
We connect to the system you already publish in and read what comes out of it — articles, listings or products, with their categories and imagery.
Rules decide what is worth distributing and when: freshness, category, availability, price, what is trending, and what has already gone out.
Each item is drawn as channel-native creative in your own brand, with a caption written for the channel it is going to.
It goes out on the channels you own, on a cadence that runs when nobody is at a desk, with approval wherever you want it.
Every post is tracked by channel, category and format, and the result is put back in front of the people deciding what to make next.
The last step is the one most tools skip, and it is the one that makes the rest worth having. When you can see which categories, formats and angles travel on which channel, you stop guessing about the next thing you make.
What we believe
These are not features. They are the decisions we keep making the same way, and they are the reason the product looks the way it does.
We read your CMS, your feed or your catalogue. We do not copy your content somewhere else and ask you to maintain two versions of it. Nothing is edited at the source, and if you switch us off tomorrow your publishing is untouched.
The machine should do the parts nobody wants: resizing, rewriting per channel, remembering the schedule, chasing the long tail. What goes out under your name stays a human decision — approve it, edit it, hold it or stop it.
If a system publishes for you, it owes you an honest account of what that publishing did. Per channel, per category, per format, with post numbers kept separate from account numbers, because adding those together flatters everyone and helps nobody.
Where the product is today
We would rather be plainly behind on two of these than vague about all three. Here is exactly where each one stands.
Private beta
This is the live lane and where our attention is. WordPress publishers install a connector and are connected in minutes, with no migration and no new daily tool for editors. If you publish somewhere else, we ingest publish events over a generic bus and build the mapping with you — that route is assisted rather than self-serve.
Content Pulse for publishersFeed-led
Large inventory, structured data, and a real cost to every listing nobody sees. We work from the feed you already produce, at full-catalogue scale, and scope the connector and the cadence with you. These engagements are enterprise: sized, priced and integrated per platform rather than bought off a page.
Marketplaces and classifiedsNot yet open
The same idea applied to a product catalogue: choose the products worth posting, package them, publish on schedule, and tie the response back to sessions, orders and revenue. It is in development and follows the media product in priority. There is no live merchant integration to sign up for today, and we are not going to pretend otherwise.
Ecommerce and ShopifyIf you want evidence rather than description, the case studies are where we put it — what was done, on which channels, and what changed as a result: publisher case studies and marketplace case studies.
How to start
This is a young product being built alongside the teams using it, so the first step is always a proper conversation about your content and your channels.
How much of it, how often, in what system, and which social channels you already own. That is usually enough for us to know whether we can help.
The route in, the cadence we would run, what we would post first, and what the first 90 days should look like. Including the parts we would not do.
You choose how your posts look, what is eligible to go out, and what needs approving. Nothing publishes under your name that you have not sanctioned.
Not sure which lane you are in? Send us the detail anyway and we will tell you honestly whether this is a fit yet.
Next signal
Tell us what you publish, how much of it, and which channels you own. We will start with the workflow and the outcome you need, not with a feature list.