Is there a separate enterprise version?

No. Assessments, scoring and reports are the same on every plan. Enterprise changes the seats, the answer allowance, the contract and who you talk to.

How long is candidate data kept?

As long as the retention period you set, then the record is anonymised. Where data is processed, and by whom, is answered in writing during your security review.

Can we run a pilot before signing?

Yes. Run it on a self-serve plan with a real role. It is the same product, so you evaluate what you would buy.

What does the account manager do?

Sets up the first assessments with your team, answers the questions security and procurement send, and stays the person you write to afterwards.

For enterprise

Skills tests for enterprise.

No cap on people or answers, a service level written into the contract, and a named account manager. Your review gets its answers in writing.

Create my assessment Talk to us

Free to pilot, no card
Price quoted to your volume
Same product as every plan

Consent and privacy

Consent records1,248Stored with each submission
Access requests3Answered with a data package
Deletion requests1Anonymised, not hidden
Retention12 monthsRecords expire on their own

Example data. Privacy controls are on every plan.

What it replaces

An evaluation that starts with a demo, and one that starts with your security and privacy review.

Demo first

Vendor demo
Feature spreadsheet
Security questionnaire, late
Legal review, later
Pilot on a product nobody reviewed

Review first

Security and legal answered in writing
Pilot on the same product every plan runs
Contract with the service level in it
Rollout with a named account manager

There is no separate enterprise build to review. The pilot runs on the product you would buy.

How an enterprise rollout works

A pilot on the same product, your review answered in writing, then the contract.

1
Run a pilot on a self-serve plan
Send a real role's assessment to real candidates. Assessments, scoring and reports are the same on every plan.
1
app.assessly.app/submissions
Walk us through how you would plan the first month of this role.
Sofia MendesConcrete plan, names the risks91
Omar HaddadGood plan, vague on priorities77
Lena FischerLists tasks, no order64
2
Send us your security and privacy questions
Data handling, retention, consent and roles are answered in writing before you sign.
2
Your security questionnaire
- Consent recorded per submissionAnswered
- Retention period you setAnswered
- Candidate data package on requestAnswered
- Deletion by anonymisationAnswered
3
Sign, then roll out with a named contact
The service level goes into the contract. Your account manager sets up the first assessments with your team and stays your contact.
3
app.assessly.app/settings/team
Team members
No seat cap
Hiring operationsAdmin
RecruitersEditor
Hiring managersViewer

Example data. The candidates and answers are invented.

What your review will ask, and the answer

The questions security, legal and procurement send, and what in the product answers each one.

What they ask: Security wants to know who can see and change what.
What we answer: Admin, editor and viewer roles, enforced in the database. A viewer can read answers but cannot change an assessment or invite anyone.
What they ask: Legal asks what happens to candidate data, and for how long.
What we answer: Consent is stored with each submission. You set a retention period, records expire on their own, and deletion anonymises the record.
What they ask: Procurement needs a contract and a named person, not a card.
What we answer: A service level written into the agreement, a price quoted to your volume, and an account manager whose job includes your account.
What they ask: We run hiring in an ATS and will not copy results by hand.
What we answer: A read API returns assessments and submissions, and webhooks notify your systems when a submission arrives or is completed.

An integrity report on every answer

Language patterns, typing rhythm, timing and consistency, read together and shown to the reviewer. Signals for a person to weigh, never an automatic rejection.

Full Stack Developer, example

8 questions analysed

OverallHigh risk

AI language patterns
68/100
Turns of phrase and structure typical of generated text
Typing anomalies
3found
Stretches where the rhythm does not match a person writing
Consistency across answers
72/100
Quality and voice too even from one answer to the next
Predictability of the text
65/100
How closely each word follows from the ones before it

What it flagged

Strong AI language patterns detected (score: 68/100)
Unnatural consistency across responses (score: 72/100)
Low perplexity detected - text appears highly predictable
3 instant complete answers detected (likely pasted)
Minimal editing detected: 62% of answers had suspiciously few corrections
3 typing pattern anomalies detected

What we would do with this

Read the answers. Then ask one of these questions again in a call and listen for the same reasoning. A report is a reason to look closer, and it is never a reason on its own to turn someone down.

The scores above are invented. The risk level and the wording of every flag are produced by running the scoring Assessly itself uses on them, so this page changes when the product does.

What the Enterprise plan changes

Read from the plan features the product enforces. The service level is agreed in your contract, not published as a percentage.

What this plan switches on

Roles, so a viewer cannot editSwitched on here
Your logo and colours on what the candidate seesSwitched on here
Analytics beyond the basicsSwitched on here
Priority supportSwitched on here
Single sign-onSwitched on here
A named account managerSwitched on here
A service level agreement, written into the contractSwitched on here

What a security review will find

What a security or privacy questionnaire asks about, as the product works today. Anything not listed, ask, and the answer comes in writing.

Consent, recorded per submission
When consent is on, each submission stores what the candidate agreed to and when, in their language.
Retention and deletion
Set a retention period and records expire on their own. Deletion anonymises the record rather than hiding it.
A copy of the candidate's data
A candidate can receive a package of everything held about them, the request a privacy team gets most often.
Roles inside the account
Admin, editor and viewer, enforced in the database rather than only in the interface.
A read API and webhooks
Read assessments and submissions from your systems, and receive a webhook when a submission arrives.
The service level, in the contract
Agreed with you and written into the agreement, not a percentage printed on a page.

The same catalog every plan uses

There is no separate enterprise build. These are real templates from the catalog, the same ones a two-person team sends.

See all assessments

Common questions

Did not find your question? Write to us

Is there a separate enterprise version?
No. Assessments, scoring and reports are the same on every plan. Enterprise changes the seats, the answer allowance, the contract and who you talk to.
How long is candidate data kept?
As long as the retention period you set, then the record is anonymised. Where data is processed, and by whom, is answered in writing during your security review.
Can we run a pilot before signing?
Yes. Run it on a self-serve plan with a real role. It is the same product, so you evaluate what you would buy.
What does the account manager do?
Sets up the first assessments with your team, answers the questions security and procurement send, and stays the person you write to afterwards.

Start a pilot, and send us your review questions

Run a real role on a self-serve plan while we answer your security, privacy and contract questions in writing.