{ "schema_version": "legipro.platform_value_cards.v1", "roadmap_task_id": "SAAS-0056", "generated_at": "2026-06-29T08:51:13Z", "status": "public_safe_reusable_value_cards", "one_sentence": "LegiPro is a regulatory knowledge layer for existing accounting software, helping partners add source-backed regulatory intelligence without rebuilding the underlying regulatory foundation.", "reuse_policy": "Use these cards as neutral first-screening material across accounting platforms. They are not vendor-specific promises and do not claim live integration or partnership.", "value_story": [ "The core asset is the structured regulatory knowledge layer, not a commodity AI model.", "The orchestration layer selects the most appropriate source of evidence for each request.", "The first proof is e-invoicing/VAT/accounting-treatment review using public/test data.", "The partner keeps its own product, customer experience, auth, billing and workflow." ], "cards": [ { "vendor": "Cegid Loop", "segment": "expert-comptable practice workflow", "client_value": "Source-backed e-invoicing/VAT review packet inside accounting-practice workflows.", "what_legipro_brings": "A source-backed regulatory knowledge layer that can return cited evidence, missing facts, caution points, draft dossier/export refs and an audit id inside the partner workflow.", "why_partner_clients_care": "Users in a expert-comptable practice workflow can review e-invoicing, VAT or accounting-treatment questions without leaving the product surface they already use.", "likely_object_flow": "cabinet document or dossier handoff", "integration_readiness_tier": "first_wave_self_serve_stub", "readiness_explainer": "A fixture-only dry-run adapter shape already exists or is covered by the first-wave stub pattern.", "public_doc_confidence": "high", "unresolved_access_questions": [ "Partner credentials, LoopHub activation and test-environment scope." ], "first_proof_shape": "Partner-style context from cabinet document or dossier handoff -> LegiPro review packet -> cited sources, missing facts, risk flags, draft dossier/export id and audit id -> partner-side handoff fixture.", "outbound_positioning_line": "For Cegid Loop, LegiPro can be screened as a regulatory knowledge layer for expert-comptable practice workflow, not as a replacement front end.", "cost_and_consistency_note": "LegiPro can select structured regulatory evidence, a specialized workflow or AI support for more complex scenarios, helping partners improve consistency while keeping operational AI cost under control.", "model_stack_posture": "Designed to complement an existing software or AI stack rather than requiring the partner to replace it.", "claim_boundary": { "approved_partnership_claimed": false, "live_third_party_api_call_claimed": false, "production_integration_claimed": false, "client_reliance_claimed": false, "professional_certification_claimed": false } }, { "vendor": "Cegid Expert / Quadra", "segment": "established cabinet production workflow", "client_value": "Regulatory review packets and draft dossiers aligned to expert-comptable production workflows.", "what_legipro_brings": "A source-backed regulatory knowledge layer that can return cited evidence, missing facts, caution points, draft dossier/export refs and an audit id inside the partner workflow.", "why_partner_clients_care": "Users in a established cabinet production workflow can review e-invoicing, VAT or accounting-treatment questions without leaving the product surface they already use.", "likely_object_flow": "accounting metadata, balances, journals, GED documents and cabinet dossier context", "integration_readiness_tier": "first_wave_self_serve_stub", "readiness_explainer": "A fixture-only dry-run adapter shape already exists or is covered by the first-wave stub pattern.", "public_doc_confidence": "medium_high", "unresolved_access_questions": [ "API Standard versus Advanced API scope and partner access terms." ], "first_proof_shape": "Partner-style context from accounting metadata, balances, journals, GED documents and cabinet dossier context -> LegiPro review packet -> cited sources, missing facts, risk flags, draft dossier/export id and audit id -> partner-side handoff fixture.", "outbound_positioning_line": "For Cegid Expert / Quadra, LegiPro can be screened as a regulatory knowledge layer for established cabinet production workflow, not as a replacement front end.", "cost_and_consistency_note": "LegiPro can select structured regulatory evidence, a specialized workflow or AI support for more complex scenarios, helping partners improve consistency while keeping operational AI cost under control.", "model_stack_posture": "Designed to complement an existing software or AI stack rather than requiring the partner to replace it.", "claim_boundary": { "approved_partnership_claimed": false, "live_third_party_api_call_claimed": false, "production_integration_claimed": false, "client_reliance_claimed": false, "professional_certification_claimed": false } }, { "vendor": "Sage Accounting", "segment": "SMB accounting workflow", "client_value": "Cited regulatory review around invoice and VAT workflows without replacing Sage UX.", "what_legipro_brings": "A source-backed regulatory knowledge layer that can return cited evidence, missing facts, caution points, draft dossier/export refs and an audit id inside the partner workflow.", "why_partner_clients_care": "Users in a SMB accounting workflow can review e-invoicing, VAT or accounting-treatment questions without leaving the product surface they already use.", "likely_object_flow": "invoice, contact, accounting-entry or document context", "integration_readiness_tier": "first_wave_self_serve_stub", "readiness_explainer": "A fixture-only dry-run adapter shape already exists or is covered by the first-wave stub pattern.", "public_doc_confidence": "high", "unresolved_access_questions": [ "Sandbox authorization and product-line fit for France-specific flows." ], "first_proof_shape": "Partner-style context from invoice, contact, accounting-entry or document context -> LegiPro review packet -> cited sources, missing facts, risk flags, draft dossier/export id and audit id -> partner-side handoff fixture.", "outbound_positioning_line": "For Sage Accounting, LegiPro can be screened as a regulatory knowledge layer for SMB accounting workflow, not as a replacement front end.", "cost_and_consistency_note": "LegiPro can select structured regulatory evidence, a specialized workflow or AI support for more complex scenarios, helping partners improve consistency while keeping operational AI cost under control.", "model_stack_posture": "Designed to complement an existing software or AI stack rather than requiring the partner to replace it.", "claim_boundary": { "approved_partnership_claimed": false, "live_third_party_api_call_claimed": false, "production_integration_claimed": false, "client_reliance_claimed": false, "professional_certification_claimed": false } }, { "vendor": "Sage Active", "segment": "cloud accounting workflow", "client_value": "Source-backed regulatory intelligence alongside cloud-native accounting workflows.", "what_legipro_brings": "A source-backed regulatory knowledge layer that can return cited evidence, missing facts, caution points, draft dossier/export refs and an audit id inside the partner workflow.", "why_partner_clients_care": "Users in a cloud accounting workflow can review e-invoicing, VAT or accounting-treatment questions without leaving the product surface they already use.", "likely_object_flow": "GraphQL accounting objects, documents, entries and reporting context", "integration_readiness_tier": "first_wave_self_serve_stub", "readiness_explainer": "A fixture-only dry-run adapter shape already exists or is covered by the first-wave stub pattern.", "public_doc_confidence": "high", "unresolved_access_questions": [ "OIDC/OAuth app setup and exact France accounting object scope." ], "first_proof_shape": "Partner-style context from GraphQL accounting objects, documents, entries and reporting context -> LegiPro review packet -> cited sources, missing facts, risk flags, draft dossier/export id and audit id -> partner-side handoff fixture.", "outbound_positioning_line": "For Sage Active, LegiPro can be screened as a regulatory knowledge layer for cloud accounting workflow, not as a replacement front end.", "cost_and_consistency_note": "LegiPro can select structured regulatory evidence, a specialized workflow or AI support for more complex scenarios, helping partners improve consistency while keeping operational AI cost under control.", "model_stack_posture": "Designed to complement an existing software or AI stack rather than requiring the partner to replace it.", "claim_boundary": { "approved_partnership_claimed": false, "live_third_party_api_call_claimed": false, "production_integration_claimed": false, "client_reliance_claimed": false, "professional_certification_claimed": false } }, { "vendor": "Pennylane", "segment": "company and firm accounting workflow", "client_value": "Evidence packet and missing-fact loop for cabinet review and client-facing accounting workflows.", "what_legipro_brings": "A source-backed regulatory knowledge layer that can return cited evidence, missing facts, caution points, draft dossier/export refs and an audit id inside the partner workflow.", "why_partner_clients_care": "Users in a company and firm accounting workflow can review e-invoicing, VAT or accounting-treatment questions without leaving the product surface they already use.", "likely_object_flow": "company or firm API handoff for invoices, customers and accounting entries", "integration_readiness_tier": "first_wave_self_serve_stub", "readiness_explainer": "A fixture-only dry-run adapter shape already exists or is covered by the first-wave stub pattern.", "public_doc_confidence": "high", "unresolved_access_questions": [ "Company API versus Firm API scope for the first proof." ], "first_proof_shape": "Partner-style context from company or firm API handoff for invoices, customers and accounting entries -> LegiPro review packet -> cited sources, missing facts, risk flags, draft dossier/export id and audit id -> partner-side handoff fixture.", "outbound_positioning_line": "For Pennylane, LegiPro can be screened as a regulatory knowledge layer for company and firm accounting workflow, not as a replacement front end.", "cost_and_consistency_note": "LegiPro can select structured regulatory evidence, a specialized workflow or AI support for more complex scenarios, helping partners improve consistency while keeping operational AI cost under control.", "model_stack_posture": "Designed to complement an existing software or AI stack rather than requiring the partner to replace it.", "claim_boundary": { "approved_partnership_claimed": false, "live_third_party_api_call_claimed": false, "production_integration_claimed": false, "client_reliance_claimed": false, "professional_certification_claimed": false } }, { "vendor": "Odoo", "segment": "ERP/accounting workflow", "client_value": "Regulatory evidence layer that can sit beside configurable ERP/accounting workflows.", "what_legipro_brings": "A source-backed regulatory knowledge layer that can return cited evidence, missing facts, caution points, draft dossier/export refs and an audit id inside the partner workflow.", "why_partner_clients_care": "Users in a ERP/accounting workflow can review e-invoicing, VAT or accounting-treatment questions without leaving the product surface they already use.", "likely_object_flow": "JSON-2 partner, invoice and accounting records", "integration_readiness_tier": "first_wave_self_serve_stub", "readiness_explainer": "A fixture-only dry-run adapter shape already exists or is covered by the first-wave stub pattern.", "public_doc_confidence": "high", "unresolved_access_questions": [ "Edition, app and record-rule assumptions for a clean dry-run fixture." ], "first_proof_shape": "Partner-style context from JSON-2 partner, invoice and accounting records -> LegiPro review packet -> cited sources, missing facts, risk flags, draft dossier/export id and audit id -> partner-side handoff fixture.", "outbound_positioning_line": "For Odoo, LegiPro can be screened as a regulatory knowledge layer for ERP/accounting workflow, not as a replacement front end.", "cost_and_consistency_note": "LegiPro can select structured regulatory evidence, a specialized workflow or AI support for more complex scenarios, helping partners improve consistency while keeping operational AI cost under control.", "model_stack_posture": "Designed to complement an existing software or AI stack rather than requiring the partner to replace it.", "claim_boundary": { "approved_partnership_claimed": false, "live_third_party_api_call_claimed": false, "production_integration_claimed": false, "client_reliance_claimed": false, "professional_certification_claimed": false } }, { "vendor": "Abby", "segment": "freelancer and small-business workflow", "client_value": "Lightweight source-backed review path for freelancer and small-business accounting flows.", "what_legipro_brings": "A source-backed regulatory knowledge layer that can return cited evidence, missing facts, caution points, draft dossier/export refs and an audit id inside the partner workflow.", "why_partner_clients_care": "Users in a freelancer and small-business workflow can review e-invoicing, VAT or accounting-treatment questions without leaving the product surface they already use.", "likely_object_flow": "customers, invoices and bookkeeping status", "integration_readiness_tier": "first_wave_self_serve_stub", "readiness_explainer": "A fixture-only dry-run adapter shape already exists or is covered by the first-wave stub pattern.", "public_doc_confidence": "high", "unresolved_access_questions": [ "Partner distribution and support path for embedded review packets." ], "first_proof_shape": "Partner-style context from customers, invoices and bookkeeping status -> LegiPro review packet -> cited sources, missing facts, risk flags, draft dossier/export id and audit id -> partner-side handoff fixture.", "outbound_positioning_line": "For Abby, LegiPro can be screened as a regulatory knowledge layer for freelancer and small-business workflow, not as a replacement front end.", "cost_and_consistency_note": "LegiPro can select structured regulatory evidence, a specialized workflow or AI support for more complex scenarios, helping partners improve consistency while keeping operational AI cost under control.", "model_stack_posture": "Designed to complement an existing software or AI stack rather than requiring the partner to replace it.", "claim_boundary": { "approved_partnership_claimed": false, "live_third_party_api_call_claimed": false, "production_integration_claimed": false, "client_reliance_claimed": false, "professional_certification_claimed": false } }, { "vendor": "Inqom", "segment": "automation-heavy cabinet workflow", "client_value": "Cabinet-scale source evidence and dossier workflow for automation-heavy accounting teams.", "what_legipro_brings": "A source-backed regulatory knowledge layer that can return cited evidence, missing facts, caution points, draft dossier/export refs and an audit id inside the partner workflow.", "why_partner_clients_care": "Users in a automation-heavy cabinet workflow can review e-invoicing, VAT or accounting-treatment questions without leaving the product surface they already use.", "likely_object_flow": "documents, journals, FEC, dossiers and accounting outputs", "integration_readiness_tier": "first_wave_self_serve_stub", "readiness_explainer": "A fixture-only dry-run adapter shape already exists or is covered by the first-wave stub pattern.", "public_doc_confidence": "high", "unresolved_access_questions": [ "OAuth scope and cabinet/system-account posture for a first partner screen." ], "first_proof_shape": "Partner-style context from documents, journals, FEC, dossiers and accounting outputs -> LegiPro review packet -> cited sources, missing facts, risk flags, draft dossier/export id and audit id -> partner-side handoff fixture.", "outbound_positioning_line": "For Inqom, LegiPro can be screened as a regulatory knowledge layer for automation-heavy cabinet workflow, not as a replacement front end.", "cost_and_consistency_note": "LegiPro can select structured regulatory evidence, a specialized workflow or AI support for more complex scenarios, helping partners improve consistency while keeping operational AI cost under control.", "model_stack_posture": "Designed to complement an existing software or AI stack rather than requiring the partner to replace it.", "claim_boundary": { "approved_partnership_claimed": false, "live_third_party_api_call_claimed": false, "production_integration_claimed": false, "client_reliance_claimed": false, "professional_certification_claimed": false } }, { "vendor": "EBP", "segment": "SMB management and accounting workflow", "client_value": "Bounded review pack that can attach to established SMB accounting/management workflows.", "what_legipro_brings": "A source-backed regulatory knowledge layer that can return cited evidence, missing facts, caution points, draft dossier/export refs and an audit id inside the partner workflow.", "why_partner_clients_care": "Users in a SMB management and accounting workflow can review e-invoicing, VAT or accounting-treatment questions without leaving the product surface they already use.", "likely_object_flow": "invoices, customers, stock or Open Line import/export", "integration_readiness_tier": "partner_gated_brief", "readiness_explainer": "The value story is clear, but a partner or sandbox route is needed before a credible adapter can be promoted.", "public_doc_confidence": "medium", "unresolved_access_questions": [ "Developer module access and runtime auth details." ], "first_proof_shape": "Partner-style context from invoices, customers, stock or Open Line import/export -> LegiPro review packet -> cited sources, missing facts, risk flags, draft dossier/export id and audit id -> partner-side handoff fixture.", "outbound_positioning_line": "For EBP, LegiPro can be screened as a regulatory knowledge layer for SMB management and accounting workflow, not as a replacement front end.", "cost_and_consistency_note": "LegiPro can select structured regulatory evidence, a specialized workflow or AI support for more complex scenarios, helping partners improve consistency while keeping operational AI cost under control.", "model_stack_posture": "Designed to complement an existing software or AI stack rather than requiring the partner to replace it.", "claim_boundary": { "approved_partnership_claimed": false, "live_third_party_api_call_claimed": false, "production_integration_claimed": false, "client_reliance_claimed": false, "professional_certification_claimed": false } }, { "vendor": "Cegid XRP", "segment": "ERP and finance operations workflow", "client_value": "Regulatory evidence packet for ERP-adjacent finance workflows.", "what_legipro_brings": "A source-backed regulatory knowledge layer that can return cited evidence, missing facts, caution points, draft dossier/export refs and an audit id inside the partner workflow.", "why_partner_clients_care": "Users in a ERP and finance operations workflow can review e-invoicing, VAT or accounting-treatment questions without leaving the product surface they already use.", "likely_object_flow": "ERP invoice, customer, reporting or document handoff", "integration_readiness_tier": "partner_gated_brief", "readiness_explainer": "The value story is clear, but a partner or sandbox route is needed before a credible adapter can be promoted.", "public_doc_confidence": "medium", "unresolved_access_questions": [ "Public endpoint catalog and sandbox path." ], "first_proof_shape": "Partner-style context from ERP invoice, customer, reporting or document handoff -> LegiPro review packet -> cited sources, missing facts, risk flags, draft dossier/export id and audit id -> partner-side handoff fixture.", "outbound_positioning_line": "For Cegid XRP, LegiPro can be screened as a regulatory knowledge layer for ERP and finance operations workflow, not as a replacement front end.", "cost_and_consistency_note": "LegiPro can select structured regulatory evidence, a specialized workflow or AI support for more complex scenarios, helping partners improve consistency while keeping operational AI cost under control.", "model_stack_posture": "Designed to complement an existing software or AI stack rather than requiring the partner to replace it.", "claim_boundary": { "approved_partnership_claimed": false, "live_third_party_api_call_claimed": false, "production_integration_claimed": false, "client_reliance_claimed": false, "professional_certification_claimed": false } }, { "vendor": "ACD / i-Suite", "segment": "expert-comptable suite workflow", "client_value": "Review packet and audit trail that can support expert-comptable workflows.", "what_legipro_brings": "A source-backed regulatory knowledge layer that can return cited evidence, missing facts, caution points, draft dossier/export refs and an audit id inside the partner workflow.", "why_partner_clients_care": "Users in a expert-comptable suite workflow can review e-invoicing, VAT or accounting-treatment questions without leaving the product surface they already use.", "likely_object_flow": "cabinet documents, ledgers and shared dossier status", "integration_readiness_tier": "partner_gated_brief", "readiness_explainer": "The value story is clear, but a partner or sandbox route is needed before a credible adapter can be promoted.", "public_doc_confidence": "medium", "unresolved_access_questions": [ "Web-service access, server URL and dossier-sharing setup." ], "first_proof_shape": "Partner-style context from cabinet documents, ledgers and shared dossier status -> LegiPro review packet -> cited sources, missing facts, risk flags, draft dossier/export id and audit id -> partner-side handoff fixture.", "outbound_positioning_line": "For ACD / i-Suite, LegiPro can be screened as a regulatory knowledge layer for expert-comptable suite workflow, not as a replacement front end.", "cost_and_consistency_note": "LegiPro can select structured regulatory evidence, a specialized workflow or AI support for more complex scenarios, helping partners improve consistency while keeping operational AI cost under control.", "model_stack_posture": "Designed to complement an existing software or AI stack rather than requiring the partner to replace it.", "claim_boundary": { "approved_partnership_claimed": false, "live_third_party_api_call_claimed": false, "production_integration_claimed": false, "client_reliance_claimed": false, "professional_certification_claimed": false } }, { "vendor": "RCA / MEG", "segment": "cabinet/client exchange workflow", "client_value": "Source-backed review layer around cabinet interoperability and dossier exchange.", "what_legipro_brings": "A source-backed regulatory knowledge layer that can return cited evidence, missing facts, caution points, draft dossier/export refs and an audit id inside the partner workflow.", "why_partner_clients_care": "Users in a cabinet/client exchange workflow can review e-invoicing, VAT or accounting-treatment questions without leaving the product surface they already use.", "likely_object_flow": "journals, third parties and supporting-document exchange", "integration_readiness_tier": "partner_gated_brief", "readiness_explainer": "The value story is clear, but a partner or sandbox route is needed before a credible adapter can be promoted.", "public_doc_confidence": "medium", "unresolved_access_questions": [ "Token, Gravitee and endpoint details for a supported partner fixture." ], "first_proof_shape": "Partner-style context from journals, third parties and supporting-document exchange -> LegiPro review packet -> cited sources, missing facts, risk flags, draft dossier/export id and audit id -> partner-side handoff fixture.", "outbound_positioning_line": "For RCA / MEG, LegiPro can be screened as a regulatory knowledge layer for cabinet/client exchange workflow, not as a replacement front end.", "cost_and_consistency_note": "LegiPro can select structured regulatory evidence, a specialized workflow or AI support for more complex scenarios, helping partners improve consistency while keeping operational AI cost under control.", "model_stack_posture": "Designed to complement an existing software or AI stack rather than requiring the partner to replace it.", "claim_boundary": { "approved_partnership_claimed": false, "live_third_party_api_call_claimed": false, "production_integration_claimed": false, "client_reliance_claimed": false, "professional_certification_claimed": false } }, { "vendor": "Sellsy", "segment": "CRM-to-invoicing workflow", "client_value": "VAT/e-invoicing caution points in lead-to-cash workflows.", "what_legipro_brings": "A source-backed regulatory knowledge layer that can return cited evidence, missing facts, caution points, draft dossier/export refs and an audit id inside the partner workflow.", "why_partner_clients_care": "Users in a CRM-to-invoicing workflow can review e-invoicing, VAT or accounting-treatment questions without leaving the product surface they already use.", "likely_object_flow": "prospects, clients, quotes, invoices, tasks and events", "integration_readiness_tier": "partner_gated_brief", "readiness_explainer": "The value story is clear, but a partner or sandbox route is needed before a credible adapter can be promoted.", "public_doc_confidence": "medium_high", "unresolved_access_questions": [ "Partner access rules and OAuth app status." ], "first_proof_shape": "Partner-style context from prospects, clients, quotes, invoices, tasks and events -> LegiPro review packet -> cited sources, missing facts, risk flags, draft dossier/export id and audit id -> partner-side handoff fixture.", "outbound_positioning_line": "For Sellsy, LegiPro can be screened as a regulatory knowledge layer for CRM-to-invoicing workflow, not as a replacement front end.", "cost_and_consistency_note": "LegiPro can select structured regulatory evidence, a specialized workflow or AI support for more complex scenarios, helping partners improve consistency while keeping operational AI cost under control.", "model_stack_posture": "Designed to complement an existing software or AI stack rather than requiring the partner to replace it.", "claim_boundary": { "approved_partnership_claimed": false, "live_third_party_api_call_claimed": false, "production_integration_claimed": false, "client_reliance_claimed": false, "professional_certification_claimed": false } }, { "vendor": "Dext", "segment": "pre-accounting capture workflow", "client_value": "Evidence-backed cleanup and review prompts for captured AP/pre-accounting data.", "what_legipro_brings": "A source-backed regulatory knowledge layer that can return cited evidence, missing facts, caution points, draft dossier/export refs and an audit id inside the partner workflow.", "why_partner_clients_care": "Users in a pre-accounting capture workflow can review e-invoicing, VAT or accounting-treatment questions without leaving the product surface they already use.", "likely_object_flow": "pre-accounting documents, receipts and data-health signals", "integration_readiness_tier": "partner_gated_brief", "readiness_explainer": "The value story is clear, but a partner or sandbox route is needed before a credible adapter can be promoted.", "public_doc_confidence": "medium_high", "unresolved_access_questions": [ "Practice add-on, client connection and allowed data-health scope." ], "first_proof_shape": "Partner-style context from pre-accounting documents, receipts and data-health signals -> LegiPro review packet -> cited sources, missing facts, risk flags, draft dossier/export id and audit id -> partner-side handoff fixture.", "outbound_positioning_line": "For Dext, LegiPro can be screened as a regulatory knowledge layer for pre-accounting capture workflow, not as a replacement front end.", "cost_and_consistency_note": "LegiPro can select structured regulatory evidence, a specialized workflow or AI support for more complex scenarios, helping partners improve consistency while keeping operational AI cost under control.", "model_stack_posture": "Designed to complement an existing software or AI stack rather than requiring the partner to replace it.", "claim_boundary": { "approved_partnership_claimed": false, "live_third_party_api_call_claimed": false, "production_integration_claimed": false, "client_reliance_claimed": false, "professional_certification_claimed": false } }, { "vendor": "Tiime", "segment": "SMB invoicing and cabinet workflow", "client_value": "E-invoicing/VAT source review for SMB workflow surfaces.", "what_legipro_brings": "A source-backed regulatory knowledge layer that can return cited evidence, missing facts, caution points, draft dossier/export refs and an audit id inside the partner workflow.", "why_partner_clients_care": "Users in a SMB invoicing and cabinet workflow can review e-invoicing, VAT or accounting-treatment questions without leaving the product surface they already use.", "likely_object_flow": "customers, invoices, quotes and payment status", "integration_readiness_tier": "partner_gated_brief", "readiness_explainer": "The value story is clear, but a partner or sandbox route is needed before a credible adapter can be promoted.", "public_doc_confidence": "medium", "unresolved_access_questions": [ "API available-on-request process and auth details." ], "first_proof_shape": "Partner-style context from customers, invoices, quotes and payment status -> LegiPro review packet -> cited sources, missing facts, risk flags, draft dossier/export id and audit id -> partner-side handoff fixture.", "outbound_positioning_line": "For Tiime, LegiPro can be screened as a regulatory knowledge layer for SMB invoicing and cabinet workflow, not as a replacement front end.", "cost_and_consistency_note": "LegiPro can select structured regulatory evidence, a specialized workflow or AI support for more complex scenarios, helping partners improve consistency while keeping operational AI cost under control.", "model_stack_posture": "Designed to complement an existing software or AI stack rather than requiring the partner to replace it.", "claim_boundary": { "approved_partnership_claimed": false, "live_third_party_api_call_claimed": false, "production_integration_claimed": false, "client_reliance_claimed": false, "professional_certification_claimed": false } }, { "vendor": "Yooz", "segment": "AP and purchase-to-pay workflow", "client_value": "Regulatory review packet around supplier invoice intake and validation.", "what_legipro_brings": "A source-backed regulatory knowledge layer that can return cited evidence, missing facts, caution points, draft dossier/export refs and an audit id inside the partner workflow.", "why_partner_clients_care": "Users in a AP and purchase-to-pay workflow can review e-invoicing, VAT or accounting-treatment questions without leaving the product surface they already use.", "likely_object_flow": "AP/P2P document intake, approval and payment-status handoff", "integration_readiness_tier": "partner_gated_brief", "readiness_explainer": "The value story is clear, but a partner or sandbox route is needed before a credible adapter can be promoted.", "public_doc_confidence": "medium", "unresolved_access_questions": [ "Developer reference and partner route." ], "first_proof_shape": "Partner-style context from AP/P2P document intake, approval and payment-status handoff -> LegiPro review packet -> cited sources, missing facts, risk flags, draft dossier/export id and audit id -> partner-side handoff fixture.", "outbound_positioning_line": "For Yooz, LegiPro can be screened as a regulatory knowledge layer for AP and purchase-to-pay workflow, not as a replacement front end.", "cost_and_consistency_note": "LegiPro can select structured regulatory evidence, a specialized workflow or AI support for more complex scenarios, helping partners improve consistency while keeping operational AI cost under control.", "model_stack_posture": "Designed to complement an existing software or AI stack rather than requiring the partner to replace it.", "claim_boundary": { "approved_partnership_claimed": false, "live_third_party_api_call_claimed": false, "production_integration_claimed": false, "client_reliance_claimed": false, "professional_certification_claimed": false } }, { "vendor": "Macompta.fr", "segment": "small-business accounting workflow", "client_value": "Source-backed e-invoicing context for small-business accounting users.", "what_legipro_brings": "A source-backed regulatory knowledge layer that can return cited evidence, missing facts, caution points, draft dossier/export refs and an audit id inside the partner workflow.", "why_partner_clients_care": "Users in a small-business accounting workflow can review e-invoicing, VAT or accounting-treatment questions without leaving the product surface they already use.", "likely_object_flow": "approved invoices, tickets, payroll data and PA lifecycle status", "integration_readiness_tier": "partner_gated_brief", "readiness_explainer": "The value story is clear, but a partner or sandbox route is needed before a credible adapter can be promoted.", "public_doc_confidence": "low_medium", "unresolved_access_questions": [ "Partner API route, PA verification and sandbox access." ], "first_proof_shape": "Partner-style context from approved invoices, tickets, payroll data and PA lifecycle status -> LegiPro review packet -> cited sources, missing facts, risk flags, draft dossier/export id and audit id -> partner-side handoff fixture.", "outbound_positioning_line": "For Macompta.fr, LegiPro can be screened as a regulatory knowledge layer for small-business accounting workflow, not as a replacement front end.", "cost_and_consistency_note": "LegiPro can select structured regulatory evidence, a specialized workflow or AI support for more complex scenarios, helping partners improve consistency while keeping operational AI cost under control.", "model_stack_posture": "Designed to complement an existing software or AI stack rather than requiring the partner to replace it.", "claim_boundary": { "approved_partnership_claimed": false, "live_third_party_api_call_claimed": false, "production_integration_claimed": false, "client_reliance_claimed": false, "professional_certification_claimed": false } }, { "vendor": "Indy", "segment": "independent professional workflow", "client_value": "Potential review overlay for independent professionals once API scope is clearer.", "what_legipro_brings": "A source-backed regulatory knowledge layer that can return cited evidence, missing facts, caution points, draft dossier/export refs and an audit id inside the partner workflow.", "why_partner_clients_care": "Users in a independent professional workflow can review e-invoicing, VAT or accounting-treatment questions without leaving the product surface they already use.", "likely_object_flow": "narrow invoice or mission-data import/export", "integration_readiness_tier": "watchlist", "readiness_explainer": "The platform is worth tracking, but public API/access evidence is too thin for a first screening claim.", "public_doc_confidence": "low", "unresolved_access_questions": [ "No general public developer portal confirmed." ], "first_proof_shape": "Partner-style context from narrow invoice or mission-data import/export -> LegiPro review packet -> cited sources, missing facts, risk flags, draft dossier/export id and audit id -> partner-side handoff fixture.", "outbound_positioning_line": "For Indy, LegiPro can be screened as a regulatory knowledge layer for independent professional workflow, not as a replacement front end.", "cost_and_consistency_note": "LegiPro can select structured regulatory evidence, a specialized workflow or AI support for more complex scenarios, helping partners improve consistency while keeping operational AI cost under control.", "model_stack_posture": "Designed to complement an existing software or AI stack rather than requiring the partner to replace it.", "claim_boundary": { "approved_partnership_claimed": false, "live_third_party_api_call_claimed": false, "production_integration_claimed": false, "client_reliance_claimed": false, "professional_certification_claimed": false } }, { "vendor": "Axonaut", "segment": "front-office to accounting workflow", "client_value": "Potential evidence packet around front-office to accounting handoff.", "what_legipro_brings": "A source-backed regulatory knowledge layer that can return cited evidence, missing facts, caution points, draft dossier/export refs and an audit id inside the partner workflow.", "why_partner_clients_care": "Users in a front-office to accounting workflow can review e-invoicing, VAT or accounting-treatment questions without leaving the product surface they already use.", "likely_object_flow": "clients, quotes, invoices and accounting exports", "integration_readiness_tier": "watchlist", "readiness_explainer": "The platform is worth tracking, but public API/access evidence is too thin for a first screening claim.", "public_doc_confidence": "low", "unresolved_access_questions": [ "In-app API-key docs and supported partner posture." ], "first_proof_shape": "Partner-style context from clients, quotes, invoices and accounting exports -> LegiPro review packet -> cited sources, missing facts, risk flags, draft dossier/export id and audit id -> partner-side handoff fixture.", "outbound_positioning_line": "For Axonaut, LegiPro can be screened as a regulatory knowledge layer for front-office to accounting workflow, not as a replacement front end.", "cost_and_consistency_note": "LegiPro can select structured regulatory evidence, a specialized workflow or AI support for more complex scenarios, helping partners improve consistency while keeping operational AI cost under control.", "model_stack_posture": "Designed to complement an existing software or AI stack rather than requiring the partner to replace it.", "claim_boundary": { "approved_partnership_claimed": false, "live_third_party_api_call_claimed": false, "production_integration_claimed": false, "client_reliance_claimed": false, "professional_certification_claimed": false } } ], "vendor_count": 19, "required_vendor_count": 19, "acceptance_summary": { "all_required_vendors_present": true, "each_card_has_client_value": true, "each_card_has_object_flow": true, "each_card_has_readiness_tier": true, "each_card_has_public_doc_confidence": true, "each_card_has_unresolved_access_questions": true, "no_vendor_specific_overclaims": true, "readiness_flags_false": true }, "boundaries": { "no_approved_partnership_claimed": true, "no_live_third_party_api_call_claimed": true, "no_arr_or_paying_users_claimed": true, "no_client_reliance_claimed": true, "no_professional_certification_claimed": true, "scenario_ready": false, "answer_ready": false, "promotion_allowed": false, "human_review_complete": false, "client_reliance": false, "semantic_search_active": false, "professional_certification": false } }