Flippa is an online marketplace where people buy and sell websites, apps, and other digital assets. However, Flippa’s marketing team previously rebuilt its posting queue by hand each week so that open buyer mandates remained visible to its community. Therefore, the article below explains the marketplace, the weekly routine RecurPost replaced, the schedule Flippa’s team set up, and what Nick, a member of the team, reported afterward.
| Dimension | Before RecurPost | After RecurPost |
|---|---|---|
| Operation | Flippa, digital asset marketplace, in-house marketing team | Unchanged |
| Scheduler | Hootsuite | RecurPost |
| Recurring content | Buyer mandates, listing updates, and community announcements re-entered by hand | Scheduled once, republished on the assigned cadence |
| Weekly team task | Rebuilding the posting queue to keep buyer mandates visible | No weekly rebuild |
| Where did those hours go | Manual scheduling | Campaign and community work, reported by Nick |
| Audience engagement | Baseline not published by the customer | Increased, reported by Nick, no figure given |
| Measurement period | Not stated by the customer | Not stated by the customer |
| Plan used | Not recorded. RecurPost case studies do not specify each customer’s subscription plan. | Not recorded |
Flippa Runs a Digital Asset Marketplace With a Continuous Listing Cycle
Digital asset marketplace, in-house marketing team
Melbourne, Australia, with a US office in Austin, Texas
2009, by Mark Harbottle and Matt Mickiewicz
Flippa is an online marketplace for buying and selling digital assets, including websites, apps, e-commerce stores, SaaS products, and content sites. Flippa is headquartered in Melbourne, Australia, and also has a US office in Austin, Texas. Mark Harbottle and Matt Mickiewicz founded the company in 2009, and Flippa is also one of the operations documented in the RecurPost case studies.
Flippa’s marketing team publishes content for a two-sided community, where buyers and sellers read the same feeds. Therefore, several categories of updates return each week, including new listings, sold notices, community announcements, and buyer mandates.
A buyer mandate is a standing buy-side requirement for a specific type of asset. When Flippa publishes a mandate, sellers with a matching asset can respond to the requirement. However, a mandate can remain active until it is filled, which may take several weeks. Therefore, its ongoing nature makes a repeating publishing schedule useful for Flippa’s marketing team.
Flippa’s content repeats by category rather than by individual post. While new listings continue to arrive, the publishing need remains active, and the marketing team must continue sharing relevant updates with the community.
Flippa’s Team Rebuilt Its Hootsuite Queue by Hand Every Week
Flippa’s marketing team used Hootsuite before RecurPost and rebuilt the posting queue by hand every week to keep buyer mandates in front of the community. As a result, the team had to repeat the same scheduling work each week to maintain visibility for ongoing mandates.
Flippa’s mandates and posting queue ran on different timelines. While a mandate could stay open for weeks, the queue emptied within days. Therefore, someone had to re-enter the same mandates week after week simply to maintain a position that the content had already earned.
“The time we spent on manual scheduling was exhaustive and detracted from our other strategic activities.” — Nick, Flippa marketing team
Flippa did not have a discipline or headcount problem. Instead, the team had a repeating obligation running through a one-time scheduling setup, so the mismatch remained even when the team became more efficient. Although the team could get faster at rebuilding the queue, Flippa’s queue still needed to be rebuilt the following week.
The Publishing Workflow Flippa Set Up in RecurPost
RecurPost republished Flippa’s buyer mandates and listing updates on a schedule that the team set once. The team built this setup using RecurPost publishing workflow features, and therefore no longer needs to rebuild the queue each week.
Publishing to Every Connected Social Account From One Schedule
RecurPost publishes content according to the schedule attached to each account rather than when someone remembers to open the app. Therefore, Flippa’s team defined its posting times once, and RecurPost continued to publish each update to the connected social accounts according to that schedule.
“Adopting RecurPost allowed us to automate these processes, ensuring our content reached our community exactly when they needed it, without continual manual input.” — Nick, Flippa marketing team
RecurPost’s effect on this operation was narrow and specific. Instead of removing a variable task, RecurPost removed a fixed weekly task that Flippa’s team had to repeat. As a result, the team got back the same block of time each week rather than receiving only an occasional saving during a quieter month.
Seeing the Whole Publishing Cycle on One Calendar
RecurPost gives a team one calendar view of what is published and when across connected social accounts. Because a marketplace can run several categories of updates at the same time, this view helps the team track those updates in one place rather than checking each schedule separately. Therefore, RecurPost’s calendar helps Flippa’s team see whether 3 mandates and 4 listings are scheduled to publish within the same hour.
The Recurring Libraries Behind the Repeat Posts
Flippa’s repeating updates sit in libraries inside RecurPost. Therefore, RecurPost republishes those posts according to the cadence set for each library, which suits content that remains active until it is filled rather than content that expires the day after it is published. RecurPost explains these scheduling and recycling features on its schedule and recycle social posts page.
What Flippa Reported After the Switch
Flippa’s weekly queue rebuild stopped after the team moved its recurring updates into RecurPost. Therefore, RecurPost’s clearest documented effect on Flippa is this operational change because it reflects a change in what the team did rather than a change in how the audience responded.
Nick reported that audience engagement increased after the switch.
“Our audience engagement increased noticeably, and we could really see the difference in how our content was being received.” — Nick, Flippa marketing team
However, Nick’s engagement report has important conditions. Flippa did not publish a specific figure, a starting baseline, or a measurement period. Therefore, RecurPost reports the result as the customer described it rather than turning an adjective such as “noticeably” into a specific percentage.
Nick also described an effect on the team itself.
“RecurPost didn’t just streamline our processes; it rejuvenated our team’s enthusiasm and capacity for innovation.” — Nick, Flippa marketing team
RecurPost does not present Flippa’s reported engagement change as its own measurement, and this account does not connect the reclaimed hours to that change. Instead, Nick reported both outcomes, while no statement from Flippa establishes that one caused the other. Similarly, the results reported by other RecurPost customers come from different starting points and should therefore be considered separately.
Who This Setup Fits and Who It Does Not
The setup Flippa used fits an in-house marketing team whose content repeats by category rather than by individual post. For instance, a regional property listing site that publishes 40 new listings a week can have the same need. Similarly, a job board, directory, or events platform with a standing calendar can benefit from a recurring publishing setup. Therefore, Flippa’s fit condition is not the industry itself but whether the same type of update still deserves an audience a fortnight after it was created.
Flippa’s second fit condition is a fixed weekly scheduling task. Because Flippa’s savings came from removing a recurring block of work, an operation with an irregular scheduling load has less recurring work to remove through the same setup. Therefore, the value of the setup depends on whether the scheduling task repeats often enough to justify automation.
Flippa’s setup does not fit one-off publishing. For example, a funded startup announcing 3 launches a quarter has little content to recycle because each announcement may become outdated by the following week. Therefore, scheduling each announcement once is the more suitable approach, while a repeating library would add little value to this type of publishing.
Flippa’s setup also does not provide evidence about agency workflows. Flippa published for one brand with an in-house team, routed nothing through a client for approval, and did not document a shared workspace. In contrast, an agency managing 15 client brands, where each client approves copy before publication, needs an approval process and separate workspaces for each client. RecurPost provides these capabilities; however, Flippa’s case study does not document their use, so this account should not be treated as evidence of how those capabilities perform in an agency workflow.
Flippa moved to RecurPost from Hootsuite, so readers in a similar position may also need to understand the mechanics of switching rather than only the results of the change. Therefore, RecurPost provides the switching steps in its migration checklist, while the Hootsuite alternatives page explains the options for teams considering a move from Hootsuite.
Flippa Case Study FAQs
Common questions about how Flippa publishes recurring marketplace updates with RecurPost:
Over what period were Flippa’s results measured?
Flippa did not state a measurement period for the reported results. Therefore, RecurPost does not estimate one on the customer’s behalf. Nick’s engagement report should be read as one team’s account of a change from a manual weekly baseline rather than as a measured improvement over a defined period.
Which social platforms does Flippa publish to, and how many accounts?
Flippa’s connected account count and platform mix are not recorded in this case study. Therefore, RecurPost presents the details provided by the customer rather than filling the gap with an estimate. What the case study does document is the content type and publishing schedule, while the specific platform mix and account count remain undocumented.
Try RecurPost
RecurPost’s Agency plan covers 20 social accounts and 3 users for $79 per month, while additional social accounts cost $4 each per month. Because a team publishing at Flippa’s cadence may need to consider daily posting capacity as well as account count, RecurPost also offers recurring time slots as a $20-per-month block that adds 10 daily posting slots per social account.
20 social accounts and 3 users. Extra social accounts cost $4 each per month.
A block that adds 10 daily posting slots per social account, for teams publishing at continuous volume.
Every self-serve plan includes a 14-day free trial with no credit card required, and paid plans include a 30-day money-back guarantee.
Every RecurPost self-serve plan includes a 14-day free trial with no credit card required, while paid plans include a 30-day money-back guarantee. Therefore, you can see RecurPost pricing for each plan and add-on with its unit price, or start a 14-day free trial and add one repeating update to see how the schedule works over two weeks.
RecurPost social media management software uses the same scheduling engine for a marketplace’s listing cycle and an agency’s client roster. Therefore, Flippa’s setup represents one documented way to use the scheduling workflow.