A year of social media in one weekend.
1,098 posts. No agency. No burnout.

Here's how you do it

The whole system in seven steps

1. 1 One spreadsheet. 366 rows: headline, sub-line, and a caption column per platform
2. 2 One design, seven palettes. A theme per weekday so the feed never turns into wallpaper
3. 3 Generate the artwork. Bulk create or AI-generate 1,098 images - with a QC pass
4. 4 Host images at public URLs. A free storage bucket + a strict naming convention
5. 5 One CSV per platform. Captions, dates, times and image URLs, straight from the sheet
6. 6 Verify, then schedule. Health-check every URL, then bulk upload to the scheduler
7. 7 Stay 20% live. The scheduled year is the skeleton - topical posts go on top

That's it. Keep scrolling for the deets... the real numbers, the real mistakes, and the live brand this system runs today.

The maths that breaks people

Daily posting is the advice everyone gives and almost nobody sustains, because the maths is brutal. One post a day on three platforms is 1,098 posts a year. At an average of 20 minutes each, write it, design it, schedule it, that's 366 hours. Nine working weeks. On marketing admin. For a solo founder or a small team, that plan doesn't fail because of laziness; it fails because the volume was never survivable.

The fix isn't posting less. It's refusing to make 1,098 individual decisions. Batch the whole year as one project - one spreadsheet, one design session, one generation run, one upload - and the marginal cost of a post collapses to almost nothing. What follows is exactly how we did it for Digger Scholarships, an Australian education brand we run: 366 posts for Facebook, 366 for Instagram, 366 for LinkedIn - 1,098 posts across all three platforms, a year of daily presence.

Step 1

One spreadsheet is the entire content strategy

Everything downstream is generated from a single workbook. One master calendar tab (366 rows, one per day), then one tab per weekly theme. Every row carries the same fields:

• H1 - the headline that goes on the image
• H2 - the supporting line that goes on the image
• One caption column per platform - conversational for Facebook, professional for LinkedIn, line breaks and emoji for Instagram
• Date and theme - which day it posts, which design it wears

Writing 366 rows sounds enormous. It isn't, because themes make it seven small problems instead of one giant one. You're not writing "a year of content"; you're writing 52 Monday spotlights, 52 Tuesday facts, 52 Wednesday myths. Constraints are what make volume writable - and an AI assistant that knows your subject makes a strong first draft of each tab in minutes, which you then edit with your own voice and facts.

This is what the sheet looks like - one row per theme. Click any row, then look at the bottom of the sheet window: the finished-post preview down there swaps to show exactly what that row generates.

Step 2

One grid, seven palettes - the anti-wallpaper trick

The most common objection to batching: "366 posts from one template will look like wallpaper by week three" and you'd be correct in thinking that. The fix isn't seven different designs - that shatters the brand. It's one master layout with a palette shift per weekday - a strikethrough motif on myth-busting Wednesdays, a "SAVE THIS" corner tag on how-to Thursdays, a big serif headline on deadline Fridays.

Design the flagship variant first, get the spacing perfect, then duplicate and recolour six times using the brand book. Change only colours - never the grid, never the fonts. The consistency is what keeps it on brand.

Here are all seven templates side by side, empty. Every one has the same two text boxes - {H1} and {H2} - and Bulk Create simply fills each spreadsheet row into them:

That's the whole trick. Seven thumbnails, two text boxes, zero decisions per post. Scroll back up to the gallery and you'll see the same seven frames filled in: unmistakably one brand, never the same day twice.

Step 3

Generate the posts - use the templates

366 designs × three platform sizes = 1,098 images. Nobody makes those by hand. There's two main ways to do it. Here's how:

• Canva Bulk Create - if you've ever played Go Fish with the kids, you already have the skill: it's two matches and a "go fish". Match the H1 column to the H1 text box, match H2 to H2, then Go (the button says Generate). That's it - a theme's whole batch in one run. Canva's own Bulk Create guide is here. Three traps we hit:
  • Line breaks inside spreadsheet cells silently break the import - keep every cell to a single line.
  • Each run caps out around 300 rows, so run one theme at a time.
  • Don't generate once and resize per platform - Canva's resize needed more tweaking than it saved. Make a template each for Facebook, Instagram and LinkedIn and bulk-create each one. Three quick runs beat one run plus an afternoon of nudging text boxes.

  The batch map: 21 small runs, not one giant one

  Mon · Spotlight FB template · 52 IG template · 52 LI template · 52

  Tue · Did You Know FB template · 52 IG template · 52 LI template · 52

  Wed · Myth vs Fact FB template · 52 IG template · 52 LI template · 52

  Thu · How-To FB template · 52 IG template · 52 LI template · 52

  Fri · Deadline FB template · 52 IG template · 52 LI template · 52

  Sat · History FB template · 52 IG template · 52 LI template · 52

  Sun · Family FB template · 52 IG template · 52 LI template · 52

  7 themes × 3 platform templates × 52 weeks - 21 bulk-create runs, every one comfortably under the 300-row cap.

• An AI assembly line - Anthropic's newest model, Claude Fable 5, orchestrated Opus agents to deliver: one agent rendered every image straight from the spreadsheet through a headless-browser template, a second independent agent QC'd every batch against the source data, and a human (hi) spot-checked the results. The QC pass earned its keep: it caught "1 weeks left" typos in three posts before they went out, traced them back to the spreadsheet, and fixed both.

We split the year across both methods deliberately - the first themes through Canva, the rest through the assembly line - to road-test each and report back honestly. Both work. Canva costs nothing and needs no technical setup; the assembly line scales further and QCs itself.

Full disclosure: PM Project Change runs a Claude Max plan. Usage limits on Fable are significantly higher than the Pro tier, and a year of image generation leans on that headroom.

Either way, the principle is the same: the spreadsheet is the source of truth, and images are generated from it - never edited individually. If a post is wrong, you fix the row and regenerate.

Step 4

Host the images where a CSV can reach them

Here's the step nobody warns you about. Bulk schedulers don't want image files... they want public image URLs in a CSV column. Your 1,098 images need to live on the open internet before you can schedule anything.

We used a Supabase storage bucket - and the free tier easily covers this job: a year of post images is about 60MB against a 20GB cap. If you've never touched it, it's less scary than it sounds:

1. Create a free Supabase account and a new project.
2. In the left menu, open Storage and create a bucket. Mark it public - that's what makes the image URLs shareable.
3. Inside the bucket, create one folder per theme per platform (e.g. facebook-theme1, instagram-theme1).
4. Drag each batch of images into its folder. That's the whole upload.
5. Click any file and copy its public URL - every other URL follows the same pattern.

Name the files to a strict convention before you upload (DS-FB-DYK-007.png = brand · platform · theme · sequence). The convention is the whole game - when file names are predictable, the URLs are predictable, which means the CSVs in the next step can be generated instead of typed.

Step 5

One CSV per platform

From the master spreadsheet, generate one CSV per theme per platform: caption, year, month, day, hour, minute, image URL. Small files beat one monster - if an import fails, you lose one theme on one platform, not the year.

One note before you build anything: every scheduler provides its own CSV template, with its own column names and order. Download it from inside your tool and complete it exactly as required - the example below shows the shape, not your scheduler's exact columns.

Nothing in the curly braces is magic - they're the bits you replace with your own names:

Step 6

Verify, then schedule

The step that separates systems from gambles: health-check every image URL before uploading a single CSV. A script that pings all of them takes seconds. Ours came back 755 green, 46 red - one folder had simply been missed during upload. Two minutes to fix before scheduling; a week of broken image posts if we'd found out after. Verify, then schedule. Always in that order.

Then pick a scheduler that takes CSV bulk uploads:

• Content360 - what we used. It happily scheduled a year of posts per platform, and at the time of writing it has a lifetime deal (one payment, no subscription) - which suits this system perfectly, since the whole point is scheduling a year ahead.
• Buffer, SocialBee, Metricool - all take similar CSV bulk uploads on subscription plans. Same system, different vehicle - check each one's cap on how far ahead it will schedule.

Step 7

The scheduled year is the skeleton, not the strategy

The standard objection to scheduling a year ahead is real: feeds need room for the topical, the newsworthy, the human. So leave it. The scheduled year is your floor, not your ceiling - roughly 80 per cent of output, guaranteed to show up every single day whether you're inspired, busy, or having a terrible week. The other 20 per cent you post live: reactions, wins, behind-the-scenes, anniversaries that matter this week.

That's the actual mental-health trade at the heart of this whole system. Daily posting puts a decision in front of you 366 times a year. A scheduled skeleton means the machine posts at 9am whether you're feeling brilliant or meh - and everything you add on top is a bonus, not an obligation.