For agencies, wholesalers and service firms that already have reviewed invoice records but still reconcile open balances and ageing exceptions manually. One reviewed, non-sensitive CSV of up to 250 anonymous invoice rows in one currency plus one explicit as-of date.

Use native accounting ageing first: if QuickBooks, Xero or your current accounting system already provides the A/R ageing summary/detail you need with acceptable review effort, use it. This pilot is for a remaining reviewed-export/reconciliation gap.

Scope: stable anonymous row/invoice IDs, due date, invoice total, paid amount and reviewed OPEN / PAID / VOID status on one currency and one agreed balance basis. Duplicate IDs, invalid dates, negative/formatted amounts, paid amounts above invoice total and status/balance contradictions are held rather than guessed. Customer names and contact details are not required.

Output: remaining balance, current / 1–30 / 31–60 / 61–90 / 91+ day buckets where due evidence exists, unknown-date exceptions, bucket totals, source-row reconciliation and explicit held rows. Missing dates are never treated as overdue, and ageing does not predict collectability.

Excluded: debtor contact, collection activity, credit decisions, bad-debt/write-off advice, accounting certification, inferred payments, payment-recovery probability, legal advice, account access or accounting-system writeback.

Ask about Invoice Ageing Snapshot

For contractors, installers, agencies and project-service firms that already know their job revenue and direct-cost basis but still reconcile contribution by job manually. One reviewed, non-sensitive CSV of up to 200 anonymous jobs in one currency.

Use native job-costing first: if ServiceTitan, Jobber, Buildxact or your current project/accounting system already provides the job-cost and profitability view you need with acceptable review effort, use it. This pilot is for a remaining reviewed-export/reconciliation gap.

Scope: stable anonymous job IDs, supplied job revenue, materials, labour, subcontractor and other agreed direct costs on one written period, tax and cost basis. Duplicate IDs, negative or formatted amounts, mixed bases and internally inconsistent totals are held rather than repaired or inferred. Customer and worker identities are not required.

Output: supplied revenue, agreed direct-cost total, contribution (revenue minus supplied direct costs), contribution-margin percentage only where revenue is greater than zero, portfolio totals, source-row reconciliation and explicit exceptions. Contribution is a bounded management calculation on the supplied direct-cost basis; it is not net profit or an accounting statement.

Excluded: overhead allocation, payroll reconstruction, WIP or revenue-recognition accounting, forecast-at-completion, tax/accounting certification, staff or subcontractor blame, price recommendations, customer/vendor contact, account access or project/accounting-system writeback.

Ask about Job Margin Check

For retailers, wholesalers and small distributors that already have reviewed stock and replenishment assumptions but still compare inventory position with reorder thresholds manually. One reviewed, non-sensitive CSV of up to 500 anonymous SKU rows on one agreed quantity basis.

Use native inventory tools first: if Shopify, Square or your current inventory/POS system already provides low-stock alerts, days-of-inventory/replenishment views or purchase-order support that answers the question with acceptable review effort, use it. This pilot is for a remaining reviewed-export/reconciliation gap.

Scope: stable anonymous row/SKU IDs, current on-hand quantity, customer-confirmed on-order quantity expected to be usable within the agreed planning horizon, customer-supplied average daily usage, lead days and safety stock. Duplicate IDs, negative/formatted quantities, non-positive lead assumptions and unconfirmed on-order availability are held rather than repaired or forecast by Vox Dei.

Output: supplied inventory position, customer-input reorder point (daily usage × lead days + safety stock), threshold shortfall where positive, days of cover only where supplied daily usage is greater than zero, below/at/above-threshold flags, source-row reconciliation and explicit exceptions. Threshold shortfall is a review signal, not an order recommendation or promised stock level.

Excluded: demand forecasting, seasonality/velocity inference, supplier reliability prediction, economic-order-quantity optimization, purchase approval, automatic purchase orders, stockout/availability guarantees, account access or inventory-system writeback.

Ask about Inventory Reorder Snapshot

For contractors, manufacturers, wholesalers and makers that already have supplier quotations but still normalize comparable line items, freight and quoted fees manually. One reviewed, non-sensitive CSV of up to 100 anonymous supplier-item quote rows in one currency.

Use native sourcing tools first: if Precoro, Tradogram or your procurement/RFQ system already standardizes supplier responses and provides the comparison matrix you need, use it. This pilot is for a remaining reviewed-export/reconciliation gap.

Scope: stable anonymous quote/line and supplier IDs, one customer-confirmed item/specification key, the same comparison quantity/unit basis, supplied unit price, freight and other explicitly defined quoted fees on one currency and tax/fee basis. Duplicate IDs, negative or formatted numeric values, mismatched quantities/specifications, mixed currencies/bases and fees that cannot be allocated once are held rather than normalized by guesswork. Non-comparable quotes remain separate.

Output: normalized comparable line totals, supplier-level quoted totals where the supplied rows are complete on the agreed basis, absolute/percentage differences where denominators are valid, source-row reconciliation and explicit exceptions. A lowest observed comparable amount is descriptive only; it is not a supplier recommendation or proof of best total value.

Excluded: inferred taxes or fees, FX conversion, vendor due diligence/risk scoring, quality or delivery prediction, negotiation, supplier selection/award, savings guarantees, purchase-order creation, supplier contact, account access or procurement-system writeback.

Ask about Supplier Quote Compare

For ecommerce shops, wholesalers and product teams that already have a catalog export but still need a reviewed pre-import exception check. One reviewed, non-sensitive CSV of up to 500 anonymous product/variant rows on one agreed catalog convention.

Use native import validation first: if Shopify, WooCommerce or your current commerce platform already provides the header/mapping/import-error checks you need with acceptable review effort, use it. This pilot is for a remaining independent or overflow QA gap before you use the native importer.

Scope: stable anonymous row ID plus customer-confirmed SKU convention, title, category, price and currency fields. Before payment we agree whether SKU must be unique at product or variant level and which fields are required. Duplicate row IDs, SKU conflicts under that convention, missing required fields, invalid/negative or formatted price values, unsupported currency values and ambiguous category fields are held rather than silently corrected. A zero price is flagged for review, not automatically treated as an error.

Output: accepted-row and held-row reconciliation, duplicate/SKU conflicts, missing-field, price/currency/category exceptions and field-level counts suitable for human review before a native import. The result does not certify that every platform rule, plugin field or downstream integration will accept the file.

Excluded: copywriting, image-content or image-rights review, SEO, platform/plugin compatibility certification, live import, storefront/account access, product publishing, taxonomy redesign, inferred missing values or commerce-system writeback.

Ask about Product Catalog QA

For retailers, makers and wholesalers that already know their selling prices and direct unit-cost basis but still review contribution and customer-supplied target-margin scenarios manually. One reviewed, non-sensitive CSV of up to 500 anonymous SKU/scenario rows in one currency.

Use native margin reporting first: if Shopify, Square for Retail or your current commerce/accounting system already provides the product-cost, gross-profit and margin view you need with acceptable review effort, use it. This pilot is for a remaining reviewed-export or scenario-reconciliation gap.

Scope: stable anonymous row/SKU IDs, supplied current selling price, customer-supplied direct unit cost and an optional customer-supplied target margin from 0% to less than 100%, all on one written tax/fee/cost basis. Duplicate IDs, negative or formatted amounts, mixed bases and invalid target margins are held rather than repaired by assumption.

Output: supplied-price contribution per unit, contribution-margin percentage only where selling price is greater than zero, below/at/above supplied-target flags where a valid target exists, source-row reconciliation and explicit exceptions. When a target is supplied, the arithmetic target-price scenario is calculated from the supplied direct cost and target margin; it is a mathematical comparison only, not a recommendation to charge that price.

Excluded: demand or elasticity forecasting, competitor pricing, willingness-to-pay analysis, overhead allocation, net-profit claims, tax/accounting advice, target-margin selection, price approval, promotion strategy, automatic repricing or commerce/accounting-system writeback.

Ask about Price List Margin Audit

For small agencies and operating teams that already know their software/service terms but still reconcile cross-vendor renewal dates, recurring amounts and notice-review dates manually. One reviewed, non-sensitive CSV of up to 100 anonymous subscription/service rows in one currency plus one explicit as-of date.

Use native contract/subscription management first: if Ramp Contracts & renewals, your spend-management platform or another contract/SaaS-management tool already centralizes renewal dates, amounts, owners and reminders with acceptable review effort, use it. This pilot is for a remaining reviewed-export/reconciliation gap.

Scope: stable anonymous row/vendor labels, supplied recurring amount, customer-confirmed weekly/monthly/quarterly/annual cadence, supplied next-renewal date and optional customer-supplied notice days. Duplicate IDs, negative or formatted amounts, invalid dates/cadences, future as-of dates and contradictory supplied renewal evidence are held rather than interpreted. Annualized amount uses only the supplied cadence: 52 / 12 / 4 / 1 payments.

Output: annualized supplied recurring amount, days to the supplied renewal date, customer-input notice-review date, upcoming/past-supplied-date review queues, totals, source-row reconciliation and explicit exceptions. A past supplied date is a review signal; it is not proof that a contract renewed, expired or can be cancelled.

Excluded: contract or auto-renewal interpretation, clause extraction, cancellation/renewal execution, vendor contact, continuous monitoring or reminders, account/card access, payment blocking, savings claims, negotiation, accounting/tax/legal advice or spend-system writeback.

Ask about Subscription & Renewal Snapshot

For shops, ecommerce and product businesses that already have a sales export but still reconcile SKU/category mix, supplied direct costs and exceptions outside their native reports. One reviewed, non-sensitive CSV of up to 1,000 anonymous sales lines for one agreed period and currency.

Use native sales reporting first: if Shopify, Square or your current POS/commerce system already provides the product/category quantities and net-sales view you need with acceptable review effort, use it. This pilot is for a remaining reviewed-export/reconciliation gap.

Scope: stable anonymous line IDs plus customer-supplied SKU/category, quantity, net-sales amount and direct cost where contribution is requested, all on one written discount/return/tax/cost basis. Before payment we agree how discounts and returns are represented. Duplicate IDs, negative or formatted amounts, invalid quantities, mixed currencies/bases and rows that do not follow the agreed return/discount convention are held rather than repaired or reclassified by assumption.

Output: accepted/held source-row reconciliation, SKU/category quantity and supplied net-sales totals, sales share only where total supplied net sales is greater than zero, supplied direct-cost totals and contribution only where that cost basis is provided, plus explicit exceptions. The result describes the supplied period; it does not attribute why sales happened or predict future demand.

Excluded: customer profiling, causal or multi-touch attribution, demand forecasting, inferred costs, inventory valuation, accounting/tax certification, growth or profitability guarantees, merchandising recommendations, automatic pricing or POS/commerce-system writeback.

Ask about Sales Mix Snapshot

For ecommerce, wholesale and fulfilment teams that already have reviewed order and shipment exports but still reconcile line-level ordered-versus-shipped quantity across systems or files. One reviewed, non-sensitive standardized CSV of up to 1,000 total anonymous ORDER and SHIPMENT rows for one agreed snapshot.

Use native fulfilment status first: if Shopify, your WMS/OMS or shipping platform already shows unfulfilled, partially fulfilled and fulfilled quantities/statuses with the detail you need, use it. This pilot is for a remaining cross-export reconciliation gap.

Scope: stable anonymous record, order and SKU IDs, explicit ORDER or SHIPMENT row type, and plain non-negative quantities on one agreed unit basis. The customer confirms that all related shipments for the snapshot are included. Duplicate record IDs, invalid/formatted quantities, missing order/SKU keys, multiple ORDER lines for the same order/SKU and SHIPMENT rows with no matching ORDER evidence are held or explicitly flagged rather than merged by assumption.

Output: ordered and supplied-shipment quantity by order/SKU, matched / short / over / no-order review states, source-row reconciliation and explicit duplicate/key exceptions. These states describe the supplied files only; they do not prove that a shipment was delivered, accepted by a customer or financially settled.

Excluded: financial/payment reconciliation, carrier tracking or delivery confirmation, refund/return decisions, customer messaging, inventory adjustment, order editing, platform/account access, fulfilment execution or OMS/WMS/commerce-system writeback.

Ask about Order Reconciliation

For small agencies, studios, coworking/rental operators and service teams that already know their resource availability and bookings but still reconcile booked-versus-available capacity manually. One reviewed, non-sensitive CSV of up to 200 anonymous resource-period rows; identifiable staff names are not required.

Use native resource planning first: if Float, Resource Guru, your booking platform or another scheduling/resource-planning system already provides capacity, scheduled utilization and remaining/over-capacity views with acceptable review effort, use it. This pilot is for a remaining reviewed-export/reconciliation gap.

Scope: stable anonymous resource-period IDs, customer-defined resource type, non-overlapping period, supplied available hours and supplied booked hours under one written capacity convention. Before payment we agree whether time off, tentative bookings, maintenance/downtime or other unavailable time has already been removed from supplied capacity. Duplicate IDs, negative or formatted hours, invalid periods and overlapping rows that could double-count the same capacity are held rather than repaired by assumption. Booked hours above supplied capacity remain valid evidence of over-capacity rather than being clipped.

Output: supplied available and booked hours, utilization percentage only where available hours are greater than zero, remaining hours where positive, over-capacity hours where booked exceeds availability, source-row reconciliation and explicit exceptions. Zero supplied capacity produces an undefined utilization percentage, never an invented 0% or 100%.

Excluded: employee or contractor ranking, performance inference, hiring/staffing decisions, payroll, schedule changes, future availability or demand prediction, burnout/safety conclusions, automatic booking, account access or scheduling-system writeback.

Ask about Capacity Utilization Snapshot

For venues, events, rentals and project/service bookings that already know their deposit terms but still reconcile required-versus-recorded deposits manually. One reviewed, non-sensitive CSV of up to 250 anonymous booking rows in one currency.

Use native booking/payment tools first: if your booking, invoicing or payment platform already shows deposit requirements, recorded receipts and upcoming-start status clearly, use it. This pilot is for a remaining reviewed-export/reconciliation gap.

Scope: stable anonymous booking ID, customer-supplied required deposit, recorded deposit receipt/credit, supplied start date and reviewed booking status. Amounts must use one agreed basis. Missing or contradictory amount/status/date records stay exceptions; Vox Dei does not infer that money was received from a bank, card processor or invoice system.

Output: required-versus-recorded deposit comparison, explicit shortfall/data exceptions and an upcoming-start review queue using the dates/statuses you provide. A shortfall is a review flag, not a customer default, cancellation right or collection instruction.

Excluded: card/bank data, payment collection or reconciliation to processor settlement, refunds, cancellation enforcement, customer contact, credit decisions, contract/legal interpretation, payment-system access or writeback.

For B2B sales, agency and service teams that already have a reviewed current-pipeline export but still need a simple repeatable view of how long anonymous opportunities have remained in their supplied current stage. One reviewed, anonymized, non-sensitive CSV of up to 500 current open-pipeline rows.

Use CRM-native stage duration first: if HubSpot, Salesforce or your current CRM already exposes the time-in-current-stage and stage-age filters you need with acceptable review effort, use it. This pilot is for a remaining reviewed-export/reconciliation gap.

Scope: anonymous opportunity ID, supplied current stage, optional real stage-entered date, explicit as-of date and your own whole-day review interval from 1–365 days. Duplicate IDs, impossible dates and stage dates after the as-of date are held rather than repaired. Missing stage-entered dates remain explicit unknowns and are never converted to age zero.

Output: total, dated, current, aged and missing-date rows by supplied stage; aged rate using only rows with a usable supplied stage-entered date; median stage age for dated rows; whole-pack source-row reconciliation; and explicit held exceptions.

Excluded: win-probability, revenue or close-date forecasting; salesperson ranking; stall-cause inference; stage-change or follow-up recommendations; contact PII or email-body analysis; CRM tasks, outreach or writeback.

For retailers, makers, wholesalers and product teams that already know their list prices, direct unit costs and proposed discounts but still compare contribution scenarios manually. One reviewed, non-sensitive CSV of up to 250 anonymous SKU/scenario rows in one currency and one agreed price/cost basis.

Use native sales analytics first: if Square, Shopify or your current POS/commerce system already provides the discount and item-sales visibility needed for the decision, use it. This pilot is for a remaining scenario/reconciliation gap using customer-supplied prices and costs.

Scope: stable anonymous row/SKU IDs, list price, supplied direct unit cost, discount as an agreed amount or percentage, and units. Duplicate IDs, negative/formatted amounts, discounts outside the agreed basis and scenarios that produce invalid negative selling prices are held rather than repaired by assumption.

Output: selling price after supplied discount, contribution before/after discount, contribution difference and contribution-margin percentage where defined, plus source-row reconciliation and explicit exceptions. Contribution is not net profit and does not predict demand or volume lift.

Excluded: discount approval, demand/elasticity forecasting, competitor pricing, overhead allocation, tax advice, promotion recommendation, customer targeting, automatic repricing or POS/ecommerce writeback.

For contractors, installers, agencies and project teams that already have reviewed project/category budgets and actual costs but still reconcile them manually. One reviewed, non-sensitive CSV of up to 250 anonymous project/category rows in one currency and one agreed cost basis.

Use native job-costing first: if QuickBooks, Buildxact or your project/accounting system already provides the budget-versus-actual view you need with acceptable review effort, use it. This pilot is for a remaining reviewed-export/reconciliation gap.

Scope: stable anonymous row/project/category IDs, plain non-negative budget and actual-cost values, and one agreed reporting period/basis. Approved changes or committed costs are included only when the customer defines a consistent basis before payment; otherwise they stay outside the calculation. Duplicate IDs, negative/formatted amounts and inconsistent bases are held rather than guessed.

Output: budget, actual cost, absolute variance and variance percentage only where budget is greater than zero, plus project/category summaries, source-row reconciliation and explicit zero-budget/data exceptions. A zero budget never produces an invented percentage.

Excluded: forecast-at-completion, committed-cost reconstruction, payroll inference, accounting certification, cost-overrun blame, change-order entitlement/approval, customer/vendor contact or project/accounting-system writeback.

For distributors, wholesalers, ecommerce operators and manufacturers that already have shipment quotes and final freight charges but still reconcile them manually. One reviewed, non-sensitive CSV of up to 300 anonymous matched shipment rows in one currency and one agreed charge basis.

Use native freight audit first: if your TMS, carrier billing platform or freight-audit software already compares final invoices with original rates/quotes and flags the variance you need, use it. This pilot is for a remaining reviewed-export/reconciliation gap.

Scope: stable anonymous row/shipment IDs, quoted freight, final billed freight and a reviewed final-bill status on the same agreed transportation/fee/tax basis. Duplicate IDs, negative or formatted amounts, missing final charges and mismatched bases are held rather than guessed. Accessorial, duty or tax amounts are compared only if both sides use the same customer-confirmed basis.

Output: quoted and billed amounts, absolute variance, percentage variance only where the quoted amount is greater than zero, higher/equal/lower counts, source-row reconciliation and explicit held exceptions. A difference is a review signal, not evidence that a carrier billed incorrectly.

Excluded: carrier wrongdoing claims, invoice disputes, claim filing, negotiation, refund recovery, rate-shopping, surcharge/dimensional-weight cause inference, accounting entries, carrier/TMS access or system writeback.

For ecommerce, retail and product businesses that already have reviewed return/refund records but still combine direct return-cost components manually. One reviewed, non-sensitive CSV of up to 500 anonymous return rows in one currency and one agreed cost basis.

Use native return analytics first: if Shopify or your returns platform already provides the return/reversal and fee view you need with acceptable review effort, use it. This pilot is for a remaining reviewed-export/reconciliation gap across customer-supplied refund, reverse-shipping, handling and recovered-value fields.

Scope: stable anonymous return/row IDs, reviewed return status, plain non-negative refund, reverse-shipping, handling and recovered-value amounts on one consistent basis. Duplicate IDs, negative/formatted amounts, mixed bases and recovered value exceeding the supplied direct burden are held for review rather than repaired by assumption.

Output: supplied direct return burden by accepted row, component totals, source-row reconciliation and explicit held exceptions. The result is not represented as total net loss or profit, and original product cost is not counted again unless a separately defined scope explicitly supplies that basis.

Excluded: automatic refunds/exchanges, return-policy decisions, fraud or customer-cause inference, accounting/tax treatment, inventory write-down, carrier claims, customer contact, profitability/LTV claims or ecommerce/returns-system writeback.

For agencies, project teams, purchasing and office operations that already have reviewed approval requests but still reconcile how long pending items have been waiting. One reviewed, non-sensitive export of up to 500 anonymous approval requests plus one explicit as-of date and your own 1–365 day review interval.

Use native approval tooling first: if Asana Approvals, Microsoft Teams/Power Automate Approvals or your current workflow system already gives the approval status and ageing view you need with acceptable review effort, use it. This pilot is for a remaining reviewed-export/reconciliation gap.

Scope: stable anonymous request ID, approval type, real submitted date and a customer-reviewed normalized status of pending, approved, rejected or cancelled. Duplicate request IDs, impossible dates and submitted dates after the supplied as-of date are held rather than repaired. The review interval is customer-supplied; Vox Dei does not infer an urgency threshold from the approval type.

Output: reviewed status counts, an oldest-first pending queue, age in days, overdue flags only when age is greater than the supplied interval, pending-overdue count/rate where pending records exist, oldest pending age where defined, and explicit exceptions. A queue position or overdue flag is an administrative review cue, not a recommendation to approve, reject or escalate the request.

Excluded: approval/rejection decisions, approver assignment, authorization or permission changes, urgency/performance inference, automatic reminders/escalations, employee/vendor ranking, customer or staff messaging, account access or workflow-system writeback.

For CRM, ERP, accounting, ecommerce or migration teams that already have a reviewed source-to-target field map and want an independent pre-test-import check. Review one anonymized, non-sensitive CSV mapping plus representative sample, with mapping and sample rows combined up to 500.

Use native validation first: if the target platform’s importer already gives sufficient mapping preview and error evidence, use it. This pilot is for a remaining independent or overflow reconciliation gap before a native test import.

Scope: reviewed mapping fields plus anonymous sample rows using declared text, number, date or boolean types. Duplicate source mappings, target collisions, type changes, unmapped sample fields, missing required values and invalid declared values are held rather than silently converted.

Output: normalized reviewed mapping, row-level clean/held evidence, explicit mapping/sample exceptions, counts and one bounded state: READY_FOR_NATIVE_TEST_IMPORT or HOLD_FOR_REVIEW. Readiness applies only to the reviewed sample and is not production cutover approval.

Excluded: production imports, credentials or platform access, system writeback, merge/deduplication business decisions, PII/banking/credential data, formulas/macros, multi-object relationship migration, inferred custom transformations or customer messaging.

For contractors, suppliers and specialist vendors that already monitor public-sector opportunities but still need a bounded multi-source review across one agreed category and region. Review up to 10 agreed official public sources and up to 50 candidate records.

Use official portal search and alerts first: CanadaBuys already provides searchable tender opportunities, filters and search notifications for Government of Canada procurement, while Ontario suppliers can use Supply Ontario’s Ontario Tenders Portal for open provincial competitive procurements. If one native portal or alert already covers the required category/region well enough, use it instead. This pilot is for a remaining cross-source review gap.

Evidence contract: each retained candidate must have a stable record ID, HTTPS source URL, offset-aware capture timestamp, explicit source type and directly observed title, public buyer and closing date or current status. Missing required facts and duplicate records are held rather than inferred.

Output: a source-linked shortlist of the records that match the agreed search scope, explicit exclusions/no-match evidence where applicable, observed buyer and closing/status fields, and source-lineage exceptions. The scan preserves what the official source says; it does not upgrade an announcement or incomplete record into a bid-ready opportunity.

Excluded: bid eligibility decisions, prequalification or mandatory-requirement interpretation, bid writing/submission, award or win-probability prediction, privileged access, procurement influence, private bidder data, or any completeness guarantee across the market.

For commercial, product and research teams that already know which small competitor set matters but still need a bounded record of public offer changes. Compare up to 50 matching fields across two dated, permitted public snapshots for up to three businesses.

Use page-change monitoring first: tools such as Visualping or Distill can already monitor selected public pages and alert when text or page elements change. If the buyer’s existing monitor/history already provides the dated evidence and comparison they need, use it instead. This pilot is for a remaining reviewed field-reconciliation and evidence-packaging gap.

Evidence contract: each comparison uses a stable record ID plus chronological before/after snapshots with HTTPS source URLs, offset-aware capture timestamps, explicit source type and non-empty observed fields. Only fields present in both snapshots are comparable. A missing field is not guessed, and reversed snapshot order or duplicate records are held.

Output: the intersection of comparable fields, explicit changed-field list, unchanged observed fields where useful, dated source references and exceptions. The result describes observed public offer differences only; it does not infer why a competitor changed an offer or what the buyer should do.

Excluded: login-gated or private scraping, motive or strategy inference, competitor/customer profiling, complete-market claims, recommendation or repricing action, private analytics access, or autonomous monitoring setup on a client’s systems.

For regional suppliers, construction/material businesses and service vendors that want a bounded view of early public-project signals before those signals are confused with actual tenders. Review one agreed region/niche across up to 10 agreed public or official sources and up to 50 candidate project records.

Use official project pipelines first: Ontario already publishes current highway/project information, and Infrastructure Ontario publishes project pipelines, market updates and project-stage announcements. If those native sources already cover the required niche/region well enough, use them instead. This pilot is for a remaining cross-source monitoring and reconciliation gap.

Evidence contract: every retained project record requires a stable record ID, HTTPS source URL, offset-aware capture timestamp, explicit source type and directly observed project name, stage and location. Missing project-stage facts, duplicate records and stale/ambiguous evidence remain exceptions rather than being upgraded by inference.

Output: source-linked project-stage summaries, observed location/stage, explicit stale or missing-evidence caveats, exclusions/no-match evidence where applicable, and source-lineage exceptions. The stage is preserved exactly as observed in the reviewed source.

Excluded: tender-status inference, bid eligibility or prequalification judgment, award/win probability, sales or pipeline guarantees, private-project access, personal contact harvesting, bid submission or a claim that a government announcement is already a procurement opportunity.

For purchasing, wholesale, manufacturing and contractor teams that receive supplier price lists but still compare dated changes manually. Compare up to 500 matched items from exactly two customer-authorized price snapshots.

Use purchasing/ERP vendor-pricelist tools first: systems such as Odoo already maintain vendor pricelists and can import or update supplier prices. If the buyer’s current procurement/ERP system already preserves the vendor-price history and comparison they need, use it instead. This pilot is for a remaining authorized-export comparison gap.

Evidence contract: stable matched item ID, two chronological customer-authorized HTTPS snapshots with offset-aware capture times, numeric price and one three-letter currency. Both snapshots must use the same currency and agreed item/specification basis. Unauthorized sources, reversed dates, non-numeric prices or mixed currencies are held rather than repaired or converted.

Output: before and after supplied price, absolute change, percentage change where defined, currency, dated source references and explicit exceptions. No foreign-exchange conversion or missing-price inference is performed.

Excluded: licensed/private-source acquisition, live supplier-site scraping without permission, savings or overpayment claims, supplier negotiation, purchase recommendations, automatic repricing, purchasing action, FX conversion, contract interpretation or ERP/procurement writeback.

For small-business finance and operations teams that already have a reviewed, non-sensitive current open-payables CSV but still reconcile due dates manually. Up to 500 anonymous supplier-bill rows in one currency plus one explicit as-of date.

Use native reporting first: if QuickBooks, Xero, your ERP or another accounting system already gives you the aged-payables or supplier-balance view you need with acceptable review effort, use it. This pilot is for a remaining reviewed-export/reconciliation gap.

Scope: anonymous supplier, bill and row IDs; real bill and due dates; positive outstanding amount only. Duplicate IDs, impossible chronology, invalid dates and ambiguous amount formats are held for correction rather than guessed or double-counted.

Output: overdue, due-today, 1–7 day, 8–30 day and 31+ day amounts; anonymous supplier totals; source-row reconciliation; and explicit held exceptions.

Excluded: bookkeeping entries, bill creation or editing, payment execution or scheduling, supplier contact, bank/payment data, credit-note application, multi-currency conversion, accounting/tax/legal opinion, cash-priority advice or system writeback.

For purchasing and project-operations teams that already have a reviewed, non-sensitive current OPEN/PARTIAL purchase-order export but still reconcile remaining commitment manually. Up to 500 anonymous PO-line rows in one currency/value basis plus one explicit as-of date.

Use native reporting first: if QuickBooks, Xero, your ERP or procurement platform already provides the open-PO detail, partial-receipt status and remaining commitment view you need with acceptable review effort, use it. This pilot is for a remaining reviewed-export/reconciliation gap.

Scope: stable anonymous row, PO-line, PO and supplier IDs; real order date; optional supplied expected date; reviewed OPEN/PARTIAL status; positive committed value and non-negative received value. Duplicate IDs, impossible chronology, status/value mismatches, formatted amounts, and fully/over-received rows are held rather than guessed or double-counted.

Output: committed, received and remaining value; anonymous supplier totals; source-row reconciliation; and past-expected evidence only where a valid expected date was supplied. A missing expected date is never treated as late.

Excluded: purchasing or receiving action, PO approval/editing, invoice matching, bill entry, supplier contact, payment action, budget approval, cash forecasting, supplier ranking, contract/accounting/tax/legal opinion, FX conversion or system writeback.

For retailers, wholesalers, makers and inventory operators that already have a reviewed, non-sensitive current-inventory CSV but still reconcile stock value and last-sale recency manually. Up to 500 anonymous SKU rows, one currency/cost basis, one explicit as-of date and your own 1–365 day review interval.

Use native reporting first: if Shopify, Square, your ERP or inventory platform already gives you a usable slow-stock, sell-through, days-remaining or ageing view, use it. This pilot is for a remaining reviewed-export/reconciliation gap.

Scope: stable anonymous row and SKU IDs, non-negative plain on-hand quantity and unit cost, plus a real last-sale date or a deliberate blank. Duplicate IDs, formatted or negative numbers, impossible dates and dates after the as-of date are held rather than guessed or double-counted.

Output: source-row reconciliation, inventory value, supplied-date recency and one state per accepted row: STALE, CURRENT, UNKNOWN_LAST_SALE or NO_STOCK. Unknown last-sale dates are never inferred and do not dilute the stale-rate denominator; zero-stock rows are also excluded from that denominator.

Excluded: demand forecasting, purchasing/reorder action, price/discount or liquidation recommendation, accounting valuation/write-down opinion, tax/legal advice, product deletion, customer/supplier contact or source-system writeback.

For service businesses, agencies and B2B sellers that already have reviewed source-period funnel totals but still reconcile inquiry, qualified-lead, win, supplied-revenue and channel-cost figures manually. Up to 500 non-sensitive source-period rows in one currency.

Use native reporting first: if HubSpot, your CRM, ad stack or analytics platform already provides the source/funnel view you need with acceptable review effort, use it. This pilot is for a remaining reviewed-export/reconciliation gap, not a replacement for native attribution or traffic-source reporting.

Scope: one agreed source-label convention and period basis with non-negative supplied inquiries, qualified leads, wins, revenue and channel cost. Impossible funnel counts are held for review rather than repaired by assumption. No contact names, email addresses, click-level histories or ad-account credentials are required.

Output: source-labelled counts, supplied revenue/cost totals and descriptive funnel conversion rates where the required denominator exists. A source label describes the customer’s supplied grouping; it does not prove that source caused a lead, win or revenue outcome.

Excluded: causal or multi-touch attribution, ROI/ROAS claims, LTV or pipeline forecast, ad-platform access, campaign optimization, marketing recommendation, salesperson ranking, customer profiling, revenue guarantee or CRM/ad-system writeback.

For memberships, subscriptions and recurring-service businesses that already have a reviewed account-status export but still reconcile active, paused and cancelled accounts manually. Up to 500 anonymous recurring-account rows in one currency.

Use native reporting first: if Shopify Subscriptions, your billing platform, membership system or CRM already gives you the active/paused/cancelled and recurring-value view you need, use it. This pilot is for a remaining reviewed-export/reconciliation gap.

Scope: stable anonymous account IDs with supplied start/end dates, reviewed status and supplied monthly amount on one consistent basis. Impossible end-date/status chronology is held for review rather than repaired by assumption. No customer names, contact details, payment credentials or cancellation reasons are required.

Output: active, paused and cancelled counts, tenure from supplied dates, and monthly-value totals from the amounts you provide. The snapshot describes the reviewed export; it does not predict churn, explain why customers left or estimate lifetime value.

Excluded: churn prediction, retention scoring or outreach, LTV or revenue forecast, cancellation-reason inference, cohort-causality claims, customer contact, subscription cancellation/resume, billing action or system writeback.

For contractors, estimators, agencies and B2B service teams that already have a reviewed quote-outcome export but still need a bounded cross-period view of supplied quote status, value and decision timing. One reviewed, non-sensitive CSV of up to 500 anonymous quote rows in one currency and one agreed reporting period/basis.

Use native quote reporting first: Housecall Pro already reports open, won and lost estimate counts/values and conversion rate, while Jobber provides quote status and conversion reporting. If your field-service, CRM or CPQ system already answers the question with acceptable review effort, use it instead. This pilot is for a remaining reviewed-export/reconciliation gap.

Scope: stable anonymous quote ID, real created date, customer-reviewed won/lost/open status, plain non-negative quote amount, one currency, optional decision date and optional customer-supplied loss-reason label. Closed won/lost rows require valid decision-date evidence. Duplicate IDs, mixed currencies, formatted/invalid amounts, impossible/future chronology, decision dates before creation and status/date contradictions are held rather than repaired or reclassified by assumption.

Output: accepted/held source-row reconciliation, supplied won/lost/open counts and quoted-value totals, decided win rate only across accepted closed won/lost rows, amount-weighted decided win rate only where the accepted closed quoted-value denominator is greater than zero, open quoted value, median supplied decision days only where valid closed decision dates exist, and frequency counts only for loss reasons the customer actually supplied. Missing reasons remain unknown rather than inferred.

Excluded: causal sales diagnosis, forecasted win probability, salesperson ranking, inferred loss reasons, recovered-revenue or likely-to-close claims, pricing/discount recommendations, customer contact, account access or CRM/CPQ writeback.

For B2B service, agency, wholesale and recurring-revenue businesses that already have a reviewed customer-sales export but still need a bounded dependency view outside native reporting. One reviewed, non-sensitive CSV of up to 1,000 anonymous customer-period rows in one currency and one agreed reporting scope.

Use native reporting first: QuickBooks Online already provides Sales by Customer Summary/Detail reporting, and your CRM or accounting platform may already answer the concentration question with acceptable review effort. If it does, use that instead. This pilot is for a remaining reviewed-export/reconciliation gap.

Scope: stable anonymous source-row and customer keys, an agreed period label/basis, supplied revenue amount and one three-letter currency. Customer names, contact details and message history are not required. Duplicate source rows, invalid or formatted amounts, mixed currencies and rows outside the agreed basis are held rather than silently repaired, converted or attributed.

Output: accepted/held source-row reconciliation, anonymous ranked customer totals, total supplied revenue and top-1/top-5/top-10 revenue share plus HHI only where the accepted supplied-revenue denominator is greater than zero. Zero-total or insufficient evidence remains explicit rather than producing an invented concentration percentage. The snapshot describes the supplied period only.

Excluded: credit decisions, customer termination or diversification recommendations, customer-health or churn inference, forecasts, valuation, profitability/LTV claims, accounting or tax opinion, customer contact, account access or CRM/accounting-system writeback.

For contractors, installers, fabrication shops and project/service teams that already have a reviewed job-status export but still need a bounded cross-job calendar cycle-time view. One reviewed, non-sensitive CSV of up to 500 anonymous jobs, one explicit as-of date and customer-supplied positive whole-number target days.

Use native job management first: Buildxact already tracks job status from the job schedule, exposes Not Started / In Progress / Complete views and provides Work in Progress reporting. If Buildxact, your field-service platform or current project system already answers the cycle-time question with acceptable review effort, use it instead. This pilot is for a remaining reviewed-export/reconciliation gap.

Scope: stable anonymous job ID, customer-reviewed open/complete status, real start date, optional completion date, explicit as-of date and owner-supplied target days. Completed jobs require a valid completion date. Duplicate IDs, impossible dates, completion before start, future supplied dates and status/date contradictions are held rather than repaired or reclassified by assumption.

Output: accepted/held source-row reconciliation, completed/open counts, completed cycle days from supplied start to completion dates, median completed cycle days only where valid completed rows exist, completed jobs above the supplied target, and open age from supplied start date to the as-of date with above-target flags. Missing or invalid evidence stays explicit; an open-job age is not a predicted completion time.

Excluded: employee/subcontractor evaluation, delay-cause inference, promised completion dates or ETA forecasts, productivity or blame conclusions, contract/liquidated-damages opinions, customer notification, schedule changes, account access or project-management-system writeback.

For wholesale, distribution, manufacturing and ecommerce operations that can already see which orders are open or partially fulfilled but still need a cross-export view of remaining quantity, proportional remaining line value, promised-date lateness and ageing. Up to 1,000 anonymous order lines plus one explicit as-of date.

Use native reporting first: Shopify and WooCommerce already expose unfulfilled or partially fulfilled order status. If that native view answers the business question, use it. This pilot is only for a remaining reconciliation/reporting gap across line-level quantities, values, promised dates or ageing.

Scope: anonymous order-line ID and order ID, order date, optional promised date, ordered and fulfilled quantities, line value and one currency. Fulfilled quantity cannot exceed ordered quantity; duplicate line IDs, mixed currencies and impossible chronology are held for correction.

Output: open-line count, remaining quantity, proportional open value, 0–7 / 8–30 / 31–60 / 61+ day ageing buckets, and late-open count/rate only across open lines that actually include a supplied promised date.

Excluded: inventory-availability promises, shipment action, customer notification, cancellation, demand forecasting, accounting recognition, order-system write-back or a claim that an unfulfilled order is late when no promised date was supplied.