SiteMonk

WORKFLOW

From your first idea to a website we look after.

What do you need to prepare? When do you see the website? How do you change it after launch? Follow one child care center through a website build and Care. MVP development, independent design, and advisory have their own scopes and billing.

Read the thinking behind these choices
  1. 01 Plan & build

    Build

    Web development, custom professional design and mobile experience.

    Your ideas

    A website that works for you

  2. 02 Launch & protect

    Care

    Hosting, security, backups and monitoring.

  3. 03 Keep it current

    Improve

    Monthly reviews, updates, fixes and improvements through SiteMonk Care.

Delivery workflow

First, agree on what the website needs to do.

We start with your business and the questions your customers ask. Together, we decide which pages you need, what goes on them, and what visitors should be able to do next.

Loose black-and-white fibers become an ordered woven strip with one thin blue thread. Text: “A clear plan comes first”.

You provide or approve the business information. We organize it into content and design, build the agreed pages, and give you a preview to review before launch. We check each page on mobile, test its links and forms, and prepare it for search.

For a standard website, the build price and reasonable scope are confirmed in writing before work begins. The proposal identifies core pages, supporting pages, functions, responsibilities, and any separately priced features. We do not charge per page. Larger or different projects are assessed separately.

01 / The page lifecycle
Business questions lead to a page plan, content and design, development, release checks, publication, and a review that informs the next update.

Business questions lead to a page plan, content and design, development, release checks, publication, and a review that informs the next update.

Plan and design
Identify the visitor's question, connect the page to related information, organize approved content under descriptive headings, and define a useful next step.
Build and review
Deliver readable HTML, configure page metadata and search controls, check mobile and keyboard use, and validate the published result.
Maintain
Apply the same standards to new pages. Investigate issues after changes and use available search and usage evidence to decide what needs attention.

Agree on the work, review the result, and approve a checked version for launch.

See website pricing and scope

Design process

From visual direction to a consistent, usable website.

We clarify the goals and visual requirements, compare directions, test representative pages, and establish shared rules before completing the website. Bring your existing materials; we turn them into outcomes you can review.

The seven stages below can overlap. Your main decisions concern scope, direction, representative pages, and the final version to publish. We handle the checks between them. The full page explains deliverables, HTML/CSS previews, and the existing revision and extra-work terms.

Scroll horizontally to see all columns.

What each main review decides
Review What you see What to check What it establishes
Scope and requirements Project summary and visual references Business facts, priorities, and materials Agreed scope and visual requirements
Visual direction Two comparable direction samples Brand feel, preferences, and specific changes The direction to use in representative pages
Representative pages Real-content HTML/CSS previews Reading, hierarchy, mobile layout, and main actions A tested basis for shared rules and remaining pages
Final website A specific checked version Publishable content and included visitor paths The approved version to publish
  1. Agree on goals, scope, and visual requirements

    A project summary, visual references, and a clear account of materials still needed.

  2. Compare two visual directions

    Samples you can compare, with reasons for the visual choices and specific feedback to carry forward.

  3. Validate representative pages

    Real content, desktop and phone layouts, and key actions tested before the design expands.

  4. Establish shared rules and components

    Reusable text styles, buttons, navigation, and form states that keep the website consistent.

  5. Complete the agreed pages and states

    A whole-site preview covering page templates, content differences, and responsive behavior.

  6. Check the actual website together

    Design and implementation compared, included key paths tested, and important issues fixed and rechecked.

  7. Approve, launch, and arrange care

    The checked version published, the live result verified, and handover and contact points made clear.

A direction tested in real pages
Direction samples make choices visible; representative pages then test whether those choices support the actual content and tasks.
Shared rules that carry through
Validated typography, colors, components, and states carry into the remaining pages. Content and width changes are checked as the site grows.
The implemented result is checked
We compare the website with the confirmed design and test included actions. You approve a specific version before publication.

Every stage has a clear outcome and checks. Your decisions and the agreed revision rounds are recorded.

Read the full design process

Content updates

Need a change? Review it before it goes live.

Opening hours change, a new service starts, or a photo needs replacing. You send us the update and confirm the information; we prepare the change for review. If an editing system is included in your plan, you can make the agreed types of updates there.

Two offset print proofs carry black-and-white halftone curves, with a tiny blue registration tick. Text: “Review before release”.

We check the updated pages before publishing, then check the live result. If a release causes a problem, we can restore a known website version and investigate any connected services.

03 / Edit, preview, publish, recover
An approved source or CMS edit produces a build and preview. Checks either return the change for correction or allow a release. A post-release issue can trigger restoration of a known version.

An approved source or CMS edit produces a build and preview. Checks either return the change for correction or allow a release. A post-release issue can trigger restoration of a known version.

Editorial input
The client supplies or approves the domain content. A CMS, when included in scope, gives editors an interface for frequent updates while templates maintain the page structure.
Preview checks
Review content, links, metadata, applicable schema, mobile layout, and interactions. Changed URLs need redirect and canonical checks.
Recovery boundaries
A website rollback restores the website release. It does not reverse a payment, CMS edit, or other external service operation; those have separate recovery procedures.

An edit becomes a checked release, with a defined way back.

Ongoing care

After launch, keep the website working and useful.

Care begins when the website launches, with the plan selected before launch. It covers websites we build. Every plan includes hosting, security, backups, monitoring, necessary software updates, and a monthly SiteMonk System report. Monitoring covers the agreed pages and functions with the tools and access available.

One report a month in your client portal: what we fixed, what we improved, and what we found, including a search check-up of how search engines and AI systems read your site and what we would fix next.

Your requests use a separate monthly budget. Common maintenance and the plan's proactive search work do not use that budget. When the request budget runs out, new requests wait for the next month. Larger additions need an agreed scope and cost before work begins; a separate MVP project does not automatically fall under website Care.

When a covered problem occurs, we find the cause, make the appropriate fix, and verify the result. Search work, request capacity, and support channels differ between plans as shown below. Rankings, traffic, and AI recommendations are not guaranteed.

A short bridge reconnects a gap in a black-and-white circuit trace; a small blue test point marks verification. Text: “Trace, fix, verify”.

Scroll horizontally to see all columns.

What differs between Care plans
Plan Your requests Proactive search work Support
Care Plus Room for occasional updates. A monthly search check-up report in your client portal, with what we would fix next. Email
Care Pro Room for frequent pages and campaigns. The monthly report, and each month we pick one improvement from it and do it. You do not have to ask. Email, WhatsApp text chat
Care Max Room for ongoing content and integrations. Everything in Care Pro, plus one to two article drafts a month on topics you confirm. Nothing is published until you approve it. Email, WhatsApp text chat, WhatsApp voice calls
04 / The maintenance cycle
Checks and available reports reveal an issue. Diagnosis leads to a scoped correction or proposal, a reviewed release, and a verification that feeds the next round of checks.

Checks and available reports reveal an issue. Diagnosis leads to a scoped correction or proposal, a reviewed release, and a verification that feeds the next round of checks.

Detect and diagnose
Check the page and affected service, identify the actual cause, and record what needs to change. Search Console and available usage reports can inform the investigation.
Make the appropriate change
Maintain existing functionality within the agreed care scope. Assess larger changes separately so the owner, cost, and business purpose stay clear.
Verify and learn
Recheck the published page and connected workflow. Watch available evidence for the effect of the change, and retain findings that improve future decisions.

Common care continues between requests; each plan also defines the request budget, proactive search work, and support.

See current Care fees and detailed scope

Handover & costs

If you move on, know what you take with you.

Your domain stays under your control. If another developer takes over, we provide the full website source, content and assets, instructions to build and publish it, and a list of the accounts and services it uses. The receiving environment must support the site's actual functions and dependencies.

We clarify account ownership and access, along with ongoing costs such as the domain, hosting, and external services. When arranging a move, the plan needs to include checks that pages, links, and forms still work in the new setup.

05 / What travels with the website
Source code, build instructions, content and assets, service and account information, and URL rules form a handover. A successor deploys to a suitable environment and checks the public pages and integrations.

Source code, build instructions, content and assets, service and account information, and URL rules form a handover. A successor deploys to a suitable environment and checks the public pages and integrations.

Technical handover
Provide source, dependency and build information, deployment instructions, the content structure, and the configuration needed to operate the website.
Accounts and dependencies
Identify domain, hosting, CMS, and service ownership. Arrange appropriate access transfer; keep secrets out of public documentation and source bundles.
Separate the costs
Domain renewal, hosting usage, external services, and SiteMonk's subscription are different costs. Static delivery can reduce runtime maintenance; actual fees depend on selected services and usage.

Portability needs code, operational information, and a checked transition.