Business analysis with the ability to build.

Before choosing software, establish what the business needs it to do. I work with the people involved to map the current process, identify the rules and agree on what a better result would look like.

Those requirements are the basis for evaluating existing applications. I look at what a product covers and where it falls short before recommending whether to buy or build.

• Current and future workflows, including responsibilities and exceptions
• Business rules, data flows and acceptance criteria
• Market assessment, software evaluation and ERP fit/gap analysis

A process can accumulate extra steps over time: a duplicate entry, a spreadsheet check, an email asking someone to confirm a number. I look at why those steps exist and which ones can change.

The review also looks at ownership and controls. A shorter process still needs a clear way to handle mistakes and exceptions.

• Workflow redesign and removal of duplicate work
• Data quality, reporting and control points
• Automation opportunities after the process has been reviewed

ERP, payroll and project applications often hold different parts of the same record. An integration needs to establish which system owns each field, how identifiers match and what happens when data fails validation.

I design and build connections using APIs, databases and files, with controls for the people responsible for running them.

• Field mapping, transformations and master-data synchronization
• Scheduled or event-driven processing
• Status, exception handling and audit history

See Integration Hub

Custom development begins with a requirement that suitable existing software cannot meet. After assessing the market, I build web and Windows applications for those needs, or develop the missing parts around an existing product.

The scope includes the parts needed to run the application day to day: administration, background jobs, error handling and reporting. Development uses .NET and C#, with SQL Server, APIs and Azure where they fit.

• Web and Windows applications
• Database, API and Microsoft 365 integration
• Data processing, reports and administrative tools

You know AI could help somewhere. You don’t need AI everywhere.

Start with a job worth testing, such as searching an archive or extracting information from documents. The design needs to account for source evidence, human review and where the data is allowed to go.

• Document search and questions answered with supporting sources
• Classification, extraction and workflow assistance
• Local or cloud models chosen around privacy and hosting requirements

Explore Data Discovery

An older application may contain years of business decisions in its screens, SQL procedures and reports. Understanding those rules is part of replacing or changing the software.

I can examine the application and its dependencies, document what must survive, and assess whether an existing product can take over the job. Where a rebuild is needed, we can plan a staged transition using modern .NET, a web interface, an API or database changes.

• Code, database and dependency assessment
• Business-rule extraction and a modernization roadmap
• Rebuilding, data migration and validation alongside the existing system

Discuss a legacy application

A new ERP is an opportunity to improve the information your business relies on. Missing records, inconsistent coding and obsolete information deserve attention before they become part of the new system.

I work with your team to assess the existing data and agree what should move, where information can be added or corrected, and what can be left behind. I then build and test the migration routines and supporting integrations, giving the people responsible for the data a clear basis for review and acceptance.

Your team makes the business decisions. I help explain their implications and carry the agreed approach through the technical work.

• Reviewing existing data for gaps, inconsistencies and unnecessary content
• Defining how records and business rules map into the new system
• Building repeatable migration routines and validation checks
• Connecting the ERP with applications that need to exchange information with it

Discuss an ERP migration

See how EMS Extension prepared project time for UKG payroll.