{
  "version": "1.0",
  "updated": "2026-09-14",
  "publisher": {
    "name": "Number7 AI",
    "legal_name": "Number7 AI Solutions Private Limited",
    "product": "AIdaptIQ",
    "url": "https://number7ai.com/"
  },
  "methodology_url": "https://number7ai.com/proof/benchmarks/",
  "evidence_policy": {
    "rule": "Cite a numeric result only with its evidence type, workflow scope and limitations.",
    "statuses": [
      "customer-reported",
      "derived from customer-reported figures",
      "qualitative workflow change"
    ],
    "separation": "Results from different customers or workflows must not be combined into one benchmark."
  },
  "cases": [
    {
      "id": "pransform",
      "customer": "Pransform Inc.",
      "workflow": "Multi-client accounts payable operations",
      "source_url": "https://number7ai.com/case-studies/pransform-bpo-invoice-automation/",
      "evidence_type": "customer-reported",
      "verification": "Not independently audited",
      "claims": [
        {
          "id": "pransform-monthly-volume",
          "statement": "Pransform reports processing 50,000+ AP documents per month with AIdaptIQ in the described workflow.",
          "value_text": "50K+",
          "lower_bound": 50000,
          "unit": "AP documents per month"
        },
        {
          "id": "pransform-client-companies",
          "statement": "The described Pransform workflow spans 300+ client companies.",
          "value_text": "300+",
          "lower_bound": 300,
          "unit": "client companies"
        },
        {
          "id": "pransform-staffing-change",
          "statement": "Pransform reports that the AP staffing requirement for the described workflow changed from 12 people to 3.",
          "value_text": "12 to 3",
          "before": 12,
          "after": 3,
          "unit": "AP staff required"
        },
        {
          "id": "pransform-staffing-reduction",
          "statement": "The reported 12-to-3 staffing change is a derived 75% reduction in staffing requirement for the described workflow.",
          "value_text": "75%",
          "value": 75,
          "unit": "percent",
          "evidence_type": "derived from customer-reported figures",
          "calculation": "(12 - 3) / 12"
        },
        {
          "id": "pransform-workflow-stp",
          "statement": "Pransform reports 90%+ straight-through processing inside the described workflow boundary.",
          "value_text": "90%+",
          "lower_bound": 90,
          "unit": "percent",
          "qualification": "The public material does not provide the complete transaction-level denominator, measurement window or manual-intervention log required to reproduce the calculation."
        },
        {
          "id": "pransform-payback",
          "statement": "The production reference reports payback under one month for the described deployment.",
          "value_text": "under one month",
          "upper_bound": 1,
          "unit": "month",
          "qualification": "Customer-reported deployment result; not a forecast for another workflow."
        }
      ],
      "limitations": [
        "One scoped workflow, not a universal benchmark.",
        "A staffing requirement is not the same as total delivery cost.",
        "Document mix, policy, integrations, assistance and terminal state affect transferability."
      ]
    },
    {
      "id": "jsk-automation",
      "customer": "JSK Automation",
      "workflow": "Purchase-order intake from email PDFs, scans and WhatsApp-originated images",
      "source_url": "https://number7ai.com/case-studies/jsk-automation-purchase-order-processing/",
      "evidence_type": "customer-reported",
      "verification": "Pilot figures are not independently audited",
      "claims": [
        {
          "id": "jsk-input-channels",
          "statement": "The described JSK Automation workflow combines purchase orders from three input channels.",
          "value_text": "3",
          "value": 3,
          "unit": "input channels"
        },
        {
          "id": "jsk-intake-speed",
          "statement": "JSK Automation reports 10× faster purchase-order intake in the described workflow.",
          "value_text": "10×",
          "value": 10,
          "unit": "relative intake speed"
        },
        {
          "id": "jsk-pilot-field-accuracy",
          "statement": "JSK Automation reports 98.7% field accuracy in pilot validation.",
          "value_text": "98.7%",
          "value": 98.7,
          "unit": "percent",
          "qualification": "Pilot field accuracy is not workflow STP, posting-safe accuracy or a production-wide guarantee."
        }
      ],
      "limitations": [
        "The published evidence does not disclose a common controlled denominator for every timing figure.",
        "No staffing reduction, realized revenue uplift or payback measurement is supplied.",
        "Input source does not imply a specific direct WhatsApp API integration."
      ]
    },
    {
      "id": "fairlorry",
      "customer": "Fairlorry",
      "workflow": "Freight invoice and lorry-receipt reconciliation around an existing TMS",
      "source_url": "https://number7ai.com/case-studies/fairlorry-real-time-reconciliation/",
      "evidence_type": "customer-reported",
      "verification": "Not independently audited",
      "claims": [
        {
          "id": "fairlorry-reconciliation-cadence",
          "statement": "Fairlorry reports that manual reconciliation previously ran in 2–3 day cycles before moving toward continuous, exception-led checks.",
          "value_text": "2–3 days to continuous checks",
          "before_range": [
            2,
            3
          ],
          "before_unit": "days",
          "after": "continuous exception-led checks"
        },
        {
          "id": "fairlorry-system-boundary",
          "statement": "The described reconciliation workflow operates around the existing transport management system rather than replacing it.",
          "value_text": "Existing TMS retained",
          "unit": "system boundary",
          "evidence_type": "qualitative workflow change"
        }
      ],
      "limitations": [
        "Continuous checking does not mean every commercial dispute resolves instantly.",
        "No independently audited headcount, recovered-cash or payback result is supplied.",
        "Detected, accepted and recovered adjustments are separate measures."
      ]
    }
  ]
}