Conducted ERP readiness by leveraging Microsoft’s Power Platform

The initiative began with an in-depth diagnostic review of HCS’s cross-departmental workflows, technical literacy, and technical assets to identify critical barriers to digital integration.

Through surveys, workshops, and data analysis across Finance, HR, Procurement, and Programs, our team exposed major architectural gaps blocking immediate ERP rollout:

• Data and System Isolation: Finance, HR, and Procurement units operated on separate, siloed tracks with entirely broken or non-existent online data linkages, forcing manual reconciliation and redundant data re-entry.
• Outdated Software Tools: The primary accounting tool operated under an expired Peachtree license, legacy electronic forms relied on Microsoft InfoPath (discontinued by Microsoft), and default data tracking depended on non-collaborative, error-prone offline Excel sheets.
• Hardware and Browser Incompatibility: A significant portion of the workforce utilized legacy desktop computers running Windows 7, an unsupported operating system completely incompatible with modern web browsers and the upcoming Microsoft 365 Dynamics ERP platform.
• Low Digital Identity Standards: Many staff members lacked official corporate email accounts or struggled with basic digital skills, meaning unauthorized sharing of personal credentials posed an identity security and adoption risk.

Output: A comprehensive baseline report detailing internal control gaps, system bottlenecks, and infrastructural prerequisites for ERP positioning.

To bridge the gap between HCS’s manual status quo and full-scale ERP capabilities, our team designed an intermediate digital framework using available Microsoft 365 and Power Platform tools.

Rather than treating technology as a rigid enforcement of rules, the design phase used high-volume, low-risk sub-workflows as an educational sandbox to cultivate system trust, define relational data logic, and simulate a miniature ERP ecosystem.

iWork deployed a pilot testing structure to engineer baseline configurations and observe user adaptability:

• Standardized Data Formats: We established standardized digital entry templates with mandatory fields to replace highly volatile, inconsistent manual documentation models.
• Built-in Preventive Controls: The system architecture introduced automated structural logic, such as automatic sequential ID generation, required digital attachment uploads, and conditional overlap checks to prevent input errors at the source.
• Departmental Collaboration Bridges: Approvals were routed natively through Microsoft Teams and SharePoint, linking previously isolated teams under a single, trackable communication thread.
• Data Centralization: Redesigned liquidation workflows fed automatically into a live Payment Voucher (PV) Register, demonstrating how transaction status filters could establish end-to-end operational visibility.
• Capacity Mapping: The pilot helped identify institutional barriers to system adoption, highlighting which back-office workflows and clerical processing roles would need to evolve into higher-value analytical roles during a digital migration.

Overall, the pilot proved that structuring data inputs and building user confidence were essential prerequisites to withstand the structural rigors of a full ERP rollout.

The deployment phase successfully operationalized the digital sandbox, using the technical data and change management feedback gathered during pilot tracking to embed long-term systems governance.

• Technical Handover and Capacity Retention: HCS IT teams underwent a comprehensive, structured technical handover covering the underlying SharePoint architecture, Power Automate logic, and configuration criteria.
• First-Line Support Network: Selected project champions were trained directly on workflow troubleshooting and system diagnostics, creating a local support system to maximize uptime and reduce external consultant dependency.
• Data Hygiene and Standardization: HCS teams adopted continuous improvement frameworks, rolling out standard document naming conventions and a centralized Finance Data Dictionary to ensure clean data entry into Excel Online and Peachtree.
• Living Standard Operating Procedures: All newly introduced workflows were anchored to detailed Standard Operating Procedures (SOPs) configured with clear revision history logs, teaching staff how to update and evolve documentation independently.
• Real-Time Performance Dashboards: Power BI compliance trackers were integrated into live operations to continuously benchmark approval turnaround times, liquidation windows, and active budget utilization.

Through this initiative, HCS has successfully engineered the core data infrastructure, structural operational disciplines, and frontline digital capacity required to sustain a modern financial ecosystem. The organization has effectively migrated from a manual “black box” environment into a traceable, system-first operation.

By deploying live, automated validation logic and consolidating isolated tracking flows into unified pipelines, HCS has established a robust operational blueprint for full enterprise system integration.

Leadership now possesses real-time oversight and data-driven accountability trails, while local IT staff are equipped to maintain and scale digital configurations.

Ultimately, this project has built a realistic, low-cost bridge that prepares HCS to smoothly execute its upcoming roadmap for MS Dynamics 365 adoption and direct donor funding.