Business Analysis & Process Consulting
I analyse workflows, clarify requirements and compare software solutions. For companies that need a sound basis for their decision, with no obligation to commission development afterwards.
Discuss your process analysisStefan Pilz · Analysis available independently · 100% remote
SERVICE OVERVIEW
Business analysis provides a basis for decisions about changes to business processes and software. At SP Webconsulting, I review your current situation with you, document requirements and compare feasible solutions. You can commission the analysis independently; subsequent development is not a prerequisite.
When a company plans to buy software, product names often come up before the actual problem has been defined. Duplicate data entry, unclear handovers and an increasing number of spreadsheet workarounds are also good reasons to analyse a process. I support companies without an internal IT department as well as teams seeking a technical second opinion on a specific project.
SERVICE SCOPE
Together with the people involved, I follow a selected process from its trigger to its outcome. I record the applications, data sources, manual tasks and common exceptions. Handovers deserve particular attention: where does work wait for approval, where is information entered again, and where is ownership unclear?
We turn the problems we observe into prioritised requirements. We distinguish essential operational needs from improvements and items that can wait. This includes permissions, data quality, required integrations and ongoing support. The result is a shared basis for the business team and the people implementing the solution.
I examine different approaches: making better use of existing features, adding an integration, selecting suitable standard software or developing a custom application. The comparison covers setup effort, running costs, data migration and maintenance. My development background helps me assess implementation without treating a new build as the predetermined outcome.
POSSIBLE USE CASES
Example workflow
Follow an enquiry through the business.We document the current process and examine missing information and repeated steps.
The following examples describe possible assignments, not documented client projects.
Documents arrive by email, are saved locally and later entered into another application. We map the actual workflow and assess whether a consistent filing structure, document management or an integration would provide the greatest benefit.
Several employees update product information in the store, PIM and spreadsheets. The analysis establishes which system should own the data, which fields need synchronising and which changes require approval.
A company wants to introduce a new tool for tasks and reporting. We define testable requirements and compare possible solutions against real workflows, rather than relying on feature lists alone.
DELIVERABLES & SCOPE
We agree the deliverables before starting. Depending on the scope, these may include:
A process analysis is not a complete audit of every part of your company. Detailed code reviews, binding vendor statements, legal advice and subsequent implementation are only included where expressly agreed or covered by the appropriate specialists. Unknown interfaces or missing access may initially have to be recorded as open questions.
To get started, describe the problem, the applications involved and the people who work with them. Anonymised sample documents or screen views can help with the later assessment. We agree scope, participants and budget before starting; all discussions and reviews take place remotely.
WORKING TOGETHER
We establish the decision you want to make and the processes we need to examine. This keeps the assignment manageable.
Participants demonstrate real workflows in remote conversations and screen-sharing sessions. Existing documents support the review, and gaps in documentation become visible.
I organise the requirements, review technical dependencies and explain possible solutions. Unresolved assumptions are identified explicitly.
You receive the agreed documents and have an opportunity to ask questions. You can then decide on internal changes, implementation or further analysis.
RELEVANT EXPERIENCE
My background is over 15 years of PHP and web development. I understand the technical questions that follow from business requirements: which data is needed, where dependencies arise and what existing systems can support.
Client project · KRAFTSTOFF Fashion
Concept and technical implementation of a Shopware store for a fashion wholesaler. This project connects business requirements with the structure and functionality of the resulting system.
My own technical work
I use Paperless-ngx for document imports, filing, tagging and processing. This practical experience informs my understanding of handovers and manual tasks; it is not a client reference for process consulting.
QUESTIONS & ANSWERS
No. You can commission the analysis independently and implement the findings internally or with another provider.
Depending on the agreed scope, you receive a description of the processes reviewed, prioritised requirements and a comparison of possible solutions. This includes known dependencies, open questions and an effort estimate. We agree the documents you need before starting.
No. Existing documentation is helpful but not essential. We can map workflows together through discussions, screen sharing and practical examples. The people who work with the relevant tasks every day should be available to participate.
Yes. A defined workflow, such as incoming invoices or transferring product data, is a useful starting point. We agree the question to investigate and a budget. If dependencies on other areas emerge, we discuss them before extending the assignment.
Yes. I first examine what can be achieved with existing features, a different configuration or an integration. New software and custom development are evaluated as alternatives, including running costs, data migration and support requirements.
NEXT STEP
Describe the current workflow, the applications involved and your desired outcome. Together, we will define a useful scope for the analysis.
Your enquiry goes directly to me, Stefan Pilz. We agree the scope and costs before you commission any work.
I read your enquiry and get back to you. Together, we clarify your goals, constraints and open questions.
Depending on the project, we start with a specific implementation or an analysis agreed in advance.
You know which services and deliverables are included. We agree on scope, effort and costs before you commission the work.