Contact

Start with the issue, even if the right support shape is not clear yet.

Use Contact when a live AI, governance, security, review, responsibility, or operating-design issue needs clearer structure, or when you need help choosing the right support shape.

You do not need a polished brief. A short description is enough, especially when the issue still mixes scope, review, responsibility, operating boundaries, or management-facing explanation needs.

Choosing the inquiry type

Choose the closest path. It does not need to be perfect.

The form is designed to accept both clear inquiries and unresolved situations. If the issue is live but still hard to classify, choose service fit / unsure where to start.

Service fit / unsure where to start

Use this when the issue is real, but the right starting point is not clear yet. A short description is enough to decide whether the next step should be a Structuring Session, Focused Project, Advisory Support, or another path.

Structuring Session

Use this when the issue is still mixed and needs a focused first step to clarify the actual blockage, decision points, review questions, responsibility assumptions, and recommended next move.

Focused Project / AI Governance Sprint

Use this when an active AI adoption, governance, security, or operating-design issue needs a bounded sprint to produce decision-ready material, review logic, responsibility boundaries, requirement framing, or management-facing explanation.

Advisory Support

Use this when new questions keep appearing and the work needs recurring interpretation, review, and judgment support without becoming always-on execution coverage.

Helpful starting inputs

What is happening now

Why it matters

What feels blocked, mixed, or unclear

What needs to be decided, reviewed, owned, explained, or made workable

Other inquiry types

These are available for product or studio-related questions, but they are separate from direct advisory support.

Product support

Refund request

Team or internal use

Workshop or speaking inquiry

Inquiry form

Send an inquiry

Select the closest inquiry type and describe the issue in plain language. If the issue is still mixed, use the service-fit option and explain what is happening now.

Main service paths

Structuring Session

Focused Project / AI Governance Sprint

Advisory Support

Loading contact form…

Before you send

The first inquiry only needs to make the situation understandable.

The initial message is not expected to resolve the scope. Its job is to make the current situation, uncertainty, and possible support need clear enough to decide whether there is a fit.

You do not need a polished brief

A few lines are enough if they explain what is happening, why it matters, and what feels unclear, difficult to review, or difficult to carry.

The support shape can be adjusted later

Choose the closest inquiry type. If the selected type is not the best fit, the first response can help route it into the right support shape.

This is not a request for open-ended execution coverage

If the primary need is staff augmentation, always-on PMO coverage, or broad execution labor, this may not be the right path. If the need is clearer structure, review, responsibility, or decision support, Contact is appropriate.

Direct support and product support are different paths

Use Contact for service-fit questions and direct support inquiries. Use Support-related inquiry types for delivery, file access, refunds, or product-use issues.

Not sure where to start?

Use Contact when describing the issue is easier than naming the exact path.

If the issue is already active, Contact is a good direct starting point. Services can help clarify the support shapes first. Cases can help you recognize whether the situation is close. Support is better for delivery, file access, or refund handling. Knowledge may help when a reusable product is enough before direct support is needed.

Related paths

Related pages

Services

Go to Services to compare Structuring Session, Focused Project / AI Governance Sprint, and Advisory Support as direct support shapes.

Cases

Go to Cases to recognize representative situations before deciding whether your own context is close enough to discuss.

Support

Go to Support for delivery help, file-access issues, refund handling, and product-support boundaries.

Knowledge

Go to Knowledge for reusable products, working kits, and practical materials that may help before direct support is needed.