{"key":"ledgerbridge_retainer_and_support_model_2026_03_21","title":"LedgerBridge Retainer and Support Model","content":"LedgerBridge retainer and support model discussed on 2026-03-21.\n\nAfter setup, LedgerBridge can be sold with an optional recurring support/maintenance model.\n\nMonthly support can include:\n- scheduled execution/hosting\n- maintenance of the workflow\n- monitoring for input drift or failures\n- support for malformed files\n- minor config adjustments\n- recurring delivery of the clean report\n- traceability through logs/archive/quarantine behavior\n\nWhat support should not automatically include:\n- unlimited new custom reports\n- major workflow redesign\n- unlimited custom consulting\n- large schema changes without repricing\n\nTriggers for extra work or repricing:\n- new input file types\n- major column changes from source systems\n- new outputs beyond the original scope\n- more frequent runtime needs than agreed\n- extra reporting/analytics requests\n\nCommercial framing:\n- setup fee pays for discovery, mapping, testing, and first deployment\n- monthly fee pays for reliability, maintenance, support, and recurring runs\n\nCustomer-facing value:\n- they do not need to maintain the workflow\n- errors are caught instead of silently corrupting the result\n- the report keeps arriving without manual reconciliation\n\nStrategic goal:\n- use support as recurring revenue, but define boundaries so the business does not become cheap unlimited custom labor.\n\n---\n**2026-03-21 17:25:58 UTC | Created via MCP**","summary":"LedgerBridge retainer and support model discussed on 2026-03-21.\n\nAfter setup, LedgerBridge can be sold with an optional recurring support/maintenance model.\n\nMonthly support can include:\n- scheduled execution/hosting\n- maintenance of the workflow\n- monitoring for input drift or failures\n- support for malformed files\n- minor config adjustments\n- recurring delivery of the clean report\n- traceability through logs/archive/quarantine behavior\n\nWhat support should not automatically include:\n- unlimited new custom reports\n- major workflow redesign\n- unlimited custom consulting\n- large schema changes without repricing\n\nTriggers for extra work or repricing:\n- new input file types\n- major column changes from source systems\n- new outputs beyond the original scope\n- more frequent runtime needs than agreed\n- extra reporting/analytics requests\n\nCommercial framing:\n- setup fee pays for discovery, mapping, testing, and first deployment\n- monthly fee pays for reliability, maintenance, support, and recurring runs\n\nCustomer-facing value:\n- they do not need to maintain the workflow\n- errors are caught instead of silently corrupting the result\n- the report keeps arriving without manual reconciliation\n\nStrategic goal:\n- use support as recurring revenue, but define boundaries so the business does not become cheap unlimited custom labor.\n\n---\n**2026-03-21 17:25:58 UTC | Created via MCP**","status":"active","namespace":"general","namespace_name":"general","namespace_tier":"shared","tags":[]}