The start page explains what to include and keeps the first email focused.
Contact points back to the same manual KITPro start path.
If you landed here first, the clearest next step is still /start. This page keeps the manual contact route visible without turning it into a second intake flow.
Best first stepUse /start when you want the clearest path.
Manual email remains the approved contact path across the preview lanes.
If you want examples before writing, the resources hub is the quiet preparation path.
Use /start when you want the most useful first email.
KITPro still uses one manual path. /start explains what details help Josh review fit, and it keeps the current public process clearer than using contact as a standalone intake page.
How to use contact
This page supports the same manual flow.
Contact is a support page, not a second intake path. It exists to keep the approved destination visible and to point visitors back to the clearest start flow.
Start page first
Use /start when you are ready to send the first note. It explains what context makes the first message useful.
First preview lane
Backup & Recovery Readiness is the first KITPro service lane being validated through manual conversations.
Simple first note
Share the setup you want reviewed, what backup process exists, whether a restore has been tested, and the best way to reply.
Manual response
There is no automated workflow behind this page. Josh reviews fit manually before suggesting a next step.
Manual email shortcuts
Choose what you want to ask about
If you already know the lane that fits, use one of these shortcuts. If not, keep /start as the default first step.
Safety note: Do not send login details, integration credentials, SSH credential files, recovery codes, full environment variable files such as .env files, or private client records by email.
Backup & Recovery Readiness
Best if backups, restore notes, and recovery readiness are the main concern.
Homelab / Small Server Readiness
Best if the small-server or homelab setup needs a broader readiness review.
Documentation / Runbook Cleanup
Best if the systems work but the notes, runbooks, or handoff steps are messy.
Website / Service Deployment Readiness
Best if the main issue is a site, app, deploy path, routing context, or restart flow.
Use the resources hub if you want a quieter starting point.
Not ready to email yet? The resources page has the backup checklist, lane-specific prep checklists, and the plain-English support material behind the current preview lanes.