Jackson Calame hosts Vision Pros Live Podcast and runs First Class Business, a consulting practice serving B2B and SaaS founders. Most of what First Class Business publishes on social media originates from a podcast episode. However, each episode reached listeners once, on its release day, and then left the feed permanently. The archive continued to hold interviews with founders and operators, yet none of that material circulated after publication week.
The bottleneck was manual scheduling, not content supply. Promoting one episode across LinkedIn, Facebook and X required Jackson to queue every post by hand. Weekly recording, editing and client delivery consumed the hours that routine demanded. Jackson resolved the constraint with RecurPost, which stores social posts in evergreen libraries and republishes them on a repeating schedule. Each episode now returns to the feed weeks after release, without a new scheduling session.
| Dimension | Before RecurPost | After RecurPost |
|---|---|---|
| Operation | First Class Business, a consulting practice publishing its own content | Unchanged |
| Main content source | Podcast episodes | Unchanged |
| Getting an episode into the queue | Found and uploaded by hand, once per episode | Pulled in from the connected podcast RSS feed |
| Editorial control | Every post written and placed manually | Each imported episode is approved or rejected before it enters the library. This step stays manual by design. |
| Life of one episode | Posted once on release, then out of the feed | Republished from its library on a repeating schedule with no re-entry |
| Setup effort | Not applicable | Feed relevance and posting timing took work with RecurPost support before the workflow settled |
| Audience engagement | Baseline not published by the customer | Increased, reported by Jackson, no figure given |
| Measurement period | Not stated by the customer | Not stated by the customer |
| Connected accounts and platform mix | Not recorded in this case study | Not recorded in this case study |
| Plan used | Not recorded. RecurPost case studies do not specify each customer’s subscription plan. | Not recorded |
First Class Business Builds Its Social Content from One Podcast
Consulting practice, founder-led revenue growth
Vision Pros Live Podcast, weekly
B2B and SaaS founders and operators
Jackson Calame founded First Class Business, a consulting practice that works with founder-led companies on revenue growth. His work focuses on positioning a company as a Power Brand within its market, drawing on his background in B2B and SaaS startups.
Jackson built the practice around Vision Pros Live Podcast, his weekly interview show for entrepreneurs and operators. Most of what First Class Business publishes on social media therefore begins as a podcast episode rather than as a standalone post. The show functions as the production engine, and every social account draws from its output. First Class Business is one of the operations documented in the RecurPost case studies.
A podcast episode is expensive to produce and slow to lose relevance. Each Vision Pros Live episode requires guest booking, recording, editing and clip production before anything reaches a social feed. That same episode still carries value a year later, because the growth principles discussed inside it do not expire.
Release week, however, captures only a fraction of the total audience. The remaining listeners encounter the episode months later, or never encounter it at all.
Jackson measures social media performance by audience relationship rather than posting count. He has described his approach as a deliberate move away from engagement-chasing tactics. That standard eliminates the obvious solution to thin output, which is publishing a higher volume of cheaper material.
First Class Business consequently faced a narrow problem. The practice owned a library of durable content, and each item in that library reached its audience exactly once.
Every Episode Was Posted Once and Then Stopped Working
First Class Business promoted each podcast episode once, on its release day, but then it disappeared from the feed. Jackson’s back catalogue produced nothing after the first week of distribution. Older Vision Pros Live episodes remained available on the podcast host, yet they stopped appearing anywhere a follower would encounter them. Consequently discovery depended on a listener searching the archive directly, which almost none of them do.
The problem was not scheduling speed. Queueing one post for one episode takes under two minutes, and completing that task faster changes nothing about the following week. First Class Business was losing the value of work it had already paid for. Each episode carried the full cost of guest booking, recording, editing and clip production, but delivered a single day of reach in return.
Republishing an older episode also lacks a trigger. A new episode carries an obvious one, because the release date creates the prompt and the deadline. An episode from the previous quarter carries no equivalent signal, and no calendar entry marks its second promotion. Tasks without a trigger remain undone regardless of how simple they are.
Jackson’s archive therefore grew each week while its contribution to social media stayed at zero.
How RecurPost Turns Each New Episode into a Recurring Post
RecurPost pulls each new episode from Jackson’s podcast feed into a content library, where Jackson approves it before it joins the schedule. The workflow runs in two stages rather than one. Jackson built it using RecurPost features, and the split between import and approval defines how the entire setup behaves.
Connecting the Podcast RSS Feed so New Episodes Arrive Automatically
RecurPost reads a connected RSS feed and adds each new item to the content library you select. Jackson connected his podcast feed once, and RecurPost has handled collection ever since. Nobody on the team searches for a new episode to upload manually.
RecurPost imports three fields from every feed item:
- The Message field, which carries the post content in plain text or HTML.
- The Media URL field, which holds a public image or video link.
- The Link field, also called the Source URL, which credits the original episode.
RecurPost documents these fields on its Import Content Using RSS Feeds page. Notably, two setup conditions apply before any podcast workflow works. RecurPost reads public RSS and Atom feeds only, which rules out private or paywalled sources entirely. RSS feeds also arrive as a paid add-on priced per feed, separate from the base plan.
Approving Each Episode Before It Enters the Schedule
RecurPost holds every imported episode in the library’s Content Curation section until somebody approves it. Therefore, Jackson approves or rejects each item, and RecurPost moves only approved posts into the content library that feeds the schedule.
Notably, RecurPost does not publish directly from a feed. This feature is not designed for fully automated publishing, because every imported post requires approval first.
The review step serves an operation like Jackson’s rather than obstructing it. A podcast feed delivers whatever the show notes contain, and show notes are written for podcast players rather than for LinkedIn. Jackson edits the message before approving it. RecurPost’s Generate Caption with AI rewrites the text when the feed version reads poorly on social media. Every imported post also remains editable through the three-dot menu.
Jackson found the setup harder than the running of it. Routing feed items into the correct library, and settling the posting timing, required work with RecurPost’s support team before the workflow stabilised.
Recycling Approved Episodes on a Repeating Schedule
RecurPost keeps approved episodes inside a content library and republishes those posts on the cadence set for that library. An episode from eighteen months ago returns to the feed without anyone re-entering it. The library carries the schedule, which removes the need for a trigger on each individual episode. RecurPost explains the mechanics on its Schedule & Recycle page.
What Jackson Reported, and What That Report Does Not Prove
Jackson Calame stopped scheduling episodes one by one after connecting the podcast feed to RecurPost. This is the clearest change in what the team does, because it describes behaviour rather than an audience metric. The per-episode scheduling task disappeared from the weekly routine. The back catalogue entered circulation at the same time, which reversed the single-day distribution pattern described earlier.
Jackson also reported that audience engagement increased and that his connection with followers felt more direct. He describes the setup in his own words in the review below.
Jackson’s engagement report carries conditions, and those conditions deserve equal weight. Jackson published no figure, no starting baseline and no measurement period. The report therefore records a direction of change without recording its size.
Two variables also moved together, and this account does not connect them. A circulating back catalogue produces more posts each week, and a higher posting volume moves engagement counts independently of any other factor. Attributing the increase to RecurPost alone would exceed the available evidence. RecurPost consequently reports what Jackson reported rather than claiming a cause for it. Readers comparing outcomes will find that the Case Studies library documents operations starting from different baselines again.
Where This Workflow Transfers, and Where It Breaks Down
The setup Jackson uses fits an operation meeting two conditions: the content source publishes a public feed, and the individual items stay worth reading months after release. A podcast satisfies both. A blog carrying long-form articles satisfies them equally, as does a recorded talk series with a feed behind it.
The workflow also transfers to client work, and the transferable unit is small. One client with a podcast becomes one RSS feed pointed at one content library. A freelancer managing 3 clients who publish weekly connects 3 feeds to 3 separate libraries. Each client’s imports then arrive in a distinct queue for separate review, which keeps the content of different clients from mixing.
A source without a public feed cannot connect at all. RecurPost imports public RSS and Atom feeds only. A private podcast, a paywalled newsletter, or a platform publishing no feed requires another route into the library.
Unattended publishing from a feed remains unavailable. RecurPost requires approval on every imported item before it reaches the content library. An operator connecting a feed and walking away finds a review queue waiting instead of published posts.
RSS import costs extra. RecurPost prices feeds as a paid add-on, charged per feed on top of the existing plan. A freelancer connecting 3 client feeds therefore pays 3 add-on charges rather than one.
Jackson’s account also evidences nothing about agency collaboration. He published for his own practice, routed no post through a client for sign-off, and used no shared workspace.
RecurPost does provide an approval queue, separate workspaces for each client, and password-free client invites. This case study documents none of those features in operation. Nobody reading it consequently gains proof of how agency collaboration performs in practice.
Try RecurPost
RecurPost’s Personal plan covers 5 social accounts and includes 2 RSS feeds for $25 per month. The Agency plan covers 20 social accounts, 3 users and 20 RSS feeds for $79 per month, and prices further feeds at $10 each per month. Anyone connecting a feed per client should count feeds before counting accounts, because a feed-driven workflow reaches the feed allowance first.
2 social accounts and 1 user. No RSS feeds included, so RSS import is an add-on purchase at this tier.
5 social accounts, 1 user and 2 RSS feeds included.
20 social accounts, 3 users and 20 RSS feeds. Extra feeds cost $10 each per month on any plan.
Every RecurPost self-serve plan includes a 14-day free trial and asks for no credit card, with a 30-day money-back guarantee on paid plans. See RecurPost pricing for every plan and add-on with its unit price, or start a 14-day free trial and connect one feed to see what lands in the first week.
RecurPost social media management software runs a consultant’s back catalogue and an agency’s client roster through the same import and scheduling engine. Jackson’s setup is one documented shape of it.
Jackson Calame Case Study FAQs
Common questions about running a podcast catalogue through RecurPost:
Can RecurPost import from a private or paywalled podcast feed?
No. RecurPost imports from valid public RSS and Atom feeds only. A private podcast feed, a paywalled newsletter feed, or a platform publishing no feed cannot be connected. Content from those sources reaches a RecurPost content library through another route. Two routes remain available: uploading the post directly, or importing it from a connected social account.
Does RecurPost publish podcast episodes automatically from an RSS feed?
No. Every imported item requires approval before it enters the content library that feeds the schedule. RecurPost holds new feed items in the Content Curation section until somebody accepts or rejects them. RecurPost’s own documentation states the feature is not designed for fully automated publishing. Recycling runs automatically afterwards, which means the automation applies to republishing rather than to import.
What does RecurPost pull from each podcast episode?
RecurPost pulls three fields from every feed item: the message text, a media URL for the image or video, and the source link to the original episode. Each field remains editable before approval. RecurPost’s Generate Caption with AI rewrites the caption when the feed’s own text reads poorly on social media.
How many RSS feeds does each RecurPost plan include?
RecurPost includes 2 RSS feeds on the Personal plan at $25 per month and 20 RSS feeds on the Agency plan at $79 per month. The Starter plan at $9 per month includes none, which makes RSS import an add-on purchase at that tier. Extra feeds cost $10 each per month on any plan. That figure matters most to anyone connecting one feed per client, because the cost scales with client count.
Which RecurPost plan did Jackson Calame use?
RecurPost’s published case studies do not record the subscription plan of each customer, and Jackson’s plan is not recorded either. A single practice publishing one podcast needs 1 RSS feed and a small number of social accounts. The Personal plan covers 5 social accounts and 2 RSS feeds for $25 per month, which matches that requirement. Full limits sit on the RecurPost pricing page.