Hire a website designer when the pages do not explain the work, and wait if the only plan is a new look wrapped around the same vague sentences. The moment people search when should you hire a website designer is usually the moment the site looks current and still fails to start a conversation. You can describe the business, and the useful hire helps the site say it. You will know what to bring to the first conversation, and what you still have to write yourself.
Takeaways
- Hire when a stranger cannot tell what you do, or cannot tell how to start a conversation.
- Do not hire for a visual refresh that leaves the same vague sentences in place.
- You still have to write the facts. A designer can structure them, not invent what the firm refuses to say.
- Expect initial contact, then a detailed discussion, then implementation. That order is the work, not a promise of enquiries.
Hire When the Pages Do Not Explain the Work
You can usually tell the hire is due without a scorecard. Open the homepage as if you were new. If you cannot say what the firm does, the page does not explain the work. Open a service page. If it could belong to any firm in the trade, it does not explain the work either. That gap is the reason to hire, not a font you have grown tired of.
Website Design is the practice of giving each important page a job: explain the work and start a conversation. A designer is useful when you can describe the business out loud and the site will not carry that description. They help you turn a true account into pages a stranger can follow. They are not useful as a coat of paint on copy nobody is willing to change.
Notice the difference between "I dislike the site" and "a buyer would misunderstand us." The first can be taste. The second is a job. Hire for the second. If you only dislike the colors, and the sentences are already specific, a smaller edit may be enough. Say which of the two you mean before you ask for proposals.
A site can look current and still fail. Current is a visual impression. Explanation is a sentence. Owners get stuck when they refresh the impression and leave the sentence alone, then wonder why the phone calls are the same confused ones. The hire starts when you are ready to change the sentence.
Skip a Visual Refresh That Keeps the Vague Sentences
Do not hire for a visual refresh that leaves the same vague sentences in place. "Solutions for your needs" does not become clearer in a new typeface. A designer who agrees to restyle those lines without asking what they mean is accepting a brief that cannot succeed. You should be glad if they push back.
Read the lines you are tempted to keep. Would a stranger know what you refuse? Would they know what to send you before a call? Would they know which service is theirs? If the answers are no, the sentences are the project. Pictures can support them later. Pictures cannot substitute for them.
This is also how redesigns go wrong. Website Redesign should keep the URLs that still describe a real service and replace the pages that do not. A new coat of paint on the same vague copy is not that work. If the proposal leads with a homepage picture and says the words can come later, you are looking at the weak version of the hire.
You do not need to arrive with finished prose. You do need to arrive unwilling to preserve sentences you cannot defend. Tell the designer which lines embarrass you because they are untrue or empty. That permission matters more than a mood board.
Write the Facts Before You Hand Them Over
Decide what to hand a designer and what you still have to write. The facts belong to you. What the firm does, who it is for, what it will not take, how a conversation starts, and what the names of the services actually mean: those are not design decisions. A designer can structure them, cut repetition, and show you where a page is missing. They should not invent a business you do not run.
Write rough and true. A page of notes in your own words is a better handoff than a polished paragraph you copied from a competitor. Mark the words you are unsure about. Uncertainty is useful. It shows where the detailed discussion has to go. False certainty sends the project off in a direction you will have to undo.
Separate facts from wishes. "We want to look established" is a wish. "We have done this kind of work for firms that already have an operations lead" is a fact. The site can express the fact. It should not pretend the wish is evidence. Keep wishes out of the sentences a stranger will read as claims.
If you have several services, list them and say which ones you want conversations about. Not every thing you can do deserves a page. The list you are proud of and the list you want the site to invite are sometimes different. Hire after you have admitted the difference.
What the Designer Should Take
Hand over the jobs, not a prescription for every screen. The designer should take the structure: which pages exist, what each one must accomplish, how they link, and how an editor will change them later. They should take the visual system only after those jobs are plain. Color is a tool for making the job obvious, which is why it waits.
They should also take the editing path seriously. Build on a stack someone can keep updating after launch. If your team will change sentences, the designer should show that path, not imply it. WordPress Development is one way to do that when editors need to change pages without breaking the layout. Another stack is fine if the same test holds.
| You keep | The designer takes | Leave it until later |
|---|---|---|
| The facts of the work, including what you refuse | The structure of the pages and how they link | Color, type, and pictures |
| Which services deserve a conversation | A layout that makes each job obvious | A folder of other firms' homepages |
| The accounts in the business's name | An editing path a named person can use | Any promise about traffic or enquiries |
There are things you should not hand over. Do not hand over the right to invent results, client names, or promises about traffic. Do not hand over the login to accounts that should stay in the business's name. Do not hand over the writing of facts you have not checked. A good designer will not want those things. A careless one will fill the gaps with confident fiction.
Ask them to say the job of the homepage back to you in one sentence. If they cannot, they do not have the brief yet, and implementation would be early. That sentence is a better milestone than a first round of pictures.
How the Engagement Should Run
A sound engagement has an order: initial contact, then a detailed discussion, then implementation. That order is the shape of the work. It is not a guarantee of traffic, enquiries, or a particular look. Anyone who collapses it into "we will send a homepage and you will love it" is skipping the part where the pages learn what to say.
Initial contact is for fit. You describe the business and the failure of the current pages. They describe how they work and what they would need from you. You are both deciding whether a detailed discussion is worth having. You do need honesty about what is still unwritten.
The detailed discussion is where the jobs get settled. Which URLs stay. Which sentences are empty. Who edits the site later. What the next step on each page actually is. This is the conversation you came to have. If it turns into a tour of fonts, bring it back. Implementation should start from notes you recognize as true.
Implementation is building the pages, the editing path, and the links between them. Review it against the jobs, not against a mood. Can a stranger tell what you do? Can the named editor change a sentence? If yes, the hire did the thing you hired for. If the site is prettier and the sentences are the old ones, it did not.
Do not promise yourself enquiries because the engagement ran in the right order. Clearer pages can make a visit more useful. They do not manufacture the visit. Keep that limit in the room so nobody "solves" it with a slogan.
What to Bring to the First Conversation
You will know what to bring if you treat the first conversation as initial contact, not as a design reveal. Bring the material that lets a serious person see the gap.
Bring these:
- The homepage and the service pages as they are, with the sentences you no longer believe marked.
- A plain description of the work, in your words, including what you refuse.
- The list of services you want conversations about, which may be shorter than the list of things you can do.
- The name of the person who must be able to edit the site after launch, and what they are comfortable changing.
- Examples of messages you wish the site attracted, with the private details removed, so the jobs are concrete.
You do not need a finished sitemap, a brand book, or a competitor's homepage you want copied. Those can wait, and the last one can mislead. What you are handing over is the truth of the business and a clear refusal to keep the vague sentences. That is enough for a designer to tell you whether a detailed discussion is the right next step.
Questions
Should You Hire If You Only Dislike the Colors?
Not if the pages already explain the work and a stranger can start a conversation. A color change is a smaller edit. Hire when the sentences fail, not when you are restless about the palette. If the sentences are vague, fix those first or the new colors will frame the same problem.
Do You Have to Finish the Copy Before You Call?
You have to bring the facts, not a finished manuscript. Rough true notes are enough for initial contact. You still have to write, or approve, anything a stranger will read as a claim. A designer can structure your facts and should not invent the business.
What Is the Right Order for the Work?
Start with initial contact, then a detailed discussion, then implementation. Contact checks fit, the discussion settles the jobs and the editing path, and implementation builds from notes you recognize as true. That order is how the work runs, and it is not a promise of enquiries.
What Should You Refuse to Hand Over?
Refuse to hand over invented results, client names, or a promise of traffic. Keep accounts in the business's name. Do not let empty sentences survive just because they were on the old site. A careful designer will not need those shortcuts to make the pages clear.
How Do You Tell a Useful Hire From a Weak One?
A useful hire can say the job of the homepage back to you before they open a design file. A weak hire leads with a picture and says the words can come later. Ask for the sentence. If it matches the business you described, the conversation is pointed the right way.
Conclusion
Hire when the pages do not explain the work, and do not hire for a visual refresh that leaves the same vague sentences in place. Bring the facts to the first conversation, keep what you still have to write, and follow initial contact, then a detailed discussion, then implementation. That is how you know the hire matches the site you actually have.
If you want help deciding what to hand a designer and what you still have to write, Speak With Us.
