Paid pilot checklist

A focused pilot proves install, activation, import conversion, month-end evidence, Time Machine recovery, and license behavior before production records are trusted to the workflow. The goal is to show a small team how much work the software can take off their desk.

Recommended first sale

30-day proof of value

One reconciled source export, one reporting support package, one restore drill, and a go/no-go close review. Keep scope tight so the buyer sees value before procurement sprawl slows the deal.

$1,500Starter pilot
$3,000Conversion pilot
30 daysDecision window

Install

Verify signed installer, checksum, activation, local encrypted database path, and clean-machine launch by a non-developer.

Convert

Preview one real-world export, resolve exceptions, commit import, and reconcile source totals to the imported ledger.

Close

Run maturity/call review, reconciliation controls, and month-end/report package evidence for one review period.

Recover

Create snapshots, restore to a pre-import checkpoint, and confirm current license status cannot be rolled back.

Data custody

The pilot uses customer-controlled installation and support boundaries. Portfolio files, source imports, report packages, backups, and GL balances should not be sent to support unless a separate written authorization allows it.

Limited pilot scope

The first pilot is intentionally narrow: one source conversion, one month-end support package, one restore drill, and a documented go/no-go decision before broader production use.

Best fit
Community banks and credit unions replacing spreadsheets or legacy tracking tools.
Data model
Installed software with institution-controlled portfolio data.
Validation
Import balancing, report support evidence, and Time Machine restore proof.
Decision
Clear fit, gaps, and production-readiness notes after the pilot close review.