Building a Marketing Department That Runs Beyond Me

What happens to a business when marketing depends on one person’s memory?

The weakness becomes visible when that person is on vacation, leaves, or is simply busy the week an inquiry arrives. Inquiries get handled differently depending on who sees them. It becomes difficult to establish what was promised to a customer six months ago or what the department has committed to spending next month. Half-built campaigns and pages are harder to pick up because the thinking behind them was never written down.

Improvising is part of the job in a small company. Keeping a record of those decisions helps the business avoid solving the same problem twice.

What follows is the system I built to make the marketing work I manage easier to track, repeat, and hand over. It spans roughly seventy projects across an industrial coatings company, my marketing consultancy, a neighborhood news site, a coaching practice, a gym, and several early-stage brand projects.

The examples show how I build a marketing function, manage its daily work, and document it so the next person has somewhere to start. They describe workflows I use; any observations about results are identified separately. This is an account of my practice, not a formal evaluation of Asana or a measured study of the system’s impact.

Organizing by function and client

The workspace holds roughly seventy projects grouped into portfolios. Those portfolios organize work by business function and client account, with separate areas for budgets and archived work.

Marketing sits alongside quality, operations, shipping, banking, IT, and HR. That structure gives related work a predictable home. When a certification or shipping practice changes, I know where to look for the operational information that may affect customer-facing materials.

It also makes the workspace easier to navigate without knowing every campaign name. Someone looking for last year’s content calendar can start with the relevant business and its marketing work.

Campaigns still have a place within the system. Organizing the wider workspace by function and client gives them context and makes recurring work easier to find after a particular initiative ends.

Keeping a record of shelved work

I use four project labels: On track, Complete, Dropped, and Archived. They help me distinguish ongoing work, completed work, discontinued work, and projects filed away for reference. These are labels in my workspace, not a required sequence every project follows.

Dropped covers two situations: work that was prepared but never launched, and work that ran for a period before being discontinued. The project record needs to make that distinction clear.

A cold-email program for aerospace is an example of the first. The target list, five drafted emails, and sequence design remain on the board at the review stage. The task to build the campaign in the marketing platform was never completed. The record shows how far the work progressed; it does not establish whether the campaign would have performed well.

For work that did launch, performance has to be assessed from whatever was measured while it ran. A quiet or discontinued board is not, by itself, evidence of failure.

Keeping that record means the next person can see what was attempted and what already exists to reuse.

Procedure in Asana, records in the CRM

When I started working at Dicronite Southwest in 2019, there was no website, no CRM, and no established sales pipeline. Basic brand materials also needed to be created: a logo, colors, and standards for how the business presented itself. I had to build those foundations while developing a way to manage marketing and incoming inquiries.

By mid-2021, my involvement had shifted to smaller projects while I worked at IAA. I stayed connected to Dicronite Southwest, but I was no longer managing its marketing day to day.

Dicronite Southwest later bought Dicronite, its parent company. The business I had helped establish a marketing foundation for was now responsible for a global brand.

By the time I returned full time, the operation had changed considerably. A CRM and a developed marketing funnel were in place. My assignment was to integrate the company’s marketing and manage the processes supporting it.

Reviewing the records showed where those processes could improve: how consistently inquiries were recorded, how responses were personalized, when follow-up happened, and how leads reached the eleven businesses in the worldwide network.

Making the process repeatable

I built the inbound request-for-quote project in Asana around six steps. Each step is a task containing instructions, notes, and supporting attachments:

1. Receive — identify whether the inquiry is a direct email, form submission, copied email, or spam, and handle it accordingly.
2. Enter CRM data — create or update the contact, log the email, verify the name, and complete the contact and inquiry fields.
3. Respond — choose the appropriate response and use the supporting materials attached to the task.
4. Update contact status — record the lifecycle stage, lead status, and referral destination.
5. Schedule follow-up — create the follow-up task and enter the appropriate sequence where applicable.
6. File the email — keep the inbox focused on messages that still need attention.

The Asana project is a standing procedure. Its six tasks describe the process; individual inquiry records belong in the CRM.

That distinction matters because having a CRM does not guarantee complete records or consistent follow-up. People also need clear instructions for using it.

Someone covering the inbox can see what to check, which materials to use, and what needs to happen next. Training still matters, but it can begin with documented instructions instead of reconstructing the process from old emails.

Improving the existing operation

Through 2025 and into 2026, I worked on more personalized responses, maintaining the inquiry forms, and coordinating lead flow across the network. The records helped me understand how inquiries had been handled. The procedure gave me a place to document improvements and incorporate them into daily work.

In that period, I observed more responses, more engagement with what we sent, and more incoming leads. I have not established a measured before-and-after comparison here, so these are operational observations. They do not establish how much changed or how much of that change came from the procedure.

The same approach extends beyond inquiries. I maintain a department index covering accounts, the shared inbox, dashboards, automation, hosting, and SEO tools, alongside a standing check-in list with the business owner.

In 2019, my work focused on creating the marketing foundations. After returning, the challenge was connecting a larger operation and making its processes easier to follow. Documentation gives the company a starting point when responsibilities change.

Tracking content by channel

Two brands use the same content-calendar template, rebuilt each year. It has three parts:

• Graphics direction, assigned to the designer and kept separate from publishing.
• One task per dated occasion, planned a year ahead.
• Fields for scheduling, the website, and individual social channels, marked Yes, No, or N/A.

Channel-level tracking matters because one post can be complete in one place and pending in another. N/A distinguishes a channel that was never intended for the post from one that still needs attention.

The fields give me a quick way to check where content stands. The distinction between scheduled and published also matters: a scheduled post still needs to go live before it can be treated as published.

Asset specifications, including dimensions and file-size limits, live in the task titles. That keeps the production requirements attached to the work and reduces the need to repeat the brief.

A similar structure supports internal communications: holiday notices, closures, security awareness, and credential updates. Those communications also need dates, preparation, and a record of what has been sent.

Giving lead work a monthly rhythm

I organize demand-generation work across three boards. One tracks monthly lead pulls, with a task for each pull. Another groups work by month and source, keeping a partner’s list separate from mine. A third holds campaign planning, where the sequence is drafted before it is built in the marketing platform.

Each board gives recurring work a defined output and a place in the schedule.

The reporting project starts with the questions the dashboards need to answer:

• How many referrals came in this month?
• What industries are they from?
• What did they ask about?
• Which product line is the inquiry for?
• Which certifications does the customer need?
• What positive or negative feedback did we receive?

Starting with questions keeps the reporting requirements connected to decisions the business needs to make. It also gives me a basis for checking whether the necessary information is being captured in the CRM.

Those requirements can remain useful if the reporting tool changes, even though the data connections and reports may need to be rebuilt.

Tracking spend by line item

I track marketing spend monthly, with one task per vendor and fields for amount, category, and whether the cost is fixed or variable. Subscriptions, stock imagery, contractors, SEO tools, link management, print, and travel each have a line item and status.

A separate project records the tools and services the department uses, providing an inventory alongside the monthly spending view.

This structure gives me visibility into what marketing costs and where the money goes. It does not, by itself, demonstrate savings.

Separating fixed and variable costs helps explain the monthly baseline, but that distinction is different from whether a cost is committed or discretionary. A variable expense can still be contractually committed; a recurring subscription may be cancelable. Those obligations need to be checked before treating a line item as available to cut.

For a business building its marketing function, a useful starting point is a clear account of what is being spent, what it supports, and what obligations remain.

Managing client production and review

Across clients such as a coaching practice, a local news site, a gym, and a services brand, I use a recurring production sequence: logo work, brand standards, website development, and launch checklists for the website, social channels, and email.

That sequence describes production. Before design begins, the brief needs to establish what the business wants to achieve, who it needs to reach, and what the agreed scope includes. The production plan should serve those decisions, with existing brand assets and the client’s needs determining how much work each stage requires.

Review happens inside the task. Comment threads and attached versions keep feedback and approval decisions alongside the work they concern. An explicit approval is still needed; a comment thread alone does not establish that the client signed off.

Iterations get versioned tasks. A header might run from V1 through V5, rather than being quietly overwritten in one task. That makes the progression visible and preserves the context behind revisions.

Together, those records help me return to earlier decisions without relying on memory or searching through separate conversations.

Where the system needs work

The clearest weakness is the overdue list: a long tail of tasks past their due dates, some carried for months.