Independent engineer · Munich, Germany

Custom business software

I build custom applications, internal tools and APIs around a company’s actual workflows, including their integration, deployment and maintenance requirements.

Discuss your requirements

The client problem

Spreadsheets, disconnected tools and manual handoffs can leave a business process difficult to maintain or audit. Before building software, the workflow, users, permissions and existing systems need a shared definition.

Technical scope

  • Business web applications and internal tools
  • APIs, data models and integration with existing systems
  • Native utilities where the workflow requires local capabilities

Deliverables to agree

  • Agreed workflow, technical scope and acceptance criteria
  • Versioned application code and relevant verification
  • Deployment instructions, documentation and maintenance handover

Example engineering approach

For an internal operations tool, define who can view or change each record, implement the workflow and interfaces, then verify permissions and failure cases before deployment. The delivery includes a way for the responsible team to operate and maintain it.

Service boundaries

A discovery discussion establishes whether custom development is appropriate. Scope, acceptance, source-code ownership, hosting and maintenance are agreed explicitly; an ongoing support arrangement is not automatic.

Experience and technical context

Review my published projects and technical expertise to assess the fit for your systems. The project descriptions show the actual work; technology selection and availability are confirmed for your engagement.

Published engineering projects · Technical expertise · Professional background

Buyer questions

Can you work with an existing application?

Yes. The starting point is a review of the codebase, dependencies, deployment and business requirements. A focused improvement can be more suitable than a complete rewrite.

How is the initial scope defined?

Describe the workflow, intended users, existing systems and the outcome that would make the project useful. Those inputs become a bounded first delivery with explicit acceptance criteria.

Start with the business and technical context

Share the systems involved, the problem to solve, the expected delivery window and your access or security constraints. A short initial summary is enough to assess the next step.

Discuss a project

Related services

Enterprise integration

I connect business applications, messaging systems and data flows so that teams can change their systems without losing control of the interfaces between them.

DevOps & automation

I turn manual build, deployment and infrastructure tasks into repeatable workflows with explicit checks, permissions and recovery steps.

Production support

I help teams investigate production problems, maintain business-critical software and make operational knowledge repeatable through monitoring, documentation and automation.