Why the intake exists.

How scope is evaluated.

After submission, the scope of a possible audit is evaluated based on the workflow, and scope determines the tier and price where applicable. Scope is evaluated, not assumed.

• The number of decision points in the workflow.
• The complexity of those decisions.
• The number of systems involved.
• The degree of automation or AI involvement.
• The number of people or roles involved.
• The volume of decisions over time.
• The number of evidence sources.
• The complexity of the approval process.
• The complexity of exception handling.
• The state of existing records.
• The number of workflows in question.
• Whether the workflow spans teams.
• The availability of documentation.
• The clarity of ownership.
• The variability of the workflow.
• The presence of recurring exceptions.
• The degree of cross-system fragmentation.
• The depth of assessment requested.
• Any specific organizational requirements.
• Whether the engagement is Founder, Standard, or Enterprise in nature.

How readiness is evaluated.

Whether the workflow and organization are ready for a useful audit now, or whether some preparation would help first. An audit begins only after the process is complete.

• The workflow can be clearly described.
• The decision points are identifiable.
• The systems involved can be named.
• The people or roles involved are known.
• The evidence sources can be identified.
• The approval process can be described.
• The exception process can be described.
• Basic records exist to examine.
• A point of contact is available.
• The organization can allocate some time.
• The scope can be reasonably bounded.
• The relevant documents can be shared if needed.
• The workflow is stable enough to assess.
• The organization understands the deliverable.
• The organization understands it is an assessment.
• Expectations about timelines are realistic.
• Expectations about pricing are understood where applicable.
• The organization is ready for honest findings.
• The workflow is not mid-rebuild in a way that prevents assessment.
• The organization is ready to begin the process.

What happens after you submit.

1. Reviewed The submission is reviewed.
2. Conversation A conversation is arranged.
3. Evaluation Suitability, scope, and readiness are evaluated.
4. Scope Only if there is a good fit is an audit scoped and agreed.

Submitting does not guarantee acceptance, begin an audit, or create an engagement.

Preparing for an audit.

Practical help for a useful submission and a smooth process.

• Choose one bounded workflow to start.
• Describe what the workflow does plainly.
• List the main decision points.
• Note where AI or automation is used.
• Note where humans review or approve.
• Describe how approvals are recorded.
• Describe how exceptions are handled.
• Note where evidence is stored.
• Estimate how often decisions occur.
• Identify who owns the workflow.
• Gather any optional documents that help.
• Provide a clear point of contact.
• Be honest about current gaps.
• Avoid overstating maturity.
• Clarify what you want from the assessment.
• Understand the deliverable in advance.
• Understand this is an assessment, not a guarantee.
• Keep expectations about timelines realistic.
• Understand pricing depends on scope where applicable.
• Be ready for honest findings.

Honest trust signals.

Genuinely true for the intake, with no fabricated customers, success rates, or metrics.

• Whole process explained We explain the whole process before you submit.
• No audit begun We say plainly that submitting does not begin an audit.
• No engagement created We say plainly that submitting does not create an engagement.
• Honest evaluation We evaluate suitability, scope, and readiness honestly.
• We will decline a poor fit We would rather decline than take on a poor fit.
• Your information is private We keep your information private.
• Fictional public data We use fictional data in all public materials.
• Confidentiality on request We offer confidentiality terms on request.
• Assessments, not guarantees We are clear that audits are assessments, not guarantees.
• Opinions, not certifications We are clear that reports are opinions, not certifications.
• No timelines before scope We do not promise timelines before scope is known.
• No prices before scope We do not promise prices before scope is known.
• Founder involved The founder is directly involved.
• Early stage, openly We acknowledge our early stage openly.
• Inspectable materials We point to inspectable materials that explain our approach.