Package · Implementation
Pilot Implementation
A four-week implementation package covering a single company department, from mapping processes to deploying the first tools into production.
4 weeks of work. One company department. Six area-specific variants to choose from. Staged payment with a decision point after the first week.
Characteristics
What Pilot Implementation is
Pilot Implementation is the first full delivery package in the Applied AI methodology. Four weeks of work by the Artech team within one chosen department of the company. The package is addressed to companies beginning AI implementations in a structured way.
AI is not a goal in itself here. Some of the department's everyday problems are solved with simpler means: procedural order, small non-AI automation, a better-organized flow of information. These solutions also remain within the scope of the package. AI is applied where it genuinely shortens work time or eliminates a recurring error.
After four weeks, two things remain with the company. The first is one or two working solutions in the team's daily use. The second is a list of next steps: ideas submitted by the team itself, a map of the department's everyday problems, and ready-made descriptions of further solutions.
Variants
Six area-specific variants
Each variant corresponds to one functional area of the enterprise and includes a pre-configured catalog of typical process problems. The mechanics of the package remain shared.
Sales
For the sales department of a manufacturing company.
See the variant →Marketing
For the marketing department of a B2B manufacturing company.
See the variant →Logistics
For the logistics department of a manufacturing company.
See the variant →Service
For the service department, customer service office, or helpdesk of a manufacturing company.
See the variant →Technical Quotes
For the technical quotation department, technical tendering function, or cost-estimating unit within a manufacturing company.
See the variant →Production & Technology
For the technology department, commissioning department, production department, or operator support function within a manufacturing company.
See the variant →In situations where the client's department does not fit any of the variants (R&D, quality control, purchasing), the package is delivered under the standard mechanics, and the catalog of problem areas is built from scratch during the first week.
Fit
When it makes sense
Pilot Implementation is suited to companies in a particular organizational and decision-making situation.
Market pressure forced a decision on AI
Management has watched competitors, suppliers, and clients talk about AI. The decision has been made, but there is no plan for a first step. Pilot Implementation turns that pressure into a structured first implementation within a single department, with a measurable result within four weeks.
Following an AI Readiness Audit
The audit delivered a roadmap with a priority department. Pilot Implementation carries out the first recommendation in a way that leaves the company with both working solutions and a foundation for planning further departments.
Earlier attempts at AI did not stick
The company tested off-the-shelf tools or ran implementations that did not remain in daily use. The reason was usually not the technology, but a lack of fit with the department's real processes. A pilot with the department's team as co-author addresses this problem directly.
Planning an application to the Dig.IT program
The company is considering applying in the next Dig.IT call (the Polish Agency for Enterprise Development announced it for 2026). Pilot Implementation falls within the scope of eligible expenses. Delivering it before or alongside the application provides strategic material for the documentation.
Course
How Pilot Implementation unfolds
The four weeks of work are divided into four stages, each with a defined function.
Week 1
Department Discovery
Work with the department's team at the company's premises. Conversations with the manager and staff, observation of everyday processes, identification of recurring problems.
Week 2
Workshop with the team
Workshop sessions in which the department's team, together with the consultant, identifies specific process problems and designs solutions.
Week 3
Solution design and start of build
The selected solutions are prepared for implementation. Building of the priority tools begins.
Week 4
Deployment and presentation to the management board
Rollout of the solutions in the company's working environment, training of the team, and support during the first days of use. The package concludes with a presentation to the management board.
Results
What remains after four weeks
Pilot Implementation concludes with five parallel results that remain with the company.
- 01
Working solutions in daily use
Deployed solutions operating in the company's working environment, ready for the department team's daily work. Together with user documentation and staff training.
- 02
A list of ideas submitted by the team
Solution proposals formulated by the department's own team during the workshop. The list reflects real, everyday problems, not a generic catalog of AI possibilities.
- 03
A map of the department's everyday problems
A document organizing the department's process problems, their interdependencies, and the points where solving one problem unlocks the next. A working document for management and the department manager.
- 04
Descriptions of further solutions for future implementation
Ready-made descriptions of solutions that were not implemented within the package but are prepared for further work. Each description includes the objective, the user profile, and the data required.
- 05
A plan for further cooperation
A proposal for the next step after the Pilot: scope, timeline, terms of cooperation. No obligation to continue. The decision remains with the company.
Collaboration
The department team's involvement
Pilot Implementation works with the department's team, not around it. The consultant leads the process, but identifying problems, designing solutions, and deciding on priorities happen in collaboration with the employees who know the department's daily reality.
This model has practical consequences. The results are matched to the team's actual work, not to outside assumptions. When the package concludes, the solutions remain with the company together with the team that co-authored them and knows how to work with them and develop them further.
FAQ
Frequently asked questions about AI implementation in a manufacturing company
Answers to the questions that most often come up before deciding on a first AI implementation.
Where should a manufacturing company start with AI implementation?
The first step is choosing a department where a recurring process or operational problem exists. AI implementation delivers the fastest return when it covers a specific place of work, not the whole company at once. If the choice of department is not obvious, the natural preceding step is an AI Readiness Audit.
How long does AI implementation in a single company department take?
Pilot Implementation in one department takes four calendar weeks. During this time, process discovery, a workshop with the team, solution design, and deployment of the first tools all take place. The pace is set to allow full team involvement without paralyzing its ongoing work.
Does deploying artificial intelligence require a ready-made AI strategy for the company?
No. Implementation within a single department is designed as a first step for companies that are just beginning to work with AI. A company-wide AI strategy usually emerges only after the first Pilot Implementation, based on the real experience of one department.
How does Pilot Implementation differ from working with a software house?
A software house builds a tool according to a delivered specification. Pilot Implementation starts from discovering the department's processes and designing solutions together with the team. The specification emerges during the package. The result: solutions matched to the team's actual work, not to outside assumptions.
Is a prior AI Readiness Audit required?
The audit is not required. Pilot Implementation can start without one, if management is clear on the department where it wants to begin. The audit makes sense when the choice of department is not obvious, there are several candidates, or a strategic document is needed for a grant application.
What if the first weeks of the package don't convince us?
Pilot Implementation includes a decision point after the first week. At that point, the company decides whether to continue, based on the initial results of the consultant's work. The detailed financial mechanism tied to the decision point is provided in the offer proposal after the consultation.
How do I choose the right area-specific variant?
The variant corresponds to the functional area where the company wants to start working with AI. The choice usually follows from the Audit's roadmap or a management decision about the priority department. During the 30-min consultation, the consultant helps determine which variant best matches the department's profile.
Is the catalog of problem areas a fixed list of tasks?
No. The catalog is a starting point, not a final project specification. During the first week, the consultant verifies which areas are actually relevant in the client's department and identifies areas specific to their business. A client with a concrete idea beyond the catalog is not blocked.
Can AI implementation be financed through a Dig.IT grant?
Yes. Pilot Implementation falls within the eligible expenses of the Dig.IT program, Digital Transformation of Polish SMEs. Current funding levels and grant amounts are provided on the Grants page. The Polish Agency for Enterprise Development announced the next call for 2026; the exact date is published on the program's website, digit.arp.pl.
Who leads the implementation on Artech's side?
Pilot Implementation is personally led by Jarosław Jaśkowiak, founder of Artech Consult. The scope covers all meetings with management and the department team, workshop sessions, and the final presentation.
Pierwszy krok
The decision on Pilot Implementation takes one conversation
A thirty-minute online consultation is enough to assess whether the package is the right tool for your company and which area-specific variant best matches your department's profile.
Direct contact: kontakt@artechconsult.com · +48 609 065 717