What the company does, where it serves, and what a visitor should do next.
Pain points · desired result · next step
Start with the business problem and the result you want.
Send the business situation, the pain points, the desired public website result, the preferred address, and where customer inquiries and email portal access should go. Do not send passwords in the first message.
Business facts
Domain target
Outcome target
Intake snapshot
First review
Useful without credential exposure
1
Business
What the company does, who it serves, and which pages the first site needs.
Needed
2
Domain
Preferred public address, current ownership status, and launch timing.
Defined
3
Contact flow
Where inquiries should go and who should receive the first messages.
Planned
4
Next step
Budget target, timeline, decision maker, and the first website milestone.
Ready
Leadsinquiry path
Emailportal path
Better first impression A real website, not an abandoned template.
Clear public address Customers know where to find the business.
Email portal included mail.yourdomain.com/login with 1,000 send/receive emails per month.
Website result intake
Send the pain point, desired result, and contact goal.
The contact page is intentionally short. The first message should frame the business, current website pain, desired result, preferred public address, pages needed, budget target, and timing without exposing credentials.
What feels unfinished, confusing, slow, untrusted, or hard for customers to use.
The public address, customer action, email portal, and contact expectations that should feel fixed.
What should the first intake message include?
Include the business name, service area, preferred public address, pages needed, contact flow, timeline, budget target, current domain status, and best next step.
Should private credentials be sent in the first email?
No. The first email should be enough to review scope without attaching registrar passwords, email passwords, private keys, billing credentials, or client records.
What happens after intake?
If the request fits, follow-up can confirm scope, ownership consent, web presence goals, contact flow, price, and the first milestone.
Pre-qualification basics
Send the facts that define the desired result.
The first message should make the review useful without attaching credentials. Keep it focused on the pain, the desired customer result, and the best next step.
Legal or public name, service area, phone, location, and primary customer type.
The domain wanted, current ownership status, and launch timing.
Pages, offers, photos, forms, service areas, and the first conversion goal.
Sender names, aliases, reply-to paths, forms, desired mail.yourdomain.com/login access, and where customer messages should land.
What is available now and what credentials, keys, client records, or sensitive details should wait for a safer follow-up step.
Target start date, monthly support expectation, and the best next milestone.
Managed presence intake
Email Premium Intake
Start with the pain, desired result, and customer contact path.
Send the basic situation, preferred public address, pages needed, timing, email portal needs, and who should receive inquiries. Do not send passwords in the first email.