SAMPLE // REDACTED

Executive Summary

Subject: AI Readiness Assessment & Implementation Strategy

Curam-Ai conducted a 3-week analysis of Client Name workflows. This assessment utilized the Curam-Ai Protocol™ to identify high-friction administrative tasks.

The Bottom Line:
We identified $214,500 in recoverable annual revenue. This figure is validated by raw data sampling (See Appendix A).

1.1 The "Size of the Prize" (Year 1)

Metric	Current	Future	Delta
Admin Burden	45 hrs/week	12 hrs/week	-65%
Proposal Velocity	08 /month	14 /month	+40%
Error Rate	4.2%	<0.5%	Risk Mitigated
Net Impact	—	—	+$214,500

SAMPLE // REDACTED

2.0 Workflow Analysis

Priority A: Beam Schedule Digitization

Problem: Manual transcription from PDF to Excel.
Validation: We processed 50 historical schedules. (See Appendix B for failure analysis).
Result: Azure AI Document Intelligence extracted tabular data with 98.5% accuracy.

Priority B: Drawing Register Management

Problem: Version control errors leading to site rework.
Risk Cost: $35,000 per major rework event.
Solution: Power Automate file parser.

SAMPLE // REDACTED

3.0 Investment & ROI Analysis

3.1 Cost of Implementation

Wave 1 Setup	$12,000
Configuration	$10,000
Training	$6,500
Total Year 1	$28,500

3.2 Operational Cost Analysis (Azure Consumption)

Based on the sampling of 50 documents, the ongoing cloud consumption costs are negligible relative to labor savings.

Resource	Unit Cost	Volume	Monthly Cost
Azure AI Doc Intelligence	$10 / 1k pages	450 pages	$4.50
Logic Apps / Flow	$0.000125 / action	2000 runs	$2.50
TOTAL OPEX	—	—	< $10.00 / mo

3.3 Value Realization

Admin Time Recaptured	$142,000
Risk Mitigation	$35,000
GROSS RETURN	$214,500

SAMPLE // REDACTED

4.0 Phased Execution Plan

Wave 1: Foundation (Month 1)

Governance Configuration.
Invoice Processing Deployment.
Beam Schedule Extraction Deployment.

Wave 2: Growth (Months 2-3)

Tender Assistant Deployment.
ERP Integration.

Commercial Guarantee

Curam-Ai stands by the Protocol. The Phase 4 Statement of Work (SOW) includes:

30-Day Warranty: Any bugs or logic errors fixed at no cost.
Performance Retention: Client holds 15% of fee until success metrics are met.
IP Ownership: 100% transfer of source code and flows to Client Tenant.

TECHNICAL APPENDIX

5.0 Technical Validation: Data Diary

To validate the ROI assumptions, Curam-Ai ran a random sample of 50 vendor invoices. The table below represents the raw system logs.

Doc ID	Processing Time	Confidence	Status
INV-2024-001	4.2s	0.99	SUCCESS
INV-2024-002	3.8s	0.98	SUCCESS
INV-2024-003	4.1s	0.98	SUCCESS
INV-2024-004	5.6s	0.82	FLAGGED
INV-2024-005	3.9s	0.99	SUCCESS
INV-2024-006	2.1s	0.45	FAILED

TECHNICAL APPENDIX

6.0 Failure Mode & User Experience

The system is designed to "Fail Safe." Below is the actual Teams Notification generated when File INV-2024-004 (Flagged) required human intervention.

The Human-in-the-Loop Workflow

🤖 FINANCE BOT • Now

⚠️ Review Required: Low Confidence Score

The invoice from Local Courier has a confidence score of 0.82.
Potential Issue: Date format ambiguous.

Please verify before export to Xero.

Review Document

Action Taken: Staff member clicked "Review", corrected the date, and the system learned from the correction.

TECHNICAL APPENDIX

7.0 Prototype Logic (Power Automate)

The following logic block demonstrates the validation step preventing ABN fraud.

// STEP 4: VALIDATION LOGIC
// PREREQUISITE: SharePoint List "Approved_Vendors" must exist.

$Vendor_Check = SharePoint.GetItems(
    List="Approved_Vendors",
    Filter="ABN eq '@{items('Extract_ABN')}'"
);

If (length($Vendor_Check) == 0) {
    // FAIL SAFE
    Post_Message_Teams(Channel="Finance Alerts", Message="⚠️ FRAUD ALERT");
    Terminate(Status="Cancelled");
}
        

System Prerequisite: This logic requires the "Approved_Vendors" list to be synchronized with your ERP master data.