02 / THE SCOPE

A complete website,
ready for launch.

Thirteen work items, organised into four practical workstreams. These describe the agreed scope, not completed delivery.

GROUNDED IN YOUR EXISTING WEBSITE

Clearer journeys for patients, families and professional referrers.

Your current site presents psychiatric assessments, treatment and medico-legal reports. The refresh should make those service pathways easier to understand, while carrying forward approved content, consultation options and professional information.

HomeServicesAbout UsContact Us

These are the main pages observed on the current site, not a final page inventory. Its “Book a consultation” link leads to Contact Us. Phase 1 provides an enquiry journey; new appointment scheduling remains outside scope.

Reference: existing PsychCare Online website ↗
A

Establish the foundation

A secure starting point, with visibility over access and spend.

3 items
1.1AWS account foundation

One AWS account, organised with AWS Organizations from day one. A starting structure that can support additional accounts as the platform grows.

1.2Guardrails & cost baseline

Least-privilege access, root MFA, CloudTrail activity logging, cost allocation tags and Budgets / applicable Free Tier alerts.

1.9Hosting infrastructure as code

S3 stores the site; CloudFront delivers it quickly; ACM provides TLS certificates. Terraform makes the setup repeatable and reviewable.

B

Create the website experience

A clear, accessible home for PsychCare Online.

4 items
1.3Design system

A modern, responsive brand refresh with accessible layouts and WCAG-informed design.

1.4Static website & content migration

Rebuild the existing pages in Next.js using static export, and move the approved content from WordPress.

1.6Search engine essentials

Page metadata, structured data, sitemap and permanent (301) redirects to preserve existing URLs where needed.

1.8Installable web experience

A PWA manifest, icons, service worker and offline shell. Visitors can install it where their browser supports it; this is a frontend-only feature.

C

Connect enquiries & insight

The essentials for a useful, measurable website.

2 items
1.5Serverless contact form

API Gateway receives enquiries, Lambda validates and processes them, and SES sends the notification email. Spam protection is included.

1.7Analytics with consent

Google Analytics 4 through Google Tag Manager, with consent handling to control analytics activation.

D

Deliver & launch with confidence

A repeatable release process and a carefully checked cutover.

4 items
1.10DNS migration & email continuity

Move DNS hosting to Route 53, carry over Microsoft 365 MX, SPF and DKIM records, verify TLS and complete the go-live cutover.

1.11Source control

A GitHub repository with branch protection and appropriate secrets management.

1.12Automated deployment

GitHub Actions builds the site, publishes to S3 and invalidates CloudFront as needed. Keyless OIDC provides access to AWS.

1.13Quality assurance & launch

Cross-device checks, Lighthouse and performance review, accessibility checks, form testing and client sign-off.

03 / THE BIG PICTURE

Simple on the surface.
Strong underneath.

JAMstack, in plain English: ready-made web pages, with small on-demand services for the actions that need them.

01

When someone visits your website

The site is ready to serve, without a WordPress server running behind every page.

ROUTE 53 · DNSFinds the website address, like a directory. Your browser then connects securely.
Your visitorOpens PsychCare Online
CLOUDFRONT + ACMFast, secure deliveryDelivers pages over HTTPS
AMAZON S3Website filesStores the exported Next.js site

CloudFront serves cached pages near visitors and retrieves files from S3 when needed. Route 53 directs the browser; it does not handle the page content.

02

When someone sends an enquiry

A short, on-demand journey from the contact form to your existing inbox.

WEBSITEContact formVisitor submits an enquiry
API GATEWAY + LAMBDACheck & processValidate input and apply spam controls
AMAZON SESSend notificationDelivers the enquiry by email
MICROSOFT 365Your existing inboxThe team receives the message
HOW UPDATES REACH THE SITE

Approved change in GitHub automated build publish to S3 refresh CloudFront

Keyless AWS access · repeatable releases · infrastructure defined in Terraform
THE ADVANTAGE / BUILD ONCE, GROW IN STAGES

A foundation for a
fully modern platform.

Phase 1 establishes the infrastructure and delivery backbone for future services. The same approach can underpin a wider platform with connected workflows and agentic AI: software that can carry out approved, multi-step tasks across connected systems.

Three layers: Phase 1 foundation, future connected services, and future agentic AI workflows.
PHASE 1 · IN SCOPE

Website & cloud foundation

AWS account structure · access controls · activity logs · cost visibility · APIs · automated releases

FUTURE PHASES · SEPARATELY SCOPED

Connected business services

Lead management · booking · payments · data integrations · customer communications

LONGER-TERM DIRECTION · NOT INCLUDED

Agentic AI across the platform

Assist with enquiries, coordinate administrative tasks and support staff workflows with defined permissions and human approval where needed.

Phase 1 creates a starting foundation, not a finished AI platform. Future AI work needs its own data design, integrations, permissions, privacy review, evaluation and monitoring. AI services and their running costs are outside this scope.

01

Less routine upkeep

Static pages reduce the moving parts and plugin maintenance of a traditional WordPress site.

02

Controlled expansion

Add services as needs become clear, with an account structure and delivery process already in place.

03

A practical path to AI

Defined APIs, controlled access and repeatable deployment provide useful building blocks for future automation.

04 / DELIVERY & LAUNCH

From foundation
to a confident go-live.

Approximately 15–26.5 working days of effort, across 3.5–6 elapsed weeks. Timing depends on content, access and review turnaround.

  1. 01

    Align & establish

    Confirm content and design direction, resolve launch decisions, establish the AWS account and guardrails.

  2. 02

    Design & build

    Create the responsive website, migrate content and add the contact form, SEO, analytics and PWA essentials.

  3. 03

    Connect & verify

    Put hosting and automated releases in place. Prepare DNS records and test the complete visitor journey.

  4. 04

    Approve & launch

    Complete client review, cut over DNS, verify the live site and confirm Microsoft 365 email continuity.

What “ready to launch” means

  • Agreed pages and migrated content reviewed
  • Responsive layouts, accessibility and performance checked
  • Enquiries delivered and spam controls tested
  • Redirects, metadata, sitemap and consent checked
  • HTTPS, DNS and Microsoft 365 records verified
  • Installable PWA and offline shell tested
  • Automated release process verified
  • Client sign-off recorded
05 / COST & ASSUMPTIONS

Small running costs.
Clear expectations.

The supplied SoW estimates remain the planning baseline. Confirm the final forecast against the chosen services, traffic and account eligibility.

EXPECTED AWS RUNNING COST*$3–8/ month

Low-traffic planning estimate from the supplied SoW.

MONTHLY BUDGET TARGET*≤ $15/ month

Monitored with alerts. A target, not an enforced spending cap.

Keep these assumptions visible

  • Serverless does not mean zero total idle cost. Some services have recurring charges; Route 53 hosted zones are one example. Usage, logging and optional services can add cost. AWS DNS pricing ↗
  • Budget alerts are not a hard cap. Notifications can arrive after charges are incurred. Review the forecast and agree how alerts will be handled. AWS Budgets guidance ↗
  • Free Tier depends on account eligibility and plan. Do not assume 12 free months. Current new-account free plans last up to six months, and joining AWS Organizations triggers an upgrade to the paid plan. Confirm applicable credits and allowances during setup. AWS plan guidance ↗
  • GitHub builds target $0 within included allowances. Confirm the repository plan, runner choice and usage. No unlimited free build commitment is implied.
  • Optional WAF changes the forecast. The SoW allowance is approximately $5–10/month extra; actual charges depend on the selected protection and traffic. AWS WAF pricing ↗

* AWS figures are in USD, not GBP. These are operating estimates, not a fixed quote or an implementation fee. Confirm taxes, traffic and any separately billed subscriptions before approval. This page describes the planned customer website; its hosting estimate is not a quote for this shared brief.

06 / DECISIONS TO MAKE

Four choices
to close the brief.

These remain open from §9 of the supplied summary. They are discussion items, not assumed decisions.

01

Who should we benchmark?

Name the competitor websites that should inform the design and content review.

To confirm
02

Include AWS WAF?

Agree whether to add the web application firewall, and confirm its effect on the monthly budget.

To confirm
03

How will content be edited?

Choose developer-managed updates or a headless CMS. Confirm any CMS cost and scope impact before including it.

To confirm
04

What comes first in Phase 2?

Prioritise the next services and automation opportunities based on the business’s needs.

To confirm
SAVED FOR LATER

A focused Phase 1 keeps delivery clear.

The following are deferred or outside the current scope:

Lead managementEmail automationAI chatbot & agentic AIOnline bookingOnline paymentsPWA push notificationsEmail-provider migration

Microsoft 365 → Zoho migration is not included. Future platform capabilities will be scoped and costed separately.

THE PHASE 1 OUTCOME

A launchable website today.
A platform to build on tomorrow.

Modern website · preserved email · clear cost visibility · room to grow

This client brief organises the Phase 1 summary supplied for PsychCare Online. It is not a delivery status report or a replacement for the signed Statement of Work. The delivery sequence and future-platform diagram explain the approach; they do not add contracted deliverables.

Implementation terms. Specific services and APIs may be adjusted during implementation to balance cost and performance, while preserving the agreed Phase 1 scope and functionality. Any material impact on the agreed budget, timeline or deliverables will be discussed and agreed with the client before proceeding.