Important work is not moving forward
Planned features compete with maintenance and day-to-day demands. A clearly scoped work package needs an experienced developer who can understand the system and take it through implementation, testing and review.
Support for your development team
Move development forward. Strengthen your team.
Your team knows the product—but delivery is under pressure, a difficult technical problem is blocking progress, or an important decision needs a second perspective. Lutrisoft provides hands-on development support where it makes a difference.
You work directly with Max Dietrich, founder of Lutrisoft and a developer with over ten years of experience. We contribute working code, discuss trade-offs openly and share the knowledge your team needs to continue independently.
Where could your team use support?
Additional support is useful when it addresses a specific need. Together, we clarify whether implementation, an outside perspective or focused problem solving will help most.
Technical questions are holding the team back
A recurring defect is hard to reproduce, an architectural decision remains unresolved, or knowledge is concentrated in a few people. A fresh perspective and practical collaboration can help the team find a way forward.
Services in detail
Four ways to support your development team
We combine these areas as needed. The deliverables below are examples; we agree on the actual scope, responsibilities and acceptance criteria before starting.
Software development within your team
When does this make sense?
When a feature, integration or improvement needs hands-on implementation and your team has limited capacity or needs additional experience.
What can we deliver?
- Implemented features or improvements within an agreed work package.
- Automated tests and reviewable changes that follow your codebase's conventions.
- Technical notes and a handover covering decisions and remaining work.
How do we work?
We learn the relevant workflows and system boundaries, agree on a manageable first task and deliver changes in small increments. Coordination and reviews keep the implementation aligned with your product and technical standards.
Code and architecture reviews
When does this make sense?
When you want a second opinion on a planned change, need to assess risks or are weighing different approaches to a technical decision.
What can we deliver?
- A focused review of agreed code paths, interfaces or architectural decisions.
- Prioritized findings with explanations, trade-offs and actionable recommendations.
- A discussion with your team and, where agreed, an implementation example or decision record.
How do we work?
We review against your requirements rather than an idealized architecture. Findings distinguish concrete risks from optional improvements, so your team can decide what is worth changing.
Technical problem solving
When does this make sense?
When a difficult defect, unexpected system behavior or an integration problem is blocking development and the cause is unclear.
What can we deliver?
- A reproducible scenario or a documented investigation with evidence and remaining uncertainties.
- A targeted fix or a reasoned recommendation for the next technical step.
- Regression tests and diagnostic improvements where appropriate.
How do we work?
We narrow down the problem together, test hypotheses and use measurements rather than guesswork. We make progress and open questions visible; not every investigation can promise an immediate fix.
Development processes and knowledge sharing
When does this make sense?
When changes get stuck in reviews, local setup is difficult or important technical knowledge is not shared widely enough.
What can we deliver?
- Focused improvements to agreed development, testing or review workflows.
- Practical documentation, setup instructions or examples your team can use.
- Pair programming and knowledge-sharing sessions around actual project work.
How do we work?
We start with a concrete source of friction and try a small improvement with the team. The goal is a useful working practice—not additional ceremonies or a wholesale process overhaul.
What working together can look like
From a specific need to useful contributions
We adapt collaboration to your project and team. A focused review can be a starting point, just as a clearly defined implementation task can.
-
Clarify goals and responsibilities
We discuss what is blocking progress, which outcomes matter and who is responsible for technical and product decisions. We agree on scope, communication and the necessary access.
Possible outcome: A shared understanding of the task, responsibilities and acceptance criteria.
-
Understand the system and agree on the first task
We review relevant documentation, code and tests, and clarify open questions with your team. A manageable first task helps check assumptions before taking on a larger scope.
Possible outcome: A practical starting point with known dependencies and open questions made explicit.
-
Implement, review and adjust
We deliver reviewable changes, discuss findings early and validate the results with tests and feedback. Short check-ins help keep the work aligned with your priorities.
Possible outcome: Working changes or actionable findings, with transparent progress and decisions.
-
Share knowledge and hand over clearly
We explain the implementation, document relevant decisions and discuss remaining limitations. Pairing and focused handovers help your team take the work forward.
Possible outcome: Code, documentation and shared understanding that remain with your team.
Direct collaboration, clearly agreed scope. You work directly with Max Dietrich, Lutrisoft’s founder and developer. We agree on the services, responsibilities and collaboration model for your project. Additional specialists from the network are involved only by agreement.
OTTO: the central product detail page
While working at OTTO through an employee leasing arrangement, I contributed to the central product detail page, implementing various features and improvements.
This example is from Max Dietrich's previous work as a software developer and is not a Lutrisoft client reference. More project experience on the homepage →
What would help your team move forward?
Tell us briefly about your product, your team and the work or technical challenge you need help with. Useful context includes your technologies, the desired outcome and any timing constraints.
Together, we can clarify whether a focused review, implementation work or a broader support engagement is a suitable next step.