Answers
Straight answers to what you are already wondering.
What SalesSynq is, what it costs, what it refuses to do, and where its limits are — in plain language, kept current.
SalesSynq spots at-risk deals early and tells your team exactly what to do next — and shows you the evidence behind every call it makes. This page answers what buyers actually ask: what it does, what it costs, what it reads, how it handles your data and your AI review, and what SalesSynq refuses to claim about itself.
You should not have to find out in the QBR.
Every question below came from someone who had already been surprised by their own pipeline at least once, and wanted to know whether this would stop it happening again. Answers are plain, including the ones where the answer is that we have not built it yet.
What is the one-sentence version?
SalesSynq spots at-risk deals early and tells your team exactly what to do next.
Everything below is an expansion of that sentence, or a limit on it. There are 42 answers here, grouped by what you are trying to find out, and the last section lists the things we will not say about ourselves. If your question is missing, ask — the ones that keep coming up end up on this page.
- 1
Connect your CRM
Read-only, in a few minutes — or upload an export and skip the credential entirely. Nothing in your CRM changes either way.
- 2
See what is actually at risk
Every deal weighed against the evidence behind it, not the stage it claims. Where the evidence is too thin, you are told so rather than guessed at.
- 3
Act while it still matters
The deal owner gets the specific next move on the deals that need one, with the evidence attached so the conversation starts at the second question.
Skip all of it and the pattern repeats. The forecast holds all quarter, then moves in the last two weeks. You get asked why in the board meeting and the honest answer is that you did not know.
Change it and the quarter feels different. Pipeline reviews stop being a guessing game. You walk into the board meeting already knowing which deals move the number.
SalesSynq is in private beta and invite-only, with general availability targeted for Q3 2026. You can still run a pipeline audit from a file today, without product access and without giving anyone a credential.
What is SalesSynq, and is it for me?
SalesSynq spots at-risk deals early and tells your team exactly what to do next. It reads your pipeline from your CRM or an export, weighs every open deal against the evidence behind it rather than the stage it claims, and shows you what it looked at. You never have to take a score on faith — you can open it and check it.
Deals slip quietly. The champion stops replying, the delivery date moves, the renewal goes cold — and the CRM still says the stage is fine, so nobody looks until the review. Around $2 trillion is lost every year to revenue leakage across go-to-market motions. Source: Boston Consulting Group, 2022. Almost none of it arrives as a bad forecast. It arrives as a number nobody could take apart in time to act on it.
Revenue leaders, RevOps and sales managers in mid-market B2B teams who have to defend a number to a board — and the security, legal and privacy reviewers who have to approve the tool that produced it. If "the model says so" would not survive a follow-up question in your business, this was built for you.
Pipeline reviews stop being a guessing game: every deal arrives with the evidence behind it, so the argument is about the deal instead of the data. Your team spends its week on the deals where the week still matters. And you walk into the board meeting already knowing which deals move the number, and what was done about them.
No, and you should not want it to be. It sits beside your CRM and reads from it. Your reps keep working where they already work, your system of record stays the system of record, and SalesSynq does not write to your CRM records. If you came looking to replace a CRM, we will tell you on the first call that this is not that.
One read on where a deal actually stands, based on the evidence behind it rather than the stage it sits in. One click shows you exactly what SalesSynq looked at to get there. The same evidence always gives the same answer. Its correctness certificate is checked whenever the score is served; if that certificate fails, the numeric score and components are withheld.
Partly, and the split is the whole design. Ordinary code makes every decision and every number, which is why the same evidence always gives the same answer. AI only writes the sentence explaining a decision already made, tied to that exact decision so the explanation cannot drift from it. AI stays off until you switch it on, one workflow at a time.
How does it work, and can I trust the number?
Ordinary code, running against the evidence captured at the moment of scoring. There is no language model in that path and no training step on your history. A test that breaks the build enforces it: the same evidence must produce the same score, or nothing ships. That is what lets you re-run a score in front of a sceptical colleague and get the same answer.
Yes, and it takes one click. Every score opens onto what SalesSynq accepted as evidence, the rules in force when it looked, and the answer it reached. It can be recomputed in front of you and compared against what was stored. A number you can check is a number you can defend in a room full of people who would rather it were wrong.
The Synq Score and the risk reads behind it, against the evidence captured at the time. It does not stretch to every signal in the raw feed, and it does not cover early warnings. The claim is kept narrow on purpose, because the narrow version is the one that survives being tested by your own team.
Nothing is published. When the evidence is too thin, SalesSynq tells you it does not know instead of guessing — and shows you what it could not see. There is no neutral-looking placeholder and no score assembled out of two weak signals. A fake middling number is worse than a blank one, because you cannot argue with it and you cannot act on it either.
On a list of what SalesSynq will not guess at, and why — in the main view, not behind an upgrade. Being told where your evidence runs out is not a premium feature. We describe that list in words rather than percentages, because a high refusal rate would not prove quality either.
No. It tells you what the current evidence supports about where a deal stands and which way it is moving. It is not a percentage, and SalesSynq publishes no accuracy statistics for it. A tool that hands you a number and cannot show you how it got there has given you a feeling with a decimal point on it.
A low, mid and high scenario for the quarter that anyone can reproduce, broken out by bucket, with the swing deals and the missing inputs named. It is a sensitivity range recomputed from the same evidence — not a statistical prediction, and not built from your history. Two people running it on the same inputs get the same band, which is what makes it usable in a forecast call.
A read on who is actually involved in a deal: the roles people claim, set against the engagement you can observe, resolved into a plain state and one next relationship move. It is not an influence model and not a prediction. It tells you which part of the buying group went quiet — usually the thing you find out too late.
What does it connect to?
Your CRM (HubSpot, Zoho, Freshsales), your conversations (Slack, Teams, Gmail, Outlook, both calendars, Zoom, Gong), your delivery tools (Jira, Linear, GitHub) and your support desk (Zendesk, Freshdesk). Salesforce and spreadsheet data arrive as an export you upload. Pipedrive, ChurnZero and Trello are coming soon; upload an export from them in the meantime.
Not a connection — an upload. Export an opportunity report, upload it, and about ten minutes later you have a scored pipeline and a plain account of what your data could and could not support. You get the same picture; you refresh it by uploading again rather than automatically. We will not call that a connector, because you would find out in week three.
No. It is read-only by default and does not write to your CRM records — no field mapping pushes a value back the other way. The one thing it can send is a task into a work tool such as Jira or Slack, and that is a separate permission you grant per tool: refused until you grant it, and refused again the moment you revoke it. That is why the security review tends to be short.
Yes, and it is the sensible way to start. The pipeline audit runs entirely from a file: export your open deals, upload them, read what comes back. Nothing is installed, no credential is exchanged, and nothing is sent back into the system you exported from. You find out whether this is worth your time before you give it access to anything.
A plain account of what your export could and could not support: which fields arrived, which owners and accounts could not be matched, where stage and close date contradict each other, and every deal SalesSynq declined to score with the reason. It comes before any score, so you judge your data before you judge the output.
About ten minutes from a CRM login or one upload. The uncomfortable artifact — what your data can and cannot support — comes first, then the scored pipeline for everything that cleared the bar. Most teams find something in the first report that they were already half expecting and had no way to prove.
What does it cost, and can I buy it yet?
Plans are published on the pricing page with their seat, active-deal, connection and monthly signal limits, billed monthly or annually. The largest tier is quoted rather than listed. It is the same page everyone sees — no number is held back until a qualification call.
Not self-serve. SalesSynq is in private beta and invite-only, with general availability targeted for Q3 2026. You can request access, and you can run a pipeline audit from a file without product access at all — which is the only honest way to evaluate something you cannot yet simply buy.
There is a pipeline audit. Export your open deals, upload the file, and keep the scored pipeline and the data report whether or not the conversation goes anywhere. It is not a time-boxed trial of the whole product; it is a real answer about your own pipeline, from a file, without giving anyone access to your systems.
General availability is targeted for Q3 2026, and nobody is moved onto terms they have not agreed to. Pricing, availability and connection facts on this site are re-checked monthly, and the date at the foot of every page tells you when someone last looked at them.
What happens to our data?
Your data is loaded into your own workspace and scored there. Everyone else who touches it is listed publicly — infrastructure, AI providers, operational tooling, marketing analytics — with what each one handles. Where it is deployed and where it sits are a written answer you get before you sign anything, not a badge on a page.
No. The score comes from ordinary code rather than a model built on your history, so there is no training step to opt out of. Where AI drafts explanatory text, training on customer data is contractually excluded, and every path where free text can reach an AI provider is named in the published list rather than described in general terms.
Yes, and it is already published. The data processing agreement is a public page, as is the list of who else processes your data and the terms of service. Your privacy team can read all three, mark them up and come back with questions before anyone from SalesSynq has been in a meeting with them.
Yes. Your workspace and its contents can be removed on request, and there is a published route for data subject rights requests. The audit log is a separate matter: entries can be added but not edited afterwards, which is a different promise from retention. You get that in writing, per data type, before you sign.
We hold none today and will not imply otherwise. SOC 2 and ISO 27001 are evidence programmes in progress. What exists now is a published security overview, a data processing agreement, a published list of who else touches your data, and an audit log that cannot be rewritten after the fact. Read those and judge, rather than taking a badge on trust.
How is the AI kept in its lane?
No. It stays off until you switch it on, one workflow at a time. That is a feature rather than a gap: your governance people can approve SalesSynq first, then decide separately how much AI they want inside each workflow. Nothing about the scoring depends on the AI being on at all.
It writes the sentence explaining a decision ordinary code has already made. Each sentence is tied to that exact decision, the figures it quotes come from the system rather than from the model, and anything consequential waits for a person to approve it. The AI never sets a score and cannot act on your behalf.
A public web address that returns a machine-readable description of the system: what it does, where AI is involved, where it is not, and which version of the policy is in force. Your reviewer can fetch it before the first call — no account, no NDA, no sales cycle. It is linked from the legal hub and the trust pages.
The same way on every page: a preliminary classification we made ourselves, a control map anchored in the code, and counsel review still pending. It is our own reading rather than a regulator’s finding, and the public disclosure reports that state plainly instead of implying a review that has not happened.
It does not store or use model-derived emotion, sentiment, tone or personality fields. Those fields are discarded, rejected at the database boundary and excluded from scores and recommended actions; no setting disables that control.
Decisions, and the material changes around them. Customer entries cannot be edited or deleted. Each workspace keeps its own chain. That lets you answer "why did it say that, back in March?" months later, in front of someone who is entitled to a real answer.
Can this be turned on our people?
No. SalesSynq publishes scores for deals and aggregate teams, never performance scores or rankings for named people. That is enforced in the product, not promised in a policy. The product refuses it in two separate places, and there is no setting, admin toggle or support ticket that turns it on. A policy is a sentence; a refusal built into the product is a wall, and only one of those survives a change of management.
Aggregate reporting suppresses groups below five by default. A workspace administrator may raise that threshold or lower it no further than two. Individual scorecards, rankings and performance metrics remain prohibited regardless of the aggregate threshold.
They can tighten every policy. The aggregate group threshold has a bounded range: five by default and no lower than two. Administrators cannot enable named-person scoring, rankings or performance metrics. That hard stop is what prevents the bounded group setting from turning into individual surveillance.
What are the limits?
Access is invite-only until general availability in Q3 2026. Checking a score against its evidence covers the Synq Score and the risk reads behind it, not early warnings. Salesforce is an upload rather than a connection. And SalesSynq will tell you it does not know more often than a tool that guesses — that is the trade you are making.
On architecture and approach, yes — there are comparison pages for the tools you are probably also evaluating. We also cite selected vendor-published customer outcomes as market context. We do not turn those figures into a SalesSynq result or superiority claim, because no controlled same-cohort comparison exists. Comparing your pipeline against other companies’ data is deliberately not served at all.
By the date at the foot of it. Availability, pricing and connection facts are re-checked monthly, and answers are rewritten when the product changes rather than left to age quietly. If you are about to quote something from here in a board paper, check that date first — that is what it is for.
What will SalesSynq not claim?
These are things we could say, that tools in this category do say, and that we cannot support. Publishing the list is unusual, which is exactly why it is useful to you: a vendor who tells you where the boundary sits can be checked against it, and a vendor who never mentions one cannot.
- That we are more accurate than any named competitor. No controlled same-customer, same-horizon comparison exists.
- A SalesSynq customer or internal performance result. The available generated certification corpus was authored to test deterministic separation, so it is not predictive evidence. Selected vendor-reported outcomes appear only as source-bound market context.
- Any comparison of your pipeline against other companies. It is deliberately not served, and the ability to do it was removed rather than hidden behind a setting.
- That SalesSynq writes into your CRM. It reads. Sending a task into a work tool is as far as it goes, and only on a permission you grant per tool.
- Uptime or capacity figures. We have not measured them under real load, so we do not publish them.
- Certification badges. SOC 2 and ISO 27001 are evidence programmes in progress; we hold neither today.
- That early warnings can be checked against their evidence the way a score can. That covers the Synq Score and the risk reads behind it, and no further.
- That the product has been shaped around your own history. Nothing is built per customer — you can raise its thresholds, you cannot teach it your habits.
- That a score proves business impact. It shows what SalesSynq saw and what it concluded from it, which is a smaller claim and a true one.
Nothing on this list is permanent. When one of them becomes defensible it moves off here and onto a product page with the evidence attached — and this page will say when it moved.
On compliance the wording is the same everywhere: a preliminary classification we made ourselves, a control map anchored in the code, and counsel review still pending. We describe ourselves as neither certified nor approved by anyone, because we are not.
Still holding a question this page did not answer?
Ask it and you will get a straight answer, including 'we have not built that yet'. Or stop reading about it and point it at your own deals — that is the faster way to find out.
Private beta is invite-only and requires approval. General availability targeted for Q3 2026.
Last updated . We refresh beta status, availability dates and integration status on a monthly sweep.