Leava GmbH

00Services

Eight ways to build, connect and look after software.

  1. 01 Custom software development
  2. 02 Web application development
  3. 03 Backend and API development
  4. 04 Cloud architecture and DevOps
  5. 05 Systems integration
  6. 06 Workflow automation
  7. 07 Quality assurance and testing
  8. 08 Software maintenance and technical consulting

01

Custom software development

Applications designed around a specific business process, data model and set of users.

Close-up of a circuit board with metallic traces

Common needs

  • A process run through spreadsheets and email has outgrown them
  • Standard software requires too many workarounds
  • Data is scattered across tools and hard to trust

Typical scope

  • Requirements analysis and domain modelling
  • Application architecture
  • Implementation of business logic and user interfaces
  • Data migration from existing sources

Delivery approach

Work starts by documenting the current process with the people who use it. The application is then delivered in increments, each one usable and reviewed before the next begins.

Possible deliverables

  • Working application deployed to an agreed environment
  • Source code in your repository
  • Architecture and operations documentation

02

Web application development

Browser-based products, portals and internal tools that work across devices.

Common needs

  • Customers need self-service access to their data
  • Internal teams rely on outdated or slow tools
  • A product idea needs a first production-ready version

Typical scope

  • Interface and interaction design in collaboration with your team
  • Frontend development
  • Authentication and permissions
  • Accessibility and performance work

Delivery approach

Frontend and backend are developed together so that the interface reflects the system’s real capabilities. Usable previews are shared throughout development.

Possible deliverables

  • Responsive web application
  • Component library or UI conventions
  • Automated tests for key user flows

03

Backend and API development

Services, data stores and interfaces that other applications rely on.

Server racks in a dimly lit data centre

Common needs

  • Several applications need access to the same data
  • Partners or customers require an API
  • An existing backend has become slow or difficult to change

Typical scope

  • API design (REST or event-based)
  • Database design and optimisation
  • Background jobs and queues
  • Authentication, authorisation and rate limiting

Delivery approach

Interfaces are specified first and agreed with their consumers. Implementation follows with contract tests, so changes on either side are caught early.

Possible deliverables

  • Documented API specification
  • Backend services with automated tests
  • Database schema and migration scripts

04

Cloud architecture and DevOps

Infrastructure, deployment pipelines and monitoring that make software dependable to run.

Common needs

  • Deployments are manual and risky
  • Environments differ in undocumented ways
  • Problems are noticed by users before the team

Typical scope

  • Cloud architecture design
  • Infrastructure as code
  • CI/CD pipelines
  • Logging, metrics and alerting
  • Backup and recovery procedures

Delivery approach

The current setup is reviewed and documented first. Improvements are introduced step by step, keeping existing services running during the transition.

Possible deliverables

  • Infrastructure definitions in version control
  • Automated build and deployment pipeline
  • Monitoring dashboards and runbooks

05

Systems integration

Reliable connections between the applications an organisation already uses.

Network cables plugged into a switch

Common needs

  • The same data is entered in more than one system
  • Files are exchanged manually between departments or partners
  • A new tool must work with legacy systems

Typical scope

  • Analysis of systems, data formats and ownership
  • API and file-based integrations
  • Data mapping and validation
  • Error handling and reprocessing

Delivery approach

Each integration is designed with explicit failure handling: what happens when a system is unavailable, data is invalid or a message is duplicated.

Possible deliverables

  • Integration services or connectors
  • Data mapping documentation
  • Monitoring and alerting for integration failures

06

Workflow automation

Reducing repetitive manual steps in operational and administrative work.

Common needs

  • Staff spend time on routine copying, checking or reporting
  • Approvals depend on email chains
  • Recurring reports are assembled by hand

Typical scope

  • Workflow analysis with the people involved
  • Automated triggers, rules and notifications
  • Approval flows
  • Scheduled reports

Delivery approach

Automation targets the steps where it clearly reduces effort or errors. Human review is kept where judgement is needed, and every automated step is logged.

Possible deliverables

  • Automated workflows in production
  • Audit logs of automated actions
  • Documentation of rules and exceptions

07

Quality assurance and testing

Testing strategies and automation that make changes safer to release.

Abstract network of connected nodes

Common needs

  • Releases often introduce regressions
  • Manual testing slows down every release
  • There is little confidence in existing test coverage

Typical scope

  • Test strategy and coverage review
  • Unit, integration and end-to-end test automation
  • Test data management
  • Integration of tests into pipelines

Delivery approach

Testing effort is focused on the areas with the highest risk and usage first, then expanded. Tests run automatically on every change.

Possible deliverables

  • Automated test suites
  • Test strategy document
  • Pipeline integration with clear reporting

08

Software maintenance and technical consulting

Continuing care for existing systems and independent technical advice.

Common needs

  • An application has no active maintainer
  • Dependencies and frameworks are out of date
  • A technical decision needs an outside perspective

Typical scope

  • Code and architecture reviews
  • Dependency and security updates
  • Bug fixing and incremental improvements
  • Technical due diligence and planning

Delivery approach

Maintenance begins with an assessment of the codebase and its risks. Work is then planned in a prioritised list agreed with you and revisited regularly.

Possible deliverables

  • Written assessment with prioritised recommendations
  • Regular updates and fixes
  • Documented changes and release notes