For a stretch of my time in cross-border payments, I was the social program: one person writing, designing, scheduling, and reporting, with no dedicated designer and no media budget worth bragging about. My first attempt looked the way most small-team social looks: post when something's ready, boost whatever seemed strong, watch the reach number climb, repeat. It produced a busy feed and nothing I could point to in a review. Headcount was off the table, so the campaign had to run as a system, because the system is the only part of the operation that shows up every week whether or not you're having a good one.
Message before visuals
I start every campaign before a single asset exists: by writing the message down. The working document is an internal library, the key messages I'm committing us to, the misconceptions the audience actually holds, the language patterns we can repeat without wearing them out, and the narrative angle that ties it together.
This looks like overhead until week three. Then it's the reason a caption, a carousel, a short-form video, and a repurposed cut all sound like the same campaign instead of four teams improvising. Write the message once and everything downstream gets cheap.
Templates that cut production cost
A campaign one person can sustain is a campaign with low marginal cost per asset. So my second investment is reusable structure: headline blocks, quote card designs, explainer frames, carousel skeletons, a few video layouts. Built once, filled many times.
I built the frames to get five versions out without waiting two weeks on a designer I did not have. Once the frames exist, making a post means filling one in, design leaves the critical path of every individual post, and the only thing that still has to be good each week is the message going into the frame.
One idea adapted to four platforms
Cross-posting the same asset everywhere reads as laziness to the audience and performs like it. Here's what adaptation looked like for one idea from the payments campaign, the social-proof claim that our platform was trusted by 10,000 businesses:
- LinkedIn, a short narrative post: what those businesses actually move across borders and why they switched, with the number as the closer.
- Instagram, a quote card straight from the template library: the customer count as the headline, one line of context, nothing else.
- Facebook, problem first: the cost and delay of legacy cross-border transfers, then the proof that 10,000 businesses had already moved on.
- Short-form video, the number in the first second as the hook, then one concrete customer scenario, under thirty seconds, nothing spare.
Same claim, four shapes. I wrote the claim once, in the library; the templates made the four shapes cheap.
Distribution is a rhythm
Posting “when something's ready” produces scatter. I know, because that was my first system, if it deserves the word. What replaced it is a deliberate weekly sequence: warm-up content to open, then one educational post, one credibility post, one practical post, something lightweight, and then something deeper. Stacked in that order, a week of posts reads as an argument being built. And since one person schedules all of it, the rhythm doubles as the production plan. I always know what kind of post I owe next, which is half the battle when nobody is assigning you anything.
Testing ad angles without a testing budget
The paid side of a resource-constrained campaign lives or dies on angle testing. An angle is the core premise of the ad, the problem it names and the emotional trigger it pulls, distinct from the image, the headline, or the CTA. My first tests changed all of those at once, which turns out to be a reliable way to spend money and learn nothing. So I split it into two phases.
Phase 1: find the image
Run 10–20 images in small-budget click-through-rate tests with no copy variation. One ad set, duplicated 9–19 times, only the imagery changes. This isolates visual attention before any messaging variable enters the test.
Phase 2: find the angle
Take the winning image, duplicate the ad set, and vary one angle per ad, identical everywhere except the copy. Three days, roughly $20 per ad set, then scale or cut on the early indicators. In one round for a payments product, the three candidate angles were:
- Discount, “Save 20% on Cross-Border Payments”
- Benefit, “Simplify Your Payment Process in Minutes”
- Social proof, “Join 10,000 Businesses Trusting Our Payment Solutions”
Social proof beat the next-best angle on click-through rate by 15% relative. I wouldn't have guessed it, and that's the argument for the process: guessing is free and worthless; a $20 three-day test is nearly free and decisive.
Close the loop: social is an input too
A post's life doesn't end at publish. I fed posts into newsletters, video scripts, and sales enablement material, and mined strong comments for new topics and testimonial sources. Sales and support hear the real questions, objections, and knowledge gaps every day. That's content signal you can't buy, so I collected it from them deliberately. And because I kept the message consistent across social, email, and live conversations, each channel reinforced the others instead of diluting them.
Metrics that mean something
I stopped reporting reach and impressions. What I watch: saves, replays, comments with real questions, longer dwell time, and whether people share the piece privately. Each of those signals has a decision attached, or it isn't worth watching. When people saved a post and shared it privately, I expanded it, rewrote it longer, or cut it into a video using the same template frames. A comment with a real question became the next week's educational post, which I then wrote. A post with big reach and nothing else, I retired, however good it looked on the platform dashboard.
The honest limitation: this system makes production cheap and testing decisive, but it doesn't make attribution clean. I can defend the 15% angle win and the three $20 ad sets that settled it; I can't hand you a tidy revenue line for organic social, and I won't pretend to. What I can show is where every dollar and hour went, and what decision each one bought.
What I'd tell a peer starting this tomorrow
If you're the one person running social somewhere: write the message library before you make anything, build the templates before you post anything, and spend your first $20 on an angle test instead of a boost button. Clear message → reusable structure → platform-specific execution → consistent distribution → feedback loop.