Custom software development · Europe
Custom software for companies whose processes no longer fit off-the-shelf tools.
0x41 Labs supports mid-sized companies on demanding platforms, internal business systems and integrations — from technical clarification through to dependable delivery.
- 01Frame
- 02Clarify
- 03Decide
- 04Build
- 05Hand over
- Confidential & independent
- Vendor-independent technical assessment. Project information is not passed on.
- Real architecture questions
- For projects with genuine integration, data and architecture questions — not for simple websites.
- €10,000–75,000
- Typical range of the custom software projects covered. Smaller and larger ones occur.
The situation
When off-the-shelf software stops being enough, the technical decision has to hold.
The project is decided internally and it matters. What is missing is not commitment but confidence: requirements are only partly settled, technical feasibility is unverified, integration with existing systems is open — which makes the effort estimate a guess on an uncertain basis.
This is exactly where the expensive mistakes happen. Not during development, but in the decisions before it: an architecture that cannot carry the integration. A budget built on an incomplete requirement. A technology choice nobody reviewed independently.
A wrong technical decision before the start costs more than the review that would have prevented it.
Typical starting points
Three situations where technical clarification pays for itself.
The process fits no standard product
An important internal system or process cannot sensibly be modelled in off-the-shelf software. Today it runs on spreadsheets, email and workarounds.
Several systems have to work together reliably
ERP, CRM, data sources or legacy components need to be connected — dependably, traceably, and without degrading data quality.
A product is planned, the technology is open
A new digital product or platform is on the table, but architecture, effort and technical risks have not been settled with any confidence.
Not every software problem belongs here. Simple websites, classic WordPress projects and plain developer capacity for individual tickets are explicitly not the offer.
Services
Three areas. One technically accountable person.
Each area starts from the situation you are in — and ends at a concrete result, not at a list of technologies.
Technical Discovery
The project is decided, but feasibility, architecture and effort have not been settled with any confidence.
A written basis for the decision: what should be built, how it can sensibly be implemented, what effort is realistic, and which risks could derail it.
Requirements analysis · Target architecture · Effort range · Risk assessment
Custom business software
An important process runs around the standard software — in spreadsheets, email and manual intermediate steps.
Internal tools, workflows and platforms that model the actual process instead of bending it to fit someone else's product.
Internal applications · Workflow systems · Dashboards · Process automation
System integration & delivery
Several systems, data sources or legacy components have to work together reliably.
Dependable data flows between existing systems, and an implementation that also holds up in production.
APIs · Data flows · Legacy connectivity · Deployment & operations
Approach
Four steps, in this order.
The order is the point: clarified before built, not alongside it.
- 01
Frame
Understand the goal, the problem and the system landscape. What should change operationally — and what stands in the way today?
- 02
Clarify
Make risks, architecture and effort dependable before development budget is committed. This is the paid first step.
- 03
Build
Implement with focus, with the technical questions decided rather than left to escalate mid-sprint.
- 04
Hand over & evolve
Stabilise close to production, hand over documented, and extend along real requirements.
Selected work
Anonymised projects.
Each example shows the starting point, the critical technical question, my role and the result.
MedTech · Computer vision · approx. 4 months
- Starting point
- A large German health and medical supplies provider wanted to move a measurement that previously happened in-store onto the customer's smartphone.
- Critical question
- Can geometric measurements precise enough for a medical fitting be derived from smartphone camera images?
- My role
- Technical feasibility assessment, image-processing concept, mobile application, backend and production deployment.
- Result
- The critical question — achievable accuracy under real capture conditions — was answered before full build-out, not after months of development.
FinTech · Trading platform · approx. 6 months
- Starting point
- A platform needed to secure transactions between parties unknown to each other, without holding users' funds itself.
- Critical question
- How can escrow logic be built so that no party — including the operator — can unilaterally dispose of the funds?
- My role
- Architecture of the trading and escrow logic, backend, infrastructure and production deployment.
- Result
- A multisig escrow architecture with cleanly separated rights of disposal — decided before development, not corrected afterwards.
Analytics · Business software · approx. 2.5 months
- Starting point
- Operational data sat in POS systems and several separate sources. Reporting was produced manually and reassembled every time.
- Critical question
- Which data has to be consolidated, and how, so that reporting becomes dependable and stops requiring rework?
- My role
- Data model, integration of the source systems, analytics application and operations.
- Result
- One dependable central view where every report had previously been assembled by hand.
System integration · Wholesale · approx. 3 months
- Starting point
- A mid-sized German wholesale business ran a years-old in-house application for order processing alongside its ERP. The two systems knew nothing of each other — article and customer data were maintained in both places, and where they disagreed, whichever version someone had last corrected by hand won.
- Critical question
- Can the existing ERP interface carry a bidirectional sync — or does data ownership between the systems have to be drawn differently?
- My role
- Analysis of the system landscape and the interfaces that actually existed, target architecture, data model, implementation of the integration, and production operation.
- Result
- The intended bidirectional sync could not be made reliable with the available interface — decided during clarification, not after months of silent data divergence. The ERP stayed the system of record for master data and the in-house application took process data only. Duplicate maintenance and the manual steps it caused are gone: around 22 hours a week in total.
Some projects are subject to strict confidentiality and security requirements. The case studies are therefore anonymised: they show the type of problem, the scope of responsibility and the result, without exposing clients or sensitive systems.
Accountability
Who carries the technical responsibility.
There is no sales team behind 0x41 Labs that takes on a project and hands it off internally. I take projects on myself, assess them technically and own the implementation. From the first assessment through to operations you deal with the same person.
That comes with a limit, and it belongs here: I take on work I can genuinely judge and deliver. If a standard product is the better answer, or a project needs a larger team, I say so — before an engagement, not after.
Senior technical judgement, a straight answer on risk — and no disclosure of confidential project information.
- Technical assessment
- Architecture, integration and feasibility questions before development starts. That is the core of the work, not a preliminary chat about it.
- Working together
- With internal IT teams, business departments and management — including as an independent technical counterpart to an existing supplier.
- Communication
- Technical matters presented so that a decision becomes possible. Without unnecessary complexity and without buzzwords.
- Confidentiality
- Project information is not passed on. That is precisely why the references on this site are anonymised.
FAQ
What to know before getting in touch.
Primarily mid-sized companies with a concrete custom software project — typically in the €10,000 to €75,000 range, though smaller and larger ones occur. What matters is less the amount than the kind of open questions: the characteristic pattern is that real integration, data or architecture questions need resolving, rather than development capacity being the thing that is missing.
Simple websites and landing pages, classic WordPress projects, small standard integrations, and the search for cheap developer capacity for individual tickets. A fully specified project that only needs implementing does not need clarification beforehand either.
Yes, that is the normal case. I work alongside internal IT teams, business departments and external suppliers — often precisely when an independent technical assessment of an existing supplier's claims is what is needed.
With a short description through the form. That is followed by a free written pre-check of whether technical clarification makes sense for your project. If it fits, the paid Technical Fit Check follows: a 45-minute call for €295 net with a short written assessment within one business day. Only after that does it get decided whether a Technical Discovery, direct implementation, or no joint project at all makes sense.
Because some of the projects are subject to confidentiality and security requirements. Client names, logos or identifying details would breach those commitments. The anonymised examples instead show the type of problem, the scope of responsibility and the result — which is what matters for an assessment anyway.
The first step is free: you describe your project through the form and receive a written assessment of whether technical clarification makes sense at all. Only the Technical Fit Check that may follow — a 45-minute call with a written assessment — costs €295 net, and it is credited in full against a Technical Discovery commissioned within 14 days. The Discovery itself starts at €2,500 net.
Next step
Do you have a custom software project where architecture, effort or integrations are not yet settled?
Describe the project at a high level. After a short review you will get the next sensible step — without having to send confidential project details through the form.