The first step in building a company website isn't the design. It's three questions: who do you want to reach, what are you offering them, and what should happen at the end of their visit. When a client already has answers to these at our first conversation, the project almost always goes faster and with fewer rounds.
A short, well-thought-out brief also makes sure that every developer you ask is quoting for the same job. You can see what the price includes, what counts as extra work, and how you'll know the site is actually finished. In this article I describe what I usually ask clients for before we give a price.
What is the website's main job?
"Online presence" is too broad to plan around. Define the visitor's next step instead: requesting a quote, booking a consultation, buying something, or asking for a specific document.
Someone who knows exactly what they want needs different content from someone still comparing options. A company site can serve both, but each page should have one clearly recognisable job.
On the Agrider machinery dealer site, for example, most visitors are looking for a specific machine, so the machine page and the enquiry are the main path. The valuation tool and the leasing calculator help people who are still deciding. At a consulting firm it usually makes more sense to understand the client's situation and problem first. The form follows from that decision as well.
What page structure should you plan?
The homepage should give a quick overview: who you help, with what, and how you can back that up. Important services deserve their own pages if they answer different needs and different searches.
For a service business I usually start from something like this:
- a homepage with the main offer and the next step;
- service pages for different client needs;
- an about page with real professional background;
- case studies you have permission to show;
- a contact page with a quote request that actually works;
- a knowledge base for recurring pre-decision questions.
This is a template, not a required page count. Three good service pages are worth more than fifteen that repeat each other. In our own web development work we always start from the business goal.
What content should you gather in advance?
A service name isn't enough to understand an offer. Write down what problem people come to you with, what you deliver, how you work, and when you are not the right choice.
Prepare your logo, usable photos, team introductions and any permissions you need for case studies. If you don't have your own photos, say so at the planning stage. In my experience projects slip on content far more often than on development.
For the FAQ, start from your actual client conversations. What affects the price? What needs preparing? Who is the contact person? What happens after the order? If these are answered on the site, the enquiries you receive will be better too.
Which features do you really need?
Tie every feature to a concrete user task. A booking tool is useful if there are real time slots and real people behind it. A client portal makes sense if clients regularly check documents or statuses.
Anything without an owner can safely be left out of the first version. That was the key with our own product, DogDietLab: the first working version took about two weeks, because we only built what it couldn't work without. Still, leave room in the plan for later additions.
List integrations separately: CRM, newsletter, payments, invoicing, booking or other company systems. Don't just write "we need integrations", but what data needs to go where, and when. With Agrider the precise requirement was that the machine stock loads automatically from an XML feed instead of being typed in by hand. Described at that level of detail, the work can be estimated.
WordPress, a ready-made platform or custom development?
The choice depends on content editing, business functions, hosting and future changes, all together. There is no platform that suits everyone.
On a content-heavy site the editing workflow matters most. On a client portal it's permissions and data flows. For a fast-changing service it's development flexibility. On a multilingual site it's how translations and URLs are handled, which we lived through four times over with the four country stores of Melini.
A site built with AI help still needs its functions, data handling, access rights and search visibility checked. A fast prototype doesn't replace a proper handover check. For the decision itself, the comparison of template vs. custom websites is worth reading.
What should you ask for on SEO and tracking?
SEO starts with the page structure. Every important page needs a purpose, its own title, description and clear text, and internal links should lead the reader on to related questions.
On a JavaScript-based site you need to check separately whether the content is visible to search engines. Our own site is built this way, so from time to time we fetch every URL as Googlebot and check that the text, title and description are in the HTML everywhere. A nice view in your browser is not an SEO check.
For tracking, keep a button click and a successful form submission separate. A click on a phone number doesn't mean a conversation happened either. To judge business value you also need feedback from sales.
How do you compare quotes?
Send the same brief to every candidate and ask them to state separately:
- the pages and features to be built;
- who is responsible for copy and images;
- how many revision rounds are included;
- the integration and tracking work;
- one-off and recurring costs;
- the terms for handover, access and maintenance.
Two similar totals can hide very different amounts of work. I wrote more about pricing in the website cost guide, and about timelines in this article.
What should you check at handover?
Walk through the main path on your phone too. Is the offer clear? Does the menu work? Can the form be filled in? Does the enquiry arrive where it should? Is there a confirmation, and does the site handle mistakes in the form? We had good reason to take the last two seriously on our own site: because of a hidden spam-trap field, messages filled in by the browser's autofill weren't reaching us for a while.
Ask for the access details, an editing guide and the name of whoever is responsible for maintenance. When replacing an existing site, there should be an old-to-new URL list and a tested redirect plan.
Make the handover criteria checkable. Instead of "modern and fast", agree on specific page types, test cases and the bugs to be fixed.
Frequently asked questions
Is a single page enough for a company?
For a single offer and a simple customer journey, it can be. If you have several services that people search for separately, separate pages help visitors find their way.
Who writes the copy?
This needs to be settled in the quote. The business brings the expertise; the web copy can be written by the developer or a copywriter under a separate agreement.
Do I have to start a blog?
No. Get the service pages and the contact path right first. A knowledge base is useful when you can regularly answer real client questions.
Can the site be extended later?
Yes, if the content system and the page structure support it. It's worth mentioning likely extensions in the brief already.
What should I send with my first quote request?
The main business goal, your services, the features you need, the address of your current site and your planned deadline. Also say what content is already ready.
Planning a company website, or replacing the one you have? Send me your goal and the features you need, and we'll talk through the best way to start.
Background for the technical part: Google JavaScript SEO basics.

