How we work
Problem before technology.
The starting point is always your business problem, never a tool. A few rules follow from that, and we stick to them in every project.
Principles
What you can expect from us
Problem before technology
First we establish what a process costs and what should change. Which technology fits follows from that.
Business value before technical elegance
A simpler solution is the right one if it is cheaper and more robust.
Proof before promises
We assess whether the solution fits your materials and requirements using selected examples within an agreed scope.
Short cycles, clear decisions
You see something that works early on: regular interim results and clearly separated project stages, after each of which you decide again.
Use what exists, build what is missing
First check whether it already exists. Then build.
No custom code if an existing solution solves your problem more cheaply, faster and more safely.
- Check existing standard software.
- Integrate where the core function is already there.
- Use open source where control or hosting matter and the solution is mature.
- Build from scratch only where integration or differentiation make the difference.
- Bring in specialists – for security, ERP or legal questions, for example.
What we commit to
Commitments that are written into every larger proposal
- 01
A limited start
We first clarify your needs in a free introductory call. Any subsequent feasibility study is commissioned separately and has a clearly limited scope.
- 02
Assess feasibility without production changes
During the feasibility study we do not access your production systems. We work with documents you provide, test data or a test environment.
- 03
People decide
Critical steps still require human approval. We automate the preparation, not the responsibility.
- 04
Documented handover
Client-specific code, documentation and agreed access are handed over – with an operations manual and an exit clause. Third-party software remains under its own licence terms.
- 05
Data sovereignty
We agree the operating model and data processing with your IT team. Your own company environment is the preferred starting point; external services and ongoing costs are clarified in advance.
- 06
Traceable
Minimal permissions, separate credentials, logging and documentation – auditable on request.
Working together
What we need from you
- One contact person from the department who knows the process
- Examples and data – real, anonymised or as test data
- A contact in your IT team for security and integration questions
- Someone who can decide whether to proceed
Fit
When we are a good fit – and when we are not
Company size matters less than you might think. What counts is the economic value of the process and clear responsibilities and decision-making processes – explicitly including departments within large companies that have their own budget. The points below are a helpful starting point, not entry requirements; whatever is still open, we clarify together.
Good starting points
- A recurring process with measurable effort
- Examples, data or history are available
- A department with budget and decision-making authority
- Security requirements can be defined
- An IT contact, in-house or external – we add the capacity and specialist knowledge the case needs
- An existing workflow that current tools do not yet handle well
When we are not the right choice
- “Build first, look later” – without a goal, a scope and a budget
- Autonomous decisions in legal, HR, medical or financial matters without the appropriate expertise and compliance structure
- Highly critical live systems without adequate safeguards
- One-off special tasks with no recurring benefit
AI where it adds value
AI is a tool, not a product.
Where AI is used, the legal assessment – under the EU AI Act, for example – belongs in the feasibility study, not at the end of the project. For specialist questions we bring in experts.