1. Technology CRM
  2. Features
  3. Technical evaluations
Feature · Technical evaluations

Technical evaluations

Review the evaluation environment, trial end, active seats and security evidence alongside the sales opportunity.

OverviewEvaluation Review Inbox
Technology CRM · Technical evaluations

Evaluation Review Inbox

Approval conditions

New
IdParentEnvironmentTrial endsActive seatsSecurity review
IDD-735OPP-41604ENV-22410 Oct860SR-980
IDD-968OPP-20364ENV-51908 Oct320SR-464
IDD-859OPP-72002ENV-32808 Oct330SR-421
IDD-393OPP-41385ENV-98308 Oct420SR-263
IDD-597OPP-43144ENV-91222 Oct380SR-504
6 of 6 records
IDD-735Technical evaluations · TE-48626
Submitted
ParentOPP-41604
EnvironmentENV-224
Trial ends10 Oct
Active seats860
Security reviewSR-980
Example screen with sample data

What you can do

Give the evaluation outcome a clear basis

A technology sale may need a trial or technical evaluation before the customer can decide. Relationship Owner records the evaluation environment, trial end date, active seats and security review against the opportunity. Those details give Sales Manager a defined evidence set to inspect when the evaluation is submitted.

The evaluation has its own revision and status. Draft work becomes Submitted for review, and approved evaluation work can proceed to Completed. This lifecycle describes the evaluation decision. The opportunity remains responsible for its separate commercial stage and eventual Won or Lost outcome.

How the work is organized

  • Evaluation context. Relationship Owner describes the environment and records the trial end. Active seats and the security review provide further context for the evaluation discussion. Agree how those observations are collected before treating them as decision evidence.
  • Independent decision. Sales Manager reviews the submitted revision and can approve, reject or return the work. The decision needs to apply to the evidence actually submitted. Changed evaluation content requires the appropriate correction and renewed review.
  • Controlled completion. Only approved evaluation work proceeds to Completed. The operation history records the actions taken against the evaluation, so the team can distinguish a submitted trial from an outcome that has been independently reviewed.

What to agree during setup

Define what the environment description should identify and what the team means by an active seat. Agree who provides the seat observation and the security review information. A written security assessment should identify the evidence and conclusion relevant to the customer; agree how the findings support the evaluation decision.

Decide the trial end interpretation using the operating time zone and the customer’s evaluation plan. Agree what supports approval and what a Return must explain to Relationship Owner. If trial information comes from a product or technical system, configure that connection during implementation and make its observation timing clear to the reviewer.

Check the handoff on an actual case

Rehearse a platform evaluation in a customer’s test environment. Relationship Owner records the planned trial end, observed active seats and the customer’s security review response. Submit the current revision with the supporting opportunity files available to Sales Manager.

Have the reviewer return the evaluation because the security explanation needs clarification. Correct the evidence and submit it through the agreed review path. Then approve the corrected revision and complete the evaluation. Attempt completion of a different, unapproved revision and confirm that it cannot proceed. Finally, inspect the opportunity: completing the evaluation must not itself record customer acceptance or change the opportunity to Won.

What your team sees

  • Evaluation Review Inbox — Submitted evaluations waiting for an independent decision.
  • Trials Ending — Open evaluations whose trial end falls within a week or has already passed.
  • Evaluation Progress Board — Evaluation progress from Draft through reviewed completion.

Follow the work through

Run technical evaluation review, then continue the commercial discussion through proposal and negotiation.

What it keeps track of

Data model
Technical evaluations
Technical evaluation records supporting a recorded evaluation outcome.
Opportunities
Sales opportunities with lifecycle, expected value and expected close date.
Organizations
Operating organizations that own accounts, opportunities and team membership.
Record attachments
Evidence files attached to an opportunity with visibility scope.
Operation receipts
Durable receipts for guarded operations with stable operation keys.

Who uses it

Permissions
Relationship Owner
, Sales Manager, Auditor.
Relationship Owner
Prepares the evaluation evidence, Sales Manager independently decides it, and Auditor follows the recorded actions.

Set up Technology CRM your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started