Due to increased demand, text TeamShift to hold the next available slot.+1 717 740 8200Call instead
TeamShift

plumbing monthly summary

Your service vs. new-construction margin, delivered reliably every month-end

Most plumbing owners can't say, without a night of spreadsheet work, whether service calls or new-construction jobs actually carried the month. The numbers sit scattered across the field software, the bank feed, and a pile of supplier invoices. TeamShift runs a deterministic monthly operation that pulls those sources, splits margin by work type, flags what changed, and delivers the packet to your inbox. You approve it; it's done. No spreadsheet night, no waiting on the accountant.

Positioning

Built for searchers who already have the problem.

Most plumbing owners can't say, without a night of spreadsheet work, whether service calls or new-construction jobs actually carried the month. The numbers sit scattered across the field software, the bank feed, and a pile of supplier invoices. TeamShift runs a deterministic monthly operation that pulls those sources, splits margin by work type, flags what changed, and delivers the packet to your inbox. You approve it; it's done. No spreadsheet night, no waiting on the accountant.

The problem

Service and new-construction margins hide in different places

A plumbing owner searching for a monthly summary usually has a specific blind spot: service tickets and new-construction jobs run on different math, but the bookkeeping blends them. Service is high-volume, fast-pay, parts-heavy. New-construction is slow-pay, draw-based, labor-heavy. When both land in one P&L line, you can't tell which one is funding the other. By the time the accountant closes the books weeks later, the month is gone and the pattern is already repeating. The operation that should deliver this clarity every close simply doesn't exist yet.

  • Service revenue and new-construction draws often land in the same income account, so margin by work type is invisible until someone manually separates them.
  • Supplier invoices for a new-construction job can arrive a month after the labor was paid, distorting which period looks profitable.
  • Field software reports job-level numbers; the bank feed reports cash; neither reconciles the two into a single owner-ready read.
  • Sensitive decisions — repricing a service plan, chasing a builder's unpaid draw — belong to you; the gap is the reliable operation that surfaces the numbers so you can make them.

Workflow

We map your sources, split by work type, and route the packet for your sign-off

TeamShift connects the places your numbers already live — the field software, the accounting file, and the bank feed — and runs the same deterministic operation each month. Every job is tagged service or new-construction using your own categories, then totaled for revenue, material cost, and labor against each bucket. The draft uses the plain language you define up front. Anything genuinely ambiguous — an uncategorized large invoice, a job that spans both types — is escalated to you with a one-line question, not quietly bucketed. You approve the packet; it closes.

  • We pull from your existing field software, accounting file, and bank feed — no new dashboard to log into.
  • Each job is tagged service or new-construction using categories you define, so the split matches how you actually run.
  • Uncategorized or split-type jobs are routed to you with a specific question; the operation holds until you answer.
  • You approve the summary format and wording once, then review and approve each month's packet before it counts as done.

Delivered outcome

A reliable margin read lands in your inbox ready to act on

What you receive is short and actionable: revenue, cost, and margin for service versus new-construction, plus what moved from last month and why. You scan it in a few minutes, approve it, or send back a question — and the operation doesn't close until you do. Pricing, collections, and staffing decisions stay yours. The summary delivers the ground truth on demand; if new-construction ran thin again, you have the number to take to a bid renegotiation the same morning.

  • The summary fits on one screen: two columns, the month's change, and a plain note on what drove it.
  • Repricing a service plan, firing a slow-paying builder, or shifting crews between service and new work stays your call — made with a clear number in hand.
  • Sending a question back is one reply; the packet doesn't close until you approve it.
  • Each month builds on the last, so you can confirm whether a change you made actually moved the margin.

Proof

A monthly margin read is a question owners search at every close

Plumbing owners look up how to separate service from new-construction profit at every month-end, because the question recurs and generic accounting advice never answers it for a two-trade shop. That makes it a durable search wedge, not a one-time spike. This page links to related operations — getting the books cleaned first, the HVAC version, and reports that run themselves — so the topic reinforces itself and earns mentions from owners who finally received a straight, reliable answer.

  • The service-vs-new-construction margin question is evergreen: it returns every close, for every multi-trade plumbing shop.
  • Generic small-business accounting content never splits by trade work type, leaving a specific gap this page fills with a concrete delivered outcome.
  • Internal links to books-cleaned, the HVAC summary, and self-running reports build a connected money-clarity cluster.
  • Owners who receive a reliable monthly read tend to cite and forward it, earning mentions instead of buying them.

Questions

Before you request it

How does TeamShift split service work from new-construction in the summary?

The operation tags each job using the categories you already use in your field software, then totals revenue, material, and labor against the service bucket and the new-construction bucket separately. Jobs that span both types or aren't clearly categorized are routed to you with a specific question before the summary closes — so the split reflects how you actually run, not a system guess.

Does TeamShift make any financial decisions for me?

No. Every sensitive decision — repricing a service plan, chasing an unpaid builder draw, shifting crews between service and new work — is yours, made after you review the packet. The monthly summary is a deterministic operation that delivers where the money went across service and new-construction. You approve it and decide what to do with it. TeamShift never acts on pricing, collections, or staffing.

What do I need to provide to get a monthly summary set up?

Access to the three places your numbers already live: your field software (like ServiceTitan or Housecall Pro), your accounting file (like QuickBooks), and your bank feed. You also define once how you separate service from new-construction work. After that, the operation runs each month — drafting the packet from those sources and routing it to you for approval before it closes.