Website care pilot¶
Status: tooling ready; awaiting customer website URL, 2026-09-18
The first recurring-service pilot provides repeatable page checks and a monthly evidence report. No customer has been enrolled, contacted or billed. Customer identity/domain, maintenance scope, included work, price and response commitments still need to be recorded.
Procedure: ../sops/docs/SOP-032-website-care. Implementation:
assistant/scripts/website-care.py; configuration example and monthly report template are
in assistant/docs/website-care*.
The checker accepts 1–10 explicit public HTTPS URLs and records response status, page title and current TLS validation. It does not submit forms, crawl the website, run security scans or claim continuous uptime. Existing Uptime Kuma is the planned continuous-monitoring tool.
Run a reviewed configuration¶
python3 /home/angel/assistant/scripts/website-care.py --config /path/to/customer-pages.json --output-dir /path/to/private-reports
Example configuration structure (replace with the actual reviewed customer URLs):
{"pages":[{"url":"https://example.com/","expected_title":"Example Domain"}]}
Each run creates timestamped JSON and Markdown evidence. A monthly report adds monitored scope, incident history from actual monitoring, completed work, unresolved items and next actions. Unmeasured items remain explicitly unmeasured. Sending the report is a separate Sales action.
Draft recurring offer — internal, not sent¶
Start with one existing customer and one site. Sell a defined maintenance service, not a promise that a website can never fail. These are scope options, not approved pricing.
| Option | Included scope | Explicit limits |
|---|---|---|
| Care | Agreed public-page checks, configured uptime monitoring, monthly evidence report and issue triage | Fixes quoted separately; monitoring does not prove forms or checkout work |
| Care + updates | Care plus a fixed monthly allowance for approved text/image changes | Allowance, turnaround and rollover must be agreed; redesigns and new features excluded |
| Improvement partner | Care + updates plus one agreed small improvement per month and results review | Requires a scoped backlog; no ranking, traffic or sales guarantees |
The simplest pilot is Care + updates, provided the site stack and access allow safe changes. Use the existing checker and Uptime Kuma, not another subscription or custom portal. Backups, restoration, dependency updates and form testing are included only after separately confirming access, safe procedures and coverage. Do not imply these are already monitored.
Proposal copy for Sales review¶
I can keep looking after the website we built, with routine checks, a monthly health summary and a small allowance for updates. You would have one place to report issues and a clear record of what was checked and changed. Larger changes would be quoted separately before work starts. Once we agree the pages, update allowance and response window, I can offer a fixed monthly plan.
Before quoting: confirm site URL and platform, customer ownership/access, covered pages, monthly work allowance, support hours and response target, third-party charges, monthly fee, cancellation terms and exclusions. No enrollment, billing or customer contact is authorized by this draft. Operating procedure stays in SOP-032; this section only defines the offer.
Log¶
-
2026-09-18: Added three internal recurring-care scope options, a pilot recommendation, proposal copy and commercial-decision checklist. No price set and nothing sent.
-
2026-09-18: Prepared pilot, draft SOP-032 and report template. Four website fixture tests passed as part of 40 total workflow tests. No customer-facing checks or monitoring enrollment performed because the domain is not yet known.