Alongside our own products, LN Software is interested in working with people who have a concrete software problem to solve. That may call for a focused consultation, a defined build, or an initial investigation before anyone commits to implementation.
A useful first conversation begins with the work a person needs to do. Who encounters the problem? What do they do today? Which part is slow, unclear or unreliable? What would a better outcome allow them to achieve? Those answers make it easier to choose a sensible technical approach and to recognise when software is only part of the solution.
For consulting, bring the decision that is holding you up. You may be weighing an architecture, trying to reduce a complicated integration, or deciding which part of an idea is worth testing first. Relevant context and a specific question are more useful than a polished presentation.
For project work, the first step is to define a boundary. We would want to understand the intended users, existing systems, important constraints and the evidence that would count as success. A useful scope also explains what happens after the first release: who operates the software, who owns its source and how further changes are considered.
An exploratory conversation is not a delivery promise. Availability, responsibilities, commercial terms and the right working arrangement need to be agreed for each project. The aim is to make that agreement concrete enough that both sides know what they are choosing.
To start, write to hi@ln.software with the problem, the people affected and any timing constraints. A brief, clear account is enough to begin. If there is a practical next step, we can define it together.