The Two-Hour Onboarding: Getting Your Shop's History Into a System
The thing that stops most shops from adopting a real quoting system isn't cost and isn't the learning curve. It's the blank slate. Every tool you've tried starts you at zero — empty customer list, no pricing, no history — and asks you to spend weeks feeding it before it's useful. So you look at the mountain of setup, decide you don't have the time this month, and go back to the spreadsheet. The system that would save you time never gets adopted because adopting it looks like more work than staying stuck.
Here's what that dread misses: you're not starting from zero. Your shop's entire pricing history already exists — it's sitting in QuickBooks, in years of invoices and estimates that record exactly what you charged, who you charged, and what the work was. The onboarding problem isn't data entry. It's connection. And once you reframe it that way, getting a system up to speed stops being a multi-week project and becomes a two-hour afternoon. This matters because speed compounds: the shop that responds to a request first wins a disproportionate share of the work, and you can't respond fast from a system that doesn't know you yet.
Why "starting from zero" is the wrong mental model
The blank-slate dread comes from tools that treat your history as something you have to type in. That framing is backwards for a service business, because the most valuable thing a quoting system can know — what you actually charge — is already recorded in the software you use to get paid.
QuickBooks has been quietly keeping your pricing memory the whole time. Every invoice is a data point: this customer, this kind of job, this price, this date. Multiply that across a year or two and you have a dense record of how your shop prices — far richer than anything you'd reconstruct by hand, and more accurate, because it's what really happened rather than what you remember happening.
So the onboarding question isn't "how do I build a pricing database from scratch." It's "how do I point a system at the pricing database I already have." That's a connection, not a construction project, and it's the difference between a two-week slog and a two-hour setup.
The two-hour onboarding, step by step
Here's the actual sequence. Block out one afternoon and work through it in order — most of the two hours is waiting for imports to finish, not typing.
- First 15 minutes — connect QuickBooks. This is the single highest-leverage step, because it pulls your customer list and your invoice history in one move. No re-typing customers, no rebuilding a pricing sheet. The connection does the heavy lifting.
- Next 30 minutes — let the history load and skim it. Once connected, your past invoices and estimates come across. Don't audit every line — just skim to confirm your major customers and typical jobs are there. You're checking that the memory landed, not proof-reading it.
- Next 30 minutes — quote one real job. Pick a request that's actually on your desk right now and quote it end to end. This is the real test: does the system pull the right customer, surface what you charged them before, and get you to a sendable number fast? Quoting a live job teaches you more than any tutorial.
- Final 45 minutes — set your defaults and send it. Set your standard terms, your sending domain, your follow-up cadence. Then send the quote you just built. You've now done a full cash-cycle loop — request to sent quote — on real work, in your first afternoon.
Why connecting QuickBooks is the whole game
The reason this works is that QuickBooks is a warm start, not a cold one. A system that mines your last 12 to 24 months of invoices knows your pricing before you've quoted a single new job through it — it closes the "what does this thing even know about my shop?" gap on day one.
- Your customers come pre-loaded. No typing a customer list. The people you've invoiced are already there, matched and ready to quote against.
- Your pricing comes pre-loaded. What you charged for similar work is right there, so your first quote out of the system is grounded in your real numbers, not a generic template.
- It gets sharper as you go. The QuickBooks history is the cold-start signal; every new quote you send refines it. Within your first handful of jobs, the system is converging on how your shop actually prices — not a vendor's idea of it.
Two hours against the months you'd save
Weigh the trade honestly. The cost is one afternoon — call it two hours, most of it waiting on imports. The return is every hour after that: quotes that go out in minutes because the customer and pricing are already known, follow-ups that run on their own, invoices that don't require re-typing into QuickBooks because the job data is already connected.
Picture a $500K shop doing 30 quotes a month, each currently taking the better part of an hour between digging for past pricing, drafting, and formatting. Cut that to minutes and you've bought back most of a workweek every single month — for a two-hour setup you kept avoiding because it looked like two weeks. That's the actual math the blank-slate dread hides: the onboarding you're afraid of is shorter than a single day's worth of the quoting it replaces.
The reason to do it this afternoon rather than "someday" is that every day you wait is a day your history sits unused and your quotes stay slow. The data's already there. Connecting it takes an afternoon. The blank slate was never real.
If you'd rather your quoting system show up already knowing your customers and your pricing — because it read your QuickBooks history instead of asking you to type it — Setell connects QuickBooks in minutes and quotes from your real numbers on day one. Free tier is 3 AI quotes a month; paid plans from $49/mo. Start free.Ready to quote faster?
Start free — no credit card. See your first AI-drafted quote in minutes.