Partnerships
Potential partnerships, channel relationships, or collaboration ideas that are not direct setup buyers.
Serious Inquiries
This page is for partnerships, larger private deployments, custom scope questions, and other serious inquiries that should not compete with Session 0.
Contact Route
Implementation buyers should still go through `/book`. `/contact` exists so nonstandard or higher-level inquiries get a serious route without muddying the core conversion path.
The route should be useful for serious inquiries that are not the same thing as buying a setup engagement right now.
Potential partnerships, channel relationships, or collaboration ideas that are not direct setup buyers.
More advanced deployment paths that likely need a broader conversation before a Session 0 route makes sense.
Nonstandard implementation questions that need a higher-level fit check first.
Serious public-facing inquiries that are not part of the implementation funnel.
Routing Guidance
The boundary between `/contact` and `/book` should stay explicit so the funnel does not blur.
The inquiry is nonstandard, exploratory at the business level, or not primarily about starting a setup engagement.
The buyer is trying to get OpenClaw planned, scoped, and deployed on a real implementation path.
Implementation Buyers
Buyers who are really trying to get OpenClaw planned and deployed should not be trapped in a generic contact loop.
The eventual form should make the inquiry type explicit so the response path is clearer from the first message.
Channel, agency, referral, or strategic fit conversations.
Larger-scope or more specialized deployment questions.
Interviews, podcast appearances, written features, or event-related outreach.
Qualified questions that do not fit the booking path but still need a real response.
Serious Inquiry Form Shell
This route stays intentionally lighter than `/book`, but still gathers enough signal to route a qualified nonstandard inquiry properly.
The route should help ClawFoundry triage qualified nonstandard inquiries without undermining the main implementation path.
Nonstandard opportunities get a cleaner path instead of being forced through the Session 0 funnel.
If the inquiry is really a setup engagement, the next step should still be the booking route.
This page should gather enough to triage the inquiry without becoming a second onboarding flow.
Support Route CTA
The support pages exist to reduce hesitation and clarify scope. The primary action remains the same: book Session 0, get the setup path defined, and move from interest to implementation.