Most businesses already have more useful content topics than they realise. The topics appear in customer emails, telephone calls, enquiry forms, sales notes and questions that employees explain repeatedly. The difficulty begins when this information is scattered and every new publishing week starts with a blank page.
A 90-day content plan turns everyday questions into a manageable working rhythm. It is more than a list of publication dates. A useful plan connects the customer need, the business answer, the right format, the responsible person and the next step available to the reader.
This guide presents a practical way to collect customer questions, choose priorities, build a three-month calendar and review the result. The examples can be adapted to different service businesses. They do not prescribe a particular platform, publishing frequency or guaranteed outcome.
1. Decide what the content plan must help achieve
Before writing a topic list, name one main business objective. It may be to explain services more clearly, prepare customers for an initial conversation, reduce repeated questions or help people compare suitable solutions. Choose a quarterly direction that the team can support with accurate information.
Connect the objective to customer action. “Create more content” does not explain what should change. A more useful objective is that readers understand what information to prepare, how to choose a service category or which questions to ask during the first discussion.
Document boundaries as well. If the business does not yet offer a function, do not present it as a finished service. If conditions are agreed individually, do not invent a universal price or delivery time. Clear boundaries make the writing credible and factually accurate.
2. Select a specific audience situation for each part of the plan
One article cannot serve equally well someone who has only begun to recognise a problem and a customer already preparing technical project information. Separate at least three stages in the plan: recognising the problem, assessing possible solutions and preparing for a conversation or enquiry.
Describe the audience through a situation rather than only a job title or industry. Examples include a manager whose website enquiries are processed manually, a service owner considering an online booking calendar, or a team that publishes regularly without connecting topics to customer questions.
This description determines the language and level of detail. A reader recognising a problem needs a clear explanation. Someone already evaluating a solution benefits from a checklist, a process example and questions to prepare.
3. Collect questions where they already occur
Build the idea library from existing conversations. Review email subjects, enquiry categories, call notes, sales summaries, support questions and comments. Record the substance of the question without copying customer names, contact details or other unnecessary personal information.
Involve people who speak with customers every day. Sales staff may know the questions asked before a decision, project managers see uncertainty at the beginning of delivery, and support staff notice questions after implementation. A short shared review often produces a fuller topic map than individual brainstorming.
Agree on one simple place where questions are recorded. Each entry only needs the question, context, service topic, customer stage and responsible expert. Consistent recording matters more at the beginning than a complex tool.
4. Preserve the customer's wording and clarify the intent
The words customers use reveal how they understand a problem. Keep the initial question close to its original meaning, then record what the person is actually trying to decide. A question about price may conceal a need to understand scope, compare alternatives or avoid unexpected work.
Not every customer phrase becomes a strong headline without editing. Conversational wording can be turned into a clear title suitable for reading and search while preserving the original intent. Answer the central question first and add detail afterwards.
Mark questions that cannot receive one public answer. If the solution depends on company processes, systems or project scope, explain the evaluation criteria and invite the reader to prepare relevant information for an individual discussion.
5. Group questions into topic clusters
When the list is large enough, combine related questions. One cluster may cover website content, another booking flows, and others integrations, automation or practical AI use. Grouping reveals when a broad subject should become several focused materials.
Choose one foundation piece for every cluster. It should explain the subject from the starting point to a useful next step. Shorter articles, checklists, examples and social posts can then support it. The foundation piece does not need to answer everything; it needs to make the structure understandable.
Avoid several articles with nearly identical promises. Compare each proposed topic with the published archive. If a question has already been covered, choose a narrower angle, improve the existing material or create a practical follow-up.
6. Prioritise topics with simple criteria
Do not select priorities only because an idea sounds interesting. Consider how often the question occurs, how important it is to a customer's decision, whether the business has a verifiable answer and whether the subject matches the current offer. These criteria filter out fashionable topics that do not support the customer journey.
A simple high, medium or low rating is enough. A complicated scoring system is optional. What matters is that the team can explain why a topic was chosen and which reader question it answers.
Mark seasonal or time-limited subjects separately. If a material has a deadline, schedule preparation early enough. Build the remaining calendar around durable topics that can be updated when the offer changes.
7. Connect every topic to the next customer step
For every material, decide what the reader can do afterwards. An introductory explanation may lead to a related article. A practical guide may lead to a preparation checklist. A service-evaluation article may lead to an enquiry for a discussion.
The call to action must match the content. An article about content planning should not suddenly send the reader to an unrelated booking feature. A relevant link lets the reader continue naturally and supports a coherent site structure.
An enquiry form is not a purchase or payment confirmation. The call-to-action wording should explain what the person will submit and what may happen next. When individual assessment is required, state it clearly.
8. Build a 90-day rhythm the team can maintain
Divide three months into weeks and reserve space for the main materials. Choose the publishing frequency according to available time, fact checking and asset production. A realistic rhythm the team can finish is more useful than an overloaded calendar of unverified drafts.
Record more than the publication date. Include the topic, audience stage, format, subject expert, draft deadline, review deadline, image requirement, internal links and status. The calendar then becomes a working tool rather than a decorative table.
Leave space for unplanned but important questions. Every day does not need an assigned post. Capacity in the calendar allows the team to respond to real customer needs without losing the main quarterly direction.
9. Start with the question and then select the format
First determine what answer the customer needs, then choose the format. A complicated decision may require a detailed article. A sequential task suits a checklist. One focused tip may fit a short post, while a short video or illustration can make a process easier to see.
One question can support several materials when each has a separate purpose. A foundation article explains the context, a short card highlights one action, a video demonstrates a process and an enquiry page collects the necessary information. The factual answer must remain consistent across them.
Do not copy one text mechanically into every channel. Adapt length and structure while preserving meaning. Each format should communicate its main idea even when the reader does not open the others.
10. Outline the article before writing the full draft
Prepare a short outline first: central question, direct answer, required explanations, example, verification steps, internal links and call to action. This structure prevents repetition and keeps the reasoning in a logical order.
Headings should make the article easy to scan. Each H2 answers one sub-question and develops the previous point. When a section becomes too broad, divide it into H3 steps or a separate article. Headings do not need the same keyword repeated everywhere.
The introduction should quickly explain who the article serves and what the reader will gain. The ending should provide a practical next step without repeating the entire text. Use calm, concrete language and explain technical terms.
11. Treat images as part of the content
An image should help explain the article. A content-planning guide can use a process illustration, a visual question library, a question transformed into several formats and a review scene. Four distinct images create rhythm and divide a long article into manageable parts.
Write meaningful alt text for every image. Describe its function in this article rather than repeating the filename or listing decorative details. If an image contains important written information, include that information in the article text as well.
Before publishing, check file size, proportions, sharpness and mobile display. Use material permitted for publication and exclude customer personal data, private correspondence and unauthorised brands.
12. Assign a source and approver for business facts
Every article needs a person who can verify company facts. That person confirms the service description, process order, conditions and wording that may affect customer expectations. A content editor can check structure, language and links but cannot invent missing business information.
When information is uncertain, mark the question in the draft and resolve it before publication. Do not fill the gap with an assumption about price, timing, outcome or integration capability. A clearly stated limitation is more valuable than a confident guess.
Keep a short record of who reviewed the material and when. This makes later updates easier because the team knows who to ask when the service or process changes.
13. Plan Latvian and English as one editorial task
Both versions of a multilingual article must communicate the same factual information. Complete and review the primary version first, then translate it while preserving the heading hierarchy, meaning of examples, internal links and call to action.
Translation is more than replacing words. English sentences should sound natural without adding new promises or removing important limits. Service names and button labels should follow the terminology used on the corresponding language version of the site.
Check SEO fields, alt text, canonical and hreflang as well. The language switch should open the matching version of the same article. Internal links in English content should lead to English pages when those pages exist.
14. Divide the workflow into clear statuses
A simple workflow can include topic, outline, draft, fact review, language review, images, ready to publish and published. Define what must be complete before a material moves to the next status. This prevents an unfinished draft from being mistaken for a finished article.
Assign responsibility according to expertise. The subject expert supplies facts, the writer creates the draft, the editor checks clarity, and the publisher verifies WordPress fields and the public result. In a small business, one person may hold several roles, but the steps still help.
When work becomes blocked, name the missing item in the calendar. “Waiting” does not explain the action required. “Waiting for confirmation of service steps” or “waiting for image licence review” is more useful.
15. Verify the material before WordPress publication
Before upload, check the title, excerpt, H2 and H3 sequence, internal links, enquiry link, images and alt text. Confirm that the draft contains no unapproved prices, client examples, statistics or guarantees. Review each language separately.
Save the article as a draft first. Read the saved version and compare the important fields: status, slug, featured image, SEO title and description, service metadata and the English object. Correct any field that WordPress has discarded or altered before publication.
Publication is complete only after the public page has been checked. Open both language versions and verify image loading, links, archive cards, canonical, hreflang and structured data. The editor status alone does not prove the complete public experience.
16. Repurpose material while keeping one source
After the foundation article has been approved, create shorter materials from it. Select one idea for a social post, one sequence for a checklist and one visual example for a video concept. Keep the foundation article as the factual source.
When core information changes, update the primary material first and then review the derived formats. Otherwise different channels may contain contradictory conditions. Mark relationships between materials in the content library.
Repurposing does not mean publishing the same post indefinitely. Give each format a specific reader need. Sometimes the best next action is to update an existing article rather than create another nearly identical page.
17. Review results at the end of the quarter
At the end of the 90-day period, compare the plan with the completed work. Which topics received expert answers on time? Which formats required more work? Which links did people use, and which questions continued to appear in conversations? Select only data that supports the next decision.
Interpret numbers alongside the purpose of the material. An article designed to prepare customers for a conversation may be valuable without large traffic if it helps produce clearer enquiries. A frequently viewed article may need a clearer next step when readers do not continue.
Record three decisions for the next quarter: what to continue, what to improve and what to stop. The review then becomes the beginning of the next plan rather than a separate report.
18. Practical example: from a question list to a quarterly calendar
Imagine a small professional-services company receiving questions by email, telephone and a website enquiry form. For one week, the team records the substance of each question in one table without copying personal customer data. Every entry includes the service topic, customer stage, frequency and the employee able to verify the answer.
The review reveals three recurring clusters: preparing for the service, understanding the process and choosing between different approaches. The team selects one foundation article for each cluster. Remaining questions become sections, focused follow-ups or topics for a later quarter.
During the first month, the company publishes a material that helps readers recognise the problem and prepare. The second month contains a more detailed process guide. The third month provides comparison criteria to use before a conversation. Short posts between the foundation articles answer one specific question or share part of a checklist.
Every calendar item has a draft date, fact reviewer, language review and image task. An expert confirms business facts before publication. The writer completes Latvian, prepares English after approval, and the publisher verifies links, SEO fields, alt text and the saved WordPress draft.
If an expert cannot confirm a topic in time, the team does not publish a guess. It moves the material and uses the next priority question with a verified answer. The reason remains in the calendar so the quarterly review can distinguish limited capacity from unclear responsibility.
At the end of the quarter, the company looks beyond page views. It checks whether basic questions appear less often in sales conversations, whether readers continue to related materials and whether enquiries contain more useful preparation information. These observations are compared with the original objective before the next 90-day topics are chosen.
The example shows that a 90-day plan is a visible set of working decisions. Topics may change when customer questions or the offer changes, but every change retains a reason, an owner and a review step.
19. Practical checklist for the next 90 days
Confirm that the plan has one main objective, a defined audience situation, real customer questions, topic clusters and clear priorities. Every planned material needs an owner, deadline, format, fact reviewer, image requirement, internal links and next step.
Review the calendar before each production stage. Check that team capacity still supports the plan and that the offer has not changed. If a topic is no longer relevant, move it and select the next priority customer question.
CANIMAPS DIGITAL helps businesses organise website content, a public blog and content-planning work around the actual company offer. Read how a content plan can explain your offer and how an enquiry form fits the customer journey. To discuss your website and content needs, send an enquiry for a conversation.