Partner Launch Kit.
Everything needed for a serious first conversation: the demo path, leave-behind materials, pilot request form, security boundary, source boundary, and 30-day pilot framing.
Show it in ten minutes.
Lead with one workflow. Do not pitch a platform rollout. The goal is to prove the discovery process can produce a partner-ready decision packet.
- 1Open the public demo.Start at the image-led homepage and say: LedgerPilot helps a firm find the safest first AI-use pilot. It does not do the accounting work.
- 2Load a demo scenario.Use bookkeeping close, tax notice routing, audit support, or billing/WIP to show the workflow-only path without client data.
- 3Show the sidecar.Point to pressure point, firm context, trigger, systems, approver, and 30-day outcome.
- 4Prepare the review packet.Show the AI-use lane, why it was selected, first-week step, proof metric, and controls.
- 5Close with the boundary.Open the source page and security page. No client files in discovery. Professional review remains required.
What to hand over.
These are the materials to send after a first conversation or keep open during a partner walkthrough.
30-day pilot shape.
The first ask should be one workflow conversation, one owner, one approval point, and one measurable proof metric.
Map the workflow.
Name the trigger, source systems, approver, prohibited data, and packet output before anything is built.
Test the support lane.
Use approved workflow notes only. Keep drafts, routing, summaries, and checklists under human review.
Review proof.
Measure owner assignment, reviewer-ready packets, stale items, follow-up loops, or time to review.
Request a workflow pilot review.
Capture only business contact details and workflow pressure. No client files, taxpayer identifiers, bank data, payroll registers, tax returns, or private financial statements.