First, confirm who the account belongs to. The order should be placed in the company's legal name, with a role email address that will outlive any single employee. If an agency is ordering on your behalf, ask them to use your details, not theirs, so the service never becomes a hostage in a commercial dispute.
Second, confirm the operating system and software. Ask the developer whether the website needs PHP, a particular database version or Windows and ASP.NET. Because Linux and Windows shared plans cost the same, the choice should depend purely on what the application needs. Getting it right at the start avoids a second migration later.
Third, confirm the email layout. Decide which role mailboxes you need, who reads each one and how much storage your industry tends to use. If the company relies on email for tenders and orders, discuss whether mail should sit on its own plan or server so that website problems never interrupt it.
Fourth, confirm the money side. Agree which payment method finance will use, who receives renewal invoices and which budget line the hosting belongs to. We do not accept cash payments, so choose bank transfer, a cheque deposited into our account, a wallet such as Easypaisa or JazzCash, or a card, and keep the reference with the invoice.
Fifth, confirm the move. If there is an existing website, ask us to migrate it for free and agree a quiet time for the switch. Lower the DNS cache time in advance, test the copied site before changing nameservers, and keep the old account alive for a few days in case a forgotten mailbox needs to be retrieved.