Most useful for practitioner-led payroll content aimed at Canadian accounting firm owners and staff.
Best for
A vendor selling to Canadian accounting firms in a category that does not compete with payroll.
Not for
A payroll software competitor seeking neutral endorsement, published rates, or verified audience demographics.
Key takeaways
Mid-period raises can force manual split-rate math at about 10 minutes per employee.
A client in Japan missed a provider cutoff for 25 employees at midnight.
A time-off spreadsheet had wrong dates, an unlogged sick day, and a moved anniversary entitlement.
Check first: Confirm recent post analytics, impressions, commenter roles, audience survey, and comparable payroll results.
Main ideas
The payroll features that matter erase a specific manual step · Build inside your own firm first, then let the prototype shape the product · Missed cutoffs, not hard payroll, are the fear worth designing against
Brian runs an accounting firm and builds Nooma, payroll software for accounting firms and their clients.
In the LinkedIn posts reviewed, they focus on practical payroll problems: migrating client data, calculating pay changes mid-period, handling late approvals and tracking employee time off.
The posts show how those problems arise in an accounting firm’s day-to-day work and describe product workflows intended to address them.
Brian connects specific operational friction to a concrete product decision.
For example, a post about mid-cycle raises explains the split-rate calculations staff may do by hand, then describes date-ranged scheduling as a way to automate them.
A post about a late approval uses a client’s missed cutoff as context for Nooma’s auto-run feature, while noting that auto-run cannot fix an unresponsive client.
That mix of practical detail, product explanation and stated limits makes the posts useful to people seeking an accounting-firm perspective on payroll work.
Brian C.'s posts argue that payroll pain is rarely a vague difficulty.
Read more
It is a specific, repeatable operational failure: a raise that lands mid-cycle, an approval email that misses a cutoff, or a time-off spreadsheet with stale dates.
The software should remove the manual step, not just the symptom.
The arguments draw on running an accounting firm and building Nooma, the payroll software that firm uses.
Each post moves from a named failure to a design choice, usually ending with a question for the reader.
The payroll features that matter erase a specific manual step
Brian C. argues that firms tell clients to wait until the start of a pay period for a raise not because of policy, but because payroll software handles mid-period rate changes poorly, pushing split-rate calculations onto whoever runs payroll.
Read more
The cost stacks up across employees and clients, and the same gap appears with temporary allowances, deductions, reimbursements and short-window benefits. The proposed fix: set date-ranged items with effective-from and effective-to dates before the period opens, so the split rate calculates automatically instead of living in a spreadsheet.
When a raise lands mid-cycle, someone counts the days at the old rate, counts the days at the new rate, and calculates the final gross by hand — "easily burns 10 minutes per employee," and if the recalculation is skipped the pay run is wrong.
Build inside your own firm first, then let the prototype shape the product
The recurring method across the posts is to run the process yourself, feel the friction, build an internal fix, test it on real files and shape the customer-facing version around what the prototype proved.
Read more
Brian C. states the principle directly: the fastest way to build good onboarding tools for firms is to feel the onboarding friction yourself. The migration post is the clearest example.
Brian C. describes vibe-coding an internal tool that takes a file from any legacy payroll software and converts it into a Nooma import file, using deterministic matching of pay types between platforms. The tool is in internal use first, running on real client worksheets, while a colleague named Hugh prepares the production version firms will use directly.
Missed cutoffs, not hard payroll, are the fear worth designing against
Brian C. reframes what keeps firm owners awake: not “is payroll hard” but “did I miss something” and “will that email land before cutoff.”
Read more
The design response is a later default cutoff and a documented fallback, with auto-run as a safety net for salaried teams whose payroll rarely changes, backed by off-cycle or adjustment runs for corrections.
A prospect told Brian C. about a client travelling in Japan who sent a midnight payroll approval for 25 employees after the provider's cutoff had passed, leaving only a support ticket. Nooma's auto-run is described as using a 4:30pm ET cutoff instead of noon — about 4.5 extra hours of buffer — with a two-day grace period available on request.
Brian C. names the limits alongside the product claims: a feature described with its boundaries is more credible than one presented as a universal fix.
Read more
The caveats specify who the feature is for, what it backs up and what remains outside the software's control.
In the cutoff post, auto-run is designed for salaried teams with stable payroll and presented as a backup plan.
Brian C. writes that “none of that fixes an unresponsive client.”
In the migration post, the tool is explicitly described as a prototype being dogfooded internally, with the production version still being built.
Time off is a data-reconciliation problem: show the process, not a slide deck
Brian C. argues that recurring time-off pain comes not from policy ambiguity but from data drift: slightly wrong dates, an unlogged sick day, an anniversary that bumps an entitlement without anyone noticing.
Read more
The data is reconciled by hand, then the cycle repeats the next month. The proposed response moves the record out of the inbox and into the platform; the format makes the same point by demonstrating the actual steps.
The monthly loop: the client's spreadsheet arrives, someone reconciles it manually, the pay run goes out, and the cycle repeats.
Nooma's time-off module is described as offering phone-based leave requests, automatic accrual updates, manager approvals with team visibility, and current balances across leave types.
A demo on 13 August, “The Spreadsheet Costing You Every December: Time Off, Done Right,” is advertised with “no slides.
The reader question is part of the method, not a sign-off
Nearly every post asks accounting-firm readers how they handle the same problem: mid-cycle raises, the payroll story that still wakes them at 2am, or the time manual data entry costs their team.
Read more
The questions are diagnostic, not rhetorical, consistent with the posts' focus on building from observed friction.
The mid-cycle raise post closes by asking whether firms make clients wait or do the manual math. The migration post asks how much time a team typically loses to manual data entry when switching payroll software for a client.
This post shows how the creator reasons: name a specific workflow, quantify the manual effort, show what can go wrong if someone skips a step, then point to the feature that removes it.
Read more
It answers “what does this person actually know about payroll operations?” better than any bio line.
This post takes a piece of everyday payroll advice—tell clients to wait until the start of a pay period before giving a raise—and shows why it exists: when a raise lands mid-cycle, whoever runs payroll has to count the days at the old rate, count the days at the new rate, and calculate the final gross by hand.
Brian C. puts a number on the cost (about 10 minutes per employee, stacking up across multiple staff and clients) and notes that the same headache applies to temporary allowances, deductions, reimbursements, and short-window benefits.
The post describes the fix in Nooma: items can carry effective from/to dates set before the period opens, so split rates calculate themselves instead of living in a spreadsheet.
It closes by asking readers how their firm handles mid-cycle raises.
For brands planning a campaign
Usable as a co-marketing hook: a payroll or accounting-tech partner could build content around the same problem—mid-cycle rate changes and date-ranged scheduling—and invite accounting firms to compare how their current software handles it. Brian C. promotes Nooma, so any partnership is likely to offer distribution or audience access rather than a neutral third-party endorsement.
This is the clearest window into how the work gets made.
Read more
It shows a build-in-public approach: an internal prototype is tested on real client files before a customer-facing version ships. It also explains why the author has standing to write about migration.
Brian C. describes payroll data migration as one of the worst parts of switching platforms: hours of re-keying employee details and copying pay types row by row.
They then describe an internal tool built to solve it: it takes an export from any legacy payroll software and converts it into a Nooma import file.
The tool is used internally first: raw worksheets go in and import-ready output comes out with no manual typing.
Most of the logic is deterministic because pay types are matched directly between platforms, and a colleague, Hugh, is preparing the production version firms will use.
The post explains the principle behind the approach—the best way to build onboarding tools for firms is to feel the onboarding friction yourself—and closes with a free white-glove onboarding offer through the end of 2026.
For brands planning a campaign
A partner could co-produce a migration-focused asset—a teardown, checklist, or live walkthrough of moving a firm off legacy payroll—and use its concrete, demonstration-driven framing. The existing onboarding offer is a commercial term, not a partnership proposal; any combined offer would need to be designed separately.
It shows the link between a customer anecdote and a shipped product decision without overclaiming: the post names what the feature does not fix.
Read more
For a newcomer assessing judgment, that combination of specificity and admitted limitation is the most informative thing here.
The post opens with a scene: an email arrives at midnight on payroll approval day for 25 employees.
The client was traveling in Japan, the provider's cutoff had already passed, and the only option was to open a support ticket.
Brian C. frames the real fear for firm owners not as “is payroll hard” but as “did I miss something” or “will that email land before cutoff,” then connects it to a design choice: Nooma's auto-run uses a 4:30pm ET cutoff instead of noon, described as 4.5 extra hours of buffer, with a two-day grace period available on request.
The post is candid about the limits: auto-run was designed for salaried teams with little change, works as a backup so nobody's pay is delayed, and adjustments are trued up later with an off-cycle run.
It does not fix an unresponsive client.
A second post tells the same story with light edits, including the same question to readers about the payroll story that still wakes them at 2am.
For brands planning a campaign
Strong material for a partner that wants to talk about payroll cutoffs, approval timing, or error recovery.
A joint survey or discussion prompt (“what is your worst payroll-cutoff story?”) fits the format the author already uses.
The two near-identical posts mean a partner should use one example, not both, in any campaign asset.
A strong first post for a general reader who wants to know who this person is.
Read more
It gives the accounting-firm-plus-software-builder position in one sentence, then demonstrates it by dissecting a workflow the reader likely recognizes.
This post states the dual role plainly: “I run an accounting firm.
I also built the software my firm uses to run payroll.”
It then walks through the recurring time-off problem: the client sends a spreadsheet, dates are slightly off, a sick day was never logged, an anniversary date bumped an entitlement and nobody noticed.
Each month brings manual reconciliation, followed by a repeat the next month.
The fix described is Nooma's time off module: employees request leave from their phone, accrual rules update automatically, managers approve with team visibility, and balances stay current across leave types in one platform.
The post also announces a live demo on 13 August, explicitly with “no slides.
Just the actual workflow,” and directs readers to a registration link in the comments.
For brands planning a campaign
The live-demo format is directly reusable: a software partner could co-host a workflow session where a real task is completed on screen rather than presented in slides. The demo date has passed, so treat it as a format example rather than a current event.
Practitioner-built software as the recurring argument5
Corpus gaps that affect topic confidence5
Cutoff risk and auto-run as a payroll safety net2
Payroll migration and onboarding friction1
Mid-cycle pay changes and date-ranged scheduling1
Time-off spreadsheets and live workflow demos1
Payroll migration and onboarding friction
Brian C. describes payroll data migration as one of the most painful parts of switching platforms, especially for accountants and bookkeepers who re-key employee details and copy pay types row by row.
Read more
They built an internal tool to convert exports from legacy payroll software into a Nooma import file, tested it on real client moves, and used deterministic matching for existing pay types. The post says a production version for firms is planned and tested on real files.
Build for Brian C.’s firm first, test on real migration files, then shape the customer-facing product from that experience.
For brands planning a campaign
A payroll software partner can co-market around migration and onboarding relief, demonstrating time saved, fewer errors, and hands-off import workflows. The strongest angle is practical proof rooted in firms’ actual pain, not generic platform claims.
Brian C. argues that firms tell clients to wait until the start of a pay period for raises mainly because payroll software handles mid-period rate changes poorly.
Read more
The post breaks down the manual split: count days at the old rate, count days at the new rate, then calculate final gross pay by hand.
It can take about 10 minutes per employee, adding up across clients.
Nooma’s date-ranged scheduling is presented as the fix for raises, temporary allowances, deductions, reimbursements, and short-window benefits.
For brands planning a campaign
A partner can build content around payroll accuracy, reducing manual work, and handling edge cases that generic payroll demos skip. A co-marketing offer could include a workflow teardown or a calculator showing the cost of manual proration.
Brian C. tells the story of a client in Japan whose midnight payroll approval for 25 employees missed the provider’s cutoff, leaving only a support ticket.
Read more
They position Nooma’s auto-run, with a 4:30pm ET cutoff described as 4.5 extra hours versus some competitors, alongside a possible two-day exception and off-cycle or adjustment runs for corrections. Auto-run is designed for salaried teams with stable payroll, but can also serve as a backup plan.
Lead with a high-stakes operational failure, then connect it to a product design choice and a practical safety-net workflow.
The cutoff story appears in two posts with small wording changes; treat it as one recurring argument, not two independent examples.
For brands planning a campaign
A partner can co-market around deadline reliability, approval risk, and business continuity. Show how missed cutoffs lead to missed paydays, and how a specific cutoff and exception process can change the outcome.
Brian C. describes running an accounting firm and building the payroll software the firm uses.
Read more
The time-off post focuses on spreadsheet errors: slightly wrong dates, missed sick days, anniversary-driven entitlement changes, and monthly manual reconciliation.
Nooma’s time-off module is shown through phone-based leave requests, automatic accrual updates, manager approvals with team visibility, and current balances across leave types.
They also promote a live demo on 13 August called The Spreadsheet Costing You Every December: Time Off, Done Right, with no slides and the actual workflow.
Use a compact live demo of a real workflow instead of a slide presentation, and tie the invitation to a recurring seasonal pain point.
For brands planning a campaign
A partner can sponsor or produce live workflow demos and practical webinars for accounting firms. Show the actual product path from employee request to manager approval and balance update, not just a feature list.
Practitioner-built software as the recurring argument
Across the posts, Brian C. returns to a consistent position: the product agenda comes from running an accounting firm and feeling the operational friction directly.
Read more
Each post usually starts with a specific failure, explains the manual work or risk, connects the problem to a Nooma feature, and ends with a question or call to action. The formats are short LinkedIn text posts with hashtags, first-person anecdotes, and direct questions to accounting-firm readers.
Problem story, operational detail, product response, reader question, and a soft or direct Nooma call to action.
Promotional weight varies: some posts are mostly educational, with a closing offer, while the time-off demo post is more explicitly event-focused.
For brands planning a campaign
A software partner should match the practitioner-led tone and build campaigns around named firm workflows, not abstract thought leadership. The best-fit co-marketing gives Brian C. room to describe real client pain and how the partner’s product changes the work.
The five posts are LinkedIn text posts with no publication dates; one cutoff story is duplicated.
Read more
Before committing to a campaign, ask for a dated review that includes video, transcripts, articles, external interviews, and a fuller archive. The topics covered here are payroll operations, migration, cutoff risk, time off, and practitioner-built software.
For brands planning a campaign
Before scaling or signing a campaign around Brian C., commission a deeper corpus review with dates and additional formats to verify current themes, cadence, and whether the same operational arguments recur outside LinkedIn. Treat the current topic map as directional, not exhaustive.
The named business in Brian’s posts is Nooma, the payroll software they say they built and their accounting firm uses to run payroll.
Read more
The posts cover Nooma product decisions, a migration prototype, and live demos, written from the perspective of someone inside the company rather than an outside promoter. They also refer to running an accounting firm but do not name it.
Nooma
Owned business
Brian says they built the payroll software their firm uses to run payroll and writes about Nooma in the first-person plural: “we built” auto-run and the time-off module, “our pay types,” and “come check us out at Nooma.”
Read more
Posts describe Nooma as Canadian payroll software for accounting firms, covering an internal migration prototype, a 4:30pm ET auto-run cutoff versus a noon cutoff, date-ranged scheduling for mid-period rate changes, and a time-off module demo. The posts establish that they built the software but not whether they own Nooma, founded it, or work there; ask about their role before assessing the relationship.
Brian C.'s posts follow a recognizable shape: a specific payroll failure, the manual work it creates, the design decision made in response and a question for accounting-firm readers.
Read more
Start with the migration post to see the method in full: they built an internal tool to convert legacy payroll exports, tested it on real client files and let it shape the customer-facing product.
The cutoff post best shows a risk turned into a concrete design choice; the time-off post makes the same argument through a live workflow rather than a slide deck.
These are a practitioner's working notes on which manual steps software should remove, not broad industry commentary.
Each closes with a question for firm owners deciding how to run payroll for clients.
PayrollPayroll softwareRunning an accounting firmPayroll data migrationPayroll approval deadlinesEmployee time off and leaveCanadian payrollSoftware built by practitionersAccounting firm ownersShort LinkedIn text posts
Both write about automation's impact on accounting work.
Read more
Chad Blackburn argues that each wave of accounting technology has compressed repetitive tasks — data entry, reconciliations, first-pass tax prep and report assembly — leaving judgment as the specialist's value. Brian C.'s posts apply the same premise by removing a manual payroll step rather than addressing a symptom.
Chad Blackburn writes about the accounting field as a whole: how jobs change and how reports should pass from contributors to finance with definitions and sources intact. Brian C. writes from one firm's payroll operations and the software being built for it, focusing on product-specific fixes rather than where the profession is going.
Amy Cooper writes operational first-person pieces in the same shape as Brian C.'s: a concrete failure scenario (a peak forecast that a 3PL contract tolerates only within 15–20%, or a system that breaks at 4x today's volume), a short set of considerations and a question asking readers what they will do about it.
Read more
The domain is different — ecommerce fulfillment, 3PL contracts and supply-chain peak planning rather than payroll and accounting firms — and the fix is a plan and a named owner for when things go wrong, not a software feature.
Both write from inside client-facing accounting work.
Read more
Audrey Geisman describes meeting weekly with a client, reviewing cash flow, AR and AP line by line, and measuring progress in payroll cycles.
Brian C. describes running an accounting firm and building the payroll tool the firm uses.
Both draw on their own experience.
Audrey Geisman writes about outsourced-accounting relationships: how embedded a fractional resource becomes, what a client owes the relationship and how consistency moves a client from survival to growth. Brian C. focuses on payroll operations and design decisions meant to remove manual steps, not client relationships or advisory positioning.
For a payroll-software partnership, the decision is whether Brian C.'s following includes the accounting firm owners and staff who choose and run client payroll.
Read more
Their posts target that group with topics including mid-cycle raises, time-off spreadsheets, approval-day cutoffs and payroll migrations, often closing with a direct question to firm owners ("How does your firm handle mid-cycle pay raises right now?").
Repeated hashtags (#CanadianAccounting, #Payroll, #AccountingFirms) point to a Canada-focused practitioner readership.
The only measured audience figure stated here is 4,456 LinkedIn followers, observed 8 October 2026.
Before committing, ask for recent post analytics, including impressions and commenter roles, a short audience survey, and recent results for comparable payroll topics, depth and formats.
LinkedIn followers
4,456
LinkedIn profile linked from the reviewed posts · 2026-10-08
Brian C’s posts describe no partnership or sponsorship program, sponsor policy, media kit, rate card, audience-overview pack, or published way to request a partnership.
Read more
A buyer cannot price a deal or check standard terms from the public information.
What the posts show is a business relationship, not a creator offer.
They run an accounting firm and build Nooma, payroll software for Canadian accounting firms and their clients.
A payroll software company approaching them would be speaking to someone who sells to the same firms, so any arrangement would be a direct commercial conversation — integration, reseller or referral terms, revenue share, or a joint campaign — rather than a media buy from a neutral commentator.
Several operating facts in the posts would shape that conversation.
Free white-glove onboarding is offered to firms migrating payroll, open through the end of 2026, with the firm only reviewing and approving the import.
Auto-run payroll uses a 4:30pm ET cutoff instead of noon, and the grace period can be extended by two days for a client exception.
Date-ranged scheduling handles mid-period raises, temporary allowances, and short-window benefits so split rates calculate without spreadsheets.
A time off module replaces the leave spreadsheet that arrives by email.
On 13 August, they demonstrated that process in a live demo with no slides, registered through a link in the post's comments.
The writing style matters for any co-marketing.
Posts come from the operator's side — raw migration worksheets, a client in Japan who missed a payroll cutoff, an approval-day email at midnight — and close with a question put straight to firm owners.
A partner would need to match that problem-first, product-led voice.
Two of the five posts repeat the same midnight-email story, suggesting a small set of recurring selling points rather than a range of formats to plug into.
Before committing budget, ask for a written description of what they will accept, who reviews partnership requests, and how pricing and disclosure work.
A vendor selling to Canadian accounting firms in a category that does not compete with payroll — practice management, bookkeeping automation, client accounting, or payroll-adjacent compliance services — wants practitioner-led content aimed at firm owners and the staff who run client work.
Read more
The campaign can accept that the creator also sells a product of their own and is not a neutral commentator.
Why this fits.
Brian C's posts put the buyer and the writer in the same room.
Every one addresses firm owners and staff directly, most closing with a question to them ("How does your firm handle mid-cycle pay raises right now?"), and the hashtags are Canadian and practice-specific (#CanadianAccounting, #Payroll, #AccountingFirms).
That is the same readership a firm-facing software vendor needs to reach.
The craft matches what a co-marketing asset needs to do.
Posts start from a named operational failure rather than a product claim: a raise landing mid-pay-period that forces manual split math at roughly 10 minutes per employee; a client in Japan whose midnight approval missed a provider cutoff for 25 employees; a time-off spreadsheet with wrong dates, an unlogged sick day, and an anniversary date that quietly moved an entitlement.
Each post then shows the manual work, names what breaks if a step is skipped, and points to the specific fix.
A partner gets concrete, demonstrable material instead of generic thought-leadership copy.
The operator-and-builder position is the strongest asset.
The time-off post states it plainly: they run an accounting firm and build the payroll software that firm uses, and have seen the workflow from both sides of the desk.
That supports a co-marketing angle grounded in real client work, and the build-in-public migration post — an internal tool tested on real worksheets before a customer-facing version ships — gives the partner a credible story about how to test something on real files before launching it.
Their format preferences are usable.
The announced live session was explicitly "no slides.
Just the actual workflow."
A partner can reuse that: a screen-share walkthrough of one task done end to end rather than a feature deck.
Limits to price in.
The only measured audience figure available is 4,456 LinkedIn followers observed 8 October 2026, with no demographics, geography, seniority, employer mix, or engagement data.
Five LinkedIn text posts are available, and one story, the midnight cutoff email, appears in two posts with light edits, so the set of distinct selling points is smaller than the post count suggests.
Ask for recent post analytics and named commenter roles before setting reach expectations.
Commercial shape: no partnership program, media kit, rate card, or inquiry route is published in the posts, so this would be a negotiated direct commercial conversation — integration, referral, revenue share, or a joint campaign — not a media buy off a published price list.
When to choose a specialist
A payroll software company that competes with Brian C's own product wants a neutral, third-party endorsement — an independent comparison or recommendation that puts its platform ahead of alternatives — plus an audience buy with a published rate card and verified audience demographics.
Read more
Why this fails.
Brian C's posts do not present them as an independent voice in that category.
They state that they run an accounting firm and build Nooma, the payroll software that firm uses to run payroll, and promote it directly: date-ranged scheduling for mid-period raises, auto-run with a 4:30pm ET cutoff, a time-off module, free white-glove onboarding through the end of 2026, and a live product demo on 13 August.
A competitor asking for a favourable comparison is asking the vendor of a rival product to endorse against their own commercial interest.
Any arrangement here is audience access or distribution, not third-party validation, and a reader-facing page should say so plainly.
There is also no buy to price.
No sponsor policy, media kit, rate card, audience-overview pack, or published way to request a partnership appears in the posts, so a buyer cannot check standard terms or disclosure practice.
Ask for those details before committing.
The audience cannot be qualified from what is published.
The only measured figure is 4,456 LinkedIn followers.
There are no demographics, geography, seniority or employer-type breakdown, or engagement data — comment counts, impressions, or who is actually replying.
Topical overlap with a payroll campaign is content alignment, not proof that the following contains payroll decision-makers at firms.
The content base is thin for a paid commitment.
Five LinkedIn text posts are available, and two repeat the same midnight-cutoff story.
Matching a partner's cadence would depend on a small set of recurring selling points rather than a varied format range.
The absence of visible brand partners or sponsored posts is not proof that none exist, but it means disclosure norms and past commercial conduct are unknown.
A second kind of poor fit has the same root: a general-reach consumer or HR brand wanting broad audience scale, or a campaign needing a creator who stays neutral across competing payroll platforms.
Both require information that the posts do not provide.
A worked campaign example
Worked angle for the campaign aimed at a vendor selling to Canadian accounting firms in a non-payroll-competing category: "The Manual Math Audit" — a three-part co-produced series plus one live workflow session, built entirely from problems Brian C has already written about, with the partner's product shown as the second step in each fix and Nooma's role disclosed.
Part 1, mid-period raises.
Open on the everyday advice firms give clients — wait until the start of a pay period to give a raise — and the real reason: the software cannot handle a mid-cycle rate change, so someone counts days at the old rate, counts days at the new rate, and calculates gross by hand.
Use the roughly 10-minutes-per-employee figure from the post, then multiply it across several staff and several clients.
The partner's contribution is the comparison the reader can run themselves: a short checklist of the pay items that break mid-period — raises, temporary allowances, deductions, reimbursements, short-window benefits — and what each platform in their stack does with them.
Part 2, the missed cutoff.
Use the midnight-approval story once, not twice: an email arrives on approval day for 25 employees, the approver is half a world away, the provider's cutoff has passed, and the only option left is a support ticket.
Frame the real fear as the post does — not "is payroll hard" but "will that email land before cutoff" — and keep the honest limitation the post keeps: none of this fixes an unresponsive client.
The partner adds an approval-timing worksheet: who approves, by when, and what the fallback is for each client.
Part 3, the time-off spreadsheet. Walk through the monthly loop described in the post — dates slightly off, a sick day never logged, an anniversary date that moved an entitlement, manual reconciliation, and the same thing again next month — and show what the request-approve-balance path looks like when it is not a spreadsheet.
Live session. Follow the format already used: 45 minutes, no slides, one real workflow completed on screen from employee request to manager approval and updated balance, with time for firm owners to describe their own version of the problem.
Asset and handoff.
Ship one blank, portable worksheet on the campaign page — the pay-item audit from Part 1, with a filled example alongside it — so a firm can run it against its own client list without the rest of the series.
The partner should be able to complete the blank sheet and use the result in a real client conversation before this is called finished.
Voice and disclosure.
Match the problem-first, operator-side voice: raw worksheets, a named client failure, operational detail, then the product response.
Keep internal field names and review language out of the copy.
State clearly in the series that Brian C builds and sells Nooma and that the partner is a separate company, and say what the commercial relationship is.
What to settle first.
Ask for recent post analytics — impressions and the roles of people commenting — plus a short audience survey, and confirm in writing what Brian C will accept, who reviews partnership requests, how pricing works, and how disclosure is handled.
Treat the live demo date in the post as a past event and a format example, not a slot to book.
The 4,456-follower figure observed 8 October 2026 is the only measured audience number available; do not build a reach forecast beyond it.
Choose Audrey for a relationship-led campaign about outsourced accounting.
Read more
In one post, she recounts meeting weekly with a client to review cash flow, receivables and payables—tracking progress from having one payroll cycle in the bank to planning for growth.
In another, she describes the communication and shared commitment that can make an outsourced resource feel like part of a client’s team.
These examples make the client relationship tangible. For a campaign focused on payroll software for accounting firms, ask Brian C. for examples of Canadian payroll workflows and product demonstrations.
Chad Blackburn
Choose Chad for a broader accounting-technology or finance-reporting campaign.
Chad’s examples focus on the profession and reporting handoffs. For a campaign centered on Canadian payroll workflows and product demonstrations, ask Brian C. for examples of those.
Five LinkedIn text posts by Brian C cover payroll data migration, mid-cycle pay changes, approval cutoffs and time-off workflows, plus a LinkedIn follower count of 4,456 observed 8 October 2026.
The posts here have no publication dates, so this page describes their recurring arguments rather than a sequence or a change over time; two posts retell the same midnight-cutoff story and are treated as one example.
Comparisons with other creators draw on posts dated April to September 2026 and are limited to how their topics, teaching approach and formats differ.
The posts here do not establish signature books, shows, earlier work, audience demographics or engagement data, and no sponsorship terms are published — no video, transcript, article or long-form writing was available.
