Guided submission · sheilastudios.com

Structured intake for technical work that needs a real review path.

This form is designed to capture enough context for routing and first-pass technical review without asking for sensitive access up front. Our team typically reviews intakes within 24 hours and sends a confirmation link by email.

Phase 1

Primary contact

Phase 2

Scope and urgency

Phase 3

Technical context

Primary contact

Who should we follow up with?

Helps us route the intake cleanly and send the confirmation link to the right person.

Name Email

Company / project name Preferred contact method

Project scope

What kind of help do you need?

Helps us assign the right review path and distinguish immediate debugging from research or investigation work.

Service type Urgency level

Business impact A short sentence is enough if that is all you have right now.

Technical context

Give us the best bounded technical picture you can.

This is the part that usually makes the review queue materially better.

Problem summary What is happening, what should be happening, and what changed if you know. Stack / platform / context Helps us assign the right specialist and understand where the seam might be. Safe links / artifacts, if available Optional. Useful examples: error logs, Loom repro, repo path, architecture notes, trace links. If you do not have safe artifacts yet, a strong written summary is still enough to start.

Security directive

Do not send passwords, private keys, seed phrases, or broad production credentials. Sensitive data exchange happens later through narrower, audited channels if the work moves forward.

Back to landing page