AI and automation services for businesses in Poznań
As an AI freelancer based in Poznań, I build agents and chatbots and automate business workflows. I connect CRM, ERP, email and calendars. We can meet in Poznań by appointment or work remotely.
We start with how you work, whether on your own, with a team or in a business. Together, we choose tasks to simplify and agree the scope.
Free call. Automation from PLN 490 net, final price once the scope is agreed.
From your workflow to a working solution
- Use casesSales, documents, data and service
- Implementation and testingStages, exceptions and a shared trial
- PricingStarter prices from PLN 490 net
AI implementation and systems integration
I'm Damian Baranowski, a freelancer from Poznań. Professionally I work as a Business Automation & AI Manager, previously as an AI Engineer. I implement AI solutions and integrations for businesses. We can meet in Poznań by appointment. I also work remotely across Poland.
Things I have built include:
- integrations of various systems, apps and tools, including CRM,
- an n8n automation that schedules jobs in a calendar on its own and picks the right resources, passing unusual cases to AI,
- voice and chat agents for customer service, with a knowledge base and CRM connection,
- an online course platform with lessons, quizzes, flashcards and certificates,
- a booking and contact form system, which runs on this website.
AI and automation pricing
“From” prices, net, with 23% VAT included below. No end date. I issue a VAT invoice.
| Service and scope | Price | Typically |
|---|---|---|
| AI and automation | ||
| Simple automationOne workflow, e.g. form → spreadsheet → email or a notification for your team. | from PLN 490 netfrom PLN 602.70 including VAT | Examples: simple automation |
| Automation with AIOne inbox or one type of document, e.g. sorting emails with draft replies, or reading invoices. | from PLN 1,490 netfrom PLN 1,832.70 including VAT | typically PLN 1,500–3,500 net |
| Chatbot or assistant with your company knowledge baseFor your website or your team. It answers from your materials and hands the case over to a person. | from PLN 1,990 netfrom PLN 2,447.70 including VAT | typically PLN 2,000–5,000 net |
| CRM, ERP and API integrationsSeveral systems, stages and tests. We set the scope after reviewing the process and access. | typically PLN 3,000–10,000 net | Tell me about the process |
| Automation maintenanceOptional. I check that it works and fix it after changes in the tools. n8n, Make or API fees are paid by you. | from PLN 99 net / monthfrom PLN 121.77 including VAT | Details: maintenance |
- Final price after our call. We fit it to the scope and it may be lower than the listed price.
- 15% off for a portfolio credit. For agreeing to show the project in my portfolio. It can't be combined with the referral programme; the better discount applies.
- Tool costs are separate. I give you the n8n, Make or AI model API fees before we start, so nothing comes as a surprise.
- Acceptance based on tests. Before we start, we agree the acceptance criteria: which examples we use to check the result and what should happen when something is missing.
How much does automation and an AI chatbot cost? Tool prices and examples
AI pilot, budget and handover
Where should you start with AI implementation?
On a free call, we discuss one workflow, its goal and the tools you already use. If a pilot makes sense, we agree what data it will process, which steps require approval and how we will check that it works.
Can you start with a budget of up to PLN 2,000?
Yes. That covers one process: one inbox or form and one target system, e.g. automation with AI from PLN 1,490 net. Tool fees are agreed separately, before we start.
How do we test a chatbot or AI agent?
We agree the acceptance criteria before we start: which answers and actions are correct and how the solution should react to missing data and integration errors. We check the hand-over to a person and the approvals, if they are part of the scope.
What about personal data in a chatbot?
When I process data on your behalf, we sign a data processing agreement. The AI model provider, such as OpenAI or Anthropic, processes the data as your processor or as a sub-processor, depending on whose API account is used. We agree which data goes to the model, and the person on the other side is clearly told they are talking to AI.
What you can automate in your business
Below are potential use cases we can adapt to your work. Before implementation, I review the process, available data and the capabilities of your tools, then propose a specific scope.
Sales and CRM
Example flow
- Enquiry
- CRM contact
- Owner’s task
- A form enquiry reaches the CRM with information about where the customer came from.
- A new contact is assigned to a person and receives a task according to agreed rules.
- A conversation creates a reminder to follow up or prepare a quote.
- Customer details and the agreed scope fill in a proposal template for review.
- An accepted quote in the CRM creates a job in the delivery system, and progress updates return to the customer’s account owner.
Customer service and jobs
Example flow
- Message
- Case queue
- Responsible person
- Messages from forms and email enter one queue of cases with the appropriate categories.
- A new enquiry receives a case number and an acknowledgement.
- A job moves between people or departments, with assigned tasks, deadlines and approval of the next stage.
- An approaching deadline or a missing reply triggers a reminder for the person responsible.
- A change in job status prepares or sends an agreed update to the customer.
Documents and administration
Example flow
- Form data
- Document
- Review
- Attachments from selected messages go to the right folders and receive consistent names.
- Form data fills in a document, report or confirmation template.
- A request or document is routed for approval according to its value, type and the responsibilities of designated people.
- Deadlines from a document register appear on a task list or calendar.
- Data read from documents enters a summary, while unreadable or missing fields go for review.
Data and reporting
Example flow
- System data
- Shared report
- Verification
- Data from several systems feeds a shared spreadsheet or report without repeated copying.
- A recurring summary of sales, jobs or team workload reaches the designated people.
- Missing fields, invalid formats and suspected duplicates are flagged for correction.
- Sales, cost and delivery data come together in a report, while differences between systems are flagged for review.
- Exceeding an agreed threshold, such as the number of open cases, triggers a notification.
E-commerce and order fulfilment
Example flow
- Order
- Order management
- Store status
- A store order passes the necessary data to an order management or inventory tool.
- Fulfilment and shipping statuses return to the store or a team summary.
- Product data is prepared for import and checked for missing information.
- Agreed product, price and stock data are exchanged between the store, warehouse and wholesaler, with discrepancy checks.
- A return or complaint enters a register with a deadline and a person responsible.
Marketing and communication
Example flow
- Content
- Approval
- Publication plan
- Form signups reach the right list with source information and the consents recorded.
- A change of CRM stage updates the audience segment and prepares the next campaign task, following recorded consents and contact rules.
- Campaign data from several tools enters one shared summary.
- Materials and tasks move from preparation through approval to scheduled publication.
- Unsubscribing updates the related lists used in the agreed process.
AI and connections between tools
Example flow
- Message
- Draft reply
- Your approval
- A longer message or case receives a short summary for the person handling it.
- AI suggests a category and extracts the information needed from text for review.
- Approved materials are used to prepare a draft reply for acceptance.
- Searching company instructions helps find an answer with a reference to its source.
- An assistant combines information from a support request, the CRM and instructions to suggest a next step for your approval.
Who it is for
If you regularly re-enter the same information, track deadlines in several places or search inboxes and spreadsheets for a case status, it is worth looking at that process.
These needs occur in service businesses, sales teams, online stores, agencies, workshops and businesses fulfilling orders. We start with a specific task and how the team works.
Experience connecting systems
I integrate a variety of systems, apps and tools in my professional work, including CRM. I choose solutions to suit the client’s needs and way of working, and continually develop my skills.
I start by understanding the process and checking what is possible. If a solution requires exploring a new technology, I include that stage in the scope and schedule.
From conversation to a checked process
I learn how you work
We agree the workflow, data and expected outcome. We define how we’ll know the solution works and which decisions remain yours.
We agree scope and cost
I check the tools’ capabilities and required access. You receive the scope, quote and schedule. We split larger projects into stages.
I build and test thoroughly
I test the agreed scenarios, permissions, invalid data and interrupted connections. I also check retries for duplicate actions.
We check the result
We run a trial together against the agreed acceptance criteria. We agree how to spot a problem, stop the process and do the work manually.
I launch and hand over
We agree how to launch; larger solutions are rolled out in stages. You receive instructions and access. Monitoring, maintenance and further changes have a separately agreed scope.
Scope, costs and ongoing support
Pricing depends on scope, complexity, the number of system connections and implementation time. Tool costs and ongoing maintenance are agreed separately.
You will find the starter prices in the price list. The final price depends on the number of tools, available integrations, data quality, process variants and the testing needed. Before we start, we agree on the price or how the agreed stage is billed.
We discuss external tool, API and AI service costs separately when they are needed. Automation maintenance and changes after implementation have a separately agreed scope; they are not automatically included in website care packages.
We choose accounts and permissions to suit the process. We agree where data goes, who can access it and which actions need approval. We record documentation and handover arrangements in the project agreement.
Questions about automation and integrations
Which process should we start with?
A task that repeats, has a recognisable flow and takes team time. It could be transferring enquiries to a CRM, preparing a report or tracking job statuses. On our call, we choose a starting point and agree how to tell whether the solution works correctly.
Can you connect systems I already use?
I check the capabilities of the specific tools: existing integrations, APIs, data export and import, and available permissions. I propose a connection method on that basis. If a system lacks the access needed, we discuss alternatives before implementation starts.
What does system and CRM integration involve?
Passing agreed data and events between tools. For example, a website enquiry could create a CRM contact, while a sales stage change prepares a task for the team. We agree which system is the source of each piece of information, when it is updated and how duplicates are handled.
Do you also work on larger processes?
Yes, we can plan a process involving several tools, teams and stages. First, we map dependencies, exceptions and responsibilities. I divide larger scopes into parts that can be checked and accepted separately, rather than launching everything at once.
Does automation always require AI?
No. Data transfer, reminders and many rules can run without AI. AI can help with text work, such as summarising a message or preparing a draft reply. The choice depends on the task, predictability of results and operating costs.
Will AI make decisions and send messages on its own?
We agree separately which actions the system performs and which need human approval. An AI draft reply can wait for review before it is sent. Important actions and exceptions have a defined approval path; using AI alone does not authorise unrestricted actions in your tools.
How do you check that it works correctly?
I test agreed scenarios, data correctness and the result in the destination systems. I also check incomplete data, duplicates, repeated events, connection errors, permissions and behaviour after a retry. Before production, we run a shared trial and acceptance against agreed criteria.
What happens when the process encounters an error?
The project defines how to detect the problem and notify the right person. We agree what can be retried, what needs manual review and how to stop the process. Retries must account for the risk of duplicate records or performing the same action twice.
What data and access do you need?
To start, a process description and the tool names are enough. Once the scope is agreed, we prepare the access and trial data needed. Permissions are limited to agreed tasks, and we agree how data is shared and used before work starts. We also agree which data the solution records, how long it keeps them and how to revoke its access.
How much does automation cost and how long does it take?
Simple automation costs from PLN 490 net, automation with AI from PLN 1,490, and a knowledge-base chatbot from PLN 1,990. The final price and deadline depend on the number of systems, available integrations, data quality, exceptions and the scope of testing. Before we start, you get the scope, price and deadline in writing.
Will maintenance be needed after implementation?
It may be needed, e.g. when a provider changes its API, permissions expire or the way your business works changes. Automation maintenance costs from PLN 99 net per month and is optional. It is not part of the website care plans.
What will I receive when the work is complete?
The solution within the agreed scope, operating instructions and a description of the accounts and access needed. We define the handover of configuration, code and documentation in the project agreement. I also explain how to recognise a problem and what to do if the task needs to be performed manually.
Tell me what you do manually today

Write which tools you use, which steps you repeat and the outcome you want. You do not need to know the technical solution to start a conversation.