Fences

Intake

Tell us what you are trying to ship

Share a non-confidential summary. We respond by email with next steps and whether Fences is the right fit. If you prefer not to use the form, email us directly—same expectations apply.

Email [email protected]

Succinct takeaways

No confidential...

No confidential details required to start

Use the secure intake form below. For abuse resistance and delivery, the production environment should configure Cloudflare Pages secrets for email (for example Resend) or a webhook—see docs/deployment.md.

Source references

  1. Date: 2026-05-03 Status: Active architecture ## Purpose
FAQ
Frequently asked questions
Legacy legal delivery thrives on delay and context loss. This section does not.

We review non-confidential intakes and respond by email. If there is a fit, we describe next steps and how representation would be structured in writing.

Non-confidential first pass

Intake controls

No confidential facts yet
Channel Secure form (preferred) and email fallback
Routing Structured summary, matter type, and preferred work channel
Form fallback Use email if server path is unavailable
Contact [email protected]
Email intake Review disclaimer

Intake form

If the form cannot reach our servers (for example local dev without Cloudflare Functions), use email with the same fields in the body.

Use a short summary with enough context for Fences to route the inquiry and choose the right follow-up path.

Next action

Start the right intake.

Route the issue into a non-confidential first pass, then move the real case into the protected channel.

Email [email protected]