How To Work With A Web Designer Without Endless Revisions
27 Aug 20263 min read
“It is not quite what we had in mind” is difficult feedback to act on, especially near the end of a website project.
A better working relationship starts earlier. Your designer needs to understand the business decisions behind the website, and you need to understand what you are being asked to approve.
You do not need to arrive with every answer. The aim is to make the important questions visible before they become expensive changes.
Bring The Business Context
Explain who the website is for and what you want those people to do. Share the questions customers ask, where the current website causes confusion and what your team struggles to update.
Bring examples rather than only adjectives. “Customers cannot tell which service includes installation” gives a designer more to work with than “We need a premium feel”.
Useful starting material includes:
- Your main audiences and services.
- Existing brochures, product information and brand guidance.
- Common sales and support questions.
- Pages or functions that must be retained.
- Known deadlines and who needs to approve the work.
Be open about gaps. If photography or copy still needs to be produced, that belongs in the plan.
Agree On The Problem Before The Appearance
The Design Council’s Double Diamond separates understanding and defining a problem from developing and testing solutions.
For a website project, that means checking the purpose and structure before debating the colour of a button.
Ask your designer to walk through a typical customer journey. Where does someone arrive? What do they need to understand? What might prevent them from enquiring?
A simple page outline can reveal missing information before a polished design makes everything feel settled.
Explain Why You Like A Reference
Reference websites can help, but “make it like this” leaves room for different interpretations.
Point out the specific quality you mean. Perhaps the product comparison is easy to read, the photography feels relevant or the enquiry process is straightforward.
Also identify what you do not want. You may like a site's visual style but dislike its long opening animation.
Use references to discuss principles, not to copy another company's branding or content.
Give Feedback In Terms Of The Reader
Try replacing a preference with the concern behind it.
Instead of “Make this section bigger”, explain that the service area is easy to miss and customers need it before requesting a quote. The designer can then suggest an appropriate solution.
Separate factual corrections, usability problems and personal preferences. All may be worth discussing, but they should not carry the same weight.
When possible, attach feedback to a specific page or section. A screenshot with a short explanation is more useful than a long message referring to “the thing near the bottom”.
Consolidate Decisions Without Hiding Disagreement
Choose someone to collect feedback and confirm the final direction. This prevents the designer from receiving contradictory instructions through separate conversations.
That person should not simply forward every comment. Discuss conflicts internally, or bring the unresolved decision to the designer with the business reasons on both sides.
Keep a record of what was approved and what is still open. If a decision changes, ask how it affects the scope and schedule before work continues.
Review Real Content And Real Tasks
Placeholder copy can make a design look tidier than the finished website. Review with representative headings, long product names and realistic amounts of text.
Ask to see mobile layouts and try important interactions. Can someone find a service, read the details and complete an enquiry? Can your own team update the information it owns?
Agree review points at the beginning, so questions are raised while there is still room to respond.
Make Handover Part Of The Conversation
Before launch, establish who will maintain the website, what training is needed and how outstanding issues will be recorded.
A useful handover lets your team perform its normal work, not just receive a folder of files.
The best collaboration combines your understanding of the business with the designer’s ability to turn that understanding into a usable website. Clear questions and timely decisions give both sides room to do their job well.
What A Corporate Website Should Do For Your Business
Someone hears about your business and looks you up. Can they quickly understand what you offer, decide whether it suits them and find a way to talk to you?That is a useful starting point for a corporate website. It does not need to impress visitors with complicated effects. It needs to give them the information and confidence to take the next step.For your team, it should also be a reliable place to send people, whether you are introducing the company, answering a question or following up on an enquiry.Explain What You Do Without A Sales CallA visitor should not have to read your entire company history to work out whether you can help.Start with your main services or products, who they are for and what someone can expect. Use the words customers use in conversations with you. If an offer is complicated, explain it with an example.A manufacturer might organise information by product range and application. A professional-services firm might explain the situations it helps with. The right structure depends on what your customers need to decide, not how your departments are arranged.Give People Something Useful To CheckBefore getting in touch, a potential customer may want to know who you are, what you have done and how to reach you.A clear About page, accurate contact details and relevant examples of your work help answer those questions. Use project descriptions to explain what you delivered. Include testimonials or results only when you have permission and evidence to support them.You do not need an impressive claim in every paragraph. A specific, truthful explanation is more useful than saying you are the best.Support The Sales Conversations You Already HaveThink about the documents and explanations your team sends repeatedly. Could a page answer the same questions clearly?A service page can set out what is included. A project example can show relevant experience. A product page can bring specifications and downloads together. Your salesperson can then send a useful link instead of rebuilding the explanation in every message.This does not replace a conversation. It gives both sides a better starting point for one.Make It Clear How To EnquireOnce someone is interested, the next step should be easy to find.Use a clear contact button and ask for the information you need to start a useful conversation. Explain what happens after someone submits the form. Avoid asking for a complete project brief when a short introduction would do.Check the journey on a phone as well as a computer. Can the visitor read the page, tap the right button and complete the form without struggling? A beautiful page is not much help if getting in touch is difficult.Answer Questions Before They Become Another EmailYour team already knows many of the questions customers ask. Those questions are a good place to start when planning content.Explain how to request a quote, what information is needed and where to find support. For a product business, that might include specifications, stock enquiries or delivery arrangements. For a service business, it might mean clarifying the process and what affects the scope.Keep answers specific to your business. A useful FAQ answers a real concern; it is not a place to repeat search phrases.Keep Business Information In One PlaceWhen a service changes or a new product is introduced, someone needs to update the website. Decide who owns each part of the content and how changes are approved.Your team should be able to make the routine updates it is responsible for, with appropriate training and support. Also agree who handles technical upkeep and what happens when something needs fixing.A website is more useful when people can trust that its information is current.Choose A Clear Job For Each PageBefore adding more pages or features, ask what each one helps a visitor do. Is it explaining an offer, answering a concern, showing relevant work or helping someone contact you?Then review whether the website supports those jobs. Customer questions, feedback from your sales team and properly configured website data can help you decide what needs attention.A website does not guarantee sales. It can give customers a clearer picture of your business and make it easier for your team to help them.Need A Fresh Look At Your Website?Ask Orangesoft for a free website audit. Share your current website and what you would like it to do better.
28 Sept 2026 · 4 min read
Custom Website Or Template: What Does Your Business Need?
A template might look close to what you want. A custom design might promise more freedom. How do you decide which is worth paying for?Start with the work the website needs to do. A business with a straightforward offer faces a different decision from one with several audiences, a large product range or a complicated enquiry process.Neither approach guarantees a better website. The important question is how well the finished site fits your customers and the people looking after it.What A Template Gives YouA template provides an existing layout and set of design choices. Your team adapts these with your content, images and branding.This can be a sensible starting point when the structure already suits your business. For example, a service company may need a clear introduction, service pages, project examples and a contact form. If the template handles those well, there may be little reason to redesign every component.The work is not finished when a template is chosen. Someone still needs to organise the information, prepare useful copy, check it on phones and make sure enquiries reach the right person.Where A Custom Design HelpsCustom design starts around your requirements rather than an existing page layout.It can be useful when visitors need to compare detailed products, find information across different business units or follow a journey that standard layouts handle poorly. It also gives the design team more room to express a distinctive brand.Consider a supplier whose customers choose products by application, size and material. A layout built around those decisions may be more useful than one organised around a large banner and a short product grid.That does not mean every part needs to be built from scratch. A custom design can still use an established content system and familiar components.Separate The Design From The FeaturesThe words "template" and "custom" do not tell you whether a website can support a booking form, product catalogue or connection to another system.Ask the provider to show how your actual requirements will work. Which features already exist? Which need configuration or development? Are there ongoing subscriptions or restrictions?Do the same for everyday editing. Ask to see how your team would add a service, update a project or replace a document. A flexible-looking website is not much help if routine changes are difficult.Compare The Whole ScopeWhen comparing proposals, check what each includes:Planning the pages and customer journeys.Writing, editing and entering the content.Design changes and review rounds.Forms, integrations and testing.Training, handover and ongoing care.A lower quote may simply cover less work. A higher quote needs to explain what the additional work is and why your business needs it.Avoid paying for flexibility you cannot see yourself using. Equally, look carefully at a template that needs extensive changes just to meet your basic requirements.Keep Search And Mobile Use In The ConversationNeither custom design nor a template automatically brings search rankings or enquiries.Ask how the proposed site will organise important information, preserve useful existing URLs and work on smaller screens. Review a real page with your content, not just an attractive demonstration filled with short sample text.The useful test is simple: can someone understand the offer, find an answer and contact you without getting stuck?Make The Decision With A Real BriefList the pages you need, the tasks visitors must complete and the updates your team expects to make. Share examples of what is difficult on your current website.Then ask the provider to explain where a template fits and where a more tailored approach would help. You are choosing a workable website, not a label.Not sure which approach fits? Talk To Us About Your Website.
27 Sept 2026 · 3 min read
How To Build A Product Catalogue Customers Can Actually Use
A customer asks which model will fit their project. Your salesperson sends a brochure, follows up with a specification sheet and then checks whether the image shows the latest version.A digital product catalogue can bring those details together. The aim is not simply to put the brochure online. It is to help someone find a suitable product, understand its differences and ask a useful question.That matters whether you sell furniture, machinery, components or specialist equipment.Start With How Customers ChooseYour internal product codes may make sense to your team but mean little to a first-time buyer.Find out what customers ask for. Do they start with an application, material, size, capacity or product family? Use those decisions to shape the categories and filters.Keep the options specific enough to help. A filter called "Type" is less useful when buyers cannot tell what the types mean. Clear labels and short explanations can make a technical range easier to explore.Let experienced customers search by model or product code too. They may already know exactly what they need.Give Each Product A Dependable HomeA product page should bring together the information needed to evaluate that product. Depending on the range, that may include:A clear product name and reference code.Photographs showing the relevant version.Key specifications, with units clearly stated.Available variants and compatible accessories.Current brochures, manuals or technical drawings.A way to ask about that specific product.Use a consistent structure across comparable products. If one page lists dimensions and another hides them in a download, comparisons become harder than they need to be.Put the main information on the page itself. Downloads can provide detail without making every visitor open a document just to understand the product.Keep Similar Products Easy To Tell ApartNear-identical names and images can leave buyers unsure which version they are viewing.Explain the meaningful differences. A comparison might show sizes, materials or intended uses. Avoid filling it with details that are identical across the whole range.If a choice depends on the customer's setup, say what information your team needs to advise. A catalogue should help someone reach the right conversation, not make a specialist decision look simpler than it is.Make The Enquiry Carry The Product DetailsWhen someone selects "Enquire About This Product", the product name or code should travel with the enquiry.Ask for the details that will help your team respond, such as quantity, intended use or delivery location. Do not ask customers to copy information that the website already knows.For buyers considering several items, a shortlist or enquiry basket may be useful. They can discuss the group together without treating it as an online purchase.Decide Whether You Need Checkout At AllA catalogue and an online shop do different jobs.If prices depend on specifications, quantities or installation, an enquiry may be the right next step. If products have clear prices and fulfilment arrangements, online ordering might be appropriate.Make that distinction visible. Visitors should know whether they are requesting a quote, checking availability or placing an order.Plan Who Keeps It CurrentAgree who updates descriptions, specifications, images and downloads. Decide what happens when an item changes or is discontinued.An older product page may still help existing customers find a manual. Instead of removing it without explanation, consider marking its status and pointing to an appropriate replacement where one exists.Before launch, ask someone outside the product team to find a suitable item and send an enquiry on a phone. Watch where they hesitate. Those moments often reveal what needs a clearer label or a better explanation.Planning a catalogue? Discuss Your Product Range With Us.
26 Sept 2026 · 3 min read
Who Controls Your Business Domain Name?
Your business has used the same website address for years. But if you needed to renew it, move the website or change providers tomorrow, would anyone know where to start?Domain control is easy to overlook while everything is working. It becomes important when the only person with access leaves, a renewal notice goes to an old inbox or a new website is ready to launch.A short check now can help you find the gaps before the address is needed for something urgent.Know What The Registration CoversA domain name is the address people use to reach your website. Registering it is different from buying website design, hosting or email services, even when one supplier arranges all of them.The registrar manages your domain registration. The registrant is the person or organisation recorded as holding that registration.Ask your provider to confirm those details. A paid website invoice, a company logo on the homepage or access to the content editor does not, by itself, tell you who controls the domain account.Check The Record And The AccountStart with your domain provider's account and registration records. Confirm the registrant information with the provider if anything is unclear.Public domain lookups may hide personal contact details. An incomplete public result is not proof that something is wrong, and it may not tell you who can actually sign in.For Malaysian domains, MYNIC's domain-management guidance explains the different contact roles and management processes. For other extensions, check the relevant registrar and registry rather than assuming the same rules apply everywhere.Keep Access Within The BusinessYour company should know which account controls the domain and how an authorised person can recover it.Use an organisation-managed contact route and secure access arrangements. Enable multi-factor authentication where available, and keep recovery information in an approved place. Avoid relying entirely on a former employee's personal email or one supplier's private account.An external team may need technical access. That does not mean they need unrestricted control over registration and billing. Ask what access is required and use separate roles where the provider supports them.Give Renewals An OwnerRecord the renewal date, the provider and the person responsible for payment. Check that reminders reach someone who will act on them.Automatic renewal can help, but it still depends on current account and payment details. Confirm renewal in the provider's account rather than assuming that no news means everything is fine.Be careful with unexpected renewal emails. Open the provider's known website directly or contact them through a trusted channel before paying or sharing information. ICANN's advice for registrants covers account security and renewal-message awareness.Treat A Website Move As A Separate JobChanging the website does not always require transferring the domain registration. Moving a domain to another registrar is also different from changing where the website points.Before anyone makes changes, ask which services use the domain. Your email and other business tools may rely on the same settings.Have the responsible technical team plan the change and confirm what will stay untouched. Do not cancel the old service simply because the new homepage looks ready.Keep A Simple Handover RecordYou do not need to keep passwords in a shared document. Keep a record of where access is managed, who is authorised, who handles renewals and who to contact for help.Review it when staff or suppliers change. A domain should remain manageable even when the people looking after it change.Preparing for a website handover? Talk To Us.
25 Sept 2026 · 3 min read
