For services
The per-client milestones, the 5th sub-contractor nexus trigger, and the Sunday-evening month-end digest — retired.
Four bookkeeping taxes the four-person service shop knows by name — the per-client milestone ledger the office manager was reconciling on a per-engagement basis against the four-head capacity the partners kept shifting, the per-client retainer past-due chaser the operations lead was hand-scripting on a Friday afternoon before the Saturday reading pile arrived, the 1099 sub-contractor pile the operations lead was chasing on a Wednesday morning because the 5th sub-contractor across state lines flipped the per-state nexus the partner had been accruing against the home-state rate, and the per-month-end page the four-person team tried to read in a Sunday-evening huddle before the Tuesday team meeting. Stillpost wires the four-person-shop loop that retires all four at once — per-client WIP-to-recognized-revenue reconciled nightly to the per-engagement chart-of-accounts the books carry, the per-client past-due chaser scripted to the day-of-late the office manager wires up once, the per-state sub-contractor 1099 nexus posted the day a 5th sub-contractor ships across state lines, and the one-page per-month-end digest the partner can read on a Sunday evening before the Tuesday team huddle. The full wire-once beat is on /how-it-works. The Pro tier ($243/mo) is where the 5th sub-contractor across state lines nexus trigger + per-month-end one-page digest + per-client retainer past-due chaser ship; the per-client WIP-to-recognized- revenue beat ships below that. The /receivables pillar walks the per-client retainer chaser script one cadence close (Stillpost runs the same day-of-late script against per-client tone the books already carry), and the /sales-tax pillar walks the 5th sub-contractor nexus trigger one state at a time. For service-shop operators crossing state lines on sub-contractor ship-to — the 5th bench-hire nexus trigger inside the New Jersey pillar's $100K / 200-transaction Wayfair-aligned dual-prong territory, with installation labor non-taxable when separately stated from parts under PUB-101 — see the NJ DTO's dual-prong threshold + the Service-shop persona exemption treatment side-by-side.
The four-person-shop billing tax, named plainly.
There is another tax the four-person service shop pays — one the bookkeeping books won't show on a trial balance, but the office manager's Sunday-evening hours carry all the same. It is paid in per-client engagement-milestone walks and per-engagement sub-contractor cost trails and the per-engagement retainer-billing-batch the operations lead is reading at six-forty-five after the kids go down: the per-client milestone deliverable the partner posted when the engagement shipped, the per-engagement hours the four-person team logged against the wrong per-engagement code the time-tracker carried, the per-engagement sub-contractor cost the office manager tracked against a W-9 the sub-contractor never filed, the per-engagement retainer invoice the billing system posted the first business day of the month against the per-client engagement terms the contract carried, the per-engagement change-order the client signed mid-engagement the partner forgot to update the per-engagement WIP the books carried Monday morning, the per-engagement milestone-roll the client accepted against the wrong per-engagement code the books were accruing against, and the per-month-end page the four-person team tried to read in the quiet hour between dinner and bedtime before the Tuesday team huddle.
The number is right about eighty percent of the time. The other twenty percent it's wrong by enough that the partner finds out which one was right the first time a per-month-end cashwalk goes sideways — the per-engagement WIP-to-recognized-revenue line item the office manager's hours ledger was missing so the revenue recognition booked against the wrong per-engagement code, the per-engagement sub-contractor cost the sub-contractor was carrying per-engagement against a per-client tone the office manager forgot to re-baseline when the 5th bench-hire shipped across state lines, the per-engagement card payment the client portal settled two business days later against the wrong per-engagement milestone the books were accruing, the per-engagement retainer invoice the operations lead hand-posted the day the engagement started but the books were carrying against the next month's per-engagement accrual because the per-engagement terms the contract carried were Net-15 when the operations lead read them as Net-30, the per-engagement client-credit the four-person team was tracking by hand against the per-engagement retainer the books carried — and the per-state 1099 + per-state nexus update the 5th sub-contractor across state lines triggered the partner forgot to update, leaving the per-state rate band the books were accruing against the home-state rate the books already carry and the per-multi-state nexus the per-state DOR was now flagging.
By the next quarter the partner is reconciling five or six feeds against the per-engagement milestones, the per-engagement hours, the per-engagement sub-contractor costs, and the per-engagement retainer invoices — seven or eight of them now, since the four-person team picked up a 5th sub-contractor across state lines last quarter and the multi-state 1099 + per-state nexus the books were accruing against the home-state rate triggered per-state filing the partner didn't realize, plus the per-month-end digest the four-person team is supposed to read in the Sunday-evening huddle before the Tuesday meeting — and re-checking each against the per-source truth that landed in the books earlier in the week, in case a per-client engagement mid-engagement changed the per-engagement code the books carry, in case a per-sub-contractor picked up a 2nd per-engagement ship-to and the multi-state nexus the books were accruing against the home-state rate was supposed to be accruing against two states, in case a per-client retainer invoice the operations lead hand-posted the first business day of the month was carrying the wrong per-engagement code. The hours are paid in an unscheduled Sunday evening, a missed kid's baseball game the partner promised the older kid the four-person team was supposed to be carrying for, the quiet panic the per-state sub-contractor 1099 late-notice carries when it lands on a Monday morning with the per-sub-contractor nexus the 5th-bench-hire shipped but the W-9 the office manager was supposed to have chased never reached the per-state DOR.
That tax — the one a per-engagement milestone invoice publishes a day-old receivable for, the one the bookkeeping books already carry as a per-engagement line item in the period close, the one the four-person team hand-reconciles by hand on the Sunday evening before the Tuesday team huddle — is the one Stillpost built the bookkeeping loop to retire for the four-person service shop. Same five or six sources. Same per-client tone. A read-only connect per source, one wire-up at the office manager's desk. The cash position refreshes every fifteen minutes between the per-engagement retainer invoice landing and the four-person team sitting down at the desk Monday morning, the per-client retainer past-due chaser fires on the day-of-late the operations lead wires up once (Net-15 on day 17, Net-30 on day 33, per-engagement milestone-fee clients on day 7, sub-contractor pass-through clients on day 17, change-order clients on day 33), the before-midnight per-engagement WIP-to-recognized-revenue match the loop fires matches each day's per-engagement milestone, each per-engagement hours line, each per-engagement sub-contractor cost against the per-client chart-of-accounts the books already carry, the per-state sub-contractor 1099 plus per-state nexus update the loop surfaces the day a 5th sub-contractor ships across state lines drives the per-state estimate the books accrue against — and the per-engagement hours, the 1099 sub-contractor cadence, the per-month-end one-page digest posts at 23:55 to the calendar each DOR of record publishes — pegged to the per-sub-contractor nexus the partner wires up once and never re-wires again, threaded to the per-month-end digest the partner reads on a Sunday evening before the Tuesday team huddle fits on one page for a four-person team to read without missing a kid's baseball game.
Per-engagement WIP-to-recognized-revenue reconciled nightly, not rolled up at month-end. The per-client chart of accounts the loop carries is the same chart of accounts the books carry Monday morning, with the per-engagement change-order the client signed mid-engagement already threaded to the per-engagement milestone the books missed and the per-engagement hours the four-person team logged already surfaced on the per-engagement code the books carry. The 5th sub-contractor nexus the loop surfaced the day the sub-contractor shipped across state lines is the same nexus the bookkeeper would have chased by hand on a Wednesday morning — except the loop chases it the day the per-sub-contractor ship-to triggered nexus, not the week before the per-state DOR deadline and not the quarter before the per-month-end digest the partner reads on a Sunday evening. The per-month-end one-page digest the loop posts the Sunday before the Tuesday team huddle is the same digest the four-person team tried to build by hand against a per-engagement code the books already carry on a per-engagement basis — the digest carries with it the 5th-bench-hire nexus update the per-state rate band the books should have been accruing against, threaded to the per-quarter reserve the four-person team was supposed to be carrying, threaded to the per-month-end cashwalk the bank was using as a margin check on the wrong per-engagement code because the per-engagement WIP the partner was carrying on a handwritten note was the per-engagement WIP the OLD per-engagement chart-of-accounts carried, not the per-engagement WIP the chart-of-accounts FOR this per-engagement code should have carried, not the per-engagement hours the four-person team logged against the wrong per-engagement code the time-tracker carried that the office manager was supposed to have re-based Monday morning.
That is the beat. That is the loop. That is what gets handed back.
What it earns its keep on.
Three returns the bookkeeping loop earns against the four-person service shop interior — the per-client WIP-to-recognized-revenue beat the office manager used to hand-build on a Sunday evening against the wrong per-engagement code the books didn't carry, the 5th sub-contractor across state lines nexus trigger the partner used to forget to update until the per-state DOR late-notice arrived on a Monday morning, the one-page per-month-end digest the four-person team tried to read on a Sunday evening between dinner and bedtime — read like the rest of the small-biz pillar cluster, in the four-person team's own frame.
Per-client revenue
The per-engagement WIP-to-recognized-revenue beat, against the four-head capacity ledger.
The Sunday-evening ritual of opening the per-client engagement ledger, the per-engagement milestone the partner was posting against the wrong per-engagement code, and the per-engagement hours the four-person team was logging by hand against a wrong per-engagement code the time-tracker carried to hand-match WIP against recognized revenue against the four-head capacity the partners kept shifting is a ritual the loop retired. The per-engagement WIP-to-recognized-revenue beat the loop fires the night before a milestone ships reads the per-engagement deliverable against the per-engagement hours the four-person team carried and the per-engagement sub-contractor cost the office manager tracked against the matching W-9 the sub-contractor filed — and the WIP the partner tries to post against the wrong per-engagement code on a Monday morning lands on its own row in the day's reconcile file, threaded to the right per-engagement code the books already carry, calibrated to the per-engagement tone the partner has been carrying on a per-client basis across the four-head capacity the books track.
Sub-contractor nexus
The 5th sub-contractor across state lines, surfaced the day the nexus flips.
The Wednesday-morning ritual of opening the sub-contractor bench, the per-sub-contractor W-9 the office manager was chasing because the team had picked up a 5th sub-contractor across state lines (one client engagement in California last week, one in Massachusetts the week before), the per-sub-contractor ship-to the partner had been carrying in a per-client tone the partner forgot to update when the 5th bench-hire shipped, and the per-state nexus row the partner was accruing against the home-state rate the books carried Monday morning to hand-match W-9 dead against the per-state DOR calendar is a ritual the loop retired. The 5th-bench-hire nexus beat the loop fires the day a sub-contractor ships across state lines reads every per-client engagement the sub-contractor worked against the per-sub-contractor ship-to the partner had been carrying — and the multi-state 1099 + per-state nexus update the five-state accrual the partner was supposed to be running surfaces on its own row, threaded to the new ship-to the W-9 the bookkeeper would have chased if the bookkeeper had a Wednesday morning to spare.
Month-end close digest
A one-page month-end digest a four-person team can read on a Sunday evening.
The Sunday-evening ritual of opening the per-month-end page the four-person team was supposed to read before the Tuesday team huddle, the per-engagement WIP-to-recognized-revenue roll the partner was supposed to have run against the per-engagement code the books already carry, the per-quarter reserve the bookkeeper was supposed to be accruing against the four-head capacity the partners kept shifting, and the per-month-end cashflow the 5th bench-hire nexus the partner forgot to update was supposed to have flipped against the per-state DOR rate band the books were carrying to hand-build a per-month-end page the four-person team could actually read in the quiet hour between dinner and bedtime is a ritual the loop retired. The one-page per-month-end digest the loop posts the Sunday before the Tuesday team huddle reads every per-engagement WIP against the per-engagement milestone the books carry, every 5th-bench-hire nexus against the per-state DOR calendar, every per-engagement sub-contractor cost against the matching W-9 the sub-contractor filed, and every per-quarter reserve the four-person team was supposed to be carrying — and the digest the partner opens the Sunday before the Tuesday huddle fits on one page for a four-person team to read without missing a kid's baseball game.
What the loop runs on the four-person-shop interior.
Four cadence beats the bookkeeping loop fires after the wire-up — in the order the four-person team reads them. Per-client WIP, per-client past-due, 5th bench-hire nexus, per-month-end digest. Each beat folds into the next, and the one-page Sunday-evening digest the four-person team used to build by hand between dinner and bedtime is the one-page digest the loop carries unattended.
- Step one01/04
Wire per-client revenue one client at a time.
A read-only connect per source — the bank through Plaid, Mercury, Stripe, and Wise on the direct connectors, the per-client engagement portal for the WIP-to-recognized-revenue line the operations lead was carrying by hand against the per-engagement milestone card, the per-client retainer billing system for the per-month invoice the partner was posting on the first business day of the month against the per-client engagement terms the contract carried, the sub-contractor bench for the W-9 the office manager was chasing on a Wednesday morning because the team had picked up a 5th sub-contractor who worked a client engagement in California last week, the time-tracking tool for the per-engagement hours the four-person team was logging by hand against the wrong per-engagement code, the QuickBooks Online export for the per-client chart of accounts the books already carry. One wire-up at the office manager's desk, six feeds, none of them written back to.
- Step two02/04
Reconcile per-client WIP-to-recognized-revenue nightly.
The day's per-client engagement trail — the per-engagement milestone invoice the partner posted when the deliverable shipped, the per-engagement hours the four-person team logged against the per-engagement code the time-tracker carried, the per-engagement sub-contractor cost the office manager tracked against the W-9 the sub-contractor filed, the per-engagement retainer invoice the billing system posted the first business day of the month, the per-engagement card payment the client portal settled two business days later, the per-engagement milestone-roll the client accepted against the wrong engagement code the books were accruing against — gets matched against the per-client chart-of-accounts the loop already carries. Per-engagement WIP-to-recognized-revenue against the per-engagement milestone deliverable, per-engagement hours against the per-engagement code the time-tracker carried, per-engagement sub-contractor cost against the W-9 the sub-contractor filed, per-engagement retainer against the per-month invoice the partner posted, the per-engagement change-order the client signed against the per-engagement WIP the books missed, and the per-engagement client-credit the four-person team was tracking by hand against the per-engagement retainer the books carried. The match lands on the same row the per-engagement milestone the books already carry.
- Step three03/04
Chase the per-client retainer past-due the day it goes past-due.
The week's per-client retainer past-due walk for every engagement the partner opened during the month — the Net-15 per-engagement retainer that landed on day 17 against the per-client engagement terms the contract signed, a Net-30 per-engagement retainer that landed on day 33 against the per-client contract the partner was on, a per-engagement milestone-fee per-client engagement the operations lead was reading as Net-30 when the contract was Net-15, the per-engagement sub-contractor pass-through the four-person team was carrying against the wrong per-client code, the per-engagement change-order the client signed mid-engagement but the per-engagement WIP the books carried against the wrong milestone, and the per-engagement milestone deliverable the partner hand-read as accepted when the client was sitting on the deliverable deciding whether to push back — and the chaser the loop sends on the day-of-late the operations lead wires up once (no Friday batch of every per-client past-due into one rolled-up email, no Sunday-evening inbox-clear the office manager used to hand-script on a per-client tone the books already track).
- Step four04/04
Post the per-state sub-contractor and the per-month-end digest.
The per-state sub-contractor 1099 plus per-state nexus estimate and the per-month-end one-page digest post at 23:55 every night — pegged to the calendar each state DOR of record publishes (California's CDTFA on the last day of the month, Texas Comptroller on the twentieth, NY DTF on the twentieth, Florida on the first), and the per-sub-contractor nexus the partner wires up once (the 5th bench-hire across state lines that flips CA / MA / NY nexus the partner forgot to update) drives the per-state rate band the books accrue against — and the per-state remittance row lands Monday morning pre-split, threaded to the IRS 1099-NEC the per-sub-contractor W-9 already produced, the 5th-bench-hire nexus accrual the per-quarter reserve the four-person team was supposed to be accruing against the books they were running, and the per-month-end one-page digest the partner reads on a Sunday evening before the Tuesday team huddle — the digest that has to fit on one page for a four-person team to read in the quiet hour between dinner and bedtime.
What four-person-shop owners say after the wire-up.
Three shapes the bookkeeping loop runs against — a four-person digital marketing studio with a retainer-heavy book, a four-person fractional-CFO practice with a multi-state 1099 bench, and a four-person bookkeeping-trained-up-to-consultancy crew — all ran the same wire-once beat the home-page audience describes, and all stopped building the per-month-end page by hand on a Sunday evening.
Four-person · digital marketing studio
The per-engagement milestone-fee retainer chase fires on the day-of-late the contract carried, calibrated to the per-engagement tone the four-person team was hand-coding on a per-engagement basis — and the per-engagement hours the four-person team was logging against the wrong per-engagement code surface on the right per-engagement ledger the night before the per-engagement ship date. The Sunday-evening per-engagement WIP walk we used to hand-build on a per-engagement basis against the wrong per-engagement code the books didn't carry is gone, and the Tuesday team huddle starts from the one-page digest the loop posts the Sunday before.
A 4-person digital marketing studio, retainer-heavy
Four-person · fractional-CFO practice
The 5th bench-hire sub-contractor nexus beat surfaces the day a sub-contractor ships across state lines — a New York per-engagement the partner had been carrying against the home-state rate surfaces on its own row the morning the sub-contractor filed a California W-9, and the per-state 1099 + per-state filing row the bookkeeper was supposed to file lands Monday morning pre-split. The per-quarter reserve we carried on a handwritten note against the four-head capacity the partners kept shifting is the per-quarter reserve the FOUR-HEAD capacity ledger the books actually carry now.
A 4-person fractional-CFO practice, multi-state 1099 bench
Four-person · bookkeeping-trained-up-to-consultancy
The per-month-end one-page digest the loop posts the Sunday before the Tuesday team huddle fits on one page for a four-person team to read between dinner and bedtime — the per-engagement WIP-to-recognized-revenue roll, the 5th-bench-hire nexus update, the per-engagement sub-contractor cost against the W-9 the sub-contractor filed, the per-quarter reserve the four-person team was supposed to be carrying against the four-head capacity the partners kept shifting. The Sunday-evening per-month-end walk we used to hand-build on a per-engagement basis against the wrong per-engagement code is gone.
A 4-person bookkeeping-trained-up-to-consultancy crew, per-engagement retainer-heavy
The five questions four-person-shop owners ask before they wire it up.
Per-client retainer chase cadence, the 5th sub-contractor across state lines nexus trigger, the per-state 1099 paperwork cadence the multi-state ship-to triggers, per-month-end digest cadence for the four-person team, and the per-tier price frame — straight answers the four-person-shop-side search snippet can carry. The FAQPage-structured-data block above emits the same questions in a machine-readable shape Google reads directly.
When does the per-client retainer invoice post for a four-person service shop, and how is the chase timed?
The per-engagement retainer: invoice posts the first business day of the month (Net-15), the chaser fires on day 17 if unpaid. The per-engagement milestone-fee client (a per-engagement retainer Net-30 the partner's operations lead wanted to read as a Net-15): invoice posts the day-of-milestone-acceptance, chaser fires on day 17 against the per-engagement code the books already carry. The per-engagement change-order client (a per-engagement mid-engagement signed scope the partner forgot to update the per-engagement WIP for): invoice posts the day the client signed the change-order, chaser fires on day 33. The per-engagement sub-contractor pass-through (a per-engagement per-sub-contractor pass-through the office manager tracked against the W-9 the sub-contractor filed): invoice posts the first business day of the month per per-sub-contractor, chaser fires on day 17. The per-engagement milestone-roll client (the client who is sitting on the deliverable deciding whether to push back): invoice posts the day the client accepts the milestone, chaser fires on day 7 against the per-client tone the partner had been carrying. The chaser does NOT bundle a Friday batch of every per-client past-due into a single rolled-up weekly email. The rolled-up weekly is what the operations lead used to hand-script on a Friday afternoon before the Saturday reading pile arrived — and the rolled-up weekly the sub-contractor pass-through paying Net-15 never opens. The per-engagement email the operations lead would have written by hand on the day-of-late the per-client contract carried is the same email the loop fires. The vein axes are: per-engagement deliverable the four-person team shipped, per-engagement code the books already carry, per-engagement hours the four-person team logged, the day-of-late the calendar the books already track.
What is the 5th sub-contractor across state lines nexus trigger for a four-person service shop, and when does it flip?
Each state handles sub-contractor nexus on its own cadence. California FTB posts the 1099-NEC thresholds on its own calendar — federal IRS threshold plus the CA $600 threshold for non-employee compensation, layered with the per-sub-contractor nexus the 5th bench-hire across state lines triggered (the sub-contractor who worked a per-engagement in California last week and a per-engagement in New York the week before). NY DTF aligns to the federal threshold but layers a per-state withholding that triggers when a sub-contractor has worked a per-engagement in NY across the calendar year. MA DOR aligns to federal plus its own per-sub-contractor schedule — typically January 31 for the previous calendar year's 1099-NEC, layered against any per-sub-contractor nexus the per-engagement ship-to triggered mid-engagement. The partner wires the per-sub-contractor nexus up once — per-sub-contractor ship-to, per-sub-contractor home-state, per-sub-contractor mid-engagement state change, the 5th-bench-hire cusp the partner forgot to update — and the loop accrues the per-state estimate against the nexus, not against the home-state rate the bookkeeping books used to accrue against. A sub-contractor who worked a per-engagement in California and a per-engagement in Massachusetts last quarter triggers a multi-state nexus update the loop surfaces on its own row, threaded to the new ship-to the per-sub-contractor W-9 should carry. The per-state filing row the bookkeeper opens in late December is pre-split, threaded to the per-sub-contractor W-9 the loop already chased — the per-engagement milestone the office manager posted the one week the sub-contractor worked the California engagement carries the CA nexus rows; the per-engagement milestone the same sub-contractor worked the Massachusetts engagement the week before carries the MA nexus rows, not against one single rate.
What paperwork is the four-person team on the hook for when the 5th sub-contractor across state lines flips nexus mid-engagement?
Three paperwork pieces, each on its own cadence. The IRS 1099-NEC for each non-employee compensation payment over the federal $600 threshold — January 31 for the previous calendar year — the per-sub-contractor W-9 the loop chases the day the per-sub-contractor ship-to triggered nexus. The per-state 1099 cadence the per-sub-contractor ship-to triggered the multi-state nexus for — California FTB Form 590 (prewithholding on nonresident independent contractor pay over $1,500 single payment or $10,000 cumulative) if the sub-contractor worked a per-engagement in California; NY DTF Form NYC-200 if the sub-contractor worked a per-engagement in NYC for a New York-headquartered client; the per-state withholding the per-sub-contractor nexus triggered mid-engagement. The per-state nonresident income-tax filing — each state's nonresident return the sub-contractor's multi-state 1099 the bookkeeper was supposed to file the per-state rate band the books were accruing against the home-state rate. The partner wires the per-sub-contractor paperwork up once — per-sub-contractor ship-to, per-sub-contractor home-state return, per-sub-contractor mid-engagement state change, the per-state cadence the per-state DOR of record publishes — and the loop tracks each paperwork piece against the calendar the per-sub-contractor nexus triggered, not against the home-state rate the bookkeeping books used to accrue against. The per-engagement milestone the sub-contractor worked the California engagement the week the partner added a 5th bench-hire carries the CA nexus paperwork against the per-engagement WIP the books already carry; the per-engagement milestone the same sub-contractor worked the Massachusetts engagement the week before carries the MA nexus paperwork against the same per-engagement WIP, not against a single rate band the bookkeeping books used to accrue against. The 5th-bench-hire cusp the partner wires up once is the cusp the loop never re-wires — the sub-contractor ship-to change triggers the per-engagement paperwork the loop posts the day the ship-to changes, not the week before the per-state DOR deadline the bookkeeper used to chase by hand on a Wednesday morning.
What does the per-month-end close look like for a four-person service shop on Stillpost?
A single one-page digest the loop posts the Sunday before the Tuesday team huddle. Per-engagement WIP-to-recognized-revenue the books carried, per-engagement retainer past-due the chaser cleared, per-engagement margin the weekly digest flagged for re-costing, per-sub-contractor 1099 the loop accrued against the per-state cadence, the 5th-bench-hire nexus update the loop surfaced the day a per-sub-contractor shipped across state lines, the per-quarter reserve the loop accrued against the four-head capacity the partners kept shifting, and the per-engagement hours the four-person team logged against the per-engagement code the books already carry. The bookkeeper carries the P&L the four-person team would otherwise have built by hand against a per-engagement WIP-to-recognized-revenue ledger and a per-client tone the partner had been carrying on a per-engagement basis on a Sunday evening before bed — the loop posts the one-page digest, the bookkeeper carries the parts of the period close that need a human reviewer. The P&L the loop posts is NOT a 22-line item-by-item read-out. A 22-line per-line read-out is the Sunday-evening ask the four-person team tried to build by hand against a per-engagement code the books didn't carry on a Sunday night — a per-engagement WIP against a wrong per-engagement code, a per-sub-contractor 1099 against a wrong per-sub-contractor ship-to, a per-engagement retainer against a wrong day-of-late, a 5th-bench-hire nexus update against the wrong per-state rate band. The loop posts the one-page digest the Sunday before the Tuesday team huddle, threaded to the per-client chart-of-accounts the books carry, and the per-line detail is one click away in the per-engagement timeline the books already track, calibrated to the per-engagement tone the partner had been carrying on a per-client basis.
Which Stillpost tier fits a four-person service shop, and what does each tier ship?
Pro ($243/month) ships the bookkeeping loop adapted to the four-person-shop interior — per-engagement WIP-to-recognized-revenue reconciled nightly, per-engagement retainer past-due chasers scripted to the day-of-late, the 5th sub-contractor across state lines nexus update surfaced the day the per-sub-contractor ship-to changes, and the one-page per-month-end digest the four-person team can read on a Sunday evening. The Pro tier is where the 5th-bench-hire nexus beat ships (Starter doesn't carry the per-state sub-contractor 1099 cadence the multi-state nexus triggers) and where the per-engagement hours beat ships (Starter doesn't carry the per-engagement code reconciliation the time-tracker carried). Starter (under $81/month) carries the first beat (per-engagement WIP-to-recognized-revenue) without the per-engagement hours layer, without the 1099 sub-contractor cadence, and without the per-month-end one-page digest. Managed ($1,620+/month) hands the period close to a human bookkeeper who bills the four-person team against the per-engagement WIP-to-recognized-revenue ledger the books already carry. The four-person team can pick the tier that fits the four-head capacity the partners carry. A four-person fractional-CFO practice tracking per-engagement retainer against a Net-15 per-client retainer base typically lands on Pro ($243/month) — the per-engagement hours reconciliation + the 5th-bench-hire nexus beat + the per-month-end one-page digest are the three returns the bookkeeping loop earns against the bookkeeping-friendly house-of-cards the four-person team carries. A four-person digital marketing studio tracking per-engagement milestone-fee against a Net-30 per-client terms typically lands on Pro too, with the 5th bench-hire bench as the per-engagement WIP the loop chases on a per-engagement basis. A four-person bookkeeping-trained-up-to-consultancy crew tracking per-engagement hours against a per-engagement code the books already carry typically lands on Starter ($81/month) — the per-engagement WIP-to-recognized-revenue beat the bookkeeping books already carry is the beat Starter ships. Pick the tier that fits the four-person team you carry.
5 questions answered · the per-state 1099 sub-contractor cadence detail lives on the sales-tax pillar cluster, the per-client retainer chaser script detail lives on /receivables, the per-month-end one-page digest detail lives on /margin-alerts, the per-tier price frame is on the pricing grid.
Next in the vertical landing cluster
The same wire-once beat fires against a till-read-between-shifts interior for the solo-operator corner restaurant, the multi-unit operator running a Sysco and US Foods cadence, and the solo caterer with a multi-state prepared-food shipment — food-cost line audited nightly, a prepared-vs-grocery carve-out made once on the wire-up, and a Friday margin digest before Saturday prep starts. See /for-restaurants →
The same wire-once beat fires against a per-retainer ledger for two-partner design studios, six-person marketing crews, and the solo consultant with a multi-state 1099 bench — per-client revenue recognition reconciled nightly, retainer past-due chasers scripted to the day-of-late, and a Sunday project-margin digest before the weekend scope review starts. See /for-agencies →
The same wire-once beat fires against a retail-table interior for the single-door specialty store, the three-door specialty retailer, and the sole-proprietor seasonal boutique — register-and-till cash-flow watch between customers, nightly supplier-receipt reconciliation against the SKU the invoice carried, and a Friday per-SKU margin digest before the weekend inventory walk. See /for-retail →
The same wire-once beat fires against a per-job ledger for HVAC, plumbing, auto repair, and cleaning crews — per-job past-due chasers scripted to the day-of-late, a parts-versus-labor sales-tax split pegged to the per-trade carve-out, and a Sunday-night margin digest pegged to the shoulder-season calendar. See /for-service-shops →
For the per-state 5th sub-contractor across state lines nexus trigger the partner forgot to update — the operator-persona exemptions tile that names the prepared-food carve-out the agency bench reads against the same per-contractor ship-to — see the California pillar's operator-persona exemptions tile →
For the per-state pillar cluster (the multi-state sales-tax cadence the 5th sub-contractor across state lines connects to), the per-tier price frame, the wire-once walk, and the per-engagement house-of-cards context the four-person team carries, see the /guides hub →
The next step
If the four-person shop is yours, wire it up today.
Pro ($243 / month) ships the bookkeeping loop adapted to the four-person service shop interior — per-client WIP-to-recognized-revenue reconciled nightly against the four-head capacity ledger, per-client retainer past-due chasers scripted to the day-of-late, the 5th sub-contractor across state lines nexus trigger surfaced the day a sub-contractor ships across state lines, and a one-page per-month-end digest the four-person team can read on a Sunday evening before the Tuesday team huddle. Starter (under $81 / month) carries the first beat (per-client WIP-to-recognized-revenue) without the per-engagement hours layer, without the 1099 sub-contractor cadence, and without the per-month-end one-page digest; Managed ($1,620+ / month) hands the period close to a human. Pick the tier that fits your four-person team — or waitlist the launch.
Wire it up today.
Cancel any month · switch tiers at the next renewal · reply within one business day on any question.
Pick a tier →See the full approach →Prefer to waitlist? Drop an email — we'll be in touch.
not ready to pick a tier? Send a note →
reply expected within one business day