Microsoft Automation for SMEs

Process Improvement &
Microsoft Automation

I help businesses reduce rework, improve process reliability, and make better use of operational data through practical Microsoft-based solutions.

Process
First Approach
M365
Native Tools
SME
Focused

Built with
Power Automate · Power Apps · Dynamics 365 · SharePoint · SQL

Why Cornejo Logic

What makes my approach different

Rather than focusing only on tools, I start by understanding the process itself — its inputs, outputs, bottlenecks, and common sources of error.

Process-first, not tool-first

I focus on the real business problem before deciding which tool should be used.

Designed to reduce rework

I identify repeated admin effort, misunderstandings, and process gaps that create inefficiency.

Built for practical use

The goal is not just automation, but a workflow the business can actually use and maintain.

Data-aware implementation

I help structure process data to better support internal reporting and KPI tracking.


Workflow Approach

How it works

A structured, four-step approach that goes from understanding the problem to ongoing support after deployment.

1
🔍

Process Review

I meet with the client to understand the process in detail, identify manual bottlenecks, unclear handovers, and common sources of error.

2
🧭

Solution Design

I design a practical Microsoft-based solution using the tools already available in the client’s environment wherever possible.

3
⚙️

Build and Testing

I build the automation, test the logic, and adjust the workflow based on real business requirements.

4
🛡️

Support and Maintenance

After deployment, I provide monitoring, troubleshooting, and support — because real-world process variations and exceptions often emerge after implementation.


Services & Pricing

Practical services for process improvement and automation

Projects are priced based on scope, complexity, and business requirements. The examples below are starting points for smaller business engagements.

Discovery / Process Review

A$250

A focused review of one business process, including an initial discussion, high-level assessment, and a recommendation on whether the process can be improved or automated.

Starter Automation

A$950

Best for one simple workflow such as approvals, reminders, notifications, or a small internal admin process. Includes basic testing and one round of small adjustments.

Business Workflow

A$1,900

Designed for more connected processes involving approvals, notifications, SharePoint actions, or internal workflow logic. Includes testing, refinement, and short implementation notes.

Advanced Workflow / CRM / Portal

From A$3,800

For more complex solutions involving Dynamics 365, Power Pages, multi-step logic, document movement, or broader operational workflow design.

Support Plans

Basic

A$300/month

Up to 2 support hours per month. Ideal for businesses with a small number of simple automations.

Standard

A$650/month

Up to 5 support hours per month. Includes monitoring, minor fixes, reviews, and small updates.

Advanced

A$1,200/month

Up to 10 support hours per month. Ideal for businesses with multiple connected workflows or more active automation environments.

Additional support: A$95/hour. Unused hours do not roll over. New builds and major changes are quoted separately.


Support & Maintenance

Why support is necessary

Business automations are not always “set and forget”. Over time, flows can be affected by changes in business rules, connector behaviour, permissions, disabled accounts, data variations, or Microsoft platform updates.

Ongoing support helps with monitoring, troubleshooting, fixing failed runs, adjusting logic, updating actions, and maintaining ownership and stability when operational changes happen.

In practice, support often means reviewing alerts, correcting broken steps, updating flow actions, and resolving issues before they disrupt the business process.


Client Requirements

What clients need to provide

Clients should already have the relevant Microsoft 365 environment and licences required for the solution they want to implement.

To ensure continuity, ownership, and proper governance, automations should be built inside the client’s own Microsoft environment rather than under a personal account.

For this reason, clients are expected to provide a business account or service account under their domain for implementation, ownership transfer, and long-term operational use.

That account should be treated as an ongoing operational account and should not be disabled after deployment, because disabling the connected account can cause automations to fail.

Where required, ownership and key actions should be transferred to the client’s designated operational account so the solution remains within the client’s own system.


Contact

Let's discuss your process

If your business is dealing with repeated admin work, unclear approvals, disconnected data, or underused Microsoft tools — I can help assess whether the process can be improved or automated.

Initial enquiries are handled by email first. Virtual meetings are available by appointment. Or email to admin@cornejologic.com