1. Validate
Use the free or diagnostic path when the buyer still needs a go/no-go read on market, pain, offer, and risk.
Provisioned solutions, not customer chores
Your Deputy helps customers either launch a proof-backed business system or add service-business automation alongside the tools they already use. Every path has onboarding intake, setup states, acceptance evidence, and a delivery receipt that states what passed.
The job to be done
Everything points to one of three paths: validate an idea, provision a workspace, or activate a purchased outcome bundle.
Use the free or diagnostic path when the buyer still needs a go/no-go read on market, pain, offer, and risk.
Use the guided intake when the buyer is ready to create the workspace, blueprint, persona, and setup states.
Use a solution offer when the buyer has paid for a specific outcome and can provide the required authorization.
Two product lanes
The business succeeds when each persona lands on the right promise: build a new revenue system, or improve an existing service business without ripping out its current software.
For founders and agencies that need a customer-specific business system: offer, runtime page, lead capture, generated code, deployment scaffolding, acceptance evidence, and handoff files.
Compare build packagesFor HVAC, plumbing, cleaning, med spa, and local operators that already use Jobber, Housecall Pro, Stripe, QuickBooks, calendars, or a CRM and want the follow-up gaps closed.
Inspect specified automationsSolutions
Each offer has a clear delivery boundary. The page says what is provisioned, what is staged, and what depends on customer-owned vendor accounts or module deployability evidence.
A fast signal on whether the idea deserves deeper work.
Business documents and launch narrative. No live runtime deployment.
The first offer that provisions a customer-specific workspace and launch bundle.
Fulfillment
The customer selects the solution that matches their immediate need.
The form asks for the business, persona, goals, permissions, and systems the backend needs.
The system creates tenant records, entitlements, workflows, files, setup states, and seed data.
The customer sees what completed, what is staged, and what authorization remains.
Open the solution catalog to inspect offer examples, generated files, live boundaries, and acceptance evidence.
Credential intake, tenant creation, launch records, runtime pages, lead capture, workflow templates, module activation records, generated application code, deployment scaffolding, generated files, and receipts.
Stripe, Twilio, Resend, CRM, domains, calendars, analytics, and similar services require valid credentials and permissions. A queued job is not the same as a completed vendor setup.
Service automation modules and packs remain specified until build, UI, preflight, postflight, rollback, observability, billing, and tests prove they can be sold and activated.