Website Services

Website work is urgent when a customer can find the business but cannot complete the next useful action: locate current hours, understand a service, or send a request from a phone. The first diagnostic is a task path, not a visual opinion. Follow one real customer intent from an external listing or search result to a successful contact, and record every point where stale copy, a broken control, or missing ownership blocks completion.

This guide applies the general Starter Library method to website services. Use G01 for opportunity selection, G03 for AI verification, G04 for demand evidence, G05 for setup, G06 and G07 for customer contact and selling, G08 for pricing, G09 for service recovery, G10 for cash discipline, G12 for workflows, and G13 for contracts and privacy. Those guides carry the shared method; the sections below cover the operating decisions that change when this specific service is delivered.

Opportunity and Customer

The buyer group is Small local practices, independent shops, and service businesses that need a simple informational site with a clear contact path, not a complex commerce platform.

The recurring problem is Existing pages contain outdated hours or prices, are hard to use on a phone, lack accessible structure, and make the next step difficult to find.

The paid result is A small, maintainable website with approved content, mobile-friendly navigation, an accessible contact path, and an owner handoff guide. Progress must remain inspectable, and consequential changes require the buyer's named approver.

The operating boundary is You build and maintain the agreed pages. You do not invent credentials, testimonials, service claims, legal policies, or accessibility compliance certificates.

Demand evidence

Look for evidence in the public customer journey: an outdated hours page, a service menu that conflicts with a booking page, a phone layout that obscures the contact route, or a request form with no visible confirmation. Ask when the site was last updated and who controls the domain and hosting accounts. A recent staff change or unavailable former developer can explain why the issue persists, but it is not enough by itself. The buyer should describe at least one lost or delayed customer task, and the paid audit should make that path testable without promising a redesign outcome.

Fit and Skills

The fit assessment is Suitable if you can structure content, use a constrained site builder, check devices and keyboard navigation, and resist adding every feature a client requests.

The minimum skill set is Practice semantic headings, responsive layout, image alternatives, form error states, basic performance checks, content editing, backups, and a limited page-template workflow.

Use G04 to test buyer demand for website services after building this guide's artifact; capability alone is not proof.

Capability artifact

Create a four-page fictional site for a bicycle repair shop. Include services, current opening hours, a repair-request form, one approved image, and a phone contact path. Test with the keyboard, a narrow screen, a missing email field, and a simulated form-service failure. Write a handoff that tells the owner which fields they may edit and which changes require a new scope.

Startup Budget

These website services USD ranges are planning inputs; confirm each cost with current local quotes and keep first-test loss affordable.

• Domain and a simple hosted site: 20 to 250 USD per year and 0 to 40 USD monthly.
• Approved stock imagery or icon license: 0 to 100 USD.
• Accessibility and link checking tools: 0 to 50 USD monthly.
• Testing devices or browser services: 0 to 150 USD.
• Template or learning material: 0 to 200 USD.
• Contingency for hosting and content corrections: 50 to 200 USD.

Skill Acquisition

Operating sequence

Inventory the current pages and page owners, collect approved facts into a content sheet, choose a small page set, build a development copy, test navigation and forms, obtain a named approval, publish during an agreed window, and preserve the prior site. Every page receives a purpose, primary action, content owner, and last-reviewed date. Images need permission and descriptive alternatives; phone visitors need tap-friendly controls and readable text.

Acceptance test

A page is not ready because it looks polished. Test the main path at phone width, by keyboard, with missing form values, and with a failed submission route. Check headings, link labels, image alternatives, contact details, and the destination of every action. Record known accessibility limits and do not claim a full compliance audit. A person who owns the business facts approves the exact published version.

Setup

Create a development site separate from production, record domain ownership and recovery access, define who approves copy and images, and keep a rollback copy before publishing.

Launch controls

Separate development from production, confirm who owns the domain and hosting accounts, and record recovery access without copying passwords into project notes. Take a backup before publishing. Approve copy, prices, hours, images, and contact routes in writing. Keep the development site out of public indexes and verify that test submissions do not reach the customer's live queue.

Use G05 and G13 for jurisdiction-specific setup, privacy, and legal questions.

Concrete Offer

A four-page starter site with home, service, about, and contact pages. Includes one approved content workshop, responsive layout, a working contact route, basic accessibility checks, one correction round, and a handoff recording how to edit approved fields.

First acceptance evidence

The proof is a launch record showing the exact approved pages, the tested customer task, defects found and corrected, the publishing window, and the rollback location. Include a five-minute handoff session in which the owner completes a routine edit and demonstrates where a broken form would be reported. That evidence is more useful than a promise about traffic.

Use G07, G08, and G13 to write the scope, payment, approval, and stop condition.

Outreach

Send one specific observation about a page or contact path. Offer a short paid audit when the owner is unsure, and avoid implying that a redesign will guarantee customers.

Look for businesses whose current site is broken, has stale hours, lacks a mobile contact route, or is being created through an unavailable former developer.

Acquisition test

Review fifteen local sites and select only prospects with one concrete issue such as outdated hours, a phone page that hides contact details, or a request form that lacks an error state. Lead with a paid page-path audit when the owner is not ready to buy a build. Do not claim that a redesign will increase sales; sell the verified task improvement and the approval process.

Use G06 for the lawful contact method and record each reply and next action.

Pricing and Unit Economics

An illustrative starter build is 800 to 3,000 USD. Ongoing approved edits may be 75 to 250 USD monthly or a fixed hourly/block rate. Keep hosting, domain, third-party fees, and major content writing separate.

Count discovery, content cleanup, design, build, device checks, publishing, training, and correction. Template reuse improves margin, but each site still needs content approval and testing.

Illustrative floor calculation

An illustrative four-page build might use 5 units for content cleanup, 18 for layout and build, 5 for device and keyboard checks, 3 for publishing and handoff, and 2 for corrections. At 45 units per direct hour, planned labor is 1,485 USD before hosting, domain, sales, and tax. A 1,600 USD fee leaves little room for repeated copy changes, so the first offer should state one consolidated correction round and a separate maintenance option.

Use G08 and G10 to set a local floor; contribution is not owner pay.

Delivery Example

The example below is an illustrative composite, not a real customer record or income promise.

A repair shop needs updated services and a clear request route. You build four pages on a managed template, use the owner's approved photos, add alternative text, test the form, and record who owns the domain. The illustrative fee is 1,600 USD plus hosting. The owner can update hours without calling you.

Delivery trace

At the repair shop, the first review identifies an old emergency number, the second confirms the photo permission, and the final test sends two requests to a sandbox inbox. The owner edits the Saturday hours after the handoff and sends the confirmation screenshot. Delivery is accepted only after the live contact path is tested and the rollback copy is identified.

Growth

Offer a small maintenance plan for approved text changes, broken-link checks, and backup confirmation. Add booking or commerce only after a separate scoped test.

Scale boundary

Repeat one constrained site type and a common quality checklist before taking larger commerce or booking projects. A maintenance block can cover approved field changes and link checks, but it needs a response window and a stop rule for feature requests. Keep a weekly sales conversation even when build work is full, because each site is a finite project rather than recurring coverage.

Use G14 before expanding website services capacity, a customer segment, or a service line; protect delivery quality first.

Risks

• Publishing incorrect service, price, legal, or safety information.
• Losing domain or hosting control because accounts are in an unknown name.
• Claiming full accessibility without a qualified audit.
• Untested forms silently failing or sending messages to the wrong recipient.

The controls above are the early-warning route. Jurisdiction-specific professional review still applies.

Privacy and AI Verification

Use approved images and customer information. AI can draft page structure or alternative text, but a human must verify facts, names, permissions, and accessibility context. Keep analytics and form data limited to what the client actually needs.

Apply the authorization, minimization, verification, and deletion process in G03, G12, and G13.

30-Day Action Plan

• Days 1-4: choose one local business type and inspect ten public websites for concrete usability issues.
• Days 5-8: build a four-page sample for an illustrative business and test phone, keyboard, links, and form errors.
• Days 9-12: create a content request, approval form, and handoff checklist. Confirm who owns the domain and hosting.
• Days 13-20: contact fifteen businesses using one truthful observation. Offer a paid audit or starter build.
• Days 21-26: deliver one approved build or audit, record actual hours, and ask the user to complete one common task.
• Days 27-30: review scope, price, and corrections. Keep the offer, narrow it, or stop based on evidence.

At day 30, continue, revise one variable, or stop.

Day-30 decision record

At day 30, record paid website services tests, costs, delivery time, rework, exceptions, one objection, and one approval delay.

Templates

Template 1

Content approval: The client confirms that names, services, prices, hours, qualifications, and photographs are accurate and authorized. The provider does not independently verify regulated or professional claims.

Template 2

Launch checklist: domain control confirmed; production backup created; pages reviewed; contact route tested; headings and images checked; analytics minimized; owner handoff recorded.

Template 3

Maintenance request: Describe the approved field to change, old value, new value, desired date, and approval contact. Changes outside the agreed fields receive a separate estimate.

Adapt contract language through G13 and local professional review.

Related General Guides

• G01, Finding a Business Opportunity That Fits
• G03, AI Assistant Basics
• G04, Validating Demand
• G05, Business Setup
• G06, Finding Customers
• G08, Pricing Services
• G09, Customer Service
• G11, Marketing Fundamentals
• G13, Contracts and Privacy
• G14, Sustainable Growth

Read the linked general guides for shared definitions, customer acquisition, pricing method, service recovery, cash discipline, workflow design, and legal and privacy controls. This specialized guide intentionally stays focused on website services operations.

Key Takeaways

• The proof is a launch record showing the exact approved pages, the tested customer task, defects found and corrected, the publishing window, and the rollback location.
• A page is not ready because it looks polished.
• An illustrative four-page build might use 5 units for content cleanup, 18 for layout and build, 5 for device and keyboard checks, 3 for publishing and handoff, and 2 for corrections.
• Review fifteen local sites and select only prospects with one concrete issue such as outdated hours, a phone page that hides contact details, or a request form that lacks an error state.
• Repeat one constrained site type and a common quality checklist before taking larger commerce or booking projects.
• Keep the service boundary, named approver, and stop condition in every offer.
• At day 30, decide from paid delivery evidence and actual contribution.