Contact

Use this form for relevant professional inquiries related to remote senior .NET work, architecture and maintainability advisory, product or project interest, article feedback, or focused technical collaboration.

I am especially interested in serious remote roles, contract opportunities, and consulting inquiries where .NET architecture, maintainability, long-lived business applications, desktop applications, or practical technical leadership matter.

  • Remote senior .NET, system architect, lead developer, or desktop application roles
  • Contract or part-time advisory work related to architecture and maintainability
  • Focused .NET Architecture Review or codebase maintainability discussions
  • Relevant questions about UCSM, MailFlow, articles, or related projects

I am not interested in SEO outreach, guest-post offers, link exchanges, generic marketing services, vague business opportunities, low-cost outsourcing proposals, or roles that require regular on-site attendance.

A useful inquiry usually includes

A short message is fine, but serious work-related inquiries are easier to assess when they include a few practical details.

  • The role, engagement, or question you want to discuss.
  • Whether the opportunity is remote, hybrid, on-site, full-time, part-time, or contract-based.
  • The main technology stack, especially if it involves .NET, C#, Azure, SQL Server, WPF, desktop applications, or long-lived business systems.
  • The current challenge, such as architecture, maintainability, modernization, technical leadership, testing, delivery risk, or codebase improvement.
  • Any relevant timing, start date, decision deadline, or expected next step.

What I do not usually need

The first message does not need to be a complete project brief. A short explanation of the situation is usually enough to decide whether a conversation makes sense.

  • A full requirements specification.
  • A complete architecture diagram or codebase overview.
  • A polished consulting brief or formal request for proposal.
  • Detailed access to source code before an initial conversation.
  • A final decision about the exact engagement format.

How an inquiry usually proceeds

The first step is usually simple. A short message is enough to determine whether the inquiry is relevant and whether a more detailed conversation makes sense.

1. Initial message

Send a short description of the role, engagement, technical question, or codebase situation you want to discuss.

2. Clarification

If the inquiry seems relevant, I may ask a few practical follow-up questions about the system, working model, timing, or expected outcome.

3. Conversation or written follow-up

Depending on the situation, the next step may be a short call, a written exchange, or a more focused discussion of the technical context.

4. Small practical start

If there is a good fit, the work can usually start with a focused review, advisory discussion, contract engagement, or clearly scoped next step.

Frequently asked

UCSM availability

Several readers have already contacted me about UCSM, especially regarding availability and pricing. The application is currently being prepared for public availability, but it is not sold directly through this personal website.

Work is underway to establish a suitable release and distribution channel. If you are interested in the application or would like to be notified when it becomes available, you are welcome to get in touch through the contact form.

For UCSM-related questions, choose Product or project interest in the form below.

For consulting, remote role, or contract inquiries, please include the technology stack, role or engagement type, remote/full-time/part-time/contract expectations, the current architecture or maintainability concern if relevant, and any preferred timing.
Include enough context to understand the inquiry. For work-related messages, the checklist above is a useful guide.