Case study · consulting practice

CloudPlan.ca

Cloud and DevOps advisory for Canadian small and mid-sized businesses, productized around one entry offer: a Cloud Rescue Audit that maps what exists, what is risky, and what to fix first.

Illustration of the CloudPlan.ca website
Role
Owner, service designer and builder
Status
MVP website, live
Stack
Static HTML, CSS and JavaScript. No database, no frontend secrets
Live
cloudplan.ca

The problem in one sentence. Plenty of businesses already have cloud services, Microsoft 365, backups, GitHub, Docker and a list of vendors — what they do not have is anyone who can say which of it is load-bearing, which of it is a risk, and what to do about it on Monday.

What I built

  • Homepage messaging focused on cloud planning, DevOps advisory, security baselines, cost control, and backup and recovery planning.
  • A Cloud Rescue Audit section with a plain-language deliverable and a 30/60/90-day roadmap, so the buyer knows exactly what arrives.
  • Service positioning for fractional DevOps leadership, monitoring and observability, Microsoft 365 and cloud security, and recovery planning.
  • A static implementation that runs on simple hosting with no backend dependency to maintain or patch.
  • Repository documentation stating the safety rules around secrets, passwords, API tokens, private keys and hosting credentials.

How it is built

A named offer, not a brochure

The Cloud Rescue Audit gives the site a commercial entry point. A generic consulting page asks the visitor to invent the engagement; a named audit does not.

Static on purpose

No database, no application server, no admin login. The smallest attack surface that can still do the job, and nothing to patch at 2am.

Written for the buyer

Plain language for business owners, with the senior cloud, security and recovery depth sitting underneath rather than on the surface.

Public-safe by policy

The repository states what may never appear in it. That rule is the reason the site can be public and the work behind it can stay private.

Why it is in the portfolio

Running the practice is the point. It is one thing to hold a senior infrastructure role; it is another to define the offer, price it, build the thing that sells it, and carry the operational responsibility for keeping it up.

It also keeps me honest. Advice I give to a team is advice I have had to take myself, on my own budget.