Discuss a project

The useful first message is short: who you are, the system you have, the constraint, and the date that matters. Email is the reliable way to start. This site has no contact form.

What to include

  • The product or system, and whether it is already in production.
  • The decision you are trying to make or the bottleneck you can already name.
  • Constraints that will not move: budget envelope, compliance, a freeze window, a vendor already chosen.
  • Whether you need a review, a slice, a full delivery, or ongoing advisory.

How I respond

If the work is a fit, the next step is a call or a short written scope. Browsing this website does not create a contract. Scope, deliverables, fees, and timing are agreed in writing.

Contact

Based in Gdańsk, Poland. Independent software engineer & consultant.

How estimates work

Share the system you have, the outcome you need, and any fixed deadline or budget range. Scope, deliverables, fees, and timing are agreed in writing before work starts.

Working together

You work directly with me. The scope, review process, documentation, handover, and any ongoing support are defined for each engagement.

  • A review or audit produces a written reading of the system and a recommended next step. It does not include implementation unless that is scoped separately.
  • Implementation includes the agreed software, the review of that work, and the handover defined for the engagement.
  • Advisory is direct collaboration on decisions and review. Meeting cadence and ongoing support are agreed per engagement, not assumed.