← Back to services
Architecture & technical consulting

Clear technical decisions. A practical path forward.

You are planning a new application, weighing technologies or questioning whether your current architecture can support the next stage. Lutrisoft helps you understand the options and make technical decisions grounded in your business needs.

You work directly with Max Dietrich, founder of Lutrisoft and a developer with over ten years of experience. We connect architectural thinking with implementation experience, making trade-offs, risks and assumptions explicit rather than prescribing unnecessary complexity.

Which technical decision needs clarity?

Consulting is useful when uncertainty is blocking progress or a decision could be expensive to reverse. We focus on the questions that matter for your product, team and operations.

A new product needs sound technical foundations

You need to decide how an application should be structured, which technologies fit and how it will connect to existing systems. The solution should meet your requirements without exceeding what your team can build and operate.

Your current system raises difficult questions

Growing requirements expose unclear boundaries, competing technical proposals or risks that are hard to assess. An outside perspective can help separate evidence from assumptions and identify a realistic next step.

Services in detail

Four ways to bring clarity to technical planning

These areas can be combined or addressed through a focused engagement. The deliverables below are examples; we agree on the questions, depth of analysis and scope together.

System and software architecture

When does this make sense?

When a new application needs a technical design or existing system boundaries no longer fit your requirements.

What can we deliver?

  • An architecture outline with responsibilities, interfaces and important data flows.
  • Documented decisions and trade-offs covering relevant quality requirements.
  • Focused prototypes or technical checks for critical assumptions, where agreed.

How do we work?

We start with business workflows, expected load, reliability needs and team capabilities. We compare suitable designs and choose the simplest structure that meets the requirements, with room to evolve where needed.

Technology and platform decisions

When does this make sense?

When you need to choose a language, framework, database or hosting platform and want to understand the consequences.

What can we deliver?

  • Decision criteria based on your requirements, constraints and operational needs.
  • A comparison of suitable options, including costs, ecosystem and maintenance implications.
  • A reasoned recommendation with uncertainties and any necessary validation steps.

How do we work?

We evaluate options against actual use cases rather than trends. Existing team knowledge, integration constraints and long-term operation matter alongside technical capabilities; a small experiment can help resolve key uncertainties.

Technical assessments and reviews

When does this make sense?

When you need an independent view of a codebase, architecture or technical proposal before committing to further investment.

What can we deliver?

  • A scoped assessment of relevant code, dependencies, interfaces and documentation.
  • Prioritized findings distinguishing observed issues, risks and open questions.
  • Actionable recommendations discussed with your technical and business stakeholders.

How do we work?

We agree on the review questions and available evidence first. Findings explain their practical impact and limitations; a focused review is not a comprehensive security audit or a guarantee that every issue will be found.

Roadmaps and implementation planning

When does this make sense?

When the direction is broadly clear but the work needs to be broken into feasible stages with explicit dependencies.

What can we deliver?

  • A prioritized technical roadmap aligned with your business goals.
  • Manageable work packages with dependencies, risks and acceptance criteria.
  • A proposed first step and checkpoints for revisiting assumptions and priorities.

How do we work?

We weigh value, effort and risk with your team, identify what must be learned first and plan useful increments. Estimates remain explicit assumptions, not promises of certainty before implementation has begun.

What working together can look like

From open questions to decisions your team can use

We tailor the engagement to the decision at hand. A focused workshop or review can be enough; deeper analysis and implementation support are agreed separately where useful.

  1. Clarify the decision and its constraints

    We discuss business goals, stakeholders, technical requirements and the decisions already made. Together, we define the questions to answer and the evidence available.

    Possible outcome: An agreed scope, decision criteria and a shared understanding of success.

  2. Assess the system and explore options

    We review relevant documentation and code, talk to your team and compare practical alternatives. Targeted experiments help investigate the assumptions with the greatest impact.

    Possible outcome: A grounded comparison of options, with risks and remaining uncertainties visible.

  3. Agree on a direction and plan the first step

    We discuss the findings, document the reasoning and translate the chosen direction into prioritized work. Your team remains involved in decisions and understands the compromises.

    Possible outcome: A documented recommendation and a feasible first work package.

  4. Hand over knowledge and validate in practice

    We explain the design, decision records and open questions. Where agreed, we support an initial implementation or review results so the plan can be adjusted using practical feedback.

    Possible outcome: Usable documentation and clear checkpoints for implementation and further decisions.

Practical advice, not architecture for its own sake. You work directly with Max Dietrich, Lutrisoft’s founder and developer, with a clearly agreed scope. Implementation work or additional specialists from the network are included only by agreement.

From experience

Housing platform: backend ownership

In my most recent project, I took technical ownership of the backend and its architecture for a platform serving housing companies.

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 technical decision are you facing?

Tell us about your product, the question you need to resolve and the constraints that matter. Existing diagrams, a brief technology overview and any timing requirements are useful starting points.

Together, we can clarify whether a workshop, focused assessment or architecture concept would be a useful next step.