SourceLace
Packs

The day each pack changes.

A pack is a ready-made setup for one team or industry: its groups and access, the business terms it uses, the protection its data needs, and agents that take over the routine work. Pick a pack to see the problems it solves, told as one person's day.

Every story describes what the pack's agents do today. You set a pack up in the SourceLace app, review each item before it is applied, and try every agent in shadow mode before it goes live. Drafts are never sent for you, and every change to a record waits for a person's approval.

Sales and RevOps pack

Pipeline you can trust, and deals that do not go quiet.

Who it is for

Sales managers, RevOps and sales leaders on Salesforce, HubSpot or Dynamics 365.

Works with

  • Salesforce
  • HubSpot
  • Dynamics 365

Also works with:

  • Snowflake
  • BigQuery
  • Databricks
  • Amazon Redshift
  • Microsoft Fabric
  • Gmail
  • Microsoft 365
  • Slack
  • Teams

CRM data hygiene

For: sales operations manager

Today
Priya spends Friday afternoons exporting opportunities to a spreadsheet to find gaps. Last month a $120,000 deal sat with a close date six weeks in the past, and nobody noticed. The forecast call used it anyway.
With SourceLace
Every Friday the agent checks open opportunities and active accounts in your CRM for missing or wrong data. It flags past close dates, zero amounts, no next step, no primary contact and missing account details such as industry. Priya gets a Word report with a data quality score, issues by type and by owner, and a list per owner. If you connect your mail and turn on owner notes, it drafts a friendly fix-it email to the owners with the most issues. Priya reviews each draft and decides what to send.
What stays protected
It changes no records and sends nothing; drafts wait in Priya's mailbox, and it reads only what her own sign-in allows.
What to measure
Data quality score week over week, and the number of open deals with a close date in the past.

Weekly pipeline review

For: sales manager

Today
Amara spends Sunday evening building slides for Monday's pipeline meeting. She pulls exports, rebuilds charts and still cannot say which deals slipped since last week. The meeting turns into a status read-out.
With SourceLace
Every Monday morning the agent reads open opportunities closing soon from your CRM. Amara chooses her own deals, her team's deals or everything she can see. It works out total and weighted pipeline, what moved or slipped in the last week, stale deals, and large deals with no next step. Amara gets a slide deck, Word or PDF document with charts by stage and by owner, and three focus deals with reasons. If a number cannot be worked out from the data, the review says so instead of guessing.
What stays protected
It changes nothing and sends nothing; it reads only what Amara's own sign-in allows.
What to measure
Time to prepare the weekly review, and deals that slipped without being discussed.

Stale opportunity nudges

For: sales manager

Today
Luis knows some deals have gone quiet, but finding them means clicking through every rep's pipeline. A $60,000 opportunity had no activity for five weeks before he saw it. By then the buyer had chosen someone else.
With SourceLace
Each weekday the agent reads open opportunities, their last activity dates and owners from your CRM. It finds deals above your minimum amount with no activity for your chosen number of days, and groups them by owner. It drafts one short note per owner in your mailbox, listing their quiet deals. Each note asks for the next step and a date for each deal. Luis reviews each draft and decides what to send.
What stays protected
Drafts only: nothing is sent, no records change, and each draft lists only that owner's own deals.
What to measure
Number of open deals with no recent activity, and days from going quiet to a logged next step.

Renewal reminder

For: account manager

Today
Tomas found out about a $90,000 renewal three weeks before the date. There was no time for a usage review or an executive call. The customer signed, but for a smaller plan.
With SourceLace
Every morning the agent finds renewals in your CRM exactly 90 days away. With extra reminders turned on, it also finds those at 60 and 30 days. For each, it gathers the value, owner, open opportunities and last activity, and rates the risk as low, medium or high. If you connect your support system, it adds open and recent cases. It drafts a reminder to the account owner, or to you, with the facts and a suggested plan with dates.
What stays protected
Drafts only: nothing is sent and no records change; it reads only what your own sign-in allows.
What to measure
Renewals with a plan in place 90 days out, and proposals sent at least 30 days before the date.

Weekly quota attainment

For: revenue operations lead

Today
Every Monday Hana rebuilds the attainment spreadsheet from three exports before the leadership call. By the time it is ready, nobody has asked which open deals could close the gap. Two reps furthest behind went unnoticed for three weeks.
With SourceLace
Every Monday the agent reads this quarter's quotas, closed-won deals and open pipeline from your CRM. It works out attainment per rep, group or territory, the gap left, and how well open pipeline covers each gap. Hana gets a one-page Word or PDF report with a short summary and the attainment table. It also lists the five owners furthest behind, with their largest open deals. If you connect Slack or Teams, it prepares a short channel post, which waits for a person's approval.
What stays protected
It is read-only and changes no records; nothing is posted without a person's approval, and it reads only what Hana's own sign-in allows.
What to measure
Time to prepare the Monday attainment review, and pipeline coverage of the gap per rep.

Deal desk queue

For: deal desk analyst

Today
Kofi scrolls the whole pipeline each morning looking for deals that need his review. A 35% discount on a deal closing Friday reached him on Thursday night. The approval was rushed and the terms were wrong.
With SourceLace
Each weekday morning the agent reads open opportunities, their line items and, where your CRM records them, approvals. It lists only the deals that need a deal desk look. That means discounts above your limit, large deals near closing, and late-stage deals with no approval on record. Kofi gets a short list per reason, with owner, stage, amount, close date, highest discount and approval status. If you connect Slack or Teams, it prepares a channel post that goes out only after a person approves it.
What stays protected
It is read-only and changes no records; nothing is posted without a person's approval.
What to measure
Deals reviewed before their close date, and approvals requested in the final days of a quarter.

Monthly ARR bridge

For: revenue operations lead

Today
On the first working day Dana pulls a subscription export from the data warehouse and a bookings list from the CRM, and spends the morning reconciling them in a spreadsheet. The two rarely agree, and nobody can say quickly which customers explain the gap.
With SourceLace
On the first weekday of the month the agent reads the monthly ARR table in your data warehouse and the closed-won bookings in your CRM. Dana gets a short report with the ARR bridge: opening ARR, new, expansion, contraction, churn and closing ARR, as a table and a chart. It says whether new plus expansion ARR agrees with bookings, and lists the customers that explain any gap. If you connect Slack or Teams, it prepares a short channel post, which waits for a person's approval.
What stays protected
It is read-only in both systems and changes no records; nothing is posted without a person's approval, it reads only what Dana's own access allows, and your data protection rules apply to what the AI sees.
What to measure
Time to close the month's ARR numbers, and the share of months where bookings and ARR agree within your tolerance.
Customer Success pack

See renewals at risk early, and keep every account in view.

Who it is for

Customer success managers and their leaders, on any CRM, with support tickets alongside.

Works with

  • Salesforce
  • HubSpot
  • Dynamics 365

Also works with:

  • Snowflake
  • BigQuery
  • Databricks
  • Amazon Redshift
  • Microsoft Fabric
  • ServiceNow
  • Zendesk
  • Jira
  • Gong
  • Gmail
  • Microsoft 365
  • Slack
  • Teams

Weekly account health digest

For: customer success manager

Today
Ravi owns 60 accounts and reviews them in a spreadsheet every Monday. He missed a new priority 1 case at a key account because it sat in the service desk, not his CRM. The customer raised it on their next call.
With SourceLace
Every Monday the agent reads your accounts, owners, renewals and activity from your CRM. If you connect your service desk and call recordings, it adds new urgent cases and recent calls. Ravi gets a one-page digest of only the accounts that need attention, each with a suggested next step. Signals include a new priority 1 or 2 case, no recent activity, a renewal coming up or a falling health score. If you connect Slack or Teams, it prepares a short version for your channel, which waits for a person's approval.
What stays protected
It is read-only and changes no records; nothing is posted without a person's approval.
What to measure
Accounts with no contact for 30 days, and urgent cases the account owner heard about first from the customer.

Sev 1 escalation

For: support escalation manager

Today
When a priority 1 case opens, Elena spends twenty minutes finding the account owner, the renewal date and any open orders. Last quarter the account owner learned of an outage from the customer's CFO. The renewal was two months away.
With SourceLace
When a new priority 1 case opens, the agent finds its account in your CRM: tier, annual value, renewal date, owner and other open cases. If you connect your ERP, it adds open orders and deliveries due soon. It drafts an escalation email to the account owner and customer success manager with the facts and the next update time. It never guesses the cause. If you connect Slack or Teams, it prepares a two-line heads-up for your escalation channel, posted only after a person approves it.
What stays protected
Nothing is sent or posted without a person; the email is a draft and no records change.
What to measure
Time from a priority 1 case opening to the account owner being told, and escalations missing account context.

Renewals at risk

For: customer success manager

Today
Every Monday Grace updates a renewal risk spreadsheet by hand. An account renewing in six weeks had four open support cases and no contact for a month. It was on row 40, and she did not reach it in time.
With SourceLace
Every Monday the agent lists renewals due in the coming months from your CRM. It checks each for risk: no recent activity, no renewal opportunity yet, or a low or falling health score. If you connect your support system, it also flags many open cases or any open priority 1 or 2 case. Grace gets a one-page report of only the at-risk renewals, with the signals and a suggested next step. If you connect Slack or Teams, it prepares a short list for your CS channel that is posted only after a person approves it.
What stays protected
It changes no records, and nothing is posted without a person's approval.
What to measure
At-risk renewals found more than 60 days before the date, and renewals lost with no early warning.

Renewal reminder

For: account manager

Today
Tomas found out about a $90,000 renewal three weeks before the date. There was no time for a usage review or an executive call. The customer signed, but for a smaller plan.
With SourceLace
Every morning the agent finds renewals in your CRM exactly 90 days away. With extra reminders turned on, it also finds those at 60 and 30 days. For each, it gathers the value, owner, open opportunities and last activity, and rates the risk as low, medium or high. If you connect your support system, it adds open and recent cases. It drafts a reminder to the account owner, or to you, with the facts and a suggested plan with dates.
What stays protected
Drafts only: nothing is sent and no records change; it reads only what your own sign-in allows.
What to measure
Renewals with a plan in place 90 days out, and proposals sent at least 30 days before the date.

Onboarding check-ins

For: onboarding manager

Today
Sofia keeps a calendar of day 7, 30, 60 and 90 check-ins for every new customer. In a busy month she missed a day 30 call. The customer had an open setup case nobody had mentioned to her.
With SourceLace
Each weekday the agent finds customers in their first 90 days in your CRM and keeps those reaching a milestone day today. For each, it drafts a check-in email to the customer's main contact. The draft covers progress so far, the next step and an offer of a call. If you connect your service desk, it also covers open cases and cases solved since the start. Sofia reviews each draft in her mailbox and sends the ones she is happy with.
What stays protected
Drafts only: nothing reaches a customer until Sofia sends it, and no records change.
What to measure
Milestone check-ins sent on time, and new customers with an open case at day 30.

Usage drop watch

For: customer success manager

Today
Mateo checks usage dashboards for a few of his biggest accounts before each renewal call. The rest are never looked at, and an account that quietly stopped using the product was only noticed when its renewal came up.
With SourceLace
Every Monday the agent reads product usage from your data warehouse and compares the last four weeks of weekly active users with the four weeks before. It keeps the accounts that fell by your threshold or more, looks up each account's owner and renewal date in your CRM, and puts the ones renewing soon first. Mateo gets a one-page report with the fall, the renewal date and a suggested next step for each. If you connect Slack or Teams, it prepares a channel post, which waits for a person's approval.
What stays protected
It is read-only in both systems and changes no records; nothing is posted without a person's approval, and it reads only what Mateo's own access allows.
What to measure
How many accounts with a usage fall were contacted before their renewal, and the days between the fall starting and a person noticing it.
Finance and FP&A pack

Close faster, collect sooner, and explain the variance.

Who it is for

Accounts receivable, controllers and FP&A, on any ERP.

Works with

  • SAP S/4HANA
  • SAP ECC
  • NetSuite
  • Oracle Fusion

Also works with:

  • Snowflake
  • BigQuery
  • Databricks
  • Amazon Redshift
  • Microsoft Fabric
  • Gmail
  • Microsoft 365
  • Slack
  • Teams

AR aging digest

For: collections manager

Today
Every Monday, Priya exports open invoices from the ERP and rebuilds the aging report in a spreadsheet. It takes her the morning. By then nobody has noticed that a $60,000 invoice slipped from 31-60 days into 61-90.
With SourceLace
Every Monday morning the agent reads open customer invoices, credit memos and payments from your ERP. Priya gets a one-page report: totals per age bucket and their change since last week, the customers with the most overdue, newly overdue invoices above her threshold, and DSO for the last 90 days. If you connect mail, it also drafts the digest as an email to her. If you set a channel, it posts a short version there only after she approves it.
What stays protected
It changes no records and never contacts customers; it reads only what Priya's own sign-in allows.
What to measure
Time spent building the weekly aging report, and the amount over 60 days overdue week by week.

Overdue invoice reminders

For: accounts receivable specialist

Today
Every Tuesday, Kofi filters the open-items list and writes reminder emails one by one. A customer 70 days late gets the same friendly note as one 5 days late. Others get no reminder at all.
With SourceLace
Every Tuesday morning the agent reads open, past-due customer invoices from your ERP. It groups them by customer and age, and finds each customer's billing contact in the ERP, or in your CRM if you connect one. Kofi gets one draft reminder per customer in his mailbox. Each lists the invoices and matches its tone to how late they are, from a friendly reminder to a final one. If you turn it on, the account owner from your CRM is copied. Customers with no email address are listed in a summary instead.
What stays protected
Drafts only: nothing is sent until Kofi reviews and sends it, and no records change.
What to measure
Overdue customers reminded each week, time spent writing reminders, and days sales outstanding.

Month-end close status

For: controller

Today
On day 2 of the close, Ingrid walks the floor asking who still has parked journals. Goods received but not invoiced and unapplied cash only surface on day 4. By then they hold up the close.
With SourceLace
Each weekday morning in the first business days of the month, the agent reads your ERP. Outside that window it stops without reading anything. Ingrid gets a short report marked with the business day, such as 'Day 3 of 5': period status, unposted or parked journals, goods received not invoiced, unapplied customer payments and open intercompany items. It lists what is blocking the close, largest first, and names any area the ERP does not show.
What stays protected
It only reads and reports; it changes nothing and reads only what Ingrid's own sign-in allows.
What to measure
Days to close, and blocking items found on the last day of the close.

Monthly budget vs actual

For: financial planning analyst

Today
After each month end, Lucas pulls actuals from the ERP and lines them up against the budget spreadsheet by hand. He then digs through transactions to explain why marketing is 18% over. The pack is ready a week later.
With SourceLace
Early each month the agent reads last month's and year-to-date actuals from your ERP. If you connect a data warehouse or the budget file in Drive, SharePoint or OneDrive, it reads the budget too; if none is found, it reports actuals only and says so. Lucas gets a report with variances by department or cost center, and the three largest transactions behind each line over his threshold. If you set a channel, it posts the headline there only after he approves it.
What stays protected
It is read-only and changes no records; it reads only what Lucas's own sign-ins allow.
What to measure
Days from month end to a finished variance pack, and hours spent explaining variances.

ERP and warehouse reconciliation

For: finance systems analyst

Today
Priya's team builds dashboards on a copy of the ERP in the data warehouse. A load that dropped some invoices went unnoticed until the quarter-end review, when the dashboard and the ledger disagreed.
With SourceLace
On the third of each month the agent reads invoiced revenue or open receivables for the last months from your ERP, and the same figure from your data warehouse. Priya gets a short report with both numbers side by side per month, the difference in percent, the months outside your tolerance, and the largest documents found on only one side. The ERP is treated as the system of record. If you connect Slack or Teams, it prepares a channel post, which waits for a person's approval.
What stays protected
It is read-only in both systems and changes no records; nothing is posted without a person's approval, and it reads only what Priya's own access allows.
What to measure
Days between a data load problem and someone finding it, and the number of months that needed a manual reconciliation.
Procurement pack

Keep purchase orders moving and contracts from renewing unseen.

Who it is for

Buyers, procurement leads and budget owners, on any ERP.

Works with

  • SAP S/4HANA
  • SAP ECC
  • NetSuite
  • Oracle Fusion

Also works with:

  • Gmail
  • Microsoft 365
  • Slack
  • Teams

PO approval backlog

For: procurement manager

Today
Rafael's buyers keep asking why their orders have not gone out. He runs a release report and chases approvers one by one. A $25,000 order has been waiting nine days for one manager.
With SourceLace
Each weekday morning the agent reads your ERP for purchase orders and requisitions waiting for approval longer than your limit. Rafael gets a short report grouped by who or which step each one waits for, oldest first, with the count and value. If you set a channel, it posts the list there only after he approves it.
What stays protected
It is read-only: it never changes, releases or approves anything.
What to measure
Average days purchase orders wait for approval, and the number waiting past the limit.

Supplier contract renewals

For: contract manager

Today
Hannah keeps contract end dates in a spreadsheet that is always a little out of date. Last quarter a logistics contract renewed automatically for two years. Its 90-day notice period had passed unnoticed.
With SourceLace
Every Monday morning the agent reads your ERP for supplier contracts and agreements ending in the coming months, and the spend released against each this year. If you connect your contract files in Drive, SharePoint or OneDrive, it reads each contract for the notice period and any automatic renewal clause, and quotes it. Hannah gets a report sorted by the last day to give notice, with a suggested action per contract: renew, renegotiate or let it end. If you connect mail, it also drafts the five most urgent contracts as an email to her.
What stays protected
It changes no records and never contacts suppliers; it reads only what Hannah's own sign-ins allow.
What to measure
Contracts that renew automatically without review, and notice deadlines missed.

Late purchase orders

For: buyer

Today
Aiko has 40 purchase order lines past their delivery date across a dozen suppliers. She copies them from the ERP into emails, supplier by supplier. The suppliers she chases last are often the ones holding up production.
With SourceLace
Each weekday morning the agent reads your ERP for purchase order lines past their delivery date and not fully received. It groups them by supplier, largest open value first, and finds each supplier's purchasing email. Aiko gets one draft email per supplier in her mailbox, asking politely for a confirmed delivery date for each line, without prices. A summary shows late lines and value by supplier and plant, and suppliers with no email address.
What stays protected
Drafts only: nothing goes to a supplier until Aiko reviews and sends it, and no records change.
What to measure
Late lines with a confirmed delivery date, and average days late per supplier.

Monthly spend summary

For: category manager

Today
Each month, Elena exports supplier invoices and builds the spend report in a spreadsheet. It takes two days. Spend with no purchase order, such as a $15,000 consulting invoice, often goes unseen.
With SourceLace
On the first day of each month the agent reads last month's posted supplier invoices from your ERP, and the same month last year. Elena gets a report with totals, the top 20 suppliers, spend by category and the five suppliers whose spend moved most. It also lists invoices with no purchase order above her threshold.
What stays protected
It is read-only, changes no records and does not read bank details or tax numbers.
What to measure
Time to produce the monthly spend report, and the share of spend with no purchase order.
Supply chain pack

Find the late, the short and the at-risk before they hurt a customer.

Who it is for

Planners, buyers and supply chain managers on SAP, NetSuite, Oracle Fusion or Dynamics 365.

Works with

  • SAP S/4HANA
  • SAP ECC
  • NetSuite
  • Oracle Fusion
  • Dynamics 365 Finance and Supply Chain
  • Flexport

Also works with:

  • Snowflake
  • BigQuery
  • Databricks
  • Amazon Redshift
  • Microsoft Fabric
  • Gmail
  • Microsoft 365
  • Slack
  • Teams

Late purchase orders

For: buyer

Today
Aiko has 40 purchase order lines past their delivery date across a dozen suppliers. She copies them from the ERP into emails, supplier by supplier. The suppliers she chases last are often the ones holding up production.
With SourceLace
Each weekday morning the agent reads your ERP for purchase order lines past their delivery date and not fully received. It groups them by supplier, largest open value first, and finds each supplier's purchasing email. Aiko gets one draft email per supplier in her mailbox, asking politely for a confirmed delivery date for each line, without prices. A summary shows late lines and value by supplier and plant, and suppliers with no email address.
What stays protected
Drafts only: nothing goes to a supplier until Aiko reviews and sends it, and no records change.
What to measure
Late lines with a confirmed delivery date, and average days late per supplier.

Low stock alert

For: material planner

Today
Mateo checks reorder points in the ERP when he has time. Last month a packaging item fell below safety stock on a Friday. Nobody saw it until the line stopped on Tuesday.
With SourceLace
Every morning the agent reads stock, reorder points, safety stock and open purchase orders from your ERP. Mateo gets a short report of items below their reorder point, with those not covered by an open purchase order first. If you turn it on, a second table lists the covered items and the orders that cover them. If you connect mail, it also drafts a short alert with the uncovered items to him or to the planner you name.
What stays protected
It changes no records and sends nothing; the alert waits as a draft for a person to send.
What to measure
Items found below reorder point without cover, and stockouts per month.

Month-end close status

For: controller

Today
On day 2 of the close, Ingrid walks the floor asking who still has parked journals. Goods received but not invoiced and unapplied cash only surface on day 4. By then they hold up the close.
With SourceLace
Each weekday morning in the first business days of the month, the agent reads your ERP. Outside that window it stops without reading anything. Ingrid gets a short report marked with the business day, such as 'Day 3 of 5': period status, unposted or parked journals, goods received not invoiced, unapplied customer payments and open intercompany items. It lists what is blocking the close, largest first, and names any area the ERP does not show.
What stays protected
It only reads and reports; it changes nothing and reads only what Ingrid's own sign-in allows.
What to measure
Days to close, and blocking items found on the last day of the close.

Overdue invoice reminders

For: accounts receivable specialist

Today
Every Tuesday, Kofi filters the open-items list and writes reminder emails one by one. A customer 70 days late gets the same friendly note as one 5 days late. Others get no reminder at all.
With SourceLace
Every Tuesday morning the agent reads open, past-due customer invoices from your ERP. It groups them by customer and age, and finds each customer's billing contact in the ERP, or in your CRM if you connect one. Kofi gets one draft reminder per customer in his mailbox. Each lists the invoices and matches its tone to how late they are, from a friendly reminder to a final one. If you turn it on, the account owner from your CRM is copied. Customers with no email address are listed in a summary instead.
What stays protected
Drafts only: nothing is sent until Kofi reviews and sends it, and no records change.
What to measure
Overdue customers reminded each week, time spent writing reminders, and days sales outstanding.

Demand and supply exceptions

For: supply planner

Today
Every morning, Jonas checks stock, sales orders and open purchase orders in three screens to find shortages. On busy days he misses one. A customer order for 500 units then ships late.
With SourceLace
Each weekday morning the agent reads stock, open sales order lines and open purchase orders from your ERP (SAP, NetSuite or Oracle Fusion). Jonas gets a short report of only the materials where demand in the coming weeks exceeds supply, or would take stock below safety stock. Each shows the first shortfall date and the open purchase orders for it, and whether they are late. The report says it nets what the ERP shows and is not a planning run. If you set a channel, it posts the earliest exceptions there only after he approves it.
What stays protected
It is read-only and changes no records; it reads only what Jonas's own sign-in allows.
What to measure
Shortages found before the shortfall date, and customer orders delayed by missing stock.

Supplier on-time delivery

For: supplier quality manager

Today
Every Monday, Beatriz matches purchase order dates to goods receipts in a spreadsheet to score suppliers. It takes half a day. Her supplier reviews still rely on last month's numbers.
With SourceLace
Every Monday morning the agent reads purchase order schedule lines and goods receipts from SAP S/4HANA or SAP ECC for the last few weeks. Beatriz gets a report of on-time-in-full delivery per supplier, worst first, with the share late, the share short and average days late. It also lists the late and short lines behind the ten worst suppliers. If you set a channel, it posts the five worst there only after she approves it.
What stays protected
It is read-only, changes no records and does not read bank details or tax numbers.
What to measure
On-time-in-full delivery per supplier over time, and time spent preparing supplier reviews.

Forecast vs actual demand

For: demand planner

Today
Every Monday Tomas exports the demand forecast from the data warehouse and a list of actual orders from the ERP, and compares them in a spreadsheet. It takes half a morning, so only the biggest materials get checked and forecast errors on the rest carry on for weeks.
With SourceLace
Every Monday the agent reads the demand forecast kept in your data warehouse and the actual sales order quantities for the same weeks in your ERP. Tomas gets a short report of the materials and plants where actual demand differs from the forecast by more than your threshold, with forecast, actual, deviation in percent, and whether the forecast ran high or low. It says which materials could not be matched between the two systems. If you connect Slack or Teams, it prepares a channel post, which waits for a person's approval.
What stays protected
It is read-only in both systems and changes no records; nothing is posted without a person's approval, and it reads only what Tomas's own access allows.
What to measure
Time to review forecast accuracy each week, and the number of materials with a large deviation that were corrected in the plan.

Freight invoice review

For: logistics finance

Today
Freight invoices arrive from the forwarder all month. Priya's team pays them when they come, and only checks a handful: a duplicate or a charge nobody expected is found, if at all, when the month is reconciled.
With SourceLace
Every Monday the agent reads the last weeks of freight invoices from Flexport, if Flexport is connected. Priya gets a report of the invoices worth a second look: past due and still unpaid, possible duplicates, a charge type that is new for a shipment, and rates that moved more than your threshold compared with earlier invoices. It compares Flexport's invoices with each other, not with your contract, and covers only the freight Flexport handles.
What stays protected
It is read-only and changes no records; any email is only a draft for a person to review, and it reads only what the shared Flexport key allows, narrowed by the groups who may use it.
What to measure
Duplicate or unexpected charges found before payment, and time spent checking freight invoices each month.
HR pack

Onboarding that runs itself, and workforce numbers on time.

Who it is for

HR business partners, HR operations and people managers.

Works with

  • SAP SuccessFactors
  • Workday

Also works with:

  • ServiceNow
  • Jira

New hire onboarding

For: hr operations lead

Today
Marco learns on a Monday that a new engineer has no laptop and no login. The hire was in the HR system for three weeks, but nobody raised the IT ticket. The first day is spent waiting in reception.
With SourceLace
Each weekday the agent reads people starting in the next two weeks from your HR system: Workday, SuccessFactors or Oracle Fusion. It checks ServiceNow or Jira for onboarding tickets already raised and leaves those people out. For everyone else, earliest start first, it proposes a ticket with the start date, manager, department, location, job title, worker type and your equipment note, due three business days before the start. Each proposed ticket waits for Marco's approval, and he gets a summary of who starts, who already had a ticket and what was proposed.
What stays protected
No ticket is created until a person approves it, and pay, home addresses, birth dates and national id numbers never go into a ticket.
What to measure
New hires starting without an onboarding ticket, and days between the ticket and the start date.

Monthly headcount summary

For: hr business partner

Today
Lena builds the monthly headcount report by hand from two exports. Hires, leavers and transfers rarely add up the first time, and the report lands in the second week of the month. Department heads ask why their numbers differ from last month's.
With SourceLace
On the first working day of each month, the agent reads employments, hires and leavers from Workday or SuccessFactors. Lena gets one document with month-end headcount and the change since the month before, hires and leavers by department, and attrition for the month and the last 12 months. It adds a short note on any department whose headcount changed by more than 10%. Contractors are included only if you turn that on.
What stays protected
It changes nothing, shows any count below 5 as 'fewer than 5' so no one can be singled out, and keeps pay and personal details out of the report.
What to measure
Days after month end until the headcount report is ready, and corrections asked for after it goes out.

Work anniversaries

For: people manager

Today
Kenji realizes a week late that someone on his team reached ten years with the company. HR keeps the hire dates, but nobody checks them each week. The moment passes without a word.
With SourceLace
Every Monday the agent reads hire dates, job titles and managers from Workday or SuccessFactors. It lists the anniversaries in the coming weeks that hit the milestones you choose, such as 1, 5, 10 and 20 years. Kenji and HR get the list grouped by week: name, job title, department, manager, date and years of service.
What stays protected
It changes nothing and keeps pay, birth dates, home addresses and national ids out of the list.
What to measure
Milestone anniversaries recognized on time, and time spent checking hire dates by hand.

Monthly attrition watch

For: hr business partner

Today
Priya exports last year's leavers each month and spends a morning matching them to headcount by department. By the time the spreadsheet is clean, the leadership meeting has moved on. A team losing one in four people in a year can go unnoticed for a quarter.
With SourceLace
On the first working day of each month, the agent reads employments and leavers from Workday or SuccessFactors. It works out the 12-month attrition rate for the whole organization and for each department, location or division you choose. Priya gets a short report showing only the groups well above the overall rate, with voluntary and involuntary leavers and those who left in their first year. If no group stands out, the report says so in one line.
What stays protected
It changes nothing, never names leavers, leaves out very small groups, shows any count below 5 as 'fewer than 5', and keeps pay and personal details out of the report.
What to measure
Time spent building the monthly attrition view, and how soon a group with rising attrition reaches HR leadership.

Open requisitions aging

For: talent acquisition lead

Today
Every Monday Aisha messages six recruiters for an update on old requisitions. Answers trickle in by Wednesday, in different formats. A finance analyst role open for 120 days only comes up when its hiring manager complains.
With SourceLace
Every Monday the agent reads open job requisitions from Workday or SuccessFactors. Aisha gets a list of those open longer than her limit, 60 days by default, grouped into age bands and sorted oldest first. Each line shows title, department, location, hiring manager, opened date, days open and openings left, with the total of all open requisitions.
What stays protected
It changes nothing, and it never includes candidates' names or details, or pay ranges.
What to measure
Time spent collecting the weekly aging list, and the number of requisitions open past the limit over time.
IT service management pack

Stay ahead of breaches and keep everyone told during incidents.

Who it is for

Service desk leads and IT managers.

Works with

  • ServiceNow
  • Jira

Also works with:

  • Gmail
  • Microsoft 365
  • Slack
  • Teams

SLA breach watch

For: support manager

Today
Hannah keeps the SLA dashboard open all day and refreshes it between meetings. An urgent ticket sits unassigned through a long call and breaches its four-hour target. She hears about it from the customer.
With SourceLace
Every hour the agent reads open tickets from ServiceNow, Zendesk, Jira or Salesforce, with their SLA targets or set targets by priority. Hannah gets only the tickets already past their target or due to breach within the next hours, breached first. Each line shows number, priority, group, assignee or 'unassigned', status and time left or over. When nothing is at risk, it says so and stops. If you connect Slack or Teams and set a channel, it prepares a post of the list that waits for her approval.
What stays protected
It changes no tickets, and nothing is posted without a person's approval.
What to measure
Tickets breaching their target, and time between a ticket reaching risk and someone picking it up.

Major incident updates

For: major incident manager

Today
When the payments service goes down at 2 a.m., Sofia is fixing it and writing the first update at the same time. She hunts for the owner, the start time and last night's changes. The update goes out forty minutes late and misses the change that caused it.
With SourceLace
When a new priority 1 incident is opened in ServiceNow or Jira, the agent reads it and looks for changes made on the same service in the last 24 hours and other open incidents on it. If you connect mail, it drafts the first update to your IT managers list: impact, start time, owner, related changes and when the next update is due. It states facts only and never guesses the cause. If you connect Slack or Teams and set a channel, it also prepares a three-line post that waits for Sofia's approval.
What stays protected
Nothing is sent and nothing is posted without a person, and the incident itself is never changed.
What to measure
Time from a priority 1 incident opening to the first update, and updates that miss a related recent change.

Daily ticket backlog digest

For: support lead

Today
Each morning Tomas pieces together the backlog from three saved views in the service desk. He counts what is old, what is unassigned and what is over target by hand. By standup he still cannot say whether the backlog grew overnight.
With SourceLace
Each weekday morning the agent reads open tickets from ServiceNow, Zendesk, Jira or Salesforce. Tomas gets a short report: open tickets by priority and age, whether the backlog grew or shrank in the last 24 hours, tickets over target, unassigned tickets older than four hours and the ten oldest high-priority tickets. It uses the service desk's own SLAs when it has them, otherwise the targets you set. If you connect mail and turn it on, it also drafts the digest as an email to him.
What stays protected
It changes no tickets and sends nothing; the email is only a draft for Tomas to review.
What to measure
Time spent preparing the morning backlog view, and the number of tickets over target and unassigned over time.

Weekly ticket trends

For: service desk lead

Today
Every Monday Omar exports last week's tickets and spends two hours on pivot tables. He sees that password resets rose again, but has no time to look at why. The report goes out with numbers and no ideas.
With SourceLace
Every Monday the agent reads tickets from ServiceNow or Jira for last week and the four weeks before. Omar gets a one-page report: created, resolved and backlog, the categories that grew most, the ten most frequent issues grouped by meaning, time to resolve and SLA breaches per priority. It ends with three ideas to cut volume, such as a knowledge article, an automation or a problem record. If you connect Slack or Teams and set a channel, it prepares a headline post that waits for his approval.
What stays protected
It changes no tickets, and nothing is posted without a person's approval.
What to measure
Time spent on the weekly report, and ticket volume for the issues it flags over the following weeks.

New hire onboarding

For: hr operations lead

Today
Marco learns on a Monday that a new engineer has no laptop and no login. The hire was in the HR system for three weeks, but nobody raised the IT ticket. The first day is spent waiting in reception.
With SourceLace
Each weekday the agent reads people starting in the next two weeks from your HR system: Workday, SuccessFactors or Oracle Fusion. It checks ServiceNow or Jira for onboarding tickets already raised and leaves those people out. For everyone else, earliest start first, it proposes a ticket with the start date, manager, department, location, job title, worker type and your equipment note, due three business days before the start. Each proposed ticket waits for Marco's approval, and he gets a summary of who starts, who already had a ticket and what was proposed.
What stays protected
No ticket is created until a person approves it, and pay, home addresses, birth dates and national id numbers never go into a ticket.
What to measure
New hires starting without an onboarding ticket, and days between the ticket and the start date.
Marketing operations pack

Leads routed, followed up and traced to revenue.

Who it is for

Marketing operations, demand generation and sales development.

Works with

  • HubSpot
  • Salesforce

Also works with:

  • Gmail
  • Microsoft 365
  • Slack
  • Teams

Weekly campaign performance

For: demand generation manager

Today
Every Monday Noor builds the campaign spreadsheet from exports before the marketing stand-up. A webinar campaign brought no leads for two weeks before anyone saw it. Its budget kept running.
With SourceLace
Every Monday the agent reads campaigns, leads, lifecycle stages and opportunities from HubSpot or Salesforce. It compares last week with the week before, per campaign or source. It counts new leads, marketing-qualified leads (MQLs), sales-qualified leads (SQLs), opportunities and pipeline created. Noor gets a one-page report with totals and change, the three best and three weakest by pipeline, and active campaigns that brought no leads. If you connect Slack or Teams, it prepares a headline post for your channel, which waits for a person's approval.
What stays protected
It is read-only and changes no records; the report leaves out email addresses and phone numbers, and nothing is posted without approval.
What to measure
Time to prepare the weekly campaign review, and active campaigns with no leads noticed within a week.

Lead routing hygiene

For: marketing operations manager

Today
Dev checks for unworked leads by hand each morning, when he remembers. A demo request sat in a queue for three days because its country field was empty. The prospect booked with a competitor.
With SourceLace
Each weekday morning the agent checks leads created in the last week in your CRM. It finds leads still unassigned or in a queue, leads with no first touch after your limit, and leads missing the fields routing needs. Dev gets a short report with counts per problem, then each lead with its source, owner or queue and what is wrong. If you connect Slack or Teams, it prepares a post with the counts. The post goes out only after a person approves it.
What stays protected
It changes no records, leaves out email addresses and phone numbers, and posts nothing without a person's approval.
What to measure
Leads unassigned after a day, and hours from lead creation to first touch.

Weekly MQL to SQL funnel

For: marketing operations lead

Today
Every week Mateo exports leads and rebuilds the funnel by hand. He can see how many marketing-qualified leads (MQLs) came in, but not how many stalled or how long sales took to respond. The quarterly review argued about whose numbers were right.
With SourceLace
Every Monday the agent follows the MQLs of the last several weeks in HubSpot or Salesforce. It counts how many became sales-qualified leads (SQLs) and opportunities, and the conversion rate per lead source. It also works out the median days from MQL to SQL and the median time to first touch. It counts stalled MQLs and lists disqualified ones with their recorded reasons. Mateo gets a report he can bring to the weekly meeting.
What stays protected
It is read-only and changes nothing; the report leaves out email addresses and phone numbers.
What to measure
MQL to SQL conversion rate per source, median speed to lead, and stalled MQLs per week.

MQL follow-up nudges

For: sales development manager

Today
Aiko's team hands over marketing-qualified leads (MQLs), then chases reps in chat to see who followed up. Eight MQLs from last week's event had no call or email after two days. Two of them were from target accounts.
With SourceLace
Each weekday the agent finds MQLs in HubSpot or Salesforce that nobody has contacted within your limit. It groups them by owner. It drafts one short, friendly note per owner listing their waiting MQLs, oldest first, with how long each has waited. MQLs sitting in a queue or with an integration user are listed in the summary instead. Aiko reviews the drafts in her mailbox and sends the ones she wants.
What stays protected
Drafts only: nothing is sent, no records change, and phone numbers are left out.
What to measure
MQLs untouched after 24 hours, and median time from MQL to first touch.
Leadership pack

The week's numbers and the board pack, without the scramble.

Who it is for

Executives and business operations, across CRM, ERP and HR.

Works with

  • Salesforce
  • HubSpot
  • Dynamics 365
  • SAP S/4HANA
  • NetSuite
  • SAP SuccessFactors
  • Workday

Also works with:

  • Gmail
  • Microsoft 365
  • Slack
  • Teams

Weekly business review

For: chief of staff

Today
Every Friday, Sofia asks sales, finance and HR for their numbers for Monday's meeting. They arrive in three formats on Sunday night. The meeting starts with the numbers, not with the slipped $300,000 deal.
With SourceLace
Every Monday morning the agent reads bookings, pipeline and win rate from your CRM. If you connect your ERP and HR system, it adds billing, receivables and headcount moves. Sofia gets one review, a slide deck by default, that leads with the five numbers that moved most since last week and the decisions they point to. If you turn it on, it also drafts the review as an email to her. If you set a channel, it posts the five numbers there only after she approves it.
What stays protected
It changes no records; headcount counts below five are shown as 'fewer than 5', and leavers' names and pay are never shown.
What to measure
Time spent collecting numbers for the weekly meeting, and decisions raised in the first ten minutes.

Daily KPI watch

For: chief executive

Today
Every morning, Nadia opens four dashboards to check whether anything changed overnight. Most days nothing did. The day pipeline dropped 8%, she found out at lunch.
With SourceLace
Each weekday morning the agent checks bookings and open pipeline in your CRM. If you connect them, it also checks overdue receivables in your ERP and headcount in your HR system. It speaks only when a KPI moved more than your threshold since the day before, with both values and the three records that explain most of the move. If you connect mail, it drafts the note as an email to Nadia. If you set a channel, it posts the note there only after she approves it.
What stays protected
It changes no records and sends nothing on its own; it reads only what Nadia's own sign-ins allow.
What to measure
Time spent checking dashboards each morning, and how soon a large KPI move is noticed.

Board pack draft

For: chief financial officer

Today
Before each board meeting, Daniel's team spends weeks copying this quarter's figures into last quarter's deck. Definitions drift between quarters. A missing figure is found the night before.
With SourceLace
Daniel runs it when a board meeting is coming. If you connect your board files, it reads the last board pack for its sections, order and definitions. It gathers the quarter's figures from your CRM, and from your ERP and HR system if you connect them. Daniel gets a draft slide deck with each figure's change and source, a short factual narrative, and a last slide listing every figure still to be provided and by which department.
What stays protected
It is read-only and changes no records; headcount counts below five show as 'fewer than 5', with no names or pay.
What to measure
Days to prepare the board pack, and figures still missing a week before the meeting.
Healthcare pack

Care gaps, readmissions and coverage problems, found before they cost you.

Who it is for

Care management, clinical operations and patient access teams.

Works with

  • Epic
  • Oracle Health
  • MEDITECH

Daily admissions digest

For: clinical operations manager

Today
Each morning Grace phones six units to build the census spreadsheet. By nine o'clock the numbers have already changed. A patient on day eleven of a stay goes unnoticed for another week.
With SourceLace
Every morning the agent reads inpatient stays in your electronic health record. Grace gets a short digest: the last 24 hours' admissions and discharges by unit, and current inpatients by unit. It also lists stays longer than the number of days you set, with each patient's record id, unit and admission date. You choose which units to include. Grace and the unit leads decide what to do about each long stay. Not available on Oracle Health, which does not offer the hospital-wide searches this agent needs.
What stays protected
It changes nothing and sends nothing, includes no clinical notes, refers to patients by record id only, and patient identifiers stay masked.
What to measure
Time spent building the morning census, and long stays reviewed each week.

Care gap focus list

For: care manager

Today
Priya pulls a registry of patients with type 2 diabetes each month. She then opens each record to look for an HbA1c result in the last 12 months. With 300 patients, the list is out of date before she finishes.
With SourceLace
Every Monday morning the agent reads conditions and test results in your electronic health record. It checks up to the number of patients you set, for the condition and test you choose. Priya gets a focus list of patients with no recent result, by record id, most overdue first, with the date of each last result. The next step on each line is outreach by the care team under your own guideline. Priya and her team decide who to contact and how. Not available on Oracle Health, which does not offer the hospital-wide searches this agent needs.
What stays protected
It changes nothing, suggests no diagnosis or treatment, refers to patients by record id only, and patient identifiers stay masked.
What to measure
Patients overdue for the chosen test each week, and time from flag to completed outreach.

Weekly readmissions watch

For: care management lead

Today
Every Monday Sofia exports last week's admissions and matches them against earlier discharges in a spreadsheet. It takes most of the morning. A patient admitted twice under different units is easy to miss.
With SourceLace
Every Monday morning the agent reads last week's inpatient admissions and those patients' earlier stays in your electronic health record. It checks up to the number of patients you set. Sofia gets a list of readmissions within the number of days you set, with each patient's record id, earlier discharge date and unit, readmission date and unit, and days between. It ends with the week's readmission count and says whether more admissions existed than were checked. Sofia's team decides what to review. Not available on Oracle Health, which does not offer the hospital-wide searches this agent needs.
What stays protected
It changes nothing, includes no clinical notes and gives no medical advice; patients appear by record id only and identifiers stay masked.
What to measure
Weekly readmissions within the window, and time spent on the weekly tally.

Readmission alert

For: quality coordinator

Today
Ahmed builds the readmission tally by hand once a week. By then a patient readmitted 12 days after going home has been on the ward for five days. The care team learns about it too late to review the earlier discharge while it is fresh.
With SourceLace
Shortly after a patient is admitted, the agent reads that patient's earlier inpatient stays in your electronic health record. It lists the admissions that came within the number of days you set of an earlier discharge. Each line shows the patient's record id, the earlier discharge date and unit, the readmission date and unit, and the days between. It says whether planned readmissions can be told apart in your record system, and if not, that the list includes them. Ahmed and the care team decide what each readmission needs. Not available on Oracle Health, which does not offer the hospital-wide searches this agent needs.
What stays protected
It changes nothing, includes no clinical notes and gives no medical advice; patients appear by record id only and identifiers stay masked.
What to measure
Readmissions within the window, and time from readmission to the care team knowing about it.

Discharge follow-up check

For: transitions-of-care nurse

Today
Tomas checks every discharge from the past week by hand. He looks for a booked follow-up or a clinic visit since the patient went home. With 80 discharges a week, a few patients slip through with nothing booked.
With SourceLace
Each weekday morning the agent reads recent inpatient discharges, appointments and clinic visits in your electronic health record. It checks up to the number of patients you set. Tomas gets an exception list of patients with no follow-up booked or held, by record id, with discharge date, unit and days since discharge, oldest first. It says how many discharges it checked. Tomas and the care managers decide how to arrange each follow-up. Not available on Oracle Health, which does not offer the hospital-wide searches this agent needs.
What stays protected
It changes nothing, books nothing and gives no medical advice; patients appear by record id only and identifiers stay masked.
What to measure
Discharged patients without a follow-up within the window, and days from discharge to follow-up booked.

Eligibility before the visit

For: patient access coordinator

Today
Lena's front desk finds coverage problems only when the patient is standing at the counter. Last Tuesday a plan that ended in June surfaced at check-in. The visit started late while staff phoned the patient's employer.
With SourceLace
Each weekday morning the agent reads tomorrow's booked appointments and each patient's insurance coverage in your electronic health record. You can look up to a week ahead. Lena gets a focus list of appointments whose patient has no coverage active on the visit date. Each line shows the appointment time, the patient's record id, what is wrong (ended, not yet started, cancelled or no payer) and the plan name. The step is a call to the patient to confirm their insurance; Lena's team makes every call and every decision. On Oracle Health, you list the clinics whose schedules it checks, and it checks them one at a time.
What stays protected
It changes nothing, never says what a patient owes or whether a service is covered, and member and subscriber ids stay masked.
What to measure
Appointments with a coverage problem found the day before, and coverage problems first found at check-in.

On Oracle Health, the pack sets up only the eligibility check: Oracle Health searches encounters one patient at a time, so the other agents are left out, and the pack says why. On Epic and MEDITECH, the searches these agents use are published but not yet tried; if one is refused, the agent stops and says so. Use the healthcare pack with test data only until business associate agreements are in place with SourceLace and every provider it uses. It does not make a setup HIPAA compliant. Its agents read and report; a qualified person on your team makes every clinical, billing and coverage decision.

Healthcare claims pack

Denials, payments and payers, worked from the remittance you already receive.

Who it is for

Billing, revenue cycle and patient access teams that reach payers through a clearinghouse.

Works with

  • Stedi
  • Optum

Weekly denial work list

For: billing team lead

Today
Every Monday Dana opens last week's remittance advice one payer at a time and copies denied claims into a spreadsheet. Partial denials hide among routine contract write-downs, so some are found only when the claim is too old to appeal.
With SourceLace
Every Monday the agent reads the remittance advice your clearinghouse received in the last days you set. Dana gets a work list of claims that were denied or reduced for reasons other than the contract, grouped by payer and reason code, with the amount at stake on each, the largest first, and an optional email draft to the reviewer. Dana's team decides which claims to correct, appeal or write off.
What stays protected
It changes nothing at the clearinghouse or any payer, and sends nothing; patient details stay masked and never appear in the draft.
What to measure
Dollars in denied claims worked each week, and days from remittance to first action.

Remittance reconciliation

For: cash posting specialist

Today
Luis ties each payment to its remittance advice by hand before posting. When a payment and its claims differ by a few dollars, he hunts line by line for the reason, and the batch waits.
With SourceLace
Every Tuesday the agent totals last week's remittance by payer and by payment: billed, paid, patient responsibility and adjustments. It flags payments whose claims do not add up to the payment, and claims whose amounts do not balance, each with the difference. Luis decides how to post and what to raise with the payer.
What stays protected
It changes nothing and sends nothing; patient details stay masked.
What to measure
Time spent reconciling each week, and the number of unbalanced payments found before posting.

Payer scorecard

For: revenue cycle director

Today
Once a quarter Morgan asks an analyst for denial rates by payer. The report takes two weeks, and by the time it arrives a payer's new rule has already cost a month of payments.
With SourceLace
Every Monday the agent reads the remittance of the last weeks you set and ranks payers by the share of claims they denied. For each payer it shows billed and paid amounts, the share paid, and the most common denial reason codes. Morgan decides which payers to raise and what to change upstream.
What stays protected
It changes nothing and sends nothing; patient details stay masked.
What to measure
Denial share by payer over time, and dollars recovered after raising a payer.

Use this pack with test data only until business associate agreements are in place; it does not make a setup HIPAA compliant. A qualified person on your team makes every billing, appeal and patient-balance decision.

Get started

See your own systems in a pack.

A pilot connects your systems, applies a pack with your team, and runs its agents in shadow mode on your data, so you see the results before anything goes live.

Request a pilot How agents work