You have decided your business needs a website. You contact a developer, explain that you want something modern, and ask for a price. Then come the questions: Which pages do you need? Do you already have photos? Should customers buy online or just enquire? Who will handle the domain?
None of those questions is unreasonable. They are the details that determine the work. You do not need to know HTML, CSS or anything about servers to answer them. You just need a short plan.
Here are seven things worth preparing before you request a quote. Doing this homework can save time, make estimates easier to compare and reduce revisions once development starts.
1. Decide what success looks like
“Make me a good website” sounds clear until two people imagine completely different results. Start with what you want visitors to do.
A coaching centre may want admission enquiries. A restaurant might want people to view a menu and find directions. A supplier may need buyers to request bulk quotations. A freelancer may want visitors to see projects and book a discovery call.
Choose one primary action and, if necessary, one secondary action. For example:
- Primary: Send a WhatsApp enquiry for a quotation.
- Secondary: Browse completed work before contacting us.
You can improve the design later, but the main action should influence the page layout from the beginning.
2. Explain your business in ordinary language
Write two or three sentences answering three questions: What do you offer? Who is it for? Where or how do you provide it?
For example: “We make customised office furniture for businesses in Kanpur. Customers can request desks, storage units and reception counters based on their space. Contact us with approximate dimensions for an estimate.”
That is more helpful than “We deliver world-class solutions through innovation.” It gives a new visitor something concrete to understand.
Also note anything that makes your process distinctive: custom sizes, appointment-only service, service area, delivery terms, minimum order quantity or on-site visits. Be specific, but only promise what you can actually provide.
3. Make a realistic list of pages and features
Most small business websites can begin with a few well-planned pages: Home, Services or Products, About and Contact. A Gallery, FAQ or Blog can be added if it answers real customer needs.
Then separate the features into two groups.
Must have for launch: a working enquiry button, mobile-friendly layout, service descriptions, directions or contact details, and whatever customers genuinely need to do business with you.
Could come later: customer accounts, advanced booking, online payments, product filters, dashboards or integrations with other software.
A five-page informational website and a custom inventory-connected ordering platform are not the same project. This distinction helps a developer give a realistic quote and makes it easier to stay within budget.
4. Gather the content before design starts
Website development gets delayed surprisingly often because the words, photographs or product details are not ready. Even a beautiful layout can look unfinished when it contains generic placeholder text.
Start a folder with your logo, brand colours if you use any, a short business introduction, service details and genuine photographs. For a shop, collect product categories, sizes and relevant specifications. For a coaching centre, collect programmes, class details and the admission process. For a service business, collect examples of completed work that you have permission to show.
Do not worry if you do not have professional photos yet. Tell the developer what is available. Good typography and a thoughtful layout can still produce a strong website; pretending stock photos represent your actual team or premises is a bad substitute.
Keep sensitive customer details and private documents out of public portfolio examples unless you have permission to publish them.
5. Plan how people will contact you
This is easy to overlook because the contact page looks simple. In reality, it is often where the website either works for the business or lets an enquiry slip away.
Decide which contact methods you can respond to consistently. If customers use WhatsApp, include it. If quotations need files and detailed descriptions, a short enquiry form may be better. If you take appointments, write down how bookings are confirmed and what happens when a time is unavailable.
Before launch, test the contact process on an actual phone. Tap the call button. Open the WhatsApp link. Submit the form and check whether the message arrives in the correct inbox. If the site sends a confirmation email, make sure it is accurate and not promising a response time you cannot meet.
Also decide how much customer information you truly need to collect. A simple enquiry normally does not require date of birth, home address and multiple personal details.
6. Clarify domain, hosting, ownership and maintenance
Your domain is the website address. Hosting is where the website runs. They are related but separate services, and renewals may be billed separately from development.
Before paying an advance, ask:
- Who will register the domain, and whose account will own it?
- Where will the website be hosted, and who can access the hosting panel?
- Will the project include HTTPS, backups and basic security setup?
- Will you receive access to the website files and, where applicable, the database?
- Who handles updates, bug fixes and renewal reminders after launch?
Ideally, the business should control its own domain account and have a workable handover plan. A developer can manage the technical work without leaving the owner dependent on an account they cannot access.
If the website includes forms, logins or customer information, discuss privacy, spam prevention and how data is handled. These details are easier to plan before a site goes live than after something breaks.
7. Share a realistic budget and review process
You do not need to know the exact market price for your website before approaching a developer. But an approximate budget range and a list of priorities are helpful. They allow you to discuss trade-offs: a custom design versus a simpler launch, or an advanced feature now versus a later phase.
Ask the developer to explain what the quote includes: design, number of pages, content entry, mobile responsiveness, SEO basics, forms, hosting setup, revisions and post-launch support. Compare proposals by scope, not just by the lowest number on the page.
Also agree on who reviews drafts, how feedback will be collected and when payments are due. Giving one consolidated round of feedback is usually better than sending small changes through different messages every day.
A useful launch plan includes time for content collection, design approval, development, testing and final handover. Treat a promised date cautiously if the requirements are still changing.
Copy-and-paste brief for your developer
You can copy this into an email or document and fill in whatever you know. Leaving some fields blank is fine; the purpose is to start a useful conversation.
Business name:
Business location / service area:
What we sell or provide:
Who our customers are:
Main goal of the website:
Primary customer action (call / WhatsApp / form / booking / order):
Pages we think we need:
Must-have features:
Nice-to-have features:
Logo, photos and content available:
Websites we like (and what we like about them):
Current website, if any:
Domain and hosting already owned? (yes/no):
Who will handle enquiries:
Approximate budget range:
Preferred launch window:
Who will approve design and content:Before you approve the finished website
Make time for a final check instead of publishing as soon as the homepage looks attractive.
- Open the site on a phone and a desktop, and check the navigation.
- Read the services and contact details for mistakes.
- Test every important button, form and external link.
- Check page loading and image sizes on a normal mobile connection.
- Confirm the domain uses HTTPS and that backups are available.
- Ask for the agreed account access and handover information.
You do not have to perform every technical test yourself. You should, however, understand what has been checked and how to report a problem after launch.
A well-prepared brief makes a better first conversation
You do not have to walk into a developer meeting with a finished blueprint. Bring your goals, your real content and the questions you still have. A good development process should help you make the remaining decisions—not expect you to already know all the technical answers.
To see different ways websites can be organised, browse CodeFrom's live projects. When you are ready to explain what you have in mind, send your brief to CodeFrom.