From quote to paid: how the money side connects
The money side of a small business is usually five tools a couple sticky notes and a prayer: something quotes, something bills, something takes payment, something tracks the subscription charges, and something else — in April, with an accountant — discovers none of them are synced. This post walks 2nd Shift's money path end to end, because the design claim we're making only makes sense when you can see the whole chain: a number gets entered once, and everything downstream reads it.
It starts with a conversation
A customer tells your widget what they need. A flow walks them through it to ensure all required information is collected, and at the right moment an offer appears — targeted by the answers they just gave, selling directly from your product catalog. That's the first write: not just a lead in a marketing tool, but an offer event, with the catalog item attached, only counted in analytics only when it was actually shown.
The catalog becomes an order
Catalog products are workspace master data. When the customer orders, the cart validates against stock — real availability, refused orders with real numbers — and checkout runs on your own Stripe API key. The order, the payment state and the stock movements all land as records: the sale posts against inventory, and cost of goods computes from the ledger.
The invoice is a record
Billing reads from the same spine. Invoices carry line items that can come from the catalog, whether its time your team logged at a billable rate, or from progress draws against an estimate — with retainage held back until released, to the cent. Customers pay on a public page through Stripe, and the payment records itself into a ledger with an audit trail. Recurring work rides profiles that generate and even email their invoices on schedule; the reminder cadence runs daily whether or not anyone opened the app. No more sending endless emails attempting to follow up on unpaid invoices.
Recurring charges on the expense side get the same treatment: the subscriptions module tracks every vendor renewal, warns before the charge, and pushes the write-off into tax through an idempotent seam — one charge, one ledger row, no matter how many times anything replays.
Tax is assembled at the time
The tax module reads the whole story: sales-tax liability per agency, the P&L with Schedule C mapping, 1099 packets for contractors, depreciation from assets, VAT returns. Because the inputs came from the same records the business ran on, the filing documents are a review of decisions already made. No more last minute splicing together tax information from 12 systems to meet the deadlines, its ready the moment you need it every time you need it.
Why we're proud of the boring part
Every arrow in this post is a place where other software stacks have a copy-paste, and every copy-paste is where small businesses lose time or money — in re-typed quantities, missed renewals, un-billed hours and sales-tax reports that don't match the bank. One data spine doesn't just save clicks; it removes the seams where the errors live.
That's the money path: offer → order → invoice → payment → ledger → filing, with Joe able to answer "where does this job stand financially" from anywhere along it. The modules each got their own post under "Joe's desk" — this one was the map.
None of this requires faith in magic. Each step is a normal record with normal fields; the trick is only that the records reference each other, so the questions that used to need five tools — "is that job profitable?", "was the deposit billed?", "what's still owed?" — are queries over one connected dataset.
Related: the deep dives — offers, invoicing, tax and subscriptions — each have their own post under Joe's desk.
