How Rabe Marketing runs its whole client roster without maintaining a single platform integration

Rabe Marketing works with businesses around Lübeck: restaurants, hospitality brands, and local companies that need to show up where their customers already spend their evenings. The work is Instagram content, automation, and talking to an audience that talks back.

Agency work has a shape that most social tools ignore. Several clients, each with their own accounts, tone, calendar, and reporting expectations. Most products assume one brand and one team, then charge per seat for the privilege of splitting the difference.

Before the workspace, a typical day looked like this: schedule in one tool, pull numbers from another, answer comments in the native apps on a phone. Nothing was connected. Every client review meant stitching the picture back together by hand.

So Sven built the workspace his agency actually needed — client at the centre, platforms underneath — and put Postproxy in as the connection layer instead of maintaining Meta and LinkedIn integrations himself.

A workspace is only as good as the connections underneath it, and that is where agency-built tools usually die.

Meta and LinkedIn have different authentication flows, permissions, publishing rules, response formats, and failure states. Tokens expire. Platform behaviour changes with no warning. A rejected post still has to surface an error a marketer can act on, because a client's launch does not wait for a debugging session.

Maintaining that directly would have turned a marketing agency into a software maintenance operation. Every hour spent on token refresh logic is an hour not spent on client work, and an agency bills for the second one.

Postproxy sits between the workspace and the platforms. Sven owns the client experience and the workflow; Postproxy owns account connections, platform-specific execution, and the maintenance that never stops.

The workspace follows a post through its whole life inside the client account, which is how agency work is actually reviewed and billed.

Sven can publish to a client profile, watch how the post performs, open the comment thread it generated, and answer from the same screen. The post, the profile, the numbers, and the conversation stay attached to each other instead of living in four different products.

The setup scales the way an agency grows. Taking on a client means connecting their accounts, not scoping an integration. Adding a platform means one more endpoint, not one more project with a maintenance tail.

That keeps the agency's own product moving: new workflows, better client reporting, more automation around the parts Sven's clients actually see.