Weekly Accounting provides fractional CFO, accounting, and bookkeeping services to small and medium-sized businesses. The clients aren’t quite big enough for a full in-house finance team, but they still need someone building the financial model that drives their decisions. That’s Weekly Accounting’s job: consolidate data from every platform a client runs on into one financial picture, then help them make decisions from it.

They’re fully remote. And in a little over two years, they tripled, from fewer than 20 employees serving around 80 clients to 50 full-time employees serving 200 active clients today.

“It was very startupy,” says Kendra Edelman Smith, who has been at Weekly Accounting for four of its six years. “Everybody just had their own Gmail. We were small enough that we could get away with it. You’d CC whoever needed to be looped in and hope the right person answered.”

The operational core of Weekly Accounting is a one-to-one client-to-CFO pairing. Every client has a dedicated CFO who handles the strategic conversation, then routes requests internally to the accounting, data, or payments teams before funneling the answer back to the client. It’s a model built on a tight, personal relationship, which is part of what clients are paying for.

But when every CFO lives in a personal Gmail account, that funnel becomes a single-person bottleneck. “We had a lot of manual steps,” Kendra recalls. “You’d upload emails and PDFs, figure out who needed to see what. Everything lived in individual inboxes, so if you needed context on a client, you were chasing the different pieces of the puzzle.”

Inventing a pattern when the defaults didn’t fit

The obvious first move was a classic shared inbox: one team inbox that everybody monitors. Weekly Accounting tried pieces of that in the Gmail days, but the pattern never quite fit how their clients actually communicated. Clients aren’t writing to a generic “info@” address; they’re writing to their CFO by name, because that’s the relationship they signed up for. Try to redirect them to a different address and the client experience fractures.

“We’d set up a separate address and asked clients to use it for requests so it would land in a team inbox we could triage,” Kendra explains. “But then clients would ask, ‘Wait, which email do I use for what? I schedule meetings with one address and send questions to another?’ That’s not a great client experience.”

So in Missive, the team email client they’d adopted, Weekly Accounting built something different: every CFO gets their own team inbox. Kendra has a “CFO Kendra” team inbox. Each of her coworkers has theirs. Clients still email the CFO’s personal address and nothing changes on their side, but a rule automatically routes external messages into that CFO’s team inbox and archives the original out of the personal view.

Inside each CFO’s team inbox, a dedicated project manager triages incoming mail. The PM either responds directly when they know the answer, escalates back to the CFO when the question needs a judgement call, or creates a ClickUp task through Missive’s integration and assigns it to the data, accounting, or operations team for longer work. “The CFO only sees the things they specifically need to respond to,” Kendra says. “Everything else gets handled by the team or lands in ClickUp with the right owner.”

The layered rule setup

The routing rule sounds simple on paper, but getting it right took a couple of iterations. The first version said: any email sent to the CFO’s address that doesn’t come from a Weekly Accounting domain goes to the team inbox. That kept internal, coworker-to-coworker email out of the shared view.

Then the edge cases surfaced. Payroll-provider pay stubs were landing in team inboxes because they technically came from an outside domain. A second, exclusionary rule was added to catch them by subject line: payroll notifications stay in the CFO’s personal inbox, everything else external routes to the team.

“We got help from Missive’s support team on this piece of the puzzle. It was a really big unlock,” Kendra says. The rule has to be set up under each individual’s personal inbox because of how email account permissions work, so configuring it is now baked into Weekly Accounting’s CFO onboarding checklist.

Accounts payable, centralized but open to the whole team

The second major workflow is accounts payable. AP is a service Weekly Accounting offers its clients: bills come in, invoices need to be entered, and the client presses a button to pay. Before Missive, the AP team had to log into each client’s individual account separately to pull invoices down. Now every client has a dedicated AP team inbox inside Missive, and the AP team can comment, escalate to the CFO, and hand work off in one place.

The philosophy choice that stood out: every AP inbox is visible to every team member, not just the AP team. A data-team coworker might never touch most of them. But if they’re pulled in for support on a specific client question, they can open the inbox and see the full email history immediately instead of waiting for access to be granted.

“Most of our team inboxes are open to everyone now,” Kendra says. “They’re all client-facing work anyway, and somebody on another team might need that context at any given moment.”

Text messages, integrations, and the automation layer on top

Clients don’t only email. Some prefer texting, so Weekly Accounting uses the Dialpad integration to pull SMS into Missive. Rules route messages by phone number: if an SMS arrives from a known client number, it shows up directly in the assigned CFO’s Missive inbox. No separate app to open, no context lost.

Sitting on top of all of this is a layer of custom automation. Aleem, who owns the technical side of Weekly Accounting’s setup, wires Missive rules to webhooks that fire into n8n. “Based on those webhooks, we do a bunch of stuff,” he says. Missive tasks get created, ClickUp tasks get created, work gets routed to the right owner on the right system without anybody having to copy-paste anything across tools.

Enterprise-level support for SMBs

Kendra wanted to flag one more thing. “We have to work with support teams for other platforms, and Missive’s support team is phenomenal. Very responsive. The team members we’ve hopped on calls with have been excellent, especially given that we’re all still figuring out some of this and breaking things and then trying to fix them.”

Brett agrees. “It’s the type of support quality that makes you look at the support you’re getting from other companies differently.”

From chasing the pieces to keeping them in the same box

Two years in, Kendra contrasts the before and after in the same language she used to describe the original problem.

“The before version was very startupy. Everybody was just trying to get what they needed done immediately. You had to chase the different pieces of the puzzle. With Missive, we’re much more integrated. We collaborate in real time, we draft emails for client conversations together, we proofread each other’s replies before they go out. It centralizes the conversation. And anytime you can keep the puzzle pieces in the same box, it goes a lot farther.”

Brett Fairchild, who joined in December and now owns Weekly Accounting’s day-to-day operational view of Missive, puts it in more tactical terms. “We have these inboxes where everyone can help each other. We have visibility on what needs to be assigned and to whom. The comment system is invaluable. Every single day, Kendra and I are tagging each other on things. And being able to copy a conversation link and drop it into a ClickUp task or a meeting, that’s a small feature that saves time I wouldn’t have noticed I was wasting.”

What’s next on the roadmap inside Missive: Contact books, which will let them manage client contact data globally instead of CFO-by-CFO, making out-of-office coverage cleaner when a CFO is away. And WhatsApp, for the clients who prefer messaging over email or SMS.

For a team that’s already doing more than most firms three times its size, the honest take from Kendra is what you’d hope for. “The before version felt disjointed. This feels integrated. That’s the difference.”