Custom software for organisations and institutions
Connect your departments.
LDS develops custom software for organisations and institutions. It connects workflows across departments and extends existing systems where work is getting held up.
- Clarify responsibilities
- Track approvals
- Connect systems
Move requests forward.
Illustrative workflow
An internal purchase request involves a department, a budget owner and procurement. Without shared status information, someone has to ask each team for an update.
Record the request
Capture the need and required information in one place.
Assign responsibility
Route the request for review according to agreed rules.
Review and approve
The operational and budget owners decide whether to approve.
Share the status
Pass the approved status to procurement and the requesting department.
Possible starting points.
Track requestsAsk several departments where a request is held up and who needs to act next.
An option to assess: share a request’s status, responsible team and next task. Existing specialist systems are the starting point for reviewing interfaces and control over the data.
Find internal knowledgeSearch procedures, internal documents and past decisions again for the same operational question.
An option to assess: make approved sources searchable with direct access to relevant passages. If AI assistance is considered, access rights, source references and uncertain answers are part of the assessment.
Inform managementCopy information from several departments into a spreadsheet for every report.
An option to assess: combine agreed information from the available systems in one overview. Operational teams and IT jointly define the authoritative source and who checks the figures.
Changing roles
New work, different access.
When someone changes role internally, old and new permissions need to be considered together. A shared task list can make coordination between the business team and IT visible.
- Before
Review existing access
The previous team identifies which permissions are no longer needed for the old role.
- Next
Confirm the new need
The new team describes the required systems and has the business need checked.
- Close
Record the changes
IT records what was removed or granted. Open points remain assigned to a responsible team.
Schematic organisational case. Responsibilities and access rules are set for the actual setting.
Explore data and accessAssess value first.
Operational teams and IT assess the value, dependencies and effort with LDS. The organisation gains a basis for evaluating development and ongoing operation.
Clarify the goal
What needs to improve in the organisation?
Assess value
Compare current effort, expected impact and running costs.
Plan the route
Use, connect or build according to the real need.
Keep improving
Launch, support and adapt to actual use.
Define access first.
Operational teams, IT and data protection staff define the required data, access and approvals with us. Responsibilities and processing are agreed and documented before implementation.
Data handlingBefore getting started.
Can our existing systems be integrated?
We examine the available interfaces, data formats and access rights. We then establish which information can be transferred, what needs to be developed and whether the effort is justified.
How do you decide whether to use AI?
We assess whether AI adds value beyond explicit rules, for example when searching approved documents. This includes quality, source references, data access and running costs. Decisions with operational or financial consequences remain within the agreed approval process.
Who looks after the software after launch?
LDS provides maintenance and further development within the agreed scope. Before launch, we define responsibilities, incident support and future development. The organisation’s goals guide later changes.
What needs improving?
Describe the workflow that takes too much effort today and what you want to improve.