Hire for a website redesign when you need a map of what stays, not when you need a picture of a homepage. People look up when should you hire for a website redesign with a folder of mockups and no list of URLs. The useful hire starts with that list. The weak hire starts with a visual concept and says the words can come later.
Takeaways
- Hire when you cannot say which URLs still describe a real service and which must be replaced.
- Do not hire a visual concept that postpones the words. A coat of paint on vague copy is not a redesign.
- Ask for the URL list before a design file opens, and keep the accounts in the business's name.
- The order is initial contact, then a detailed discussion, then implementation. It is not a promise about rankings.
Hire for the Map of What Stays
The hire is due when the site no longer matches the firm and you cannot sort it yourself. You know some pages are outdated. You are afraid to touch the ones that get visits. You have opinions about the colors and no opinion, yet, about which addresses are still true. That is the moment to bring in help, and the help should begin with a map.
Website Redesign keeps the URLs which still apply and replaces the pages that no longer say what you do. A person you hire should be able to sit with your list and mark it. If they want to skip to a homepage, they are offering a different service than the one you need. You are allowed to notice that in the first conversation.
You do not need them because you lack taste. You need them because the sort is easy to avoid and costly to skip. A map forces decisions: this service stays, this campaign ends, this thin page does not get a new skin. Those decisions are the project. Taste applies them. Taste does not substitute for them.
Website Design is the wider idea: pages have jobs, and the jobs are to explain the work and start a conversation. Hire when the current URLs fail that test and you want a partner who will say so. Do not hire to be reassured that everything can stay if you change the header.
A Folder of Mockups Is Not a Brief
A folder of homepage mockups feels like progress. It is a brief only if each picture implies a URL list, which it almost never does. Pictures show a mood. The redesign needs a decision about what remains at which address. If your folder has five homepages and no spreadsheet of URLs, you have been shopping for a feeling. Put the folder aside until the map exists.
This is not a scolding about inspiration. References can show how plain you want the type, or how quiet you want the proof. They cannot tell you whether the old service page still applies. When a designer asks for the folder first, answer with the list first. You will learn quickly whether they know what a redesign is.
A new coat of paint on the same vague copy is not a redesign. Your mockups may be paint. Look at the words inside them. If the words are the old slogans, or if the words are fake lines about a generic firm, the picture is not evidence of a plan. It is evidence that the words were postponed, which is the weak hire in visual form.
You can keep one image you genuinely like, as a note about tone, and throw the rest out of the meeting. The meeting is about addresses. An image that survives should be able to sit quietly while you talk about a URL. If it cannot, it is running the meeting, and the meeting will not produce a map.
What to Ask for Before a Design File Opens
You will know what to ask for before a design file opens. Ask for the URL list with a mark on each line: keep, rewrite in place, or replace. Ask for the sentence a stranger should learn on every URL marked keep. Ask what happens to each replaced address. Ask who edits the sentences after launch. A design file that arrives before those answers is early, and you can send it back without being difficult.
Ask them to say which pages they have actually read. A concept drawn from the homepage alone has not seen the site. The awkward pages are the point. A useful hire will have opened the thin ones and the old campaigns, not only the screen you are proud of. If they have not, the detailed discussion has not started.
Ask what they will not promise. Do not promise that a redesign recovers rankings. A serious person will agree, and will talk about keeping true URLs as hygiene rather than as a forecast. Search Engine Optimization is separate work. If the pitch leads with positions coming back, you are in the wrong conversation. The right one is about what the pages say.
Write the asks down and use them as the agenda. You do not need a long procurement document. Four questions, asked before anyone shares a screen, will tell you whether this hire starts with the map. If the answers are about type, you have your answer about the hire.
The Weak Hire Starts With a Picture
The weak hire starts with a visual concept and says the words can come later. Later is how vague copy survives. The concept gets approved because it looks current. The old sentences are poured in at the end because the launch date moved. You pay for a redesign and receive a reskin. The test is simple: if the words are scheduled after the pictures are approved, the order is already the weak one.
You will hear reasonable excuses. The words are "content," and content is a later phase. The layout needs to be locked so the writers know the space. The brand has to land first. None of these require you to approve a homepage before you know which services exist. The space can flex to the sentence. The sentence should not shrink to the space.
A useful hire can work in the other order without drama. They can look at a URL, say whether it still applies, and describe the page's job in a sentence you recognize. The picture comes after you have said yes to that sentence. You are not waiting forever. You are waiting until the map is real, which is a shorter wait than a redo.
If you already have a weak engagement underway, you can still reset it. Pause the pictures. Ask for the list. Implementation that continues without the list will only get harder to undo. A week spent on the map is cheaper than a launch you do not believe.
How the Conversation Should Run
Run it as initial contact, then a detailed discussion, then implementation. That order is the work. It is not a guarantee of rankings, traffic, or enquiries. Anyone who collapses it into a reveal of a homepage is skipping the map, which is the only part you cannot get from a template.
Initial contact is for the symptom and the fit. You show the folder and you show the fear about the URLs. They tell you they would start with the list, or they tell you they would start with a concept. You decide whether a detailed discussion is worth having. You do not need to hire the whole build in that first exchange.
The detailed discussion produces the map. Keep, rewrite, replace. The sentence for each keep. The destination, if any, for each replace. The editor who will change words later, on a stack someone can keep updating after launch. Website Maintenance is the habit after that, not a substitute for the map. You should recognize every line of the map as something you could defend.
Implementation builds the kept pages, the replacements, and the editing path. You review it against the map, not against the folder you set aside. If a URL you marked replace is still live and still vague, implementation is not done. If the site is prettier and the map was ignored, the hire failed in the way you were warned about.
| Stage | What you should have in hand | It is too early when |
|---|---|---|
| Initial contact | The symptom, the current URLs, and a refusal to keep vague copy | The only artifact is a homepage mockup |
| Detailed discussion | A map marked keep, rewrite, or replace, with a sentence for each keep | The talk is about color and the list does not exist |
| Implementation | Pages that match the map, and an editor who can change a sentence | A new look went live on the old vague sentences |
What You Bring to the First Meeting
Bring the material that makes the map possible, and leave the decoration until it is asked for. You are not expected to have finished the sort. You are expected to be willing to do it before you fall in love with a picture.
Bring these:
- A list of the public URLs, even a messy export, including the pages you hope nobody opens.
- The services you still want conversations about, which may be shorter than the menu.
- Examples of sentences on the site you already know are untrue or empty.
- The name of the person who must be able to edit the site afterward, and confirmation the accounts stay in the business's name.
- Any mockup you love, labeled as tone, not as the brief.
You will know what to ask for before a design file opens, because you will have asked for the map. A useful hire will take that list and work it. A weak hire will ask to see the folder again. That difference is the decision, and you can make it before anyone sends an invoice for pictures.
Questions
Should You Hire If You Already Have Mockups?
Only if you are willing to set them aside until a URL list exists. Mockups are not a brief. The hire is for the map of what stays, not for a prettier version of a picture you already like. If the mockups contain the old vague lines, they are evidence of the problem.
What Should You Ask to See Before Any Design File?
Ask for each URL marked keep, rewrite, or replace, for the sentence a kept page must deliver, for where a replaced address goes, and for who edits the words later. If those answers are missing, a design file is early. You can say so in the meeting.
Is It a Problem If the Words Are Scheduled Last?
Yes. That is the weak hire, because words scheduled after the pictures are approved are how vague copy survives a redesign. The sentence can come before the layout is locked, and a firm that needs the picture first is painting, even if the language around it sounds thorough.
What Order Should the Engagement Follow?
Initial contact, then a detailed discussion, then implementation. Contact checks whether they start with the map, the discussion writes the map, and implementation builds what the map says. The order is not a promise that rankings, traffic, or enquiries will follow.
Who Should Own the Accounts After Launch?
The business should. A redesign does not transfer the site to the firm that drew it. Keep an owner login in the business's name, and let the people doing the work have their own access. A partner who will not share ownership is holding the site, not redesigning it.
Conclusion
The useful hire starts with the URL list, and the weak hire starts with a visual concept and says the words can come later. Ask for the map before a design file opens, and follow initial contact, then a detailed discussion, then implementation. You will know what to ask for, and you will know a coat of paint when you see one.
If you want help hiring for the map of what stays, not for a picture of a homepage, Speak With Us.
