Client portals and internal tools
LCR builds secure applications that help clients, staff and partners access relevant information, submit requests and manage work across existing business systems.
Explore client portals and internal toolsAbout LCR Technologies
Work directly with the senior engineer responsible for delivery.
LCR Technologies is a founder-led product engineering business that builds and improves business software for established businesses, software companies and consultancies.
You work directly with Lorenzo Rheinicke, the senior engineer responsible for technical decisions, hands-on development, integrations and production delivery. This gives the work one visible technical owner from requirement through release.
What LCR Technologies does
Software capabilities for business products and workflows.
Workflow automation and systems integration
LCR connects systems, decisions and human review to reduce repetitive administration and fragile handovers while keeping exceptions visible.
Explore workflow automationMobile applications
LCR builds focused iOS and Android applications connected to business systems, operational processes and, where required, dedicated hardware.
Explore mobile app developmentAI agents
LCR designs AI-assisted workflows for enquiries, intake, qualification, knowledge access and routing. Human approval and handover points remain explicit where the process requires judgement or control.
Explore AI agentsProduct development
LCR builds focused new products and important capabilities for existing applications. Scope, dependencies and acceptance criteria are agreed before estimating and delivering the work.
Explore defined product buildsWhat makes LCR Technologies different
One visible technical owner, from context to release.
Direct access to the engineer
Clients work directly with Lorenzo on product questions, technical decisions and implementation. Important context reaches the person doing the engineering work without passing through a separate account-management layer.
Ownership through release
LCR can carry responsibility from scoping and technical direction through development, verification and production release. The delivery boundary and responsibilities on both sides remain clear.
Decisions account for existing systems
New software rarely operates alone. Architecture and integration decisions consider the data, dependencies, security boundaries and operational processes already supporting the business.
Continuity across releases
Ongoing product engineering retains context as the software and its priorities develop. This supports informed changes without treating every release as an unrelated project.
Visible decisions and responsible handover
Repositories, technical decisions, access and operating knowledge remain visible. This allows LCR to continue the work or hand it over responsibly when the engagement changes.
Who works with LCR Technologies
For teams that need senior ownership of important software.
Established businesses with important software
Teams that need reserved senior engineering capacity to manage a live backlog and deliver useful improvements over time.
Businesses with a defined delivery need
Organisations with a product, integration or operational problem that requires a focused build with agreed acceptance criteria.
Software companies and consultancies
Delivery teams that need an experienced technical partner to take ownership of a project or workstream for an agreed period.
Selected work includes public product examples such as Boxley and SendRewards, alongside anonymised delivery examples in logistics, legal technology, finance and AI-assisted workflows. Review the work and LCR's role in each example
The person behind LCR Technologies
Lorenzo Rheinicke, founder and senior product engineer.
Lorenzo works directly across product decisions, software architecture, implementation, integrations and release. The client sets business priorities, provides access to the required people and systems, and accepts the outcome.
When a project requires specialist input, LCR can bring that support into the engagement with the responsibility and review boundaries made clear to the client.
View Lorenzo's LinkedIn profileHow working with LCR Technologies works
A clear path from context to working software.
- 01
Share the context
Describe the business problem, product, backlog or delivery constraint. A polished brief is not required.
- 02
Discuss the delivery conditions
LCR reviews the priorities, current systems, dependencies, responsibilities and timing before recommending a delivery approach.
- 03
Agree the right engagement
Choose a defined build, ongoing engineering arrangement or technical delivery partnership. Agree the delivery boundary, communication rhythm, capacity, fees and support expectations.
- 04
Build, review and release
LCR delivers against agreed priorities and acceptance criteria, with working software reviewed as the engagement progresses. Release and continued development follow the agreed scope.
Key facts
LCR Technologies at a glance.
These details summarise the business, its services and the ways clients can engage LCR.
| Company name | LCR Technologies |
|---|---|
| Business type | Founder-led product engineering business |
| Founder | Lorenzo Rheinicke |
| Founded | 2012 |
| Location | South Africa |
| Core offering | Senior product engineering from technical decisions through production delivery |
| Services | Client portals and internal tools; workflow automation and systems integration; mobile applications; AI agents; product development |
| Engagement models | Ongoing Product Engineering; Defined Product Builds; Technical Delivery Partner |
| Pricing | Agreed for the scope, capacity and responsibilities of each engagement |
| Contract terms | Engagement-specific |
| Communication | Working rhythm and channels agreed for each engagement |
| Website | www.lcrtech.co.za |
| Company LinkedIn | LCR Technologies |
| Founder LinkedIn | Lorenzo Rheinicke |
Frequently asked questions
Questions about working with LCR.
Will I work directly with Lorenzo?
Yes. Lorenzo works directly with clients across technical decisions, implementation and delivery. If specialist support is required, its role and review boundaries are made visible.
Can LCR improve an existing application?
Yes. LCR can own an existing backlog, add an important capability, modernise part of a system or improve integrations. Work starts by assessing the software, operating context and desired outcome.
Can LCR work alongside our internal team?
Yes. The Technical Delivery Partner model gives software companies and consultancies senior capacity for a project or workstream. Responsibilities, access and decision ownership are agreed at the start.
Does LCR provide ongoing engineering?
Yes. Ongoing Product Engineering provides reserved senior capacity for an important product and its live backlog. Capacity, priorities and working rhythm are agreed for the engagement.
How are pricing and timelines agreed?
Pricing and timing depend on the outcome, scope, dependencies, risks and responsibilities. LCR clarifies the work before agreeing the commercial and delivery arrangement.
How do we get started?
Share the software, business problem or delivery constraint through the contact page. Lorenzo will review it and use an initial conversation to determine fit and a useful starting point.
Discuss your software.
Share the product, backlog, project or delivery constraint. You do not need a polished brief, just enough context for Lorenzo to understand the outcome and suggest a useful first conversation.