How the AI proves itself

An AI that tells you
what it will not do.

Most tools like this fail one of two ways: they bury you, or they get the data somewhere you would rather not explain. We built against both.

Where every answer comes from

  • Company newsrooms, filings, investor material, earnings calls
  • Employer careers pages and public job boards
  • Funding databases, regulatory registers, trade press
  • Public pricing and product pages, compared over time

Every single card names its sources. If you cannot trace it, we do not send it.

What we will never do

  • Scrape LinkedIn or anything a platform forbids
  • Buy personal contact data - enrichment stays your own step
  • Guess things about a person they never made public
  • Score anything in secret, or hide what we held back

You can open the withheld list any time and see exactly what you were not shown.

The source classes

Ten kinds of document, every one of them checkable

Nine credible classes plus your own material, indexed together so one question reads all of it at once. Every one is a document you can open yourself.

Company newsroomFunding databaseAggregated job boardsEarnings call transcriptRegulatory registerInvestor presentationYour own account notesTrade pressPartner directoryConference programme
Key takeaway

Every single card names its sources. If you cannot trace it, we do not send it.

What was held back

The withheld list is part of the product

Anything that did not clear the bar is still readable, with the reason it was dropped attached. Silence is never unexplained.

1,522

Collected

Your whole market, researched in full.

120

Deduplicated

The same event told twelve ways becomes one story.

20

Shortlisted

Scored on trigger strength, source weight and recency.

7

Sent

Cross-checked against a second source, then written up.

Security & access

How the product itself is locked down

Who can sign in?
Named people only. There is no self-service sign-up: an account has to exist on the allowlist before Microsoft will hand it a session, and admins add or remove people from the console.
How is sign-in handled?
Microsoft Entra ID, single-tenant, over OpenID Connect. QuikSignal never sees or stores a password, and every sign-in and role change is written to an audit log.
What is kept, and where?
The signals, their sources and your workspace configuration, in a managed Postgres database. Session tokens are short-lived and scoped to the browser that signed in.
Can we bring our own sources?
On Enterprise, yes - your private material is indexed alongside the credible public classes and is never used outside your workspace.

Read the sources yourself

Every claim in your first brief opens the document it came from.