You shipped a big release in March. The company page posted four times that week, the founder wrote a long LinkedIn post, and two engineers shared it. Then April came, and the page went quiet. Nobody decided that. The calendar just stopped.
If that's your software company, your product team already produces material every week. What you lack is a system that turns it into posts without depending on one person's spare time. A social media calendar for software companies is that system, and it's smaller than you think.
Why software company calendars die after three weeks
The pattern is almost always the same. A launch creates a burst of energy, someone builds a spreadsheet with 90 days of dates, and the first three weeks go fine. Then a customer escalation lands, the person who owned the calendar gets pulled back into their real job, and the empty cells pile up.
A date grid fails because it asks you to invent content on a schedule. It has no answer to "what do we post on the 14th?" except a scramble.
Start with pillars, not dates
Before you pick a single day, decide what the calendar is made of. Four or five content pillars is enough. For a software company, these work well:
- Product in use. A feature shown solving a real task.
- Customer outcomes. What changed for a named customer, with their permission.
- Founder point of view. What you believe about your market and why.
- How we build. An engineering decision, a trade-off, something that went wrong and what you changed.
- Market commentary. A regulation, a trend or a competitor's move, read through your own experience.
Pillars do two jobs. They answer "what do we post?" before anyone asks, and they keep the feed from becoming 100% product announcements, which is the default when nobody is steering.
Testersuite, a software testing company, works this way. Their calendar mixes product news, team stories, educational content and promotions, with categories guiding the themes. In their second year with Willow, they post at least twice a week, and colleagues share from their own profiles.
You don't need every pillar every week. You need each one to show up often enough that nobody forgets it exists.
Set a cadence you can actually hold
Pick a rhythm you can hold in the worst week of your quarter.
For most software companies with 10 to 200 employees, that means 2 to 3 posts a week in total, spread across the company page and the founder's profile. Put a floor under it: at least 1 post a week on each page, every week. LinkedIn comes first. If you can't hold it there, adding more channels only gives you more empty feeds.
Why does showing up every week matter so much? In our LinkedIn consistency report, which analysed 43,738 posts from 488 B2B company pages over 12 months, pages that moved from posting in "some weeks" to posting in "most weeks" went from 106 to 233 impressions per post, and from 7,377 to 22,435 impressions a year. That's about 3x, and it's why the floor is every week.
Going from 1 post a week to 2 helps further. In the same dataset, pages posting twice a week, every week, collected 49,385 impressions a year against 31,135 for weekly posters. Per-post reach dipped only about 5% (237 versus 250).
A caveat: this is correlation from company pages, mostly our own customers. Pages that post twice a week may also be better run in other ways. Treat it as a reason to aim for two.
Build the intake: a slot, not a request
Here's where most calendars quietly fail. The pillars are fine and the cadence is realistic, but nobody has the material. So the marketing lead asks engineering for "something to post about" and gets silence.
The fix is a slot, not a request. Book a fixed 20 to 30 minutes every week where someone pulls raw material from the places it already exists.
- Product updates. What shipped, what changed, what a customer asked for.
- Support and sales questions. The three questions that came up most this week are three posts you don't have to invent.
- Customer calls. One sentence a customer said, in their words, is worth more than a paragraph you write.
- Engineering decisions. Why you chose this approach over that one.
The person running the slot doesn't write anything yet. They just collect. A shared document or board works, as long as it lives where people already work.
What stays out
Software companies handle client data, roadmaps and security details. Agree on a short list before the first post goes out:
- Roadmap items you haven't committed to publicly.
- Customer names without written permission. An NDA or contract can bar naming a client even when GDPR doesn't. And if a post shows identifiable personal data, Article 6 of the GDPR requires one of six lawful bases for it.
- Security details, including how your systems are set up, what broke and which vulnerabilities you found.
One person on the approval step should know this list by heart.
What to automate in your LinkedIn content calendar, and what not to
The word "automation" covers two very different things, and mixing them up is how companies end up with feeds nobody reads.
Automate the plumbing
- Scheduling. Writing a post on Tuesday and publishing it on Thursday morning is fine. LinkedIn allows scheduling Company Page posts through approved third-party partner tools. Check whether your tool is an approved partner before you commit.
- Reminders. A nudge to the founder before the weekly session: "Your drafts are ready for review."
- Content-bank tracking. Which pillars have material waiting and which are running dry.
- Repurposing prompts. A webinar, a release and a customer call each become several posts. Our guide to repurposing content covers how.
- Reporting. Pull the numbers together once a month so you don't build them by hand.
Keep these human
- Unreviewed AI text. Drafting with AI is fine. Triniti Solutions, a Dutch custom software company, uses AI drafts so the founders can focus on strategy. But a person reads and edits every draft before it goes out.
- Engagement. Comments and replies from software that pretends to be you. LinkedIn's help page on prohibited software and extensions says third-party tools that scrape or automate activity aren't allowed, and its User Agreement bans bots and other unauthorised automated methods. Violations can lead to account restrictions. Scheduling saves you time. Automating your presence puts your account at risk.
- The founder's voice. The founder's profile is where your point of view lives. If it reads like everyone else's, it has no job to do.
On that last point, there's no shortage of AI-written posts on LinkedIn. Originality.ai estimated in late 2024 that 54% of long-form posts were likely AI-generated, and a 2026 update put it at 81.2%. Those are a vendor's detector estimates, on English-language posts, so treat them as a direction.
We haven't found a solid study showing that lightly edited AI posts get less engagement, and we won't invent one. Our argument is simpler. When most posts sound alike, sounding like yourself is the cheapest way to stand out.
We use AI ourselves, so here's how we keep it personal. Willow Create drafts from a profile of your business: your services, audience, tone and point of view. A coach checks each draft for accuracy, tone and timing before it reaches you, and you approve, tweak or swap it. You can also add custom instructions to fine-tune future posts.
The principle holds with any tool. The draft is a starting point, and a person who knows the business has the last word.
Run the whole week in one session
Put as much of the week as you can into one sitting of about an hour, with the same people every week. One slot, one agenda, and nothing left over for Thursday.
The session, in order (owners in brackets)
- Intake (marketing lead or founder's assistant). Spend the first 20 to 30 minutes pulling raw material into the content bank, and tag each item with a pillar so gaps are visible.
- Draft (the same person, or an AI-assisted draft). Pick two or three items and write drafts in the speaker's own words. Mark anything on the "stays out" list and hold it back.
- Approve (the founder, plus the relevant engineer or product owner). Review for voice and accuracy, and check customer mentions against permissions. The founder's profile needs the founder's say, no exceptions. Ask the engineer or product owner to join for this part only.
- Schedule (the person whose name is on the post). Queue every approved post at the times you've chosen, so nothing waits on anyone later in the week.
What stays outside the session
- Replying to comments (the person whose name is on the post). Five minutes a day is enough, and it has to be you.
- The monthly review (marketing lead). Look at which pillars drew conversations and which fell flat, then adjust the mix for next month. Leave the cadence alone.
One person owns the system. Several people feed it. And nobody should be the only person who knows how it works.
When to hand the system to someone else
Ownership is the part that breaks first. In a 40-person software company, the owner is usually already doing three other jobs. Our customers show three ways of dealing with that.
United Codes, a Belgian software company building Oracle APEX tools, had no structure before it started with us. Its COO, Jackie McIlroy, owns the calendar, with coaching behind her: "Besides the 1-on-1, my favorite part is the calendar view. That is my daily dashboard of what is going on and upcoming." In 12 months, their LinkedIn followers grew 31.21% (+308), with 81,083 impressions and 6,085 engagements.
Triniti Solutions shows the founder-led version. They started from near zero, so their percentages look big. Over their first year, impressions reached 5,527 and engagements 852. As Rick Zwart puts it: "We're not marketers, but Willow made it feel doable."
And Fieldside, an IT group within Cronos, runs 17 pages in one calendar: 11 on LinkedIn, 5 on Facebook and 1 on Instagram. It's what the system looks like once a team is large enough to own it.
If you'd rather not own the system, that's what we do. We build you a quarterly content calendar, write drafts in your voice for you to review, and a coach keeps the rhythm going. If you're weighing that up, our post on whether to outsource your social media lays out the trade-offs honestly. For the software-specific version, see social media coaching for ICT companies. And if you'd rather start on your own, our guide to what to post on social media is a good place to begin.
Either way, start with the pillars this week. The dates can wait.