How PostBuddy Launched Personalized Direct Mail for E-Commerce Without Building a Custom Editor
PostBuddy is a Denmark-based startup modernizing offline direct mail for e-commerce brands. Its platform lets marketers run physical postcard campaigns the same way they run email — with audience targeting, variable personalization, and A/B testing baked in, instead of one-size-fits-all mailers handed off to a print shop.
To make that work, PostBuddy needed an in-app design editor that produced print-ready postcards and merged personalized data into every copy. As an early-stage company, the founders faced the question every startup eventually confronts: build the creative layer themselves, or embed one. They chose to embed IMG.LY’s CE.SDK. Here’s why, and what it let them ship.
The Challenge: Offline Marketing Without the Digital Toolkit
Direct mail has a stubborn problem. The channel works — a physical postcard cuts through a crowded inbox — but the tooling around it never caught up with the personalization and testing that digital marketers take for granted. PostBuddy’s founders set out to close that gap.
Offline marketing lags behind because it’s not caught up with personalizations we see in digital marketing.
The product vision demanded a design surface most marketing tools don’t have. Postcards have strict print requirements — bleeds, color fidelity, fixed dimensions — and PostBuddy’s whole premise was personalization, so the editor had to merge variable data (recipient name, offer, address) into thousands of unique copies from a single design. None of the off-the-shelf options fit. Generic design tools ignored print specifications, and the existing web-to-print solutions were either too restrictive to brand and extend, or too expensive to justify for a young company.
Equally important was friction. PostBuddy was asking marketers to adopt an unfamiliar channel; any seam in the experience would cost them.
When customers feel even the slightest friction, they postpone or abandon direct mail campaigns.
That ruled out the obvious shortcut of sending users off to an external design tool and asking them to upload a PDF. The editor had to live inside PostBuddy.
Why They Chose CE.SDK Over Building Their Own
The team evaluated building a proprietary editor and quickly recognized the cost. A print-grade editor with variable data, brand controls, and a maintainable UI is not a feature — it’s a product in its own right, and one that would compete for the same scarce engineering hours PostBuddy needed for its core mission of automating direct mail.
It’s almost impossible to imagine we could have built this company without an SDK. Doing it from scratch would’ve been a time sink.
What they needed from a vendor was specific. The editor had to embed natively inside their platform under PostBuddy’s own branding, not bolt on as an obvious third-party widget. It had to treat variable data as first-class so personalization scaled. It had to give them tight control over colors, fonts, layouts, and brand elements. And it had to handle print specifications cleanly, so no one downstream was repairing files by hand before they hit the press.
CE.SDK met all four. The deciding factor wasn’t a single headline feature — it was that embedding a mature editor let a small team ship a capability that would otherwise have consumed its roadmap.
It’s hard to imagine we could have launched PostBuddy without a design editor SDK. Customers want an integrated experience, and we needed to channel our limited resources into our core mission, not a custom editor.
How They Implemented CE.SDK
PostBuddy rolled out the editor in two phases.
The first was a proof of concept. They embedded CE.SDK to support basic postcard layout with variable placeholders, then wired in the piece that makes the product distinct: users upload a CSV of recipients and the editor auto-generates thousands of personalized postcards through mail merge, each copy resolving its own variable fields. Co-Founder Christian Vestergaard described the mechanic plainly.
We can insert variable fields on the design, export, and merge each field on the final postcard.
The second phase made the editor PostBuddy’s own. The team restyled the front end with branded CSS, color schemes, and UI elements, then built a template library so design-inexperienced marketers could start from a working layout rather than a blank canvas. They also added an in-editor checklist overlay that surfaces best practices in context — use variable fields, keep text minimal — nudging users toward the design choices that actually move response rates. Finally, the editor was wired into PostBuddy’s existing workflow and printing logic so every export came out print-ready at scale.
Throughout, the founders pointed to the working relationship with IMG.LY as a real accelerant. A dedicated Slack channel gave their engineers a direct line for integration questions.
We could speak directly with technical people. It’s rare to have that kind of quick help.
The SDK’s extensibility also meant PostBuddy wasn’t frozen at integration time. As IMG.LY shipped improvements, PostBuddy could fold them in.
We like that we can add new plugins. Every improvement you build, we can fold in easily.
The Results
The embedded editor delivered on its core promise: customers now plan, design, and personalize a campaign inside one app, with no detour through separate design software and no PDFs traded back and forth. The friction the founders worried about — the kind that makes marketers abandon a campaign — was designed out.
The in-editor guidance proved its worth in the numbers. A/B testing one campaign revealed a fourfold difference in performance between a plain, text-only postcard and a more polished layout — concrete evidence that the design variation the editor enabled, and the checklist that steered users toward it, directly affected response rates. That 4× gap became PostBuddy’s clearest argument for why an embedded, guided design experience matters in a channel most people still treat as static.
With design and personalization solved, PostBuddy could turn its attention to growth. The platform expanded from its Danish home market into Sweden and Norway, reaching all three Nordic markets, with larger European markets on the roadmap.
Overall Impact
The visible win is the product PostBuddy shipped: a personalized direct-mail platform that brings digital marketing’s targeting and testing discipline to a physical channel, wrapped in an editor customers never have to leave.
The less-visible win is what the build-versus-buy decision protected. Every hour a small founding team did not spend building and maintaining a print editor went into the automation, targeting, and integrations that are PostBuddy’s actual differentiator. Embedding CE.SDK didn’t just save engineering time once; it removed an entire maintenance surface from the company’s future and let PostBuddy ride IMG.LY’s roadmap instead of funding its own. For an early-stage startup, that’s the difference between launching and stalling.
