Skip to content
MROOT

Website Care

Keep the small things from piling up.

An optional monthly plan for a supported website: routine maintenance, a health check and a small allowance for content changes. Agree suitability and access before starting.

What you get

A defined amount of help each month.

An optional monthly plan for a supported website: routine maintenance, a health check and a small allowance for content changes. Agree suitability and access before starting.

Included in the starting scope

  • Scheduled maintenance for an agreed, supported website
  • A monthly website health check
  • Up to one hour of small content edits each month
  • A record of work completed and issues needing attention

Care is for supported websites. New pages, redesigns and integrations are separate work. Emergency response is not guaranteed. Cancel anytime; existing client agreements remain unchanged.

The work behind the offer

See how the thinking takes shape.

Examples of the engineering behind maintainable content and resilient interfaces, with each project’s context made clear.

Independent portfolio · Web application

mroot.co

One content source supplies both a conventional portfolio and an IDE-style presentation, making the relationship between content and presentation explicit.

Marc’s own portfolio project. It demonstrates content architecture, not a Care Plan client result.

Read the project record

FiveM community · Full-stack project

Katie Monroe Photography

A gallery with bundled sample content when its API is not configured, paired with explicit delivery errors and private content tools.

A community project showing fallback design. It is not a claim about uptime, monitoring results, or an ongoing care engagement.

Read the project record

These projects show the thinking behind content maintenance and graceful fallback behavior. The Care Plan’s actual coverage is agreed for the website being supported.

Working together

Know what happens next.

Work directly with Marc from the first brief to the agreed handover.

  1. Describe the goal

    Share what the business needs or what your first users should be able to do.

    A useful brief

  2. Agree the work

    Review a written scope, the deliverables, a schedule and a final quote before work begins.

    A written scope and quote

  3. Build and review

    Work directly with Marc and review the important decisions as the build takes shape.

    A working version to review

  4. Launch and hand over

    Check the agreed journey, approve publication and receive the access and documentation needed to continue.

    An agreed launch and handover

For care, first confirm the supported platform and access, then agree the recurring checks and edit allowance.

Before you decide

The practical questions.

Clear expectations make a better project.

Compare services and prices
What is included at this starting price?

Care is for supported websites. New pages, redesigns and integrations are separate work. Emergency response is not guaranteed. Cancel anytime; existing client agreements remain unchanged.

What costs are separate?

Domain, hosting, subscriptions, messaging and usage charges are separate. Additional pages, features, integrations and migrations are quoted separately.

Is emergency response included?

Emergency response is not guaranteed. The plan covers agreed scheduled care and up to one hour of small content edits each month. Larger or urgent work needs separate scope.

Does sending a brief commit me?

No. The brief starts a conversation. Scope, timing and terms are confirmed before work begins.

Your next step

Tell me about the site you need to maintain.

Describe the goal, what you have now and any practical constraints. We can work out the right starting point.

Discuss website care