ScalePad Quoter: turn won quotes into projects and charges

The handoff from sales to delivery is where MSPs leak money. A quote is won, and then somebody has to notice, build the project, remember the hardware, remember the recurring services, remember to bill the one-time items, and remember to move the opportunity in the PSA. Current's Win Quote Engine takes that whole chain and makes it a queue and a wizard: won quotes appear in front of a project manager automatically, and a few guided steps later there is a real project, real charges in Autotask, and an opportunity that has moved itself.

Admin → Integrations → ScalePad Quoter → Manage. The Integrations page sits in the Admin section of the sidebar, so it's tenant admins and super admins only. The drawer walks four numbered sections — Connection, Webhook, Won-quote workflow, What syncs — and you need Autotask connected first, because the stage picker reads your live Autotask opportunity stages.

1. 1
   1 · Connection — paste your API credentials

   In Quoter, go to Settings → Integrations → API and create an API client. Paste the Client ID and Client secret into Current. They're validated against Quoter before anything is stored, then kept server-side only — the browser never holds them.
2. 2
   2 · Webhook — paste Current's URL into Quoter

   Current shows you a webhook URL. Copy it into Quoter → Settings → Integrations → Webhooks, paste the URL, and choose the JSON format, so a win reaches Current within seconds. Optionally set a Hash Key: enter the same value in Current and on the webhook in Quoter, and every delivery is signed and verified. Current never shows a stored hash key back — only whether one is set.
3. 3
   3 · Won-quote workflow — map two Autotask stages

   Pick the Ready stage (where Quoter parks a won quote's Opportunity — this is what fills the queue) and the Converted stage (where Current moves it after conversion, which clears it from the queue). They cannot be the same stage, or the queue would always be empty. Set how far back to look for won quotes on the first connect — 30 days by default.
4. 4
   4 · What syncs

   Won quotes come in; project charges flow both ways; the opportunity stage write-back goes out. Nothing else in Quoter is touched.

The queue lives on My Day as a card, with a banner across the app so nobody misses it. It is visible to project managers and admins only — account executives see their own won deals elsewhere, and engineers and partners never see it at all.

It has two sections. Matched in Autotask is the confident set: Current found the Opportunity sitting at your Ready stage. Needs a look is the honest set: Current has the quote from Quoter but can't confirm it against Autotask yet. Clicking any row opens a detail drawer with the full story, the money as Autotask reports it, and a Refresh from Autotask & Quoter button.

Converting is a project-management action: project managers, tenant admins, and super admins only. Click Convert on a row and the wizard opens. Nothing is written until the final confirm — and on the project path, an Autotask-synced conversion dry-runs the Autotask side of the plan before that confirm, so what you approve is what happens.

1. 1
   Quotes

   Confirm the quote — and combine others if the same partner won several quotes that belong to one piece of work. Re-entering a quote that has already been converted requires an explicit typed confirmation, so you can't accidentally build the same project twice. If the AE typed an internal note on the quote in Quoter — a ship-to address, a special instruction — it appears here in a bold amber “Internal note from Quoter” banner at the top of the screen (the quote-level note plus each line item's note, combined), and you have to tick “I've read this” before you can move on. No note means no banner and no extra step.
2. 2
   Destination

   Project, for scoped work with phases, tasks, and scheduling. Or Post-sale ticket, for hardware-and-labor fulfillment — order it, install it, bill it — as a single Autotask ticket.
3. 3
   Project — partner, name, PM, mode, deadline

   Pick or create the partner company, name the project, assign a project manager, and choose the mode: Autotask-synced (Autotask stays the source of truth for time and billing) or Current-native. Charges require Autotask-synced — they push to the Autotask project. This is also where the Target go-live / hard deadline lives now — a prominent date field. Give it a date and the whole plan schedules backward so the last task lands on it. If that date physically can't fit — the plan would have to start in the past to make it — Current shows a bold red warning right here, so you catch it before you build instead of after. See "Project modes: PSA-synced or Current-native".
4. 4
   Questions — the three that change the plan

   Ordering hardware or software? adds a high-priority day-1 “Order hardware & software” task. Holding a kickoff? lets you pick internal, a kickoff call with the partner, or both — and adds the task or tasks you picked. Contract or agreement change? adds a critical “Contract / agreement change” task. All three must be answered before you can continue. (The hard-deadline question used to live here — it now sits on the Project step above, as its own Target go-live field.)
5. 5
   Build method — how the plan gets written

   Read the quote PDF (Current pulls the Opportunity's PDF from Autotask and drafts phases and tasks from it), paste a scope of work and let AI draft from that, start from one of your playbooks or Autotask templates, or create a bare project with just the day-1 tasks and build the rest yourself. This step also carries a Professional-services hours sold panel — Current counts the labor hours off the quote automatically, and you can edit the figure. When AI drafts the plan it's told that sold-hours number and your working-day window, so what it writes is built to fit the hours you sold and the deadline you set. Every generated plan is fully editable before you commit. See "Project templates and PMI playbooks" and "Matching the plan to the hours you sold" below.
6. 6
   Charges

   The line items, loaded live from Autotask. Tick what should bill (see below). Each line also carries a Counts as sold hours checkbox — labor lines are ticked by default — so you decide exactly which lines feed the sold-hours total on the build step.
7. 7
   Review → Create project & sync

   The whole plan on one page: project, tasks, charges, the stage move, whether the partner gets portal access, and whether they're emailed when work actually starts (both on by default). A quoted-vs-planned hours banner sits here too — if the plan's task hours don't match what you sold, Scale to match lines them up in one click (see below). This button is the first and only write. It runs step by step, is safe to retry, and if any single step fails it tells you exactly which one.

A project that quotes 40 hours and then plans 12 loses money quietly. The wizard keeps the two in view. On the Build method step, a Professional-services hours sold panel counts the labor hours straight off the quote's lines and lets you correct the number; on the Charges step, a Counts as sold hours checkbox on each line (labor ticked by default) decides which lines feed that total. Current hands both the sold-hours figure and your working-day window to the AI, so the draft it writes is built to fit the hours you sold and the deadline you set.

As you review the draft — and again on the final Review step — a banner compares the plan's task hours to the sold hours. If they've drifted apart, Scale to match nudges every task up or down in quarter-hour steps until the totals line up, never taking a task below 0.25 hours and never touching a milestone. It's one click, it's yours to undo before you commit, and the project manager always has the final say — Current sizes the plan for you but never overrides your judgement.

One-time line items you tick are pushed to Autotask as project charges (or ticket charges, on the post-sale ticket path) — that's the money you're owed for the work, landing where your billing runs.

On the project path, recurring items are deliberately NOT pushed. Recurring revenue belongs in a contract, and no automation should guess at your contract structure. Instead Current adds a critical day-1 task, “Set up recurring billing & contract”, with one checklist item per recurring line from the quote — and a task with unchecked checklist items cannot be marked complete. The MRR from a won quote physically cannot fall through the cracks.

The post-sale ticket path is different: a ticket is one-time by definition, so service and subscription lines are not treated as recurring there. They're shown to you unchecked, and they only bill — as one-time ticket charges — if you deliberately tick them. No recurring-billing task is created on that path.

If a quote offered the customer a choice — optional “choose one” line items — Current leaves those lines UNCHECKED on the Charges step and badges each one “Optional,” with a banner reminding you to tick only what the customer actually accepted (open the signed quote if you're unsure). This is deliberate: an accepted multi-option quote keeps every option on the Autotask quote, so pre-ticking them all would bill for hardware the customer never bought. The accepted-total check at the top of the step turns green once your ticked lines match what the customer signed for.

Not every won quote deserves a project. A firewall replacement or a batch of laptops is a fulfillment job, and the wizard has a shorter route for it: Quotes → Destination → Ticket → Charges → Review, ending in Create post-sale ticket. The Ticket step requires a ticket title, an Autotask queue, an owner, and a due date (Autotask requires one), plus optional priority, starting status, contract, and a procurement owner — the person who actually places the order. It converts exactly one quote. Current creates one Autotask ticket with a fixed order-first checklist — Place hardware order, Order received, Schedule service — and pushes the ticked lines as ticket charges.

Charges are pushed the moment the ticket is created — before the quote is marked converted — so a slow Autotask response can never leave a converted quote with an empty ticket. If a charge does fail to push (a transient Autotask hiccup, or the ticket ran out of time mid-import), the Post-sale page shows how many failed on that ticket and gives you a “Retry charges” button that re-pushes only the ones that didn't land. It's safe to tap as many times as you like — an already-synced charge is never sent to Autotask twice.

• ＋Current moves the Autotask Opportunity to your Converted stage — on both the project path and the post-sale ticket path — so a converted win doesn't linger at your Ready stage in Autotask's own "won but not processed" view. Recording the conversion is what clears the quote from Current's queue; if the stage write-back fails, Current tells you so on the result screen and you move the Opportunity in Autotask yourself (retrying the conversion re-attempts the move).
• ＋The signed quote PDF is filed onto the company in your PSA. Current copies the PDF from the won opportunity to the company's own attachments — renamed to the company name, the quote/offering name, and the date you converted (for example "Acme Corp Managed Services 8-1-27.pdf") — so it shows up in the company's Files area right away. This is best-effort: if the PDF can't be filed (it's a link rather than an uploaded file, or the PSA rejects the upload), the conversion still completes and Current shows you a heads-up so you can file it by hand. It's live for Autotask and ConnectWise; HaloPSA filing follows once its attachment API is verified against a live system.
• ＋If you left partner-portal access ticked, the partner is granted access to their project. If that grant fails for any reason, the conversion still stands and Current tells you to grant access from the project's Partner Access panel. See "Invite a partner to the client portal".
• ＋If you left partner notification ticked, the partner is emailed when the project actually starts — not when it's created. "Started" means real movement: the first task leaves a not-started status, the first time entry lands, or the earliest task's start date arrives.
• ＋The account executive who sold the deal is notified when their project starts and again when it finishes. Nobody has to chase delivery for a status update.

For the other ways a project gets born, see "Create a project: from scratch, a playbook, or a won quote" and "Building projects in your PSA from a template or won quote". For the complete list of everything Current ever writes into your PSA, see "What Current writes back to Autotask (and when)".