Your Deputy includes the launch modules required for an autonomous business unit: website, funnel, CRM, products, quotes, proposals, contracts, invoices, payments, onboarding, support, analytics, workflow automation, governed AI actions, and optional vendor adapters.

Which businesses does Your Deputy work with?

Your Deputy supports niche businesses broadly. Service-business blueprints remain one supported family, but the launcher now validates every build as a complete revenue-ready operating unit, not only as field-service automation.

How much does Your Deputy cost?

Plans start with individual modules at $19/month each, or you can save with outcome packs that bundle related workflows together. Every plan includes a 30-day money-back guarantee and you can cancel anytime.

What systems does Your Deputy integrate with?

Your Deputy integrates with internally controlled provider abstractions first, with Stripe, SendGrid, S3, CRM, analytics, and automation vendors treated as optional adapters.

Is there a free trial?

Yes. You can browse the full catalog with no credit card required. Every paid plan includes a 30-day money-back guarantee, so you can try it risk-free.

Generated builds include OWASP-aligned security artifacts, RBAC, audit logging, tenant isolation, secure headers, webhook verification, and prompt-injection precautions. Formal certifications and legal/security reviews remain customer-owned readiness steps.

Inspect the modules before selling the promise.

Q: How long does setup take?

Workflows activate immediately only when the required capabilities are already authorized. Otherwise Your Deputy creates explicit setup wizards or assisted handoffs so customers always know what is live, staged, or waiting on access.

This catalog separates two lanes: launcher build components for generated business systems, and service-business automation modules that remain specified until deployability evidence proves they can be activated and supported.

See Plans & Pricing ↓

Specified, deployable, and live states stay separate - External systems are customer-owned adapters

Public sales claims must match /maturity, product readiness, and customer-owned credential status

How it works

Three steps from idea to a promise the business can safely sell

Specify

Start with a niche, target customer, location, business model, and offers. Your Deputy records the intended module, pack, or build contract.

Prove

The work must show build, UI, preflight, postflight, rollback, observability, billing, support, and tests before it becomes a paid activation promise.

Activate

Use the generated website, revenue engine, CRM lifecycle, guided AI actions, and event workflows only within the limits shown by the receipt and readiness state.

View: For: Persona:

Plans

Choose the plan that fits your team size. Every customer starts here.

Industry Editions

Vertical-specific solution editions pre-configured for plumbers, HVAC teams, electricians, and more.

Industry Blueprints

Niche-specific operating maps that connect buyer pain points, recommended packs, workflow modules, dashboard KPIs, seasonal patterns, and activation paths.

Outcome Suites

Bundle multiple workflows with advanced reporting. Save money vs. buying them separately.

Outcome Packs

Buy a result, not another software headache. Each pack solves a specific business problem.

Individual Modules

$19 each per month. Mix and match only the workflows you need.

All Workflows

Browse every workflow that ships with Your Deputy. Filter by category, solution family, or search by name.

Category: Solution family: Archetype: Trigger:

Expert Setup

Let our team complete the authorized setup steps for you while the same onboarding record, acceptance checks, and delivery receipt remain visible.

What the launcher now produces

The marketplace is the module view of a larger build standard: revenue, operations, AI, infrastructure, security, observability, governance, and semantic validation working together.

Revenue

Every build is expected to include products, lead magnets, pricing, checkout, payment abstraction, invoices, upsells, bundles, and digital delivery workflows.

RevOps

Quotes, proposals, contracts, invoices, renewals, CRM stages, onboarding, support, analytics, and event workflows are treated as required operating modules.

AI/MCP

Generated repos expose agent permissions, prompt packs, memory scaffolds, workflow definitions, conformance metadata, and validation tests.

Assurance

OWASP ASVS, OWASP SAMM, NIST AI RMF, ISO 42001 readiness, OpenTelemetry, deployment protection, tenancy decisions, and semantic eval fixtures now ship as required evidence.

OK 24 governed agent actions

OK 15 event workflows

OK 8 agent roles

OK 1 central config

OK 7 standards gates

Built around ownership, not vendor lock-in

Your Deputy now describes, generates, and validates the full operating layer: central configuration, provider abstractions, self-hosted infrastructure, event workflows, AI-operable business actions, model routing, video/voice asset planning, standards evidence, deployment protection, analytics, and observability.

Central config

Control plane

Business identity, features, providers, secrets placeholders, billing, email, analytics, AI, MCP, and workflows are designed to be governed from one master configuration.

Provider adapters

Self-hostable core

Payments, email, storage, analytics, documents, signatures, notifications, CRM, and AI use internal interfaces with third-party SDKs isolated to optional adapters.

Validation gates

Build accountability

Generated repos are checked for required folders, schemas, workflows, governed agent actions, RevOps modules, info products, security standards, analytics, onboarding, support, observability, deployment protection, and niche alignment.

1Master config

24Agent actions

15Workflows

DockerSelf-hosted default

What every business-unit build must cover

The launcher standard validates business completeness across revenue, operations, AI, infrastructure, and security.

Area	Required output	Validation signal
Revenue	Info products, pricing, checkout, invoices, payments, upsells, delivery	Required
RevOps	Quotes, proposals, contracts, renewals, lifecycle workflows	Required
CRM	Leads, contacts, customers, deals, tickets, tasks, notes, activities	Required
AI/agents	Action registry, agent permissions, prompts, memory, retrieval surface	Required
Infrastructure	Docker stack, database, events, workers, reverse proxy, health checks	Required
Security	JWT/RBAC, audit logs, validation, CORS, headers, webhooks, tenant isolation	Required
Standards	OWASP ASVS/SAMM, NIST AI RMF, ISO 42001 readiness, and semantic eval fixtures	Required
Observability	OpenTelemetry traces, metrics, logs, trace IDs, and business event correlation	Required
Deployment	GitHub Actions checks, protected environments, concurrency, and deployment protection	Required
Tenancy	Tenant isolation, shared-table/schema/database decision record, migrations, backup, and DR	Required

Frequently asked questions

Everything you need to know before getting started.

What is Your Deputy?

Your Deputy is the launcher for autonomous business units. It generates and validates the website, funnel, products, CRM logic, RevOps, contracts, invoices, payments, onboarding, support, analytics, governed AI agents, event workflows, provider abstractions, self-hostable infrastructure, standards evidence, observability, deployment protection, and semantic promise-equivalence checks.

Which businesses does it work with?

The build contract is niche-driven. Each generated business must stay aligned to its target customer, location, business model, primary offer, secondary offers, pricing, content, proposals, contracts, onboarding, support, analytics labels, prompts, and authorized systems.

How much does it cost?

Plans map to operating scope, not a website template count. The generated business unit can include revenue products, CRM logic, RevOps documents, checkout, payment abstraction, onboarding, support, analytics, AI agents, workflows, and self-hosted infrastructure. Optional vendor integrations depend on tier, configured keys, and provider health.

What systems does it integrate with?

The default architecture uses internally controlled provider abstractions for payments, email, storage, analytics, documents, signatures, CRM, notifications, and AI. Stripe, SendGrid, S3, and similar services are supported as optional adapters, but core business logic should not depend directly on any one vendor.

How long does setup take?

The builder generates the repo, repairs known failure classes, validates the contract, and records machine-readable degraded fallbacks when external credentials are missing. Self-hosted scaffolds continue without manual handoff, while real third-party activation waits for customer-owned credentials.

Can I try it before I pay?

Yes. Start with scoring and planning, then progress to a generated business unit when you want code, deployment, RevOps, products, checkout, onboarding, AI actions, and infrastructure. The maturity page shows what is live today, partial, code-generated, or planned.

Is my data safe?

Generated builds include an OWASP ASVS/SAMM-aligned checklist, JWT/RBAC, audit logging, input validation, tenant isolation, secure headers, safe webhook verification, and AI prompt-injection precautions. Formal certifications, penetration tests, and attorney/security reviews remain customer-owned readiness steps rather than hidden claims.

What if I need to change my plan?

You can upgrade, downgrade, or cancel anytime from your dashboard. Changes take effect on your next billing cycle. There are no long-term contracts, no cancellation fees, and no penalties. If you outgrow your current plan, we'll help you find the right tier.

Ready to launch the operating layer?

Generate a niche-specific autonomous business unit with products, funnel, CRM, RevOps, payments, onboarding, support, analytics, AI agents, model routing, optional video assets, workflows, self-hostable infrastructure, OWASP/NIST governance evidence, OpenTelemetry, deployment protection, tenancy decisions, and semantic validation.

Start onboarding → Read the FAQ

A build is only ready when the business contract, code, routes, live content, modules, and quality gates pass.