Processes → Automation → AI

Less repetitive work. More control over the process.

If requests disappear in email, decisions wait for reminders, and data is copied between forms, Excel and SharePoint, I organize the process and build automations, business apps and AI agents inside Microsoft 365.

Explore the services Assess your process

Real system screenshots Microsoft 365, Power Platform and AI agents Solutions fitted to the process

From a business problem to a working process

Operational frictionemail, spreadsheets, manual reminders and no single source of status

Structured workflowintake, rules, ownership, statuses and automated actions

Visible outcomeless retyping, faster decisions and a complete history

ProcessAutomationAI

Requests without ownershipNo one knows what is new, urgent or already resolved.

Decisions buried in inboxesApprovals and comments disappear in long email threads.

Data in several placesThe same information is copied and corrected again and again.

How I can help

Three ways to improve a process.

We start with the problem and the current state, not a promise of a large implementation. Then we agree on a useful first scope and how to assess the result.

01 / REPAIR

Power Automate audit and repair

For flows that fail, depend on one person or are difficult to change safely.

Explore audit and repair

02 / BUILD

Power Apps and process automation

For requests, approvals and statuses scattered across inboxes, spreadsheets and SharePoint.

See how I structure a process

03 / AI

Copilot Studio AI agent

For recurring questions or a more structured entry point into a business process.

Explore agent use cases

Where deeper discovery or a pilot is needed, we agree on the scope, output and quote before work starts. We assess impact against a baseline, without promising specific savings in advance.

My own solutions

Three working examples. Real proof of how they work.

Open an example to see the workflow, technology and real screens from the systems I have built.

Purchase Request System

Implementation package

Purchase requests stop moving through email and receive one number, one status and one decision history.

Outcome: faster approvals with a complete audit trail.

Problem → solution → outcome

A controlled purchasing workflow in Microsoft 365.

A user submits a request in a canvas app. The system assigns a durable number, validates the data and starts approval. The decision, comments and resubmission of a rejected request remain in one place.

One point of entry: a responsive app instead of email and spreadsheets.
Decision without searching: approve or reject from an Outlook message.
Complete history: request number, status, comments and controlled resubmission.

Power AppsPower AutomateSharePointOutlook Approvals

Status: a portfolio solution built and tested in a Microsoft 365 environment. A client implementation requires adapted permissions, thresholds and approval routing.

Purchase request list with request numbers and statuses — One queue with clear statuses.

New purchase request form with validation — Validation before submission.

Rejected request details with resubmit option — Controlled resubmission.

Request Intake & Follow-up System

Implementation package

Requests from forms, phone and email enter one queue with an owner, a due date and a visible next action.

Outcome: every request receives an owner, a due date and a clear follow-up path.

From intake to closure

One queue for every incoming request.

The system receives a request, assigns a number, guides the owner through statuses and deadlines, follows up on inactivity and preserves the history if a case is reopened.

Five automations: numbering, form intake, optional AI classification, deadline control and closure.
Three responsive screens: queue, details and new request.
Team control: owner, priority, next contact and a clear status.

Power AppsPower AutomateSharePointTeamsOptional AI Builder

Status: a complete reference system built and tested inside Klimek Automation. A client setup requires mapping its SharePoint site and connections. Optional AI classification requires separate configuration and appropriate licences.

Ask about this system

Request queue in the Request Intake app — Priority, status and next-contact date in one queue.

Manual new request screen — Log a request received by phone or email.

Mobile request queue — Responsive mobile view.

Bilingual AI Agent

Live in production

The agent handles first contact in Polish or English, identifies the process problem and routes a qualified inquiry into the right path.

Outcome: a complete first-contact system, not just a chat window.

First-contact system in Polish and English

From conversation to a structured inquiry.

This is not a standalone chatbot. The agent speaks two languages, asks qualifying questions, summarizes the problem and routes the visitor to a dedicated Polish or English form. Two flows store the data in one shared list and start the follow-up process.

PL / EN webchatQualificationPL / EN formInquiries listConfirmation and alert

Two languages: the full conversation and next step in Polish or English.
Two forms and two flows: content and communication stay aligned with the contact language.
Production operation: the published agent runs on a pay-as-you-go model.

In practice: this system handles the first contact with Klimek Automation and directs each visitor to the appropriate PL or EN path.

Copilot StudioPower AutomateMicrosoft FormsSharePointAzure PAYG

Open the English form

English conversation with the live Klimek Automation Agent: the offer to send the topic, a summary of the answers and the button to the contact form — Public webchat: qualification summary and handoff to the English form.

Real implementation view of the agent's process qualification topic in Copilot Studio, shown in the original Polish workspace — Real implementation view in Copilot Studio (original Polish workspace).

Audit and repair existing solutions

Did the system work until the person who built it left?

I take over existing flows, apps and agents. I identify what really happens inside, remove failures and simplify the solution so the team can operate it safely.

Diagnosis and dependency map

I review triggers, connections, service accounts, lists, conditions, licences and the points where the process can fail.

Repair or a simpler rebuild

I repair the critical flow or agent. If the current design is too fragile, I propose a simpler option without adding unnecessary tools.

Documentation and safe handover

You receive a clear operating description, a change log, testing guidance and the information needed to maintain the system.

Typical situations: a flow stopped working, documentation is missing, the previous builder left, the agent responds inconsistently or every change risks an outage.

Describe an existing system

How I work

Process first. Automation second. AI only where it adds value.

Technology does not fix unclear rules. A useful build starts with understanding the process, not with choosing a tool.

STEP 01

Structure the process

Define the entry point, owner, decisions, exceptions and the moment a case is truly complete.

STEP 02

Automate repetition

Remove retyping, manual confirmations, deadline chasing and searching for the current status.

STEP 03

Give AI a clear role

AI classifies, summarizes or qualifies. People still make decisions and own the outcome.

AFTER GO-LIVE

You are not left alone with the system.

Each implementation includes documentation, handover and 30 days of support within the agreed scope. Further development is handled through a monthly maintenance arrangement or a separately quoted change.

Maciej Klimek, founder of Klimek Automation

About me

Operational experience combined with Power Platform.

My name is Maciej Klimek. I know processes from practical work, not only from diagrams. My background covers manufacturing, warehousing, construction, assembly and process operations. I also ran my own business and delivered projects in several EU countries.

Around 20 years of professional and operational experience. It helps me distinguish where a system genuinely removes work and where it would only add more clicks.

Microsoft Applied SkillsCreate and manage automated processes by using Power Automate Microsoft Applied SkillsBuild an agent in Microsoft Copilot Studio Microsoft Applied SkillsEnhance agents with autonomous capabilities Microsoft Applied SkillsCreate and manage canvas apps with Power Apps

Additionally: PL-7001, PL-7002 and PL-7003 instructor-led Power Platform training completed through a Microsoft Training Services Partner.

View my LinkedIn profile

The first step

Describe a process or an existing system that consumes time or repeatedly creates errors.

I will check whether it should be repaired, simplified or rebuilt. If the change does not make economic sense, I will say so directly.

Free process assessment

Before submitting personal data, please read the privacy policy.