Identify the job your website should do
A corporate website can present company information and visitor paths in a structure you choose. Every business does not need the same extensive site immediately. Translate “we need a website” into a customer task: understand a service, review work, request a quote, buy a product or find a location.
A personal portfolio, company presentation and online shop require different scope. A small start may suit one clear service; online selling also requires order and operational processes. Review the content available and the capacity to maintain it. Assess benefits alongside the responsibility for running the site after launch.
Collect recurring customer questions and limitations in current channels. Which information is missing, and where does communication break down? A site that addresses these issues has a concrete investment rationale. Old internet-use percentages or a universal “everyone needs a site” statement cannot replace that assessment for your business.
Explain the business
Present services, examples and contact information. Begin with the scope needed to answer basic customer questions.
Show a portfolio
Explain your role and scope through permitted work examples. You do not need to publish the entire archive.
Sell products
Plan payment, orders, delivery and support alongside product details. A catalogue alone may not complete the task.
Show work and help visitors assess fit
Together with an About page, a portfolio helps visitors understand who you are and what you can do. Include the original need, scope and your role alongside a finished image. Do not attribute an entire project's success to your contribution. Explain actual responsibilities and use information you have permission to publish.
The original guide's example appears in Matt Mullenweg's 2017 account: Negele Hospedales built a website for an internship application and got the role. This illustrates a different way to present work, rather than proving a portfolio site will secure everyone a job. Choose genuine examples that your readers can evaluate.
Check the scope of awards, qualifications and testimonials if used. Do not create evidence that does not exist. Verify rights to references and images. A few explained examples may answer a customer's question better than an extensive gallery without context. Assess whether a reader can explain the work you actually provide.
FROM READING TO A NEXT STEP
Turn the website need into concrete scope
Share your current channels and recurring customer questions so we can define the first release's tasks.
Make information and contact paths accessible
A business website can answer repeat questions about hours, location, service area and contact methods. Accurate information may help customers and reduce repeated explanations for staff, without guaranteeing a particular saving. Getting essential details right matters more than adding pages that cannot be maintained.
A form or email address can accept a message at any hour; this is different from staff providing a response around the clock. Explain response expectations and the appropriate contact channel. In a controlled test, check successful submission, error handling, the help route and the person responsible for receiving enquiries.
For a local business, keep website and Business Profile details consistent. Google's business information guide describes separate management routes for the official site and profile. A profile can show contact details while a site explains services more fully. Neither a website alone nor a map listing guarantees customer visits or visibility.
Visibility and marketing need their own work
Content marketing can use the website as a resource answering customer questions. Social posts, email, advertising and search can lead to a relevant page. Publishing a site does not create traffic automatically. Audience, channel, content and budget belong in one plan; low cost and high conversion are not universal outcomes.
Sharing a portfolio or service link can reduce the need to repeat the same explanation in every message. Keep the opened page consistent with the campaign's promise. Distinguish the acquisition channel from the website's job: a campaign may attract interest, while the page supplies information and an appropriate next step. Every visitor will not become a customer.
A small business can participate in evaluation with useful, detailed content, but overtaking larger competitors or gaining organic leads is not guaranteed. Review channel traffic, meaningful enquiries and sales-team assessment together. Do not equate total visits with success. Consider missing information, unsuitable targeting and communication problems separately when results are weak.
Give social media and the site distinct roles
Your own content management structure can provide flexibility in organising services and examples. Social accounts may help with sharing, community and messaging. The channels can complement each other. Before deciding social media is insufficient, examine where customers communicate and which information or tasks remain unsupported there.
More control over presentation does not eliminate dependencies. Domains, hosting, CMS, payment services and other suppliers have conditions and access requirements. A website may remain available during a social-platform outage, but shared infrastructure or configuration problems can also affect it. Do not promise that all site content will automatically remain safe.
Keep links and information consistent across channels. A brief announcement on social media and a detailed service explanation on the site may work together. Identify the primary source for each type of information. If updates must be repeated in several places, assign ownership and review. Evaluate the control gained alongside the maintenance work created.
Start with a scope you can actually operate
Include hosting and website operations in the first publication decision. Decide who controls the domain and accounts, who updates text and who monitors failures. The budget may include licences, maintenance, content and ongoing services as well as initial design. Keep unnecessary expensive modules out of the first release.
Write a purpose and an acceptance exercise for each starting page. Use real tasks such as understanding a service, reviewing an example or finding a location on mobile. For online sales, complete the order and support flow beyond the catalogue. Separate visual approval from checks that demonstrate the task works. An automated score cannot describe the whole experience.
Decide what you want to learn after publication. Are recurring questions reduced, can suitable enquiries be followed up, and can content be maintained? Relate measurement to actual customer tasks. A website can be a useful investment when its rationale comes from a concrete need and sustainable operation, rather than ownership alone.
| Initial task | Required information | Acceptance exercise |
|---|---|---|
| Assess a service | Scope, suitable customer and example | Can a visitor explain what is offered? |
| Make contact | Channel, expectation and owner | Is the message received and error visible? |
| Find the location | Correct address and opening hours | Can a mobile visitor find the details? |
| Buy a product | Product and operational information | Can the order and support flow be completed? |
BEFORE YOU DECIDE
Frequently asked questions
Does every business need a large website?
No. Set scope around customer tasks, existing channels and maintenance capacity. A small, properly operated start may be suitable.
Can a social account be sufficient?
It may meet some initial needs. Review missing detail, presentation control and transaction flows, then give channels appropriate roles.
Will building a website bring new customers?
There is no guarantee from publication alone. A suitable audience, useful content, access channels and working contact or sales processes need to come together.
Does a site provide 24-hour customer support?
Information and message submission can remain available while staff response is a separate service. State working hours and response expectations clearly.
Does a local business site replace its map profile?
They serve different purposes. Keep profile information and website location or service details consistent. Neither presence alone guarantees visibility.
What can we defer initially?
Defer modules that do not support a core customer task. Keep accurate information, working contact paths, mobile readability and operational ownership in the initial scope.
LET’S DEFINE THE SCOPE
Turn the website need into concrete scope
Share your current channels and recurring customer questions so we can define the first release's tasks.
Discuss your website