The Sunday-night edit-post cycle that quietly became your unpaid second job

“The best images of the year I shot in August. I edited the gallery in October. By the time the best-nine grid landed on Instagram in November, the couple’s first anniversary was already four months away. By March the post was old and I still hadn’t published anyone’s June wedding.”

Every business with a marketing-content obligation has the same problem in a slightly different shape. The decorator’s before-and-afters that would be the best advert in the trade if they actually got posted. The wedding photographer’s best-nine grid landing two months after the season. The aesthetic clinic’s consent-controlled before-and-after gallery sat in someone’s camera roll. The commercial-grounds foreman’s monthly photo-report that the property manager wanted last Tuesday. The device-repair shop’s “iPhone 15 screens - same-day in Haverhill” model-specific local-SEO post that never got written. The accountant’s Spring Statement / Autumn Budget / year-end thought-leadership that fires three days after the actual statement. The charity’s “here’s what your year of giving built” impact letter held up since Christmas. The gym’s class timetable + transformation-story cadence that the marketing intern half-ran before she went back to university.

The shared problem isn’t writers’ block. It’s that the publishing-side cadence runs as a Sunday-night job sat on top of the operational job - the visual-led work assembles two months late, the “why are we publishing an August wedding in November” question doesn’t have a structural answer, and the cost of fixing it is more agency hours nobody wants to pay for.

This is the software build that runs the marketing cadence on top of your operational data. Important boundary up front: we don’t write your content for you - that would be agency-hours-as-the-deliverable, which mmitech doesn’t sell. We build the publishing software you run. The shape is sealed against planpost, our own social-media scheduling SaaS, with the per-vertical content-source feed wired into the operational layer (the gallery handover, the job completion, the class timetable, the appeal milestone) so the post publishes off what already happened, not off a blank Sunday-night page.

What gets lost between the work happening and the post going up

The shape repeats; the lost reach is always the same in a different costume. A few moments - pick the ones that sound like your last quarter:

• Decoratorsthe in-progress shot of the half-painted hallway, the before of the woodchip, the after of the heritage paint job a fortnight later. Posted as a before-and-after pair, this is the conversion-driving offer in the trade; sat in your camera roll, it’s nothing. Eight in ten decorators run their best advert as a private gallery on their own phones.
• Wedding suppliersgallery delivered to the couple in October; the best-nine grid for Instagram, the location-tagged Pinterest pins, the Google Business Profile post with the venue tag, the Facebook album for the family - all the publishing-side work happens at 11pm on a Sunday because nobody else owns it. The August couple’s content publishes in November; the November couple’s content publishes in February.
• Aesthetic clinicsthe consent-controlled before-and-after gallery is regulator-sensitive (JCCP / Save Face) and Article-9 special-category data; getting it wrong is a complaints-and-investigation problem. The result is that the gallery doesn’t get published at all because the consent state is too fiddly to manage by hand.
• Commercial-grounds landscapersthe foreman’s per-site photo capture (the cut, the edges, the litter-pick, the seasonal pruning) is what the property manager actually wants to see at month-end. Currently it’s a WhatsApp thread the office manager pieces together on a Friday afternoon. The same photo set, structured right, doubles as next month’s social content - but it usually doesn’t, because the office manager’s already gone home.
• Device-repair shopsthe “iPhone 15 screens - same-day in Haverhill” model-specific weekly cadence is what drives local-SEO for repair shops; the device-model + town pair is the search the customer actually types. Currently it gets posted ad-hoc, and the customer searches for “iPhone 16 screen Haverhill” and finds a competitor.
• Gym and fitnessthe weekly class-timetable post, the transformation-story sequence (consent-controlled), the lapsed-member September re-engagement campaign on a separate consent track. Three different content streams against three different consent rules; in practice, one person writes them all on Sundays.
• Accountants and professional servicesSpring Statement, Autumn Budget, MTD ITSA milestones, year-end planning, FHL April 2025 changes, R&D rate changes - the practice marketing cadence is a calendar of regulator-side events the firm’s audience needs commentary on. Currently it fires three days late and reads as templated.
• Charitiesthe regular-giver welcome cascade, the appeal-by-appeal supporter-impact storytelling, the “here’s what your year of giving built” impact letter. Each touchpoint is the highest-retention lever in the trade; each runs late or doesn’t run at all because the supporter-engagement team is small and the appeals lead is busy.
• Pet servicesthe dog-of-the-week, the grooming before-and-after with consent, the seasonal-tip post. Both retention and acquisition content; both eat Sunday evenings.
• E-commercethe new-arrival drop, the festive cadence, the Black Friday window, the seasonal returning-customer campaign - all on top of the operational marketplace work. The content team and the ops team are usually the same one person.

These aren’t problems for a generic Buffer / Hootsuite reminder. They’re the bit between the work already happened and the audience hearing about it - which is where the next twelve months of inbound actually lives.

What solved looks like

1. The content publishes off the operational data, not a blank page

The “what am I posting this week” moment: Sunday evening, you’re sat down to write four posts for the week ahead, and the blank-page-into-marketing-content conversion is what’s eating the evening. The gallery’s delivered, the job’s done, the class ran on Wednesday, the appeal closed on Friday - but turning any of that into structured posts is still a fresh start every time.

Solved looks like: the publishing cadence reads its source data off the operational layer. A wedding-supplier’s content stream is the gallery-handover event - gallery delivered → twelve months of Instagram, Pinterest, GBP, and Facebook posts cued up against the venue-tagging metadata captured at handover. A decorator’s stream is the job-completion event - before image captured at survey, after image captured at sign-off, the pair queued automatically against the consent flag the customer ticked. A gym’s stream is the class-timetable record + the structured transformation-story consent log. An accountant’s stream is the regulator-event calendar (Spring Statement, Autumn Budget, MTD ITSA deadlines) with the firm’s commentary template wired against each. A charity’s stream is the appeal milestone calendar with the supporter-impact captures attached. The content doesn’t appear out of nowhere on a Sunday - it assembles off what already happened in the week.

2. The before-and-after engine handles per-image consent properly

The “I’d post this if I had her consent” moment: the decorator has a beautiful heritage-paint hallway, but the homeowner ticked no social media on the consent form. The aesthetic clinic has a five-star tear-trough result, but the patient only consented to treatment-record use, not gallery use. The pet groomer has Bertie’s groomed-vs-arrival pair, but the owner’s note says “face-blurred only please”. The result, in every case, is that the best content sits unpublished because the consent state is too fragile to trust to memory.

Solved looks like: consent is per-image, per-use, per-channel, and stored as a structured record alongside the photo. A gallery use yes / social media no state respects across every channel. A face-blurred only tag triggers the right pre-publication step. A treatment-record reference only on the aesthetic-clinic side means the image never enters the social queue. Withdraw-consent is one tap from the customer side and applies retroactively across every cued post. GDPR Article 9 (special-category data) lives in a separately-scoped store for clinical contexts. JCCP / Save Face audit alignment is a structural property of the build, not a quarterly review. The consent state is the gate; the engine doesn’t even queue a post the consent state doesn’t allow.

3. The metadata makes the post findable on the channel it’s published to

The “we posted it but nobody saw it” moment: the post went up on Instagram with a generic caption and three hashtags. It got eleven likes from accounts who already follow you. On Pinterest the same image, with the right location-keyword stack the algorithm actually reads, would have run for eighteen months and brought in fifty inbound enquiries. Same picture, two channels, two completely different lifetime values.

Solved looks like: the metadata for each channel writes off the structured operational record. Pinterest pins carry the location-keyword stack the algorithm reads - venue + region + season + style. Google Business Profile posts carry the local-search optimisation Google rewards - the “iPhone 15 screens - same-day in Haverhill” model-specific weekly cadence is the structural shape, not a one-off post. Instagram carries the venue-tagging discipline (the venue tag is a structural property of the gallery, not a per-post decision). Facebook carries the album structure that the family will share. TikTok and LinkedIn carry the cuts that suit each platform. Same source content, channel-aware metadata, written off the operational record at the moment of publication - not retro-fitted by hand at midnight.

4. PECR-clean by default, not as a retrofit when the ICO writes

The “we’re a bit grey on consent” moment: the firm’s email list was built up over years from enquiry-form sign-ups, business-card collections at events, the website footer opt-in box that wasn’t always there, and the customers-who-bought-something-and-got-added-because-everyone-did-that-in-2017. Nobody’s audited the consent state. Marketing fires anyway because we’ve always done it like this, and the ICO letter eventually arrives.

Solved looks like: service messages (you’re contacting the customer about a service relationship you have - a booking confirmation, a recall, an order status) run on soft opt-in, audit-trailed, with the lawful basis clear in the record. Marketing content (you’re contacting the customer about something they didn’t ask for) runs strictly behind explicit consent, with the consent moment, the wording the customer consented to, and the channel state all queryable. One-tap unsubscribe across every cued post, applied retroactively. Full audit per recipient, per consent state, per campaign. The “why did you message me” question gets answered from the record, in the same screen the recipient is in. PECR-clean as the default; the alternative is rebuilding the list from scratch when the ICO writes.

5. The voice on every post sounds like you, because the agent’s learnt your voice

The “this reads like a marketing agency wrote it” moment: the templated thought-leadership post in corporate English with a smiley face. The customer reads two sentences, hears it isn’t you, and scrolls past. Or worse - your existing audience knows it isn’t you and quietly unfollows.

Solved looks like: the voice training is the same shape as the trainable inbound AI agent - the agent reads your past posts, your past quote covering-letters, your past supporter-update emails, the way you describe what you do, and drafts in your voice. First ten posts in a new vertical fire as draft-for-you-to-send-or-edit so the voice has a feedback loop; after that, you keep the send-or-edit slot for the posts the agent’s flagged (a sensitive topic, a regulator-event-day post, a competitor mention). The routine posts go out unattended in a voice your existing audience recognises.

6. The dashboard answers “is our cadence actually on” in nine minutes

The “did we post anything this week” moment: Friday afternoon. You think the gallery posts went out Tuesday. You’re not sure. The accountant’s Spring Statement commentary was supposed to land at 9am Wednesday. Nobody’s mentioned it. You’d open the planner but you can’t remember which platform’s calendar is which.

Solved looks like: every queued post by current state (drafted / awaiting-sign-off / scheduled / published / failed / withdrawn), grouped by stream (gallery cadence / before-and-after engine / regulator-event commentary / appeal-impact storytelling) and by channel. Engagement metrics roll up against each stream so the “which content actually works for us” question is answered in two clicks, not three quarterly retros. Failed posts surface with the reason attached (consent withdrew, platform-side API rejected, voice-tuning flagged a phrase) and a one-tap re-queue. Total time on the dashboard: nine minutes. The cadence is on.

How the cadence runs, by default

The default service-business shape runs:

• Operational event capturedgallery delivered, job completed, class run, appeal milestone hit, regulator event landed, new arrival listed, new patient onboarded. The structured operational record (from your booking system, your job-management app, your gallery handover, your appeal calendar) is the source.
• Content assembles automaticallythe publishing cadence reads the operational record and queues the per-channel posts for the next twelve months against the right metadata. Before-and-after pairs assemble against per-image consent. Local-SEO model-and-town posts assemble against the inventory feed. Tax-event commentary assembles against the firm’s pre-approved template wired to the regulator calendar.
• Voice-tuned draftingthe brand-voice-trained agent drafts each post in your voice, channel-aware. First ten posts in a new vertical surface as draft-for-you-to-send-or-edit; routine posts after that go out unattended.
• Consent and PECR gateevery post checks the recipient’s consent state before queuing. Marketing on explicit consent, service messages on soft opt-in, withdraw-consent applied retroactively across the queue.
• Channel-aware publishingInstagram with venue-tagging discipline, Pinterest with the location-keyword stack, Google Business Profile with the local-search optimisation, Facebook with the album structure, TikTok and LinkedIn with the per-channel cuts.
• Engagement looppublished metrics write back to the operational record, so the “which content works for us” question is queryable across streams.
• Dashboardevery queued post, by state, by stream, by channel. Failed posts surface with the reason and a one-tap re-queue.

Per-vertical tuning lives on top - the decorator’s before-and-after engine fires off the job-completion event with the customer’s per-image consent state attached; the wedding-supplier’s portfolio cadence runs the twelve-month publishing rhythm off the gallery-handover event; the aesthetic-clinic’s gallery runs the JCCP / Save Face / MHRA Yellow Card audit alignment as a structural property; the commercial-grounds foreman’s monthly photo-report doubles as the next month’s social-content source; the device-repair shop’s local-SEO model-and-town cadence runs off the inventory feed; the accountant’s regulator-event cadence runs off the published calendar; the charity’s regular-giver welcome cascade runs off the DD-mandate-confirmed event from the Recurring Service Recall build.

Who this is for

The shape repeats across every UK SME with a marketing-content obligation and a one-person publishing team.

Visual-led trades - decorators, landscapers / commercial-grounds, roofers. The before-and-after engine is the conversion-driving offer in the decorating trade; the commercial-grounds photo-report doubles as monthly marketing-content source; the roofing trade’s lift-and-strip job is the same visual-led content shape.

Portfolio-led service businesses - wedding suppliers, aesthetic clinics, pet services, hospitality. The gallery-handover → twelve-months-of-content cadence; the consent-controlled before-and-after gallery with the JCCP / Save Face / Article 9 alignment; the dog-of-the-week and grooming pair with per-image consent; the venue’s wedding-feature publication rhythm.

Local-search-led businesses - device repair, independent garages, gym and fitness, funeral directors, tutors and nurseries. The model-and-town local-SEO weekly cadence; the class-timetable + transformation-story stream; the seasonal-tip + community-presence cadence.

Calendar-driven professional services - accountants, solicitors, professional services, charities. The regulator-event cadence (Spring Statement, Autumn Budget, year-end, MTD ITSA milestones); the firm’s thought-leadership rhythm tied to known dates; the supporter-impact storytelling tied to appeal milestones; the regular-giver welcome cascade on a separate consent track.

Inventory-driven e-commerce - ecommerce. The new-arrival drop, the festive cadence, the Black Friday window, the seasonal returning-customer campaign - all running off the product feed.

Same engine; different content-source feed; different consent rules; different platform priority.

The closest thing we’ve already built

planpost - our own social-media scheduling SaaS. Scheduled posting across Instagram, Facebook, Threads, LinkedIn, Pinterest, YouTube, TikTok, X, and Google Business Profile from a single dashboard, brand-voice prompt store, content-cadence orchestration, deliverability monitoring. Used today by mmitech for our own marketing cadence; the publishing-side software for any vertical that needs a content-and-portfolio cadence. The clearest reference shape for the marketing-software build.

mendmyi - the founder’s own UK device-repair business - runs its device-repair social cadence on planpost. The “iPhone 15 screens - same-day in Haverhill” model-and-town weekly cadence is the live shape on the retail-with-service side.

mendbuddy is the brand-voice training engine behind the drafting side - the same voice that picks up your inbound on every channel is the voice that drafts your social content. Voice consistency across customer-facing surfaces is the structural property of using one platform for both.

pharmaceutical-analytics.com is the dashboard shape behind the partner / studio view of the cadence - published / queued / failed / withdrawn states sorted by stream, engagement metrics rolled up against each stream, the “which content works for us” question answered from data rather than from instinct.

Tell us what’s eating Sunday night

What you do, what kind of content your business needs to publish (visual / portfolio / regulator-event / inventory / supporter-impact), which platform’s the one that matters most for inbound, which weekly post is currently the Sunday-night job that won’t go away, and where consent state has been getting in the way. Tell us the best image / story / case from the last six months that didn’t get published in time and we’ll come back with a sketch of what we’d build so the next twelve months don’t go the same way. No demo, no calendar widget. Email reply, scoped sketch, you decide.

FAQ