Something new needs to be built.
Share what the business needs customers or staff to be able to do, plus anything already known about timing, content, integrations or constraints.
Send the starting brief →Start a project
Start a Web Design Project
Starting a project should be straightforward. Start a web design project with Morris Standard in Builth Wells, Mid Wales. Choose the level of detail that suits you, share what you know, and the next step can be worked out from there.
01No finished briefStart with what you know
02Direct with IanNo account-management layer
03Clear next stepScope only when it makes sense
Choose the clearest starting point
Different starting points. You do not need to diagnose the solution first.
The first conversation should establish what is actually happening before a platform, feature list or budget assumption is treated as fixed.
Something is not working well enough.
Describe the friction rather than prescribing the fix. That might be too few or poor-quality enquiries, difficult administration, weak product data, slow workflows or a customer journey that no longer fits.
Explain the problem →You need a clearer view before committing.
Use the Standard Check for a structured first look at the public website, or discuss a focused review with Ian when the issue needs conversation and context.
What is useful at the beginning
A useful first message is context, not paperwork.
Send what you already know. Missing detail can be worked through later; invented certainty is less useful than an honest description of the current position.
- 01Current position
The website, platform, system or process in use today — or simply that this is a new build.
- 02What needs to change
The customer problem, commercial issue, repeated admin or operational friction that is creating the need for the project.
- 03The outcome that matters
What should become clearer, easier, faster or more useful for customers, staff or the business.
- 04Known constraints
Useful deadlines, existing suppliers, systems that must remain, compliance needs or budget boundaries if these are already known.
Before a project is scoped
The first job is to make the problem smaller and clearer.
A quote is more useful when the work has boundaries. That means understanding the current position, testing assumptions and separating what is essential from what can wait.
- 01Read
Review the information, current site or system and any evidence already available.
- 02Question
Identify gaps, assumptions and decisions that need clarification before scope is treated as fixed.
- 03Define
Set practical boundaries around the work, responsibilities, dependencies and the result being aimed for.
- 04Recommend
Agree the most sensible next step — a project, a smaller piece of work, further investigation or no work at all.
Keep the beginning proportionate
You do not need everything decided before you get in touch.
Bring the real context.
- The current website or system
- The problem or opportunity
- The outcome you need
- Known timing or constraints
Do not invent certainty.
- A final platform decision
- A complete feature specification
- Perfect copy or wireframes
- Answers to questions not yet asked
A practical next step
Send what you have. Start with what is true.
If there is enough information to scope useful work, that can happen next. If there is not, the next step should be to clarify the problem rather than rush into a build. Want to see the work first? Selected web design case studies, Ian Morris web designer or Ecommerce web design in Mid Wales.