See what your pipeline export can support. One file.

Why does my pipeline look fine right up until it does not?

You should not have to find out in the QBR. A pipeline export shows what the CRM currently says. Before you rely on it, you need to know whether statuses agree with stages, whether close dates are usable, and whether open deals have the stakeholder coverage the next review assumes. SalesSynq spots at-risk deals early and tells your team exactly what to do next.

Left alone, that gap has a shape you will recognise. A slice of the pipeline sits past its own close date and still counts toward the number. Two rows for the same account quietly double a forecast. A renewal goes quiet and nobody notices until it is gone. Then the quarter lands short, and the post-mortem turns into an argument about whose spreadsheet was right.

One supported export can expose the structural gaps that make the pipeline hard to trust: conflicting statuses, close dates that are missing or already past, and deals with too little stakeholder coverage.

How do I audit my sales pipeline?

Three steps, from a file. No connector credential or CRM write access is required.

1. 1

   Export your open pipeline

   Export the records you want to review as a supported CSV or Excel file. Common deal columns can be previewed before any rows are applied.

2. 2

   Drop it into a private workspace

   Upload the file into a SalesSynq workspace that belongs to you. It only goes one way: nothing is sent back to the system you exported from, and no field, stage or owner is touched.

3. 3

   Review the structural audit

   Review status conflicts, missing or past close dates, stakeholder gaps, and Synq Score readiness. Checks that could not run are shown as unavailable rather than reported as zero.

What is actually in the report?

The report checks the structural state of the pipeline in your workspace and shows how much of the open pipeline already has a Synq Score.

• Status conflicts: deals whose status and stage disagree about whether the work is open or finished.
• Close-date hygiene: open deals with no close date or a close date that has already passed.
• Stakeholder coverage: open deals with no contacts or no budget holder named.
• Synq Score readiness: how many open deals have a score and examples of deals still warming up.
• Unavailable checks: any section that could not run is named instead of being shown as a fabricated zero.

Three things it deliberately will not do:

• It will not predict which deals will close or display a close probability in this report.
• It will not grade or rank reps. Named-worker scorecards and leaderboards are unavailable inside the product.
• If an individual check cannot run, it is named rather than shown as a zero.

What can I bring to the audit?

Bring a supported CSV or Excel export. SalesSynq previews the detected record type, columns, and sample rows before you apply anything.

A simple pipeline audit starts with deal rows. When a provider export spans related companies, contacts, deals, and activities, use its supported bundle format so those relationships can be imported in order.

And if you would rather not send a file at all, most of your stack connects directly and read-only instead:

Salesforce is import-only: use a supported export or bundle and confirm the preview before applying it. No Salesforce credential is exchanged and the file path cannot write back.

Can I trust the numbers it hands back?

The structural findings use exact counts from the data in your workspace. A check that cannot run is listed as unavailable rather than being turned into a zero or an all-clear.

When the evidence is too thin, SalesSynq tells you it does not know instead of guessing — and shows you what it could not see. Synq Score readiness is reported separately, so deals that are still warming up are not presented as though they already have a supported score.

What happens to the file I upload?

It goes into a private workspace that belongs to you and is audited there. It is never used to produce anything another customer sees, and you can have the workspace and everything in it removed on request. The audit only runs one way — it reads a file you exported, so there is no path back into the system it came from.

If your security reviewer wants to look before you send anything, they can. The AI control map is a public page they can read without an account, and the trust page walks through the audit trail, how AI is switched on per workflow, and the limits nobody can loosen.