Lukasz Komur

Before we work together

A practical overview for founders, small companies and early teams who want to understand how direct cooperation with a software engineer can work before scheduling a conversation.

Schedule a meeting Back to main page

This page is mostly for people considering direct cooperation with an engineer instead of immediately going to a software house or building a full internal team. If I join an established company or existing engineering team, I naturally adapt to its processes, tools and policies.

Who this page is mainly for

These details are most useful for people and companies that are still shaping how technical cooperation should look.

This page is mainly for founders, small businesses, startups, early-stage teams, or non-technical decision-makers who want to work with a software engineer but are not yet sure how such cooperation should be organized.

If I join an established company, existing engineering team, or recruitment process, I naturally adapt to the company’s tools, policies, onboarding, communication rules and security requirements.

The goal is to reduce uncertainty for people who are considering direct cooperation with an engineer instead of immediately going to a software house or building a full internal team.

Startups
Small companies
Early teams
Founders
Non-technical owners
Software house alternative

Cooperation basics

A quick summary of the most common formal and practical cooperation details.

B2B
VAT invoice
Contract-based cooperation
US market experience
Remote from Europe
CET / CEST
Client device possible
Private macOS setup possible

I can cooperate on a B2B basis and issue VAT invoices for companies in Poland and Europe.
For clients outside Europe, including the United States, cooperation can be contract-based without employment on the client side.
I have experience working with US clients and teams, so the cooperation model, communication style and expectations of that market are familiar to me.
I work remotely, preferably from Europe and CET / CEST-friendly working hours.
For part-time, project-based or short-term cooperation, I can be flexible with meeting times within reasonable limits.
I can work on client-provided equipment or on my private macOS setup, depending on security and project requirements.

Secure remote setup

I maintain a security-conscious remote work setup and can also follow the client’s access requirements.

Own VPN
Secured network
MFA
Password manager
Private macOS setup
Client security policy

I use my own VPN and secured network setup for remote work when appropriate.
My professional accounts are protected with MFA and managed with security-focused practices.
If the client requires specific access rules, VPN, device policy, MFA, or internal procedures, I can adapt to that setup before starting work.

Communication setup

Communication can be adapted to the client’s workflow, team maturity and technical background.

If the client already has tools and processes, I can join the existing setup.

For smaller or side projects, I can help establish a lightweight communication flow using professional tools instead of creating unnecessary process overhead.

When working with non-technical stakeholders, I can translate technical topics into practical decisions, risks and next steps.

The goal is simple: clear context, visible decisions and enough structure to move the work forward.

Technical teams
Non-technical stakeholders
Email
Video calls
Task tracking
Documentation
Code collaboration

Availability and timezone

My preferred working timezone is Poland / Central European Time, especially for long-term or full-time cooperation.

For full-time, long-term or team-based cooperation, I prefer CET / CEST-friendly working hours.
For European clients, this usually works naturally within normal business hours.
For part-time, project-based or short-term cooperation with clients outside Europe, I can adjust meeting times when needed.
For US clients, I can be flexible with later Polish hours, but please keep in mind that 4:00 PM on the US East Coast is already around 10:00 PM in Poland, depending on daylight saving time.
I am flexible for important meetings, handovers, production topics or urgent situations, but I do not treat very late-night calls as a default working model.

Working with teams

I can join an existing team or work independently when the project needs focused technical ownership.

I can adapt to existing repositories, workflows, planning processes and communication channels.

For smaller projects, I can help organize the technical direction without adding unnecessary process overhead.

Clear context, practical communication and access to decision-makers usually matter more than heavy process.

The goal is simple: enough structure to move the work forward without slowing everyone down.

Non-profit and impact projects

I am open to selected non-profit or reduced-rate cooperation when the project has a real impact on animals, the planet, or human life.

If you are building something that helps rescue animals, protects the environment, supports emergency response, or can help save lives, you can contact me even if the project is not purely commercial.

I may be able to help design or build needed platforms, internal tools, automation, drone-related software, integrations, or other technical solutions that support the mission.

I cannot promise availability for every request, but if the project is meaningful and technically realistic, reach out and we can check what can be done.

Animal rescue
Environmental protection
Life-saving technology
Drones
Impact platforms
Non-profit support

Before we start

To avoid confusion later, it is useful to agree on a few basics early.

what problem we are trying to solve,
what kind of help or responsibility you expect,
how we will communicate and organize the work,
what access, equipment or security setup is required,
what availability and timezone overlap makes sense,
what contract, invoice or billing setup is needed.