Mukha
Menu

Mukha

System Clarity Review Intake Form

This short questionnaire helps us understand the problem, define an appropriate review boundary, and determine whether a System Clarity Review is a good fit.

Brief answers are completely fine. If something is unknown, simply say "Unknown." Please do not include passwords, credentials, or sensitive data.

01

About you

Tell us who we'll be speaking with about the review.

Name and role are enough for now.

02

The problem

Give us enough context to understand what prompted the review.

Describe the issue in your own words. You do not need to diagnose the technical cause.

For example: internal applications, APIs, ERP systems, CMS platforms, databases, integrations, authentication systems, vendor products, or business workflows.

Examples include recurring failures, difficult maintenance, undocumented dependencies, a planned migration, vendor change, reliability concerns, technical debt, or a team transition.

Tell us about any deadline, migration, renewal, vendor decision, launch, staffing change, or other timing pressure.

03

Current system context

Tell us what is already known and what may be available for review.

Include any known architecture, technologies, integrations, vendors, dependencies, or major components. "Unknown" is completely acceptable.

This may be an internal team, technical owner, business owner, vendor, or a combination of people.

Examples: architecture diagrams, API documentation, repository documentation, deployment notes, vendor documentation, process documentation, support tickets, or very little reliable documentation.

What level of access could potentially be available for the review?

Select anything that may be available. We will confirm actual access requirements later if an engagement moves forward.

Please do not send passwords, credentials, access tokens, or sensitive files through this form.

Does the affected system involve sensitive or regulated information?

Examples include personal, financial, healthcare, student, payment, or other restricted information. A general answer is enough at this stage.

If so, briefly tell us what was tried and what happened.

04

Outcome and decision

Help us understand what a useful result would look like and who will act on the findings.

For example: understanding the current architecture, identifying dependencies or risks, preparing for a migration, evaluating an integration, prioritizing technical debt, or deciding what should happen next.

This may be you, a technical lead, business owner, leadership team, vendor, or another decision-maker.

What are you primarily looking for?

Examples include systems that cannot be changed, vendor restrictions, limited staff availability, security requirements, change freezes, regulatory requirements, budget limits, or fixed deadlines.

05

Timing and next steps

A few final details help us understand whether the engagement is ready to move forward.

Has funding been approved or identified for this work? *

An exact budget is not required at this stage.

Submitting this form does not create a consulting engagement or require either party to proceed. Please do not include passwords, credentials, or sensitive data.