Most content teams are small, and the work around each post takes longer than the writing itself. You scale content with a small team by running publishing as an operation: one calendar, fixed templates, a checklist for every field, a quality check before anything goes live and a regular cycle for updating old posts, and then by cutting the manual steps between them. In research by the Content Marketing Institute, most B2B marketers with a content team said it had just two to five people, and Orbit Media's 2026 survey puts the average time to write one blog post at 3 hours and 20 minutes, before images, SEO fields, translation and social posts. Below is a workflow a small bilingual team can run every week without hiring.
How small are content teams, and what holds them back?
The most regular data comes from the Content Marketing Institute (CMI) and MarketingProfs, whose annual surveys mostly cover B2B marketers in North America. The figures are global, but the pattern is familiar to marketing teams in Egypt and the Gulf.
- Teams are small. In the edition published in October 2024, 54% of B2B marketers with a dedicated content team said it had two to five people, and 45% said they lacked a scalable model for content creation.
- Approvals slow things down. In the same edition, 33% named workflow and the content approval process as a challenge.
- Resources are the main limit. In the latest edition, published in October 2025 and based on 1,015 B2B marketers, resource constraints (time, people and budget) were among the top three challenges at 39%, and 28% struggled to create enough quality content to meet their organisation's needs.
- Teams are not about to grow. Asked where they would invest more in 2026, 45% chose AI-powered marketing tools, while human resources (salaries, training and development) came last at 9%.
Most teams will not get more people. Output has to grow through better process, not headcount.
What does it take to publish one bilingual post?
Writing is only the start. For a company that publishes in Arabic and English, one article usually involves all of this:
| Stage | What has to be done | Done again for the second language? |
|---|---|---|
| Brief | Topic, search intent, audience, sources | No |
| Writing | Body text, headings, internal links | Yes, and the Arabic should be written, not translated word for word |
| Fields | Title, slug, excerpt, category, author, keywords | Yes |
| SEO | Meta title, meta description, FAQs | Yes |
| Image | Hero image, text on the image, alt text | The image once, text and alt text twice |
| Review | Facts and figures checked, links tested, mobile preview | Yes |
| Scheduling | Publish date and time in the right time zone | Yes |
| Social | A post for each platform with the link | Yes, for each platform |
| After publishing | Check the live page, update the calendar, set a review date | No |
The 3 hours and 20 minutes in Orbit Media's survey of 1,042 content marketers covers the writing alone. Every other row is time on top, and most of it is clicking through admin screens rather than thinking. That is also where mistakes creep in: a missing meta description, an English slug on the Arabic page, a post scheduled in the wrong time zone. We look at the cost of that clicking in the hidden time cost of dashboard clicks.
Distribution is part of the job, not an extra. DataReportal counted 51.6 million social media user identities in Egypt and 38.6 million in Saudi Arabia in October 2025. Identities are not the same as unique people, but the point stands: the social posts that go with each article deserve the same care as the article itself.
Why does updating old content matter as much as publishing new posts?
Publishing more is not the same as being found. A 2023 study by the SEO data company Ahrefs found that 96.55% of the roughly 14 billion pages in its index got no traffic from Google at all. For a small team, that is an argument for improving pages that already show signs of life before adding new ones.
Google's own guidance is direct about what does not work. Its guide to helpful content asks whether you are "changing the date of pages to make them seem fresh when the content has not substantially changed", and says that adding or removing content mainly to make a site seem fresh will not help. Its spam policies also treat "scaled content abuse", many pages created mainly to manipulate rankings rather than help users, as a violation "no matter how it's created". A real refresh changes the substance.
The posts most worth updating are usually these:
- Pages that appear often in search results but get few clicks: rewrite the title and meta description.
- Posts that have been losing traffic for months.
- Posts with outdated facts, prices, years or screenshots.
- Posts with broken links, or links to pages you have since replaced.
- Older posts that a newer article answers better: merge them and redirect the old address.
What does a practical content operations workflow look like?
Give every post the same path from idea to refresh, with one owner and one clear "done" at each stage.
| Stage | What happens | Owner | Done when |
|---|---|---|---|
| Idea | Topic added to the calendar with its keyword and goal | Marketing lead | Approved in the weekly planning slot |
| Draft | Written from the template in both languages | Writer | Every section of the template is filled |
| Review | Facts, figures, links and tone checked | Editor | The quality checklist is complete |
| Approval | Final read of anything public-facing | Approver | Approved in writing |
| Scheduled | Fields, image and date set in the CMS | Publisher | Preview checked in both languages |
| Published | Live page and social posts checked | Publisher | Links and images work |
| Refresh due | Post flagged on its review date | Editor | Updated, merged or retired |
Run it on a weekly rhythm: one slot to approve the coming topics, one to review drafts, and a monthly look at the refresh list. Keep every status in one shared calendar so anyone can see what is stuck and why. One person can hold several roles in a small team, but the writer should not be the only reviewer of their own post.
Which templates and checklists save the most time?
- A post template: an opening that answers the question, headings phrased as questions, at least one table, internal links and a closing call to action.
- A field sheet: every CMS field in both languages, with the length limits your SEO tool uses.
- An image brief: size, style, the text on the image in each language and the alt text.
- A social template for each platform: the hook, the link and the hashtags in both languages.
- A bilingual glossary: how you write product names, technical terms and numbers in Arabic and English, so different writers stay consistent.
And a quality check that runs before anything is scheduled:
- Every figure links to the source it came from.
- All links open, and internal links point to the right language.
- Meta title, meta description and excerpt are filled in both languages.
- The image has alt text in both languages.
- The Arabic page uses Arabic punctuation and reads correctly from right to left.
- The publish date and time zone are correct.
- The call to action points to the right page.
How do you set up a refresh cycle for old posts?
- Set a review date at publishing time, earlier for posts with prices, figures or a year in the title.
- Pull the list once a month: posts that are due, plus any that lost traffic or show many impressions but few clicks in Search Console.
- Decide for each post: update it, merge it into a stronger post or retire it with a redirect.
- Update the substance first, then the title, meta description and image if needed. Keep the same address.
- Change the visible "updated" date only when the content really changed, and note what changed in a log.
- Share the updated post again and treat the update as a fresh reason to post.
Where does AI help, and where should people stay in charge?
AI is already part of most content teams: in CMI's latest survey, 95% of B2B marketers said their organisations use AI-powered applications. The useful question is which steps to hand over. AI does well at drafting fields from a finished article, suggesting internal links, preparing social versions, checking a post against your checklist and moving dates in bulk. People should keep the choice of topics, the facts, the final read and the approval of anything public. Google's guidance is clear on this point too: it counts large amounts of generative AI text produced without manual oversight or curation as "little to no effort". For the rules that keep AI actions safe, see our guide to permissions, approvals and audit logs.
How does Amrak handle content operations?
On our Amrak page we count 14 manual steps to publish one article by hand, from logging in and filling in fields such as the title, image, search description and publish date, through to previewing and publishing. With Amrak, a team member writes one sentence and then checks the result. HBS runs its own website, articles, marketing calendar and client portal through Amrak, as we describe in how HBS runs its own work on Amrak.
- Publish on a set date with an image. One request such as "write a post on shipping to the Gulf, add a fitting image and publish it on Thursday morning" replaces the trip through every admin screen.
- Reschedule many posts at once. When a launch moves, one request moves the whole set instead of opening each post.
- Quality checks before completion. Amrak prepares the full change before carrying it out, and your team checks the result against its own checklist.
- Approvals for sensitive actions. Messages to clients and deleting anything always wait for approval, and in the command map you agree with HBS which other actions, such as publishing to your public website, should wait too.
- Permissions by person. Each person can only reach what their permissions allow, so a writer can draft while an editor publishes.
- A log of every action: who asked, when and what changed, which also gives you a record of the updates made through Amrak.
- Small updates between posts. Commands such as "change the phone number on every page" or "add two FAQs to the maintenance page" handle the edits we cover in updating your website without a developer.
Amrak works on top of your current website and CMS with no migration, your data stays in your system and you choose your AI provider. For ready-made marketing commands, see Amrak commands by department, and for the full flow from request to action, how Amrak works.
If you want to publish, schedule and update content in both languages without growing your team, book a free discovery session for Amrak and we will map the commands your content workflow needs.
