Outcome
You will submit a clear website brief that can be reviewed without sharing credentials or forcing the implementation team to infer the business goal.
Navigation path
Custom Websites
Access
Project scope, availability, pricing, and delivery terms are confirmed after the live request is reviewed.
On this page
What you will accomplish
Goals
- State one primary website goal
- Identify useful features and references
- Submit and track a complete brief
Useful website brief
Goals guide features, and features guide project scope.
Audience
Primary goal
Required features
Content and brand
Reviewable brief
- AudiencePrimary goal
- Primary goalRequired features
- Required featuresContent and brand
- Content and brandReviewable brief
Before you start
Data, sources, and access to prepare
- Authority to request a project for the company or domain
- A known target audience
- A signed-in profile with current contact details
Prepare these details
- Identify the primary audience and conversion goal
- List required pages and workflows
- Record the current website and domain owner
- Gather inspiration links without sending account credentials
- Update your Profile contact information
Complete the task
- 1
Open Custom Websites
Main navigation > Custom Websites
Open the website request page.
Expected result: The brief form and request history load.
If this does not happen: Confirm the active workspace if prior requests are absent.
- 2
Name the project
Custom Websites > Project name
Enter one recognizable project name.
Expected result: The project can be identified in history.
If this does not happen: Use the company, market, or site purpose rather than a generic name.
- 3
Enter the current site
Custom Websites > Current website
Enter the current public website when one exists.
Expected result: The reviewer has current-state context.
If this does not happen: Leave it blank rather than entering a private administration URL.
- 4
Choose the project type
Custom Websites > What are you building?
Select one primary project type.
Expected result: The selected type appears in the brief.
If this does not happen: Choose the closest primary type and explain secondary needs in notes.
- 5
Choose the primary goal
Custom Websites > Primary goal
Select one main business goal.
Expected result: The request has a single prioritization anchor.
If this does not happen: Describe secondary goals in notes without changing the primary outcome.
- 6
Select one feature
Custom Websites > Features
Select one feature that directly supports the goal.
Expected result: The feature appears selected.
If this does not happen: Do not select a feature solely because it might be useful someday.
- 7
Add timing and inspiration
Custom Websites > Timing and references
Select the desired timing or enter one useful reference URL.
Expected result: The brief includes planning or visual context.
If this does not happen: Use only public reference URLs and treat timing as desired rather than guaranteed.
- 8
Write the required notes
Custom Websites > Anything else
Describe the audience, required pages, visual direction, and critical workflows.
Expected result: The notes satisfy the required field and clarify success.
If this does not happen: State unknowns openly instead of inventing technical requirements.
- 9
Submit the brief
Custom Websites form
Select Send website brief once.
Expected result: A confirmation names the submitted project.
If this does not happen: Keep the form open and retry once only after a clear failure.
- 10
Review request history
Custom Websites > Request history
Locate the submitted project row.
Expected result: The current review status is visible.
If this does not happen: Refresh after confirmation if history has not updated.
Website brief fields
| Field | Requirement | What it means | Format | Units | Save behavior | Downstream effect |
|---|---|---|---|---|---|---|
| Project name | Required | The request identifier | Plain text | Not applicable | Included in request history only after Send website brief succeeds. | Identifies the project in confirmation and review history. |
| Current website | Optional | Public context for an existing site | Public domain or URL | Not applicable | Stored with the brief after Send website brief succeeds. | Gives the reviewer public context for the current brand and site experience. |
| Project type | Required | The primary kind of website being requested | One option from the project-type control | Not applicable | Stored with the brief after Send website brief succeeds. | Defines the primary website category used to interpret the request. |
| Primary goal | Required | The single business outcome used to prioritize scope | One option from the primary-goal control | Not applicable | Stored with the brief after Send website brief succeeds. | Provides the main prioritization anchor for project review. |
| Features | Optional | Potential capabilities relevant to the goal | Selected feature options | Not applicable | Stored with the brief after Send website brief succeeds. | Records areas of interest for review; selection is not a final implementation commitment. |
| Notes | Required | Audience, market, pages, workflows, brand, and constraints | Plain text | Characters | Stored with the brief after Send website brief succeeds. | Supplies the detail used to evaluate scope and follow-up questions. |
Required means the field is needed to complete or support this workflow. Some screens allow a draft to save before every required item is complete. The steps and troubleshooting call out controls the product actively blocks.
Verify before you finish
- Project type and primary goal are selected
- Notes define the audience and required workflows
- No credentials or secrets are included
- Profile contact information is current
- Confirmation and request history show the brief
Troubleshooting and next steps
The form will not submit.
Likely cause: A required project name, project type, goal, or notes field may be missing.
- Read each inline error.
- Complete the named required field.
- Submit once more.
Request history cannot load.
Likely cause: The history request may be temporarily unavailable even though a confirmed brief was saved.
- Keep the confirmation details.
- Refresh later instead of submitting a duplicate.
Final verification
- Custom Websites > Timing and references: The brief includes planning or visual context.
- Custom Websites > Anything else: The notes satisfy the required field and clarify success.
- Custom Websites form: A confirmation names the submitted project.
- Custom Websites > Request history: The current review status is visible.
- No blocking warning, failed status, or unresolved validation message remains in the completed workflow.