Pre-project checklist
How to prepare materials for a new website
The bottleneck is usually scattered information and missing decisions, not code. Well-organised materials shorten the project, reduce revisions and make it easier to estimate the real cost early.
1. One sentence about the website’s purpose
Start with: “After visiting the website, the right person should understand… and then…”. For example: “A truck owner should find the right service branch and call it.” This purpose helps you decide whether a section, image or feature is genuinely needed.
2. Audiences and their questions
“All customers” is not enough. List two to four main groups and the questions they bring. Someone comparing offers needs different information from a returning client looking for a number or a job applicant.
3. A clearly organised offer
- a complete list of services or products;
- a short description of each main service;
- who it is for and what problem it solves;
- service area and locations;
- indicative prices or the quoting process;
- frequent questions and objections;
- services the business no longer provides.
If the offer is scattered across the old website, PDFs and messages, bring it together first. Copying everything without decisions will carry the clutter into the new website.
4. Evidence of credibility
Prepare factual information: years of experience, qualifications, certificates, partnerships, work delivered, reviews, projects and measurable data. Check publication permission and the right to use each client logo.
Do not invent KPIs afterwards. If you have no measurements, describe the scope and design decisions instead. Analytics can be set up later to develop a full case study.
5. Photos and graphics
- a logo, preferably in SVG, PDF or another vector format;
- logo versions for light and dark backgrounds;
- brand guidelines, colours and fonts, if available;
- photos at their original resolution, not messaging-app screenshots;
- information about authorship and usage rights;
- captions explaining what and who is pictured;
- consent from people shown, where required.
Do not crop every photo before sending it. The designer may need different proportions for phone and desktop. Keep the originals.
6. Contact and business details
Collect the correct business name, responsible person, address, phone numbers, emails, opening hours, locations, social profiles and enquiry-handling rules. For multiple branches, provide separate details and an approver for each.
7. Legal documents and data handling
Do not copy a privacy policy from a random website. Establish which forms are used, where messages go, who can access them, which analytics or marketing tools are installed and how long data is kept. If uncertain, have a lawyer or data protection specialist review the documents.
8. Access — without emailing passwords
Start with a list of services: domain registrar, hosting, WordPress, DNS, email, Search Console, Google Business Profile and any integrations. Share credentials only through an agreed secure channel. Enable 2FA, create a separate developer account where possible and remove unnecessary permissions after the project.
The domain and hosting should remain in the website owner’s account. Access handover should not depend on continuing a care plan.
9. One decision-maker
Many projects stall because three people give conflicting feedback, not because ideas are missing. Agree who collects comments and sends one approved list. Also record who approves the structure, design and launch.
10. References with reasons
Choose three to five websites and explain what works: how the offer is presented, typography, colour, menu, projects or form. “Make it like this website” does not explain whether you mean appearance, functionality or brand positioning.
Minimum starting materials
- website purpose and main audiences;
- list of services and locations;
- contact details;
- logo and available photos;
- links to the existing website and profiles;
- list of decision-makers;
- deadline, budget and important constraints;
- who prepares the final copy.
You do not need a finished website in your head. You need organised business information and someone who can make decisions.
What the developer can prepare
MAKOLOR can propose a sitemap, organise the offer, edit supplied information, create a photo checklist and help coordinate materials. Include this in the scope: collecting information from several people is work, not a free addition to coding.