Contact

Initial contact can remain minimal.
Scope, field, timing, and routing requirements are sufficient at intake.

Contact Routes

One page. Three separate intake routes. Each route is designed for a different level of disclosure and a different type of material.

Discreet Inquiry

Initial contact with minimal disclosure for early-stage or sensitive requests.

OPEN ROUTE

Submit RFP

Structured intake for a defined requirement with clearer scope, timing, and output expectations.

OPEN ROUTE

File Upload

Supporting materials can be routed separately when disclosure is staged or when the file package stands on its own.

OPEN ROUTE

Discreet Inquiry

Sensitive detail does not need to be disclosed at first contact. Use this route when the need is still being defined, when exposure is not yet ready to be described in full, or when the field requires a single controlled point of intake.

Keep this route light. Only the minimum contact fields and a short note are required at launch.

Fields marked with * are required.

Turnstile placeholder: connect Cloudflare Turnstile here before launch.

Launch route: Cloudflare Pages Function for validation and email notification to the private inbox.

RFP / Intake Route

Use this route when the requirement is already defined enough to describe scope, field, timing, and expected output in a more structured way.

This form is intended for defined project requirements. Supporting files can be attached here, but larger packages may be better routed through the dedicated File Upload path.

Fields marked with * are required.

Front-end placeholder only at this stage. At deployment, this route can be connected to direct-to-R2 upload for multi-file intake.

Turnstile placeholder: connect Cloudflare Turnstile here before launch.

Launch route: structured intake, optional file handling, and email notification to the private inbox.

File Upload

Use this route when materials should be routed separately from the initial note, when disclosure is staged, or when the primary object of the submission is the file package itself.

Recommended launch behavior: direct browser upload to a private R2 bucket, then email notification with file references. Files remain stored until manually cleared.

Fields marked with * are required.

Recommended launch guardrails: up to 5 files per submission, business file types only, and direct-to-R2 upload for larger materials.

Turnstile placeholder: connect Cloudflare Turnstile here before launch.

Launch route: private R2 storage, manual clearance only, email notification to the private inbox, no public email address exposed on the site.

Contact Routes

Response within 24 business hours.