Before you rebuild your business website
A website project becomes easier to price and deliver when it starts with a business task. “Make it more modern” can mean better photography, a clearer service list, a faster phone layout, or a completely different booking process. Those are different jobs. Before commissioning a rebuild, work through the decisions below.
Start with one useful action
Choose the primary action a visitor should take: request a quote, book a consultation, buy a product, or call the shop. Then open the site on a phone and try that action yourself. Note the steps, missing information, and anything that makes you hesitate. This gives the project a concrete starting point.
Separate the message from the mechanism
A contact button cannot explain an unclear service. Write down who you help, what you deliver, and what the first conversation will cover. Then decide whether the right mechanism is a short form, email link, appointment tool, or checkout. You may need less technology than expected, or a more deliberate connection to the way your business already operates.
Inventory the accounts before changing the design
List the domain registrar, DNS provider, host, business email provider, and any store or booking system. Confirm who owns each account and who can recover access. Website hosting and business email can be separate services. A redesign should not accidentally interrupt incoming mail, lose a domain renewal, or leave the business dependent on someone else’s login.
Define the first version in plain language
For a service business, the first version might include five pages, a portfolio, a short inquiry form, and a basic editing handoff. For a store, add the catalog size, product options, shipping rules, payment setup, and order process. For a custom tool, describe the users, inputs, outputs, and systems it must connect to. Say what is outside scope as clearly as what is inside.
Agree on content and approvals
Decide who supplies copy, images, product data, and legal policies. Name one person who can approve the work. Set review dates and define how many revision rounds are included. Delayed content often affects launch more than the code, so the schedule should show those dependencies openly.
Test the whole inquiry path
A form that displays a success message is only one part of the process. Send a clearly labeled test, confirm it appears in the form dashboard, check the destination inbox, and reply. Repeat on a phone and with keyboard navigation. Decide who follows up and where the inquiry is tracked. A useful website connects to an actual business routine.
Measure what helps you make decisions
Record inquiries, qualified conversations, proposals, wins, collected payments, and delivery time. Search impressions and social reach can help diagnose visibility, but they are not revenue. Start with a small set of measures you can maintain every week. Add tracking tools only when you know what decision their data will support, and update your privacy disclosures when the setup changes.
Ask what happens after launch
Clarify who handles updates, backups, account renewals, broken integrations, and content changes. Maintenance is a defined service, not an unlimited promise. A written care scope should say what is included, how requests are prioritized, and which platform costs remain the owner’s responsibility.
Bring the current URL, the main task visitors need to complete, and one example of what is not working to the first conversation. That is enough to start shaping a useful scope. Send a project inquiry or email info@qplldb.com.