“Deploy” should be the least interesting word in your team’s vocabulary. If releases involve a checklist, a specific person, or a quiet Friday, the pipeline is the product blocking your product.
The minimum viable pipeline
For most teams, four stages cover 95% of the value:
- Lint and typecheck — catch the cheap mistakes in seconds.
- Test — run the suite on every push, not just before releases.
- Build — produce the exact artifact that will run in production.
- Deploy — automatically to staging on merge; to production with one click or one tag.
That’s it. No Kubernetes required. A small team with this setup ships daily; a team without it ships monthly and calls it discipline.
Preview deployments change conversations
The highest-leverage feature of modern hosting platforms is the per-pull-request preview URL. Design review stops being “run it locally” and becomes “click this link.” Stakeholders comment on real behaviour instead of screenshots, and merge confidence goes up across the whole team.
Make rollback boring too
A deploy pipeline is only half done if rolling back is scary. Keep the last known-good artifact deployable at all times. The test we apply at Codefumes: could the newest person on the team roll back production alone, at midnight, without asking anyone? If not, keep simplifying.
Start this week
Pick your smallest project, add a workflow file with those four stages, and let it run for a week. The goal isn’t a perfect pipeline — it’s making shipping so cheap that improving the product becomes the only hard part left.