Contact

Use the intake for scoped requests. Use email for routing questions.

The structured intake is the default path because it captures budget, risk signals, and the requested workflow lane in a format that can be reviewed consistently. Direct contact stays available when you need to confirm fit before starting intake.

Scoped request

Ready to be reviewed against scope, budget, and risk flags.

Use the structured intake when the workflow, owner, and requested lane are already concrete enough to review.

Start structured intake

Routing question

Need a quick fit check before you start the intake.

Use direct email for narrow routing questions only, not for open-ended consulting requests or proposal work.

Reply path:

hello@selfx.dev

Preferred path: intake first for quote requests. Commercial shape stays 30/ 40/30 milestone payments with a 30-day post-handover questions-only support window.

Direct email

Public contact stays narrow and explicit.

hello@selfx.dev: Primary direct contact and Cloudflare-routed inbox for new inquiries.
contact@selfx.dev: Secondary direct contact routed to the same owner review inbox.

What to use when

Routing stays simple before any proposal work starts.

Structured intake is the default path for quote requests and scope review.
Direct email is available for routing questions before intake.
Operator-only materials stay off the public site and are shared only after fit review.

If the request is already within scope, go directly to the intake flow.

The public site does not expose internal review templates, decline-response copy, held-back SOW materials, or other operator-only assets. Those remain private and are shared only when a request has passed initial fit review.