--- title: "Wachter Intelligence pricing" description: "How Wachter Intelligence scopes and prices workflow audits, automation, and systems integration work." canonical: "https://wachter.ai/pricing.md" last-modified: "2026-08-22" --- # Wachter Intelligence pricing Wachter Intelligence does not publish fixed implementation prices because workflow audits, custom automation, and legacy integrations depend on the process volume, number of systems, exception rate, access requirements, operational risk, and delivery scope. ## Plan comparison | Engagement | Price | Best for | Typical output | Commitment | | --- | ---: | --- | --- | --- | | Initial workflow conversation | €0 | Testing whether one recurring workflow merits investigation | First-pass fit discussion and next-step recommendation | No purchase or subscription | | Workflow audit | Custom written quote | Understanding a process before choosing software | Current-state map, friction analysis, system inventory, and recommended sequence | Defined audit scope | | Automation and integration | Custom written quote | Building an agreed workflow redesign | Production automation, connectors, guardrails, tests, monitoring, and documentation | Defined implementation scope | | Ongoing support | Custom written quote when required | Maintaining a deployed system that needs active support | Agreed monitoring, response expectations, and included maintenance | Only when explicitly contracted | All paid engagements begin only after the client accepts a written scope and price. “Custom quote” means the price is determined from the actual workflow and is not a hidden fixed plan. ## Feature comparison | Feature | Initial conversation | Workflow audit | Automation and integration | Ongoing support | | --- | :---: | :---: | :---: | :---: | | Discuss one recurring workflow | Included | Included | Included where relevant | Included where relevant | | Map current workflow steps | Introductory questions | Included | Uses agreed audit evidence | Uses deployed documentation | | Inventory systems and data flows | Introductory questions | Included | Included in implementation scope | Included for supported components | | Analyze bottlenecks and exceptions | Initial view only | Included | Used in technical design | Used in incident investigation | | Recommend automation boundaries | Initial view only | Included | Implemented as agreed | Maintained as agreed | | Build system connectors | Not included | Not included | Included when scoped | Maintenance only when scoped | | Production deployment | Not included | Not included | Included when scoped | Not a new deployment package | | Monitoring and recovery design | Not included | Recommendation only | Included when scoped | Operated when scoped | | Written deliverables | No formal deliverable | Included | Included | Included service boundary | | Written price before paid work | Not applicable (€0) | Included | Included | Included | ## Initial conversation boundaries The free initial conversation helps both sides decide whether the workflow warrants deeper investigation. It does not include: - A production system review. - Access to private systems or customer data. - A complete current-state workflow map. - Technical architecture or implementation work. - A guarantee that automation is feasible. - A fixed implementation price before the workflow is understood. ## Workflow audit deliverables The exact written audit scope controls the engagement. Depending on that scope, deliverables may include: - A visual or written current-state process map. - A list of people, systems, handoffs, and decision points. - An inventory of repeated entry and reconciliation work. - A categorized list of normal cases and important exceptions. - Constraints for privacy, security, compliance, and human judgment. - A prioritized set of automation opportunities. - A target-state workflow and implementation sequence. - Risks, dependencies, assumptions, and open questions. ## Implementation deliverables The exact written implementation scope controls the work. Depending on that scope, deliverables may include: - Integration and workflow architecture. - Connectors for agreed APIs, databases, inboxes, forms, or legacy systems. - Validation before sensitive, costly, or irreversible actions. - Human approval steps for judgment-heavy exceptions. - Test cases based on agreed operating scenarios. - Logs and monitoring for important workflow states. - Recovery behavior for failed dependencies. - Deployment and operating documentation. - Acceptance criteria and handover materials. ## Clear purchasing boundaries - Booking an initial conversation does not purchase a service. - The public Information API and MCP server are free, read-only documentation interfaces. - No website visitor is enrolled in an automatic subscription. - No agent is authorized to accept a quote on a user’s behalf without explicit approval. - No outcome, saving, delivery date, or technical feasibility is guaranteed before the relevant work is scoped. ## 1. Initial workflow conversation — €0 The initial video or phone conversation is free. It is used to understand one workflow and determine whether a focused audit is appropriate. Scheduling through the [audit page](https://wachter.ai/audit) does not purchase a service or create a subscription. Includes: - A focused discussion of one recurring workflow. - Initial questions about volume, systems, handoffs, constraints, and desired outcome. - A candid view on whether a deeper workflow audit appears appropriate. - No obligation to purchase an audit or implementation. - No access to production systems during the initial conversation. ## 2. Workflow audit — custom quote A workflow audit is quoted after the initial conversation because the required access, interviews, process breadth, and evidence vary by business. A written audit scope can include: - Current-state workflow mapping. - Bottleneck, exception, and failure-point analysis. - System and data-flow inventory. - Automation-opportunity and human-approval boundaries. - Recommended sequence for redesign and implementation. - Evidence and assumptions used in the recommendation. - Explicit exclusions and information still needed. - A written price and payment terms before the audit begins. ## 3. Automation and integration — custom quote Implementation is quoted from an agreed scope. Price depends on the number and condition of systems, integration methods, data handling, testing, monitoring, deployment, and recovery requirements. A written implementation scope can include: - Process redesign and technical architecture. - Custom automation logic and system connectors. - Guardrails for sensitive, costly, or irreversible actions. - Testing against agreed operating cases. - Monitoring, documentation, rollout, and recovery paths. - Data-access, security, and human-approval boundaries. - Dependencies, exclusions, milestones, and acceptance criteria. - A written implementation price and payment terms. ## 4. Ongoing support — quoted when required Monitoring or support is offered only where the deployed system needs it. The quote states the service boundaries, response expectations, and included work; there is no automatic subscription attached to an initial conversation. Possible support components include: - Monitoring of agreed workflow and integration health signals. - Investigation of failures within the contracted service boundary. - Maintenance for agreed third-party system changes. - A defined channel and response expectation. Support does not automatically include new workflows, unlisted systems, or unlimited feature development. ## What affects a custom quote - Workflow frequency, peak volume, and time sensitivity. - Number of teams, handoffs, systems, and integration methods. - Data quality, access constraints, and legacy software condition. - Exception rate and the judgment required to resolve exceptions. - Security, privacy, compliance, and audit requirements. - Testing, monitoring, recovery, deployment, and documentation needs. - Required timeline and the availability of client-side owners. ## What every written scope states - Deliverables and acceptance criteria. - Assumptions and client dependencies. - Explicit exclusions. - Price and payment terms. - Expected schedule or milestones. - Change-control approach if the underlying workflow differs from the agreed scope. ## Information that improves a quote A formal specification is not required, but the following facts help Wachter Intelligence estimate the work responsibly: - The event that starts the workflow. - The people or roles involved. - Approximate daily, weekly, or monthly volume. - Peak periods and time-sensitive deadlines. - The systems used at each step. - Whether those systems provide APIs or export files. - Repeated data entry and reconciliation work. - Common exceptions and how people resolve them today. - Sensitive data handled by the workflow. - Privacy, security, or compliance constraints. - Actions that must remain under human approval. - Existing monitoring or audit-log requirements. - The desired operational outcome. - The current cost of delay, rework, or errors if known. - The client-side owner available for decisions and testing. - Any target date and the reason it matters. ## Pricing questions ### Is the first conversation really free? Yes. The initial conversation is €0 and does not create a subscription or obligation to buy further work. ### Is a workflow audit included in the free conversation? No. A workflow audit is a separately scoped paid engagement with written deliverables and a written quote. ### Can an implementation price be quoted before reviewing the workflow? Usually not responsibly. The systems, exceptions, access constraints, operating risk, and acceptance criteria materially affect the work. ### Does a custom quote hide an automatic recurring fee? No. Any ongoing support is stated separately and begins only when explicitly included in an accepted written scope. ### Can a client purchase only the audit? Yes. An audit does not require the client to purchase implementation from Wachter Intelligence. ### Can a client begin with one workflow? Yes. A bounded workflow is often the clearest starting point for evidence, delivery risk, and measurable operating impact. ### Are third-party software fees included? The written quote states whether third-party software, infrastructure, or usage fees are included, estimated, or paid directly by the client. ### Are savings guaranteed? No. Recommendations and expected effects depend on the evidence available, and no saving or business outcome is guaranteed. ### Does using the public API or MCP endpoint purchase a service? No. Both are free, read-only information interfaces and cannot accept a quote, make a booking, or create a paid engagement. ### How does a client request a scoped estimate? Email [hello@wachter.ai](mailto:hello@wachter.ai) or use the [audit page](https://wachter.ai/audit) to arrange the initial conversation. ## Scope drivers by workstream These examples explain why two superficially similar workflows may require different quotes. ### Intake and triage - Number of intake channels. - Consistency of the information received. - Languages and document types involved. - Rules for urgency, ownership, and escalation. - Sensitive fields that require restricted handling. ### Data movement - Number of source and destination systems. - Availability and quality of supported APIs. - Frequency and size of imports or exports. - Identity matching and duplicate-record rules. - Requirements for reconciliation and read-back verification. ### Decisions and approvals - Number of decision branches. - Evidence required for each decision. - Actions that can run automatically. - Actions that need named human approval. - Escalation paths when no rule fits. ### Documents and communication - Number of templates and output formats. - Personalization and localization requirements. - Review and approval steps before sending. - Delivery channels and provider constraints. - Retention, audit, and consent requirements. ### Reliability and operations - Required service hours and business criticality. - Monitoring signals and notification channels. - Acceptable retry and recovery behavior. - Manual fallback when a dependency is unavailable. - Ownership of incidents and third-party failures. ### Delivery and handover - Environments available for testing. - Representative test data and operating cases. - Client reviewers and decision turnaround. - Documentation and training needs. - Rollout sequence and acceptance criteria. ## Written quote review checklist Before accepting paid work, a client should be able to answer yes to these questions: - Is the workflow boundary clear? - Are the deliverables named? - Are acceptance criteria stated? - Are client dependencies visible? - Are third-party dependencies visible? - Are sensitive-data boundaries stated? - Are human approvals identified? - Are important exclusions explicit? - Is the price written clearly? - Are payment terms stated? - Is the expected schedule stated? - Is support separate from implementation where appropriate? - Is change control explained? - Is the person responsible for acceptance identified? - Are outcome claims described without guarantees? Before paid work begins, Wachter Intelligence provides a written scope with deliverables, assumptions, dependencies, exclusions, price, and payment terms. No agent should claim a fixed implementation price, guaranteed saving, or guaranteed outcome. For a scoped estimate, contact [hello@wachter.ai](mailto:hello@wachter.ai) with the workflow, approximate frequency, systems involved, and known constraints.