---
title: "How a project runs"
description: "From the first email to handover: scope, quote, build window, cutover, documentation and follow-up, plus a condensed sample log."
canonical: "https://localdeploy.dev/process"
source: "content/pages/process.md"
lang: "en"
altPath: "/zh/process"
---


## From email to handover

| Stage | What happens | What you get |
|---|---|---|
| Day 0 | Email with your setup and goal | A reply within two business days |
| Day 1–2 | Scope call: what is in, what is out | A written scope and quote |
| Build | Work in agreed windows, on your machines | Changes, verification, a rollback path |
| Cutover | Switch hostname by hostname | The old path kept until you are happy |
| Handover | Documentation and a recording | A runbook you can follow without me |
| Follow-up | Agreed window after delivery | Questions answered, loose ends closed |

## A sample log

Anonymised and condensed: a NAS with eight services, six working days.

- **Day 0 — intake.** Eight services listed, two without health checks, one certificate expiring in nine days. Reply same day with the missing questions.
- **Day 1 — scope.** Agreed: entrance, certificates and a route table. Excluded: rewriting the applications and the mail server. Quote sent.
- **Day 2 — inventory.** Ports and upstreams mapped, a snapshot taken, the old proxy config copied for rollback.
- **Day 3 — build.** Traefik running in parallel on a spare port, DNS-01 staged, four low-risk hostnames prepared.
- **Day 4 — first cutover.** Four hostnames moved; one had HSTS pinned to its old certificate and was rolled back within the window, then fixed and moved the next day.
- **Day 5 — second cutover.** Remaining three moved; the old proxy stayed in place for a week.
- **Day 6 — handover.** Route table, verification commands, rollback steps and a recording. Follow-up window agreed.

What went wrong is part of the record: the HSTS hostname and the fix are in the handover notes, not hidden.

## What gets written down

- The agreed scope and what is explicitly out of it.
- Every change, with the command or config that made it.
- How to verify it, and how to roll it back.
- Open items and the follow-up window.

Client names, addresses and credentials stay out of public notes.

## Next

- [Selected work](/work)
- [Deployment areas](/services)
- Email `hello@localdeploy.dev`

## Structured data

```json
{
  "@context": "https://schema.org",
  "@type": "WebSite",
  "name": "localdeploy.dev",
  "url": "https://localdeploy.dev/",
  "description": "localdeploy.dev helps home labs and small teams assess the hardware they already own, then deploy a local AI assistant with Cloudflare, self-hosting and containers. Free basics, fixed-scope deployment packages, clear boundaries."
}
```
