Start a project
Tell me what the website needs to explain.
You do not need to choose a website stage or prepare a polished brief before you write. Send the facts you have; I will recommend the stage that fits—or tell you that none does.
Sending project details starts a conversation; it does not buy an audit, book a call, or commit you to a project.
You're about to see how every inquiry on a site I build is handled.
By handled, I mean every valid form inquiry the site accepts is recorded before the confirmation and numbered reference appear. The reference proves that recording. It does not prove inbox delivery or that anyone has read or acted on it.
Useful project facts
Include whatever is relevant. You do not need to turn it into a formal brief first.
- what the business does;
- the current website address, if there is one;
- what the current site gets wrong, leaves unclear, or leaves unfinished;
- the service or offer a prospect needs to understand;
- the next action the prospect should take;
- any real timing or dependency I should know about; and
- if a connection may matter, the website source and business system you have in mind.
For example: “We added two services. The website still shows the old business. Referred customers cannot tell which one fits.”
Do not include passwords, access keys, payment-card details, health information, or other sensitive records in this form.
Project details
Send the project facts
Three plain sentences are enough. Use the message field for the useful facts you have.
You do not have to diagnose the website first.
Send the business facts and the part that feels unfinished. I will not turn a simple one-page need into a complete build, or a working inbox into a connected project it does not need.
The useful first step is simply to send the facts. The scope comes after I understand the job.