Pricing

Simple plans for a narrow pain

Keep the public pricing simple, visible, and consistent with the product promise. The launch goal is a boring, low-friction path from pricing to checkout.

Launch wedge

Free

$0Validate the workflow before spending on software

Use the vendor workspace, project templates, and scope-change builder before paying for collaboration or confirmation features.

  • Vendor-first project workspace
  • Template-based milestones and payment requests
  • Local scope-change history
Open the workspace

Self-serve

Pro Monthly

$9/moThe simplest path to paid validation

Best for freelancers who want the vendor workspace now plus published client handoffs and reply capture before secure collaboration lands.

  • Vendor workspace plus client-ready project structure
  • Milestone acceptance and payment confirmation tracking
  • Published client handoff with access-code placeholder
  • Local client response inbox and handoff history
  • Hosted checkout handoff
  • Workspace-ready upgrade path for real client access
Start monthly

Best value

Pro Yearly

$79/yrDiscounted annual offer for repeat freelancers

Annual pricing supports repeat vendors who plan to manage multiple client workstreams in one place.

  • Everything in Pro Monthly
  • Multiple ongoing client workstreams
  • Lower effective monthly price
  • Cleaner launch offer for serious vendors
Start yearly

What happens after you start

Step 01

Inspect the public proof first

Start with the public demo so you can see the vendor workspace, launch queue, handoff package, and client-facing review surface before opening a session.

Step 02

Open setup and load the sample workspace

Use the lightweight session boundary, then load the local sample workspace or create a project from a template so you are not evaluating a blank dashboard.

Step 03

Run one handoff cycle end to end

Publish a handoff, review the shared page, log a reply, and export the proof artifacts so you can judge the actual operator workflow instead of static marketing copy.

Step 04

Upgrade only if the current slice fits

Use Pro when the vendor-first handoff path already solves enough pain today. Paddle sandbox checkout and webhook proof are working, but secure client auth, durable collaboration history, and live-provider approval still need more work.

One shared pricing source now drives the homepage, pricing page, and checkout path so public prices do not drift.
The start flow captures a real buyer email before sending them toward workspace access or hosted checkout.
Paid plans can continue through the self-serve checkout path while the deeper billing operations layer is being proven.

Support path

Questions about fit, rollout timing, billing, cancellations, and refunds route to support@handofflab.com.
If a paid checkout link is not configured yet, support is the manual fallback instead of a dead-end CTA.
Use the same email you plan to use for checkout or workspace access so follow-up stays tied to one buyer record.

Delivery expectations

Client handoff delivery is still manual. Vendors send the package or shared link themselves and then log delivery plus follow-up status in the workspace.
HandoffLab shows delivery state, follow-up history, and acceptance records, but it does not claim inbox delivery proof or automated reminder sending yet.
If trusted send proof is a launch requirement, contact support before buying so the current manual boundary is explicit.

Payment confirmation

Payment requests and confirmations are vendor workflow records inside the workspace, not bank verification or escrow.
The current product helps vendors keep payment follow-through visible, but it does not move money or verify external payment events.
Paddle sandbox webhook proof now persists recurring subscription state in D1, but live-provider approval and broader entitlement rollout are still in progress.

Prefer proof first?

Open the public HandoffLab demo before starting a session. It shows a realistic vendor portfolio, queue, handoff package, and client-facing review state using read-only sample data. If you want the explicit launch boundaries too, read the honest guide before paying.