Tell us what is not working. Leave with a clear first conversation.
Project Intake is the deliberate path for preparing details you may choose to send to SCS for review. You do
not need a finished brief, and you can still ask one simple question without using a planning tool.
The builder prepares the request. You still control sending it.
This intake runs in the browser and opens your chosen email tool only when you choose. Your reply details,
draft, and first-touch source stay on this device until you copy, download, or open an email draft. Hosted submissions, uploads, payments,
booking, subscriptions, and accounts wait until their privacy and operating rules are ready.
Do SendPublic links, rough notes, screenshots, example sites, goals, and tool names.
Do Not SendPasswords, bank details, private API keys, or sensitive login codes by email.
AccessIf access is ever needed, use a safer temporary or permission-limited method.
ScopeThe first reply should narrow the request into one clear next build.
After You Send
The reply should make the project smaller and clearer.
You should not have to decode agency language or commit to a giant project just to get a useful answer.
01
We confirm the result
What should exist, who needs it, and what must version one accomplish?
02
We cut the extra weight
The first scope keeps the important work and names what should wait.
03
You get a clear next move
A suggested package, working range, missing pieces, and the next decision.
04
The project gets one record
Once work begins, milestones, messages, review files, approvals, decisions, and handoff stay together.
Keep sensitive details out of first-contact email.
Project Intake builds the draft on this device. Do not include passwords, payment details, private keys,
or login codes. Review the brief first, then choose what enters the email handoff.