Manual start

Start a practical KITPro conversation.

The current KITPro path is manual by design. Send a short note about what you run, what matters, and whether Backup & Recovery Readiness is the right first review lane.

Manual contactUse the approved email path.
01Start with context

KITPro conversations begin with a plain summary of what you run, what matters, and what kind of readiness question needs review.

02Keep the scope narrow

The first preview lane is Backup & Recovery Readiness Audit, focused on backup coverage, restore notes, and practical next-step recommendations.

03Stay manual for now

The public site keeps this path simple. Use the approved manual destination and include only the context needed to understand fit.

Want examples first? Review the checklist or compare the lanes.

Manual prep

Start with these details

Not sure what to include? Pick the lane that sounds closest and send the details you already know.

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

  • What needs to be backed up
  • Current backup tool or process
  • Where backups are stored
  • Last restore test, if any
  • What you are most worried about losing

Homelab / Small Server Readiness

  • What systems or services are running
  • Where they are hosted
  • What is exposed to the network or internet
  • How updates and backups are handled
  • What feels messy or fragile

Documentation / Runbook Cleanup

  • What needs documentation
  • Where notes live now
  • What steps are missing or outdated
  • What someone else would need to understand
  • What process breaks when notes are unclear

Website / Service Deployment Readiness

  • What site, app, or service is being reviewed
  • Where it is hosted
  • How it is deployed or restarted
  • DNS, proxy, and TLS details at a high level
  • What breaks if the host reboots
First email

Use the general template or keep the note simple.

A short note is enough. The goal is to make the first message useful, not polished.

What to include

  • Who you are and the business or project name
  • What system, site, server, or setup you want reviewed
  • What backup tool or process you currently use, if any
  • Whether you have ever tested a restore
  • What you are most worried about losing
  • The best way for KITPro to reply

What happens after you email

  • Josh reviews the message manually.
  • If it looks like a fit, Josh replies with a few follow-up questions.
  • If Backup & Recovery Readiness is the right first lane, Josh explains the manual review process.
  • Any deeper work, implementation, or follow-up support is a separate decision.
  • If it is not a fit, Josh may point you in a better direction.
Lane shortcuts

Choose a lane to email about

Already know which lane fits? Use one of these manual email shortcuts. If not, use the general template above or review the services page first.

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.

Not sure which lane fits? Review the service pages first.

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.

Fit check

Is this a good fit?

Use this quick check before sending the first email. KITPro is best as a manual readiness review conversation, not urgent support.

Good fit

  • You have important files, systems, backups, or restore notes you depend on.
  • You are not sure whether your backup process is enough.
  • You want a practical readiness review, not emergency recovery.
  • You can describe your setup at a high level.
  • You are okay starting with a manual email conversation.

Not a good fit

  • You need urgent data recovery right now.
  • You want managed IT support.
  • You need guaranteed restore results.
  • You are looking for an instant self-serve purchase or calendar slot.
  • You need formal certification.
Prepare first

Want to prepare before you email?

Some people are ready to email right away. Others may want to check a backup, homelab, documentation, or deployment resource first. The resource hub keeps that prep quieter than the main manual start path.

  • Emergency recovery during an active outage
  • Managed IT operations
  • A promise that every system can be restored
  • Hands-on production changes without a separate approved scope
  • An automated public workflow