Skip to content

About

An offline-first MSP client handover ledger for evidence, exceptions, and cutover responsibility.

Resources

Stars

0 stars

Watchers

0 watching

Forks

Latest commit

 

History

6 Commits

Folders and files

NameName
Last commit message
Last commit date
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Handoff Ledger

An offline-first prototype for coordinating an MSP client handover across the outgoing provider, incoming provider, and client.

It tracks who owns each request, its due date, evidence reference, unresolved exceptions, and the agreed cutover/support boundary. The goal is a portable record that makes missing work and responsibility visible without requiring both MSPs to use the same PSA.

Try the prototype

Try it online; drafts stay in your browser and are not uploaded to a Handoff Ledger server.

Open index.html in a modern browser. Data stays in that browser's local storage. Use Export JSON to move a working file between people and Export handover to create a Markdown packet. To try a pre-filled fictional scenario, download examples/sample-handover.json and import it in the app. No server or dependencies are required.

Scope and safety

  • This is a workflow prototype, not a hosted shared workspace.
  • Do not enter passwords, tokens, private keys, or other secrets. Store those in a client-approved password manager and add only a secure reference.
  • Party acknowledgements are ordinary names and dates, not cryptographic signatures or legal attestations.
  • The market and pricing hypothesis are unvalidated. Customer interviews must establish transition volume, effort, buyer, and willingness to pay before hosted product work.

Why this exists

MSP community discussions describe repeated questions after handover packets are delivered and disagreement about overlap support and the moment responsibility changes. A commenter in a small-provider onboarding discussion also identifies missing owners and a lack of cohesive process. These are qualitative pain signals, not proof of market size or willingness to pay:

Generic checklist software is already available through products such as ITFlow, ConnectWise PSA, and Hudu. The hypothesis to test is whether neutral, cross-company coordination and a dated responsibility cutover are useful enough to warrant a dedicated tool.

See the customer-discovery guide for non-leading interview questions and evidence that would support or disprove the idea.

Open source

MIT licensed. See LICENSE.

Static demo deployment

.github/workflows/pages.yml publishes only index.html to GitHub Pages when the default branch changes. Enable Pages with GitHub Actions as the build source in the repository settings. The app has no server-side storage; each visitor's draft stays in that browser's local storage.

Business model hypothesis

Keep the portable local ledger free and open source. If interviews confirm that MSPs need cross-company coordination beyond their PSA, test a paid hosted transition room with shared access, audit history, and branded exports. Per-transition and recurring pricing are both unvalidated; do not build a hosted service until a buyer and willingness to pay are demonstrated. Credentials stay in the client's approved password manager.

About

An offline-first MSP client handover ledger for evidence, exceptions, and cutover responsibility.

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages