Build what makes you different. Count what you must maintain.
Spreadsheets, low-code tools and custom software can be sensible choices. Compare Lucendus when the work of maintaining asset records, permissions, integrations and service processes is becoming a product of its own.
DIY is a spectrum, not a spreadsheet stereotype.
Microsoft describes Power Platform solutions that combine low-code components, existing data and custom code. Its guidance also calls for named owners, support, permissions, governance and application lifecycle management. A well-run internal solution can be a serious alternative. [1, 2]
IT practitioners describe SharePoint and automation alongside commercial asset tools, with process discipline as an essential part of keeping records current. The buying question is whether your organisation wants to own the application as well as the operational process. [3]
What to compare in practice.
Documented approaches and questions to test, not blanket feature scores. Source numbers refer to the references below. On smaller screens, scroll the table sideways.
| Capability | Lucendus approach | Build-it-yourself approach |
|---|---|---|
| Starting point | Configure an existing asset, service and inventory model. | Choose a spreadsheet, low-code platform or custom data model to match the scope. [1] |
| Connected records | Use linked assets, work and stock records as a starting structure. | Design identifiers, relationships, validation and synchronisation for your solution. |
| Access and change | Configure available controls and agree application responsibilities with Lucendus. | Own roles, environment policies, testing and deployment practices. [2] |
| Unique requirements | Check configuration and supported integrations against your process. | Custom code can address a distinctive requirement if you can maintain it. [1] |
| Ongoing cost | Include setup, migration, subscription and integration support in the proposal. | Include support, changes, platform usage and succession, as well as initial development. [2] |
Where connected work can help.
Start with operational building blocks
Use existing asset, service and inventory capabilities before commissioning new application logic.
Connect rules to work
Configure work types and supported actions with execution records to help explain what ran.
Reduce the amount of bespoke glue
Use agreed integrations to connect specialist systems while keeping clear ownership of the shared records.
Prove the fit with your team.
Write down the lifetime responsibilities
Include support coverage, account changes, recovery, releases and data exports.
Compare the same working slice
Implement one asset-to-service workflow in each approach and include exceptions.
Make the handover explicit
Have someone other than the original builder change a rule and recover a failed integration.
Build when the distinctive workflow justifies ownership.
A small spreadsheet can suit a bounded process; a capable internal engineering team can justify a custom application. Low-code can be a good middle ground. Evaluate Lucendus when established operational capabilities cover the core need and your team would rather configure and govern them than maintain a separate application.
Reviewed 9 September 2026. Vendor documentation establishes advertised scope; editions and configuration vary. Operator discussions provide evaluation questions, not verified benchmarks or representative findings. Lucendus descriptions reflect documented product scope; confirm your requirements in a working demonstration.
[1] Low-code and custom-code composition, data ownership and reusable components. Microsoft: modernize applications with Power Platform
[2] Ownership, support, permissions, governance and application lifecycle management. Microsoft: Power Platform roles and responsibilities
[3] Practitioners describe mixed tooling and the importance of intake and ownership processes. Anonymous accounts, not verified product benchmarks. Operator discussion: managing asset lifecycles
Explore the Lucendus capabilities.
- Workflows & ActionsConfigure operational work types, fields, conditions and actions with Lucendus. Make assignment and status changes repeatable and reviewable.
- IntegrationsConnect existing systems, records and operational events with Lucendus integrations. Plan data ownership, mapping and permissions around the workflow you need.
- Asset RegistryOrganise equipment, infrastructure, IT and biological assets with Lucendus. Connect asset identity, location, classification and work history in one registry.
Bring the workflow you need to prove.
Share the handovers, exceptions and systems that matter. We can work through where Lucendus fits and what needs to be demonstrated.