Prevoyance Universe

• Discover Define your target industries, locations, and business signals, then find prospects against the criteria you choose.
• Research Read business websites, identify contacts, and keep the evidence behind each prospect in view.
• Connect Draft tailored email sequences, approve messages in the outbox, and follow replies toward the next sales conversation.
• Control Administrator sign-in protects the workspace, with approval before sending, daily limits, and a pause control.

For Sales and business development teams building a researched, relevant prospecting pipeline.

• Scheduling Two panes to book an interview. The candidate pool grouped by category on the left, the panel and the schedule on the right, and the link and key ready to copy the moment it exists.
• Identity Consent, photo identity document and a selfie before the room opens. Never an Aadhaar number, and the consent is recorded with its timestamp.
• The room Host admission from a waiting room, host only recording, screen sharing the host approves, and speaker attribution taken from each participant's own audio rather than guessed.
• The record Transcript, summary, decisions and a plan of action. Scoring is advisory and labelled as advisory. The interviewer's rating is the rating of record.

For Hiring panels, HR teams, and anyone who runs a session that has to stand up to being read back later.

• Reason codes Every approve, refer and decline carries an explicit reason code, so the question of why somebody was declined has a specific answer rather than an appeal to a model.
• Policy as configuration Credit policy is held as configuration rather than as code, so a change to a threshold is a change an operations team can make and review.
• Deterministic The same file and the same policy produce the same decision. A result that cannot be reproduced cannot be defended to a regulator.

For Credit and risk teams running retail lending origination.

• Planned ahead The collection programme is laid out before the peak rather than absorbed during it, so field capacity is known in advance.
• Captured at the doorstep Money is recorded digitally where it is collected, which is what makes the closure position true on the day rather than at reconciliation.
• Closed properly Closure runs through to the released document and the record that it went out, because a loan marked closed with nothing released is not closed.

For Lending operations running collection and closure across a book.

• Registry checks Documents are checked against the registries that issued them rather than accepted because they look right.
• Triangulation One document is read against the others in the file, so a discrepancy surfaces as a discrepancy instead of passing as two separate facts.
• Custody Tamper evident storage with controlled access, and a full trail of every artefact held.

For Bank lending departments and their document and compliance teams.

• Eligibility The tender is read against what the company can evidence, and each criterion returns a verdict rather than a score: met, needs a consortium partner, or to be confirmed.
• The pack Pre-bid queries, covering letter, scope document, technical approach, compliance matrix, costing workbook and partner proposal.
• House standard Documents come out in the company standard: the letterhead, the running reference, the typeface and the filename convention, without anyone reformatting them by hand.

For The sales and strategy team, internal use only.

• Pipeline Leads by stage, product, sector and owner, with expected value, next action and close date. Every count on a screen is the count of the records behind it, and a filtered list reports the total of what it filtered.
• People and companies Named individuals at prospect organisations, the account each belongs to, and the activity recorded against every lead. Deleting a contact that still has leads is refused rather than taking the pipeline with it.
• Mail and import Outbound send through the configured relay and inbound polling, threaded against the lead. Spreadsheets are previewed before they are committed, and the imported and skipped counts are reported against the preview total.
• Masked by default Email addresses and telephone numbers are masked on the way out of the API, not in the browser. Reading one in the clear is a separate request that states a reason and writes an audit record holding the reason, never the value.

For The Prevoyance sales team, and the account owners who work the pipeline with them.

• Portfolio and charters A portfolio of projects under one governed root, each with a versioned charter spine that decides which action a node may take.
• Orchestration Human and AI teams arranged as a recursive spine of orchestrators and leaf agents, with delegations, dependencies and peer coordination.
• Economics Planned, reserved and actual money, time and resources, rolled up exactly from the delivery records beneath each node.
• Evidence Reports, escalations and execution records are append only, so a step can always be read back to who did it and when.

For Delivery leads and sponsors who run product work as a governed, auditable pipeline.

• Evidence Import security-audit findings and coverage records, with confirmed issues kept separate from items that still need validation.
• Reports Create a visual technical report, a PDF, or a reviewed 20-second video summary with Brag and Hyperframes.
• Workspaces Keep projects and remediation tracking in account-isolated workspaces, with internal access and administrator invitations.

For Internal audit teams, project owners, and client engagements. Audit execution currently runs in Codex; its results are imported into PreCheck.