Most people leave a brand session with sixty or eighty images and use maybe six of them. The rest sit in a folder called « photos Playa 2026 » and quietly rot. Fait que here’s the system I give my clients so that one session actually covers a season.
Step one: sort before you schedule
The day your gallery arrives, don’t post anything. Instead, open it and drag every image into four folders.
Hero images. The five or six that stop you. These go on your site, your sales page, your profile photos. Use them sparingly, because overexposure kills them.
Speaking images. You looking at the camera, mid-sentence, hands moving. These carry text well and work for anything where you’re teaching or explaining.
Environment images. Wide frames with a lot of empty space. These are your quote graphics, your announcement posts, your email headers.
Detail images. Hands, objects, your desk, your product. These are the filler that keeps a feed from feeling like a personal album, and you’ll burn through them faster than you expect.
If a photo doesn’t fit any of the four, it probably isn’t going to get used. Let it go.
Step two: assign, don’t improvise
A three-month content plan from one session needs roughly thirty to forty usable images if you’re posting three times a week and mixing in phone content. That sounds like a lot until you realize most sessions produce more than that.
Here’s the ratio that works: about one in five posts uses a hero image, one in three uses a speaking image, and the rest rotate between environment and detail. Mettons you’re planning twelve weeks. Sit down once, assign an image to each slot in a spreadsheet, and you’ve removed the daily « what do I post » question entirely.
Step three: crop like you mean it
One image is not one post. A wide horizontal frame gives you a horizontal for your site, a square for the feed, a vertical for stories, and a tight crop on your face for a profile. Four assets, one file. This is exactly why I shoot wider than looks natural and why I shoot both orientations for every setup.
The rule is that a crop has to feel deliberate. A hero image cropped so tight you can see the pixels reads as desperation. A hero image cropped to the eyes and forehead as a header can look intentional and strong.
Step four: repeat images on purpose
Nobody is tracking your feed closely enough to notice that image fourteen came back in week nine with different text. Dans le fond, the people most likely to notice are you and three peers, and none of them are your buyers.
Reusing an image with a new angle is normal. What you want to avoid is reusing it within the same two weeks, or reusing your single strongest photo so often that it stops carrying weight.
Step five: mix in the imperfect stuff
Three months of nothing but polished session images starts to read as a catalogue. Break it up with phone content: your workspace at 7 a.m., the thing that went wrong, the voice note you almost sent. The contrast makes the session images land harder, because they read as the moments you chose to make good.
A rough ratio I like: two-thirds session images, one-third phone content.
The part people skip
Rename your files. « IMG_4872.jpg » tells you nothing in December. « hero-beach-vertical.jpg » or « speaking-desk-wide.jpg » means you can find what you need in ten seconds instead of scrolling a gallery for twenty minutes every single time you post.
It takes half an hour once, and it’s the difference between a library you use and a folder you avoid.
When to book the next one
If you’re getting three months out of a session, that’s roughly four sessions a year, which is more than most people need. Two a year, spaced so you get both seasons and both energies, covers most businesses fine. You’ll know it’s time when you start recycling the same three images and feeling tired of your own face.
If you want help planning what to shoot so the session actually covers what you’re launching, tell me what’s coming up when you book. The shot list changes completely depending on whether you’re selling a program, a service, or a product.
Par Marrie-Eve
