The Nine-Month Trough: Why Accounting Marketers Win in July, Not April — and the GoHighLevel Build That Gets Them There

Every agency serving accounting firms builds the same thing first: a tax-season lead campaign. Landing page, Meta ads, a "book your tax appointment" calendar, a reminder sequence. It gets built in December, runs hot from January, and by mid-April everybody is exhausted and quietly relieved that it is over.

Then May arrives and the account goes silent.

This is the single most under-addressed structural problem in accounting marketing, and it is not a marketing problem at all. It is a business-model problem that marketing automation happens to be unusually good at solving. A firm that sells only individual tax returns has a business that earns violently for fourteen weeks and starves for thirty-eight. No amount of additional February lead volume fixes that. More leads in February usually just means more unanswered voicemails in February.

The leverage is in the other nine months. And the specific mechanism that converts those nine months from dead air into recurring revenue is boringly concrete: take the clients the firm already has, and move some measurable percentage of them from a once-a-year transaction to a monthly one.

This post is about how to build that in GoHighLevel, across many firm sub-accounts, without rebuilding it every time — and about the second problem that has to be solved alongside it, because it is the thing that poisons the client relationship before you ever get to sell them anything: the document chase.

Why does accounting revenue collapse the moment tax season ends?

Because the product most firms sell is intrinsically annual, and nothing in the standard firm workflow converts an annual buyer into a recurring one. A typical individual-return-heavy practice books somewhere between 60 and 75 percent of its annual revenue between mid-January and the April filing window. Extension work and business returns spread a portion into the autumn, but the shape stays the same: a spike, then a long flat.

Look at what that does to a firm operationally. From January to April the firm is capacity-constrained — every hour is spoken for, phones go unanswered, new enquiries get triaged badly or not at all. Firms in this window routinely fail to respond to 30 to 50 percent of inbound enquiries within 48 hours, not because they do not care but because there is no one free to care.

Then from May the constraint inverts completely. The firm has capacity and no demand. Staff utilization in a seasonal practice can swing from over 90 percent in March to under 45 percent in July. That is not a marketing softness. That is half a payroll being carried by revenue that was earned four months ago.

Meanwhile the client relationship goes dormant too. The firm speaks to a 1040-only client roughly twice a year — once to collect documents, once to deliver the return. Eleven months of silence is not enough contact to sustain trust, let alone to sell a second service.

So the firm's annual pattern looks like this: overwhelmed and unresponsive when demand is high, underutilized and invisible when demand is low, and never in contact long enough to expand the relationship. Every one of those three is addressable with sequencing.

What does the nine-month trough actually cost — in numbers?

The cost is easiest to see by comparing two firms with identical client counts. Consider a firm with 400 individual clients at an average fee of $450 per return. That is $180,000 in seasonal revenue, essentially all of it landing in a fourteen-week window.

Now assume 12 percent of those clients — 48 of them — are converted onto a monthly bookkeeping or advisory arrangement at $350 per month. That is $16,800 per month, or $201,600 annualized, and it arrives in twelve even instalments rather than one avalanche.

The firm has just more than doubled revenue without adding a single new client. It also fundamentally changed its risk profile: instead of one make-or-break quarter, it has predictable monthly cash flow that covers fixed costs regardless of season.

That is the pitch your agency should be making to accounting firms, and it is a much stronger pitch than "we will get you more tax leads." It reframes you from a lead vendor into the mechanism by which the firm restructures its own economics.

It also changes what your agency is worth. Lead generation for a seasonal business is a seasonal contract — firms churn you in May. A retainer that is producing recurring revenue conversion in July is a retainer nobody cancels in July. The nine-month build is as much about your own revenue stability as the firm's.

There is a third cost line worth naming: rework. When a firm is silent for nine months, a meaningful share of its client base drifts. Attrition in unmanaged seasonal client bases commonly runs 8 to 15 percent annually, and the firm typically only discovers it in February when the return does not come in. Re-acquisition costs several times more than retention. Off-season contact is retention infrastructure disguised as marketing.

How do accounting firms fix the off-season revenue trough?

By running a deliberate, calendar-driven campaign architecture in which the off-season is not the absence of tax season but a separate campaign with its own offer, its own audience, and its own conversion goal. The audience is the existing client base. The offer is a monthly service. The goal is conversion, not acquisition.

Practically, this means splitting the year into four campaign modes rather than treating it as one season plus dead time.

Capture mode (roughly January to mid-April). Inbound tax enquiries, fast response, appointment booking, document collection, filing. The primary automation job here is not lead generation — it is response speed and throughput, because the firm is capacity-constrained.

Conversion mode (May to August). The existing client base is worked with advisory and bookkeeping offers. This is the highest-value nine-month campaign and the one almost nobody runs. The pain of the just-completed return is still fresh, and the firm has capacity to onboard.

Expansion mode (September to November). Business-client work, extension deadline support, year-end planning outreach, and second-wave advisory conversion for clients who did not respond in summer. Also the natural window for the firm's own referral campaign.

Re-engagement mode (November to January). Every prior-year client is contacted, organizers go out, engagement letters are issued and chased, and the next season's pipeline is loaded before the phones start ringing.

The point of naming the modes is that each one gets its own sequences, its own pipeline, and its own reporting. When a firm sub-account is built this way, the account never goes quiet — there is always an active campaign with a defined goal, which is the difference between a retainer that survives the summer and one that does not.

What does the seasonal campaign calendar look like month by month?

Here is the working calendar the architecture is built around. The dates are structural windows, not filing guidance — every actual deadline used in a live campaign is supplied and confirmed by the firm.

Two structural notes about this table. First, notice that document chase and signature chase span multiple modes — they are not a tax-season feature, they are permanent infrastructure that gets used harder in some months. Second, notice that reviews and referrals are deliberately scheduled in autumn rather than April. Asking a client for a review in the week their return was rushed through is asking at the worst possible moment; asking in October, after a calm advisory engagement, is asking at the best one.

Why is document collection the single biggest bottleneck in tax prep?

Because the firm cannot start work until the client sends things, and the client has no deadline pressure until the firm's deadline is already at risk. Everything else in the workflow is under the firm's control. This one step is not.

Some vocabulary, defined once. An organizer is the questionnaire or checklist a firm sends a client at the start of the season to collect their information for the year. An engagement letter is the written agreement setting out the scope of the work and terms between firm and client, typically signed before work begins. An extension is a formal request for additional time to file, which the firm handles on the client's behalf when a return cannot be completed in the original window. A CAS practice — Client Advisory Services — is the recurring advisory and outsourced-accounting side of a firm, as distinct from once-a-year compliance work.

The bottleneck lives between the organizer going out and the file being complete. In firms without automated follow-up, the gap between initial document request and complete file commonly runs 15 to 25 days, and a meaningful share of that is pure dead time — the request sits unread, nobody follows up for a week, a partial response arrives, and the cycle repeats.

Look at what a typical manual chase actually is. A staff member, already at capacity in March, remembers that the Hendersons never sent their brokerage statement. They write an email. It says something like "just following up on the documents we need." The client reads it, cannot remember what is missing, means to check, and does not. Nine days later someone notices again.

Every failure in that story is a failure of consistency and specificity, and both are exactly what automation is good at. The reminder that works is not more forceful; it is more specific, sent on a predictable cadence, escalating across channels, with a defined end point that hands off to a human rather than looping forever.

The prize is large. Cutting an average turnaround from 19 days to 6 does not just make clients happier. It raises the number of returns a firm can process in the same fourteen weeks, which is the only way a capacity-constrained business grows during its peak.

What does an effective document-reminder cadence look like?

It escalates by channel, names specific missing items, and terminates. Here is the cadence structure used in the accounting snapshot, expressed relative to the day the document request is issued.

A few design decisions inside that table matter more than the timing itself.

Itemization is the conversion driver. The reminder should render the outstanding item list dynamically from custom fields — merge fields such as contact.missing_docs — so the client sees "we still need your 2025 brokerage statement and your mortgage interest summary" instead of "please send your documents." Specific reminders routinely convert at two to three times the rate of generic ones, because they remove the client's cognitive work of figuring out what is being asked.

Channel alternation beats channel repetition. Five emails in a row train the client to ignore your emails. Email-SMS-email-SMS keeps novelty in the sequence and reaches clients who process the two channels differently.

The sequence must exit on partial completion and re-enter. If the client uploads three of five items, the cadence should recalculate the outstanding list and restart at an earlier step rather than continuing as though nothing happened. This is the piece most hand-built chases get wrong, and it is the piece that makes clients feel unheard.

Fourteen days is the ceiling, not the target. After two weeks the automation has done everything automation can do, and continuing to send is actively harmful to the relationship. The handoff to a named human with a phone number is part of the design, not an admission of failure.

The firm owns every word. The wording about deadlines, consequences of late submission, and what the firm can and cannot do sits in approved content blocks the firm supplies. Your agency builds the slots and the timing. It does not write the tax language.

How does the new-client onboarding workflow run end to end?

As a single pipeline with automated transitions, so that a new tax client moves from enquiry to work-in-progress without anyone manually shepherding the steps. The manual version of this typically requires six to ten back-and-forth touches; the automated version needs one human conversation.

The stages look like this.

• Enquiry received. Form or call captures the contact. Speed-to-lead automation fires within 60 seconds — an SMS and email acknowledging receipt with a booking link. In peak season this alone recovers enquiries that would otherwise sit unanswered for two days.
• Consultation booked. Calendar confirmation plus reminder cadence at T-24 hours and T-2 hours. No-show rates on accounting consultations fall by roughly a third with a two-touch reminder in place.
• Scope confirmed. After the call, staff select the service type, which triggers the correct downstream branch — individual return, business return, bookkeeping, or advisory.
• Engagement letter issued. The document generates with client details merged and goes out for e-signature automatically on stage change.
• Engagement letter signed. Signature chase cadence runs until signed (covered below). On signature, the client advances automatically.
• Onboarding pack sent. Portal credentials, organizer, and itemized document request all dispatch in one automated action.
• Documents outstanding. The full document-chase cadence runs here.
• File complete — work in progress. Automation notifies the assigned preparer, pauses all client-facing chase sequences, and starts a status-update cadence so the client is not left guessing.
• Delivered. Return delivered, payment request issued, and — critically — the client is tagged for the correct off-season conversion segment.

That final step is the hinge the entire nine-month strategy swings on. If the client exits the tax pipeline without being segmented for the advisory campaign, the off-season sequence has no audience. Tagging at delivery is a five-second automation that determines whether there is a summer campaign at all.

How do you automate the engagement letter and signature chase?

With a short, sharp cadence that treats an unsigned agreement as a blocking issue rather than a background task — because it is. Work cannot begin, and every day unsigned is a day of the firm's compressed season burned.

The chase runs tighter than the document cadence because the ask is smaller. A signature takes ninety seconds; a document hunt takes an evening.

• Day 0. Letter issued by email with the e-sign link, plus an SMS confirming it has been sent.
• Day 2. Email reminder. Subject line names the action, not the document.
• Day 4. SMS with a direct link. Most signature recoveries happen here.
• Day 7. Email with the firm's approved note about scheduling implications.
• Day 10. Internal task for a staff call, and the automated cadence ends.

Two implementation details worth getting right. First, the signed-status trigger should drive the pipeline directly — when the signature webhook returns, the opportunity advances and the onboarding pack fires without human involvement. Manual stage-moving is where these workflows quietly die in March.

Second, the letter content itself is the firm's, always. Scope, terms, fee language, and any limitation of liability wording come from the firm's own template and approval process. The build merges client-specific fields such as contact.first_name, contact.entity_name, and contact.service_scope into the firm's approved document. Your agency's job ends at the merge field.

Firms that automate this step consistently report signed-agreement turnaround dropping from a week or more to two or three days, and the compounding effect across 300-plus clients in a compressed season is enormous — it is several working days of season recovered.

When should the advisory and CAS upsell fire, and to whom?

May through August, to a segment the firm defines, anchored to the friction the client just experienced. Timing and segmentation carry more weight here than copy quality.

Take timing first. The client who spent three weekends in March assembling shoeboxes of receipts has a vivid, recent, emotionally-loaded memory of that experience in May. By November it has faded into a vague sense that taxes are annoying. The window in which "there is a way to never do that again" lands as relief rather than as a pitch is roughly 30 to 120 days post-delivery.

There is also a capacity argument. A firm cannot onboard fifteen new monthly bookkeeping clients in February. It can in June. Selling in the window where fulfilment is possible is basic operational hygiene, and it is why an upsell campaign that runs in season tends to either fail or succeed destructively.

Now segmentation. The firm — not your agency — defines which client profiles are candidates for the monthly offer. Typically that means clients with business income, rental activity, multiple income sources, or a self-employed schedule attached to their return, and it typically excludes simple single-source returns where a monthly service genuinely would not help.

This gets encoded as tags applied at delivery. A practical structure:

• advisory-candidate-high — business entity clients, multi-entity, or complex activity
• advisory-candidate-mid — self-employed or rental income, single entity
• bookkeeping-candidate — clients who submitted disorganized or incomplete records
• advisory-excluded — simple returns where the firm has decided no monthly offer applies

That last tag is the one that protects the relationship. A campaign that offers monthly bookkeeping to a retired client with a pension and nothing else is the reason accounting firms distrust marketing automation. Exclusion lists are a feature.

One more segmentation input that outperforms almost everything else: clients whose document chase ran long. A client whose file took 22 days to complete has demonstrated, behaviourally, that their record-keeping is a problem. The system already knows this — turnaround days are captured in the pipeline. Feeding that signal into the advisory segment is the highest-intent targeting available in the entire account, and it costs nothing to implement.

What does the off-season advisory sequence look like week by week?

It runs across roughly ten weeks, alternates between education and invitation, and asks for a conversation rather than a purchase. The structure below is the wave-one sequence deployed in May and June.

The week-six touch is the one that does disproportionate work. It reads roughly as: your return took N days to complete because we were waiting on records — here is what that looks like when the books are maintained monthly instead. The value of contact.turnaround_days is merged in from the pipeline. It is specific, it is true, it is about the client rather than the firm, and it converts.

The week-ten human handoff also matters. Sequences are excellent at warming a base and terrible at closing a $400-a-month professional services engagement. The automation's job is to deliver a short list of interested, qualified, pre-educated clients to a human being. Anything beyond that is asking software to do relationship work.

Wave two, running July into August, targets non-responders with different framing — usually year-end planning and business-owner-specific angles rather than record-keeping pain — and typically recovers an additional 3 to 5 percent conversion on top of wave one.

How did Ledger & Loft convert 14 percent of a firm's 1040-only clients?

By running exactly the architecture above for one client firm, with disciplined segmentation and a genuine human close — and by fixing the document chase first, which is what made the advisory pitch credible.

Ledger & Loft is a six-person agency serving 18 CPA and bookkeeping firms across two metros. Before the rebuild, their situation was familiar to anyone in this niche. Every firm sub-account had been built by hand. No two were alike. All 18 accounts went quiet in May, and three firms had churned the previous summer with the same reasoning: nothing is happening, we will pick this back up in the autumn.

The rebuild ran in two phases.

Phase one: document chase, deployed across all 18 firms before the season. They built the escalating cadence described earlier once, as a snapshot component, with itemized outstanding-document merge fields and partial-completion re-entry logic. Across the portfolio, average return turnaround fell from 19 days to 6 — a 68 percent reduction. Their largest firm processed 41 more returns in the same season with the same headcount, purely from throughput recovered out of dead waiting time.

That number is what bought them the credibility for phase two. When a firm has just watched your automation add 41 returns of capacity, it will listen to your proposal about the summer.

Phase two: the off-season advisory sequence, piloted on one firm. The pilot firm had 312 individual clients, of which the firm's own criteria qualified 186 as candidates for monthly bookkeeping. The ten-week sequence ran from mid-May. Outcomes:

• 186 clients entered the sequence
• 47 booked a review call — a 25.3 percent booking rate
• 26 signed onto a monthly bookkeeping engagement
• 26 of 186 is a 14.0 percent conversion of the qualified base
• Average monthly fee of $385, producing roughly $10,010 per month of new recurring revenue for the firm
• Annualized, about $120,120 added to a firm whose prior-year total revenue was near $340,000

The friction-anchored week-six email was responsible for 19 of the 47 bookings — 40 percent of all bookings from a single touch. That is what happens when a message references the client's own documented experience rather than a generic benefit.

Ledger & Loft's own economics moved accordingly. They repriced the pilot firm from $450 to $900 per month, rolled the sequence to eleven more firms over the following two seasons, and — the outcome that actually matters — stopped losing accounts in the summer. Portfolio churn went from three firms lost in one off-season to zero across the following two.

The build itself took about a week of real work, once. Every subsequent firm deployment took under an hour.

How do you run deadline and extension reminders without giving tax advice?

By treating every date as firm-supplied data and every explanatory sentence as firm-approved content, then building timing logic that references those inputs rather than encoding any knowledge of its own.

This is a hard architectural line, and it is worth being explicit about why. Your agency is not qualified to tell a taxpayer when their return is due, what an extension does, or what happens if they miss a date. The firm is. So the system is built so that it structurally cannot express an opinion.

In practice:

• Dates live in custom fields per sub-account, not in the sequence. Fields such as location.filing_deadline_individual, location.filing_deadline_business, and location.extended_deadline are populated by the firm at the start of each cycle and confirmed in writing.
• Reminder timing is relative to those fields. T-45, T-30, T-14, T-7, and T-2 days, calculated from the date the firm supplied. Change the field, the whole cadence recalculates.
• Body copy is a firm-approved content block. The sequence merges in the firm's own wording. Your agency writes none of it and edits none of it.
• Extension messaging is a branch, not a default. When staff move an opportunity to the extension stage, the client receives the firm's approved extension explanation, the document cadence resumes at a lower intensity, and the autumn follow-up sequence is scheduled.
• A change to any deadline field triggers a review task, so nothing goes out on a stale date.

The extension branch deserves particular attention because it is where most firms lose clients invisibly. A client who goes on extension in April often hears nothing until September, by which time they have concluded the firm forgot about them. A low-intensity monthly touch across the summer — a status note and a document nudge, in the firm's language — costs nothing and materially reduces autumn scramble.

It is also, incidentally, an excellent advisory segment. A client who needed an extension because their records were not ready has just made the case for monthly bookkeeping more persuasively than any marketing copy could.

Why does every firm sub-account get rebuilt from scratch, and how do you stop it?

Because the first three builds happen before the agency notices it is building the same thing three times, and by the tenth the accounts have diverged so far that consolidating them feels harder than continuing. This is the tax an agency pays for growing without standardizing.

The symptoms are recognizable. Firm 4's document cadence has six steps and firm 9's has four, because someone was in a hurry. A fix made in one account never reaches the other seventeen. Onboarding a new firm takes two to three days of a skilled builder's time. Nobody can answer "what does our document chase look like?" because there are eighteen different answers.

The fix is a canonical snapshot with a hard separation between structure and content.

Structure is standardized and identical everywhere. Sequence architecture, timing logic, pipeline stages, trigger conditions, escalation rules, tag taxonomy, reporting fields. These do not vary by firm. If firm 12 wants a fundamentally different document cadence, that is a conversation about whether the improvement should go into the master build for everyone.

Content is parameterized and unique to each firm. Firm name, staff names, service descriptions, pricing, portal URLs, calendar links, deadline dates, approved copy blocks, engagement letter templates, brand assets. All of it lives in custom fields and content blocks populated during onboarding.

Once that separation exists, deploying a new firm becomes a checklist rather than a build:

• Load the snapshot into the new sub-account
• Populate the firm field set — name, services, pricing, portal, calendar, deadline dates
• Drop in the firm's approved copy blocks and engagement letter template
• Connect the firm's domain, sending identity, and phone number
• Run the standard QA checklist — forms fire, merge fields render, cadences time correctly, pipeline automations move opportunities, exclusion tags suppress correctly
• Go live

That runbook takes about an hour. Compared against two to three days of hand-building, the arithmetic across an 18-firm portfolio is roughly six to eight weeks of skilled labour recovered per cycle — and far more importantly, a portfolio where an improvement made once improves everywhere.

What actually goes into the accounting snapshot?

Everything that is structurally identical across firms, and nothing that is not. Here is the component inventory.

Seasonal campaign architecture. Four campaign modes with their own audiences, sequences, and goals — capture, conversion, expansion, re-engagement — plus the calendar logic that activates and deactivates them without anyone remembering to.

New-client onboarding workflow. The full pipeline from enquiry to delivered, with speed-to-lead response, consultation booking and reminders, scope branching, and automated stage transitions.

Document request and chase engine. Itemized request generation, the escalating email-SMS cadence, partial-completion re-entry, internal task escalation, and turnaround-day capture into a pipeline field.

Engagement letter and e-sign chase. Template merge, e-sign dispatch on stage change, the five-touch chase, and signature-webhook-driven pipeline advancement.

Deadline and extension campaigns. Field-driven relative timing, firm-approved copy blocks, the extension branch with summer maintenance touches, and stale-date review tasks.

Advisory and CAS upsell sequences. Wave-one and wave-two campaigns, the segmentation tag taxonomy including exclusions, the friction-anchored turnaround merge, and the human-handoff task at sequence end.

Annual re-engagement. The November-to-January campaign that contacts every prior-year client, dispatches organizers, issues engagement letters, and loads the next season's pipeline before the peak.

Referral and review campaigns. Scheduled for autumn rather than season, triggered off satisfied-client and converted-client tags.

Per-firm reporting. Covered next, because it is the component agencies most often underbuild.

What is deliberately not in the snapshot: any tax content, any deadline date, any client-facing explanation of filing rules, any fee language. Those are firm inputs, every time, for every firm.

What should per-firm reporting actually show?

The metrics that prove the two things the firm is paying for — throughput during season and recurring conversion outside it. Most agency reporting for accounting firms shows leads and cost per lead, which measures the part of the business that was never the problem.

Season metrics, reported weekly from January to April:

• Enquiry response time, median and 90th percentile. The target is under five minutes, automated.
• Enquiry to booked consultation rate. Under 40 percent in peak season usually indicates a calendar or capacity issue, not a copy issue.
• Average document turnaround days, the headline operational number. This is the metric that most directly translates into firm capacity.
• Files stalled beyond 14 days, as a live count. This is the human-intervention queue.
• Signature turnaround days, from letter issued to signed.
• Returns completed per week, against the same week last year.

Off-season metrics, reported monthly from May to November:

• Qualified advisory candidates in the segment, by tier.
• Sequence engagement — open, click, and reply rates by touch, so the weak touches can be identified and replaced.
• Consult booking rate against the qualified base.
• Conversion rate to monthly service.
• New monthly recurring revenue added, and the annualized figure.
• Client contact frequency — the share of the client base contacted in the last 60 days, which is the leading indicator of next-season retention.

Two reporting practices are worth adopting as standard. First, always show last-year comparatives once you have them; a firm cannot judge whether 6-day turnaround is good without knowing it used to be 19. Second, report the recurring revenue number in annualized terms. A firm looking at "$10,010 per month added" is looking at a nice number. A firm looking at "$120,120 annualized against a $340,000 practice" is looking at a reason to renew you at double the fee.

How should an agency package and price this?

As a one-time build plus a per-firm management retainer, with the retainer priced against the recurring revenue the off-season campaigns produce rather than against hours.

A full accounting snapshot build — all nine components above — typically runs around $1,000 as a one-time setup. That is the canonical build, built once, reused across every firm in the portfolio. It is the single highest-leverage thousand dollars an agency in this niche spends, because it is amortized across every firm you will ever onboard.

Ongoing management sits between $300 and $1,000 per month per firm. The range is driven by firm count and sub-account complexity, campaign volume and how much per-firm copy iteration is involved, reporting depth, and whether the agency wants day-to-day monitoring of the stalled-file queue and human-handoff tasks.

The pricing conversation with the firm itself changes shape once the off-season build exists. Before, the agency is selling leads into a seasonal business and being judged on cost per lead — a commodity conversation with a predictable ending in May. After, the agency is the mechanism producing measurable monthly recurring revenue from the firm's existing client base, and the retainer is a fraction of the revenue it generates.

Ledger & Loft's pilot firm was paying $450 per month for lead generation. After the advisory sequence added roughly $10,000 per month in recurring revenue, $900 per month was an obvious yes. That is not a negotiating tactic; it is what happens when the value being delivered is legible in the firm's own accounts.

One structural recommendation: price the off-season work as part of the annual retainer rather than as a seasonal add-on. Firms that pay monthly year-round expect year-round activity, and the calendar architecture gives them exactly that. Agencies that bill seasonally invite the annual churn conversation they are trying to avoid.

What does the first 30 days with GHL Spark look like?

A single canonical build, deployed to one firm first, validated, then rolled across the portfolio — never eighteen simultaneous builds.

Week 1 — audit and consolidation. We review your existing firm sub-accounts, identify the best working version of each component across them, document where they have diverged, and agree the canonical structure. If you have no existing accounts, this week is spent defining the structure against your firms' actual workflows instead.

Week 2 — build. The snapshot is built in a master account: seasonal campaign architecture, onboarding pipeline, document engine, e-sign chase, deadline campaigns, advisory sequences, re-engagement, referral campaigns, and reporting. Every firm-specific element is parameterized into fields and content blocks rather than hard-coded.

Week 3 — pilot deployment and QA. The snapshot goes into one firm sub-account. The firm supplies its approved copy blocks, deadline dates, service list, pricing, and portal links. We run the full QA checklist and test every cadence end to end with real submissions before a single client receives anything.

Week 4 — rollout and handover. Remaining firms are deployed against the one-hour runbook. Your team gets the runbook, the QA checklist, the field dictionary, and the reporting templates, so onboarding firm 19 does not require us.

From there, ongoing management keeps the calendar running, iterates the sequences against engagement data, monitors the stalled-file and human-handoff queues during season, and produces per-firm reporting.

The thing worth holding onto through all of it: the tax-season campaign is the part of this business that already works. It is loud, it is urgent, and it absorbs all the attention. The build that changes an accounting firm's economics — and your retention with them — is the one that runs in July, when nobody else is paying attention.

If you are serving accounting firms on GoHighLevel and every one of your sub-accounts goes quiet in May, that silence is not a seasonal inevitability. It is an unbuilt campaign.