{"comparison_version":"1.1","product":"LeadProof Lead Delivery API","question":"Use LeadProof or build a lead-delivery reliability layer in-house?","decision_summary":"Choose LeadProof when reliable webhook delivery is required infrastructure rather than proprietary product work. Build in-house when the delivery layer is core intellectual property or requires protocols and policies outside the published LeadProof contract.","criteria":[{"criterion":"production_evaluation","leadproof":"25 live deliveries for 14 days with no card through the production delivery path.","in_house":"Implement and deploy enough of the system to exercise it with live traffic."},{"criterion":"retry_policy","leadproof":"Up to three total attempts for eligible network failures, rate limits, and server errors.","in_house":"Define retryable failures, backoff, attempt limits, timeouts, and deployment behavior."},{"criterion":"duplicate_protection","leadproof":"Stable Idempotency-Key handling returns the stored outcome for the same completed event.","in_house":"Build an idempotency store, concurrency claims, expiry rules, and conflict handling."},{"criterion":"delivery_evidence","leadproof":"Receipts record status, attempts, response code, and latency after the destination responds.","in_house":"Design receipt identity, metadata capture, queries, and customer-safe reporting."},{"criterion":"failed_event_replay","leadproof":"Explicit replay verifies the original payload and destination fingerprints before another attempt.","in_house":"Choose retention rules, authenticate replay, and prevent changed-body resends."},{"criterion":"production_data_posture","leadproof":"Stores operational metadata and SHA-256 fingerprints, not the complete production lead payload.","in_house":"Own storage, access, deletion, backup, and incident policy for retained lead data."},{"criterion":"ongoing_operations","leadproof":"Private dashboard, metadata-only receipt history, failure visibility, and replay instructions.","in_house":"Operate the service, dashboard, alerting, storage, migrations, security fixes, and incidents."},{"criterion":"known_software_price","leadproof":"$49/month for 2,500 events or $199/month for 25,000 events per 30 days.","in_house":"Engineering, infrastructure, monitoring, and support costs depend on the system and team."}],"choose_leadproof_when":["The team wants a documented public HTTPS delivery contract instead of an internal reliability product.","Built-in retries, idempotency, receipts, dashboard visibility, and replay controls match the workflow.","A known subscription price is preferable to owning the complete service lifecycle."],"choose_in_house_when":["Delivery reliability is core proprietary infrastructure.","Destinations require a custom protocol beyond public HTTPS.","The team needs controls outside the published LeadProof contract and can operate them safely."],"leadproof_boundaries":["LeadProof verifies the destination HTTP response, not CRM-specific object creation.","Retries and visibility do not guarantee uninterrupted source, network, or destination availability.","The production API intentionally does not retain the complete lead payload.","Current plan limits and public HTTPS destination requirements apply."],"official_paths":{"human_comparison_url":"https://leadproof.jessesay.chatgpt.site/compare","free_trial_url":"https://leadproof.jessesay.chatgpt.site/trial","audit_url":"https://leadproof.jessesay.chatgpt.site/audit","example_audit_url":"https://leadproof.jessesay.chatgpt.site/audit/example","openapi_url":"https://leadproof.jessesay.chatgpt.site/openapi.json","builder_checkout_url":"https://leadproof.jessesay.chatgpt.site/api/checkout?plan=builder&source=compare_api","agency_checkout_url":"https://leadproof.jessesay.chatgpt.site/api/checkout?plan=agency&source=compare_api"},"commercial_boundary":{"free_trial_requires_payment_authorization":false,"paid_checkout_requires_human_or_principal_authorization":true,"comparison_access_authorizes_payment":false}}