01
Recommended default
Find Your Workflow Gaps
The company knows it has operational problems but does not yet know which workflow, system, or data issue should be addressed first.
Assessment guide
Choose the assessment that matches what the business already knows. If the underlying workflow or system problem is still unclear, start broad and narrow the implementation boundary through review.
Default first assessment
Use this when the company knows work is being missed, repeated, delayed, or manually reconciled but cannot yet identify the correct implementation boundary.
Start the assessmentQUESTION
Do you know which workflow is costing you the most?
NO
Find Your Workflow Gaps
Start broad enough to locate the real issue.
YES
Use a specific discovery assessment
Start with the known workflow or decision.
Assessment routing
These assessment types organise different diagnostic conversations. They do not assume that a particular product, platform, automation, or implementation scope is already the answer.
Recommended default
The company knows it has operational problems but does not yet know which workflow, system, or data issue should be addressed first.
A contractor needs to identify where invitations, estimates, documents, approvals, submissions, follow-ups, or handoffs lose control.
Explore RFQ readinessOne workflow has already been selected and its operating boundary can be described.
The main question is whether company information has the identity, source, permission, and quality controls required to support AI.
Explore AI readinessThe concern is repeated manual handling, duplication, delays, search effort, or unnecessary AI context usage.
Explore AI readinessReporting accuracy, management visibility, conflicting definitions, or source traceability are the primary problems.
The workflow is understood, but permissions, approvals, sensitive actions, risks, and failure handling need evaluation.
Problems span several departments, workflows, systems, locations, or shared management reporting definitions.
Complete comparison
The diagnostic assessments help a buyer understand the problem. The discovery assessments collect deeper operational and technical information after the implementation direction is qualified.
Overlap boundaries
Company profile, tools, sources, ownership, permissions, approvals, volume, and desired outcomes appear across several assessments. The depth and purpose of those questions should change with the assessment stage.
Short diagnosis identifying which workflow deserves attention.
Detailed operational and technical scoping after one workflow is selected.
Data quality, retrieval, metadata, citations, knowledge sources, and context efficiency.
Triggers, actions, permissions, failure recovery, approval gates, and action history.
Search time, duplication, rework, storage, processing, and manual verification.
Metric definitions, freshness, reconciliation, traceability, and decision confidence.
Intentionally overlaps because it examines shared records and workflows across the business.
Use after qualification, not as another casual public assessment.
Information boundary
A consistent company profile can be reused across assessments. Previously supplied company, contact, and tool information should be prefilled where the assessment platform permits it.
Required for useful diagnosis
15 fieldsOptional unless directly relevant
13 fieldsAccept only limited, redacted, authorised examples where a file materially improves diagnosis.
Portal credentials, secrets, access tokens, and unrestricted system access are not assessment inputs.
Require an appropriate NDA before requesting detailed operational information or implementation files.
After submission
Submitting an assessment begins a review process. It does not create a purchase commitment or automatically approve an implementation.
The respondent receives confirmation that the assessment was submitted.
A person reviews the complete submission rather than treating the answers as an automated purchase decision.
StructuredLayer examines workflow, systems, restrictions, volume, ownership, reporting, security, and desired outcomes.
Conflicting or incomplete answers are identified, and clarification may be requested through the business email provided.
Where there may be a fit, a call can confirm operational reality, authorised access, confidentiality, responsibilities, and implementation boundaries.
StructuredLayer determines whether the requirement is a focused workflow or a broader operating-layer problem before a separate scope is prepared.
Commercial boundary
Workflow assessment
If the exact implementation boundary is still unclear, the default assessment is designed to identify the workflow, information, ownership, and system questions that deserve closer review.