Custom software development
Applications shaped around a specific operational process.
00Sheet 01 — General arrangement
Software built the wayengineering drawings are made
Calla Flower GmbH designs, builds and maintains custom software, cloud environments and integrations for organisations whose operations depend on them. Every system we deliver comes with a documented structure, tested behaviour and a team that can keep running it.
- Discipline
- Documented architecture
- Method
- Incremental delivery
- Coverage
- Build, integrate, operate
- Language
- Plain, written English
01Introduction
An engineering partner, not a vendor of hours
We work with organisations that have reached the limits of manual processes, spreadsheets or software that was sized for a smaller operation. The work usually combines new development with careful changes to systems that must keep running throughout.
Our engineers take responsibility for the parts of a system they build: the data model, the interfaces, the tests, the deployment path and the observability that makes it supportable. Decisions are recorded with the reasoning behind them, so the design remains understandable long after the initial delivery.
We do not promise outcomes we cannot control. What we commit to is a defined scope, transparent progress, tested software, and a handover that leaves your team able to operate what we built.
02Core services
Eight service areas, delivered by the same engineering team
Web application development
Portals, consoles and dashboards built to current web standards.
Cloud solutions
Reproducible environments defined as code, with identity and backup planned.
System integration
Reliable data movement between applications, services and partners.
Technology consulting
Independent architecture review and build-versus-buy analysis.
Software modernisation
Progressive renewal of systems that still carry business value.
Quality assurance
Test strategy and automation that makes release readiness verifiable.
Maintenance and support
Updates, monitoring, incident response and small enhancements.
Full descriptions are on the Services page.
03Business challenges
The situations that bring clients to us
We work across sectors where operational software matters more than consumer scale: logistics and distribution, professional services, manufacturing support, education and training, and organisations running internal platforms for their own staff.
Fragmented data
The same record exists in several systems with no agreed source of truth.
Manual bridging
People export, edit and re-import files to move work between departments.
Slow releases
Every change requires lengthy manual testing, so improvements queue up.
Unsupported platforms
Frameworks or runtimes have reached end of life and block upgrades.
Key-person risk
Only one or two people understand how a critical system behaves.
Opaque incidents
Failures are noticed by users first, because nothing is monitored.
04Technology expertise
Chosen per requirement, never by default
Application layer
- Typed server and client languages
- REST and event-driven APIs
- Server-rendered and single-page front ends
- Design systems and accessible components
Data layer
- Relational schema design and migration
- Document and key-value stores
- Caching and read models
- Reporting and export pipelines
Infrastructure
- Container images and orchestration
- Infrastructure as code
- Continuous integration and delivery
- Secrets, identity and access management
Operations
- Structured logging and tracing
- Metrics and alert design
- Backup and restore procedures
- Capacity and cost review
05Delivery methodology
Short cycles, working software, written decisions
Work is planned in short cycles against a single prioritised backlog shared with the client. Each cycle ends with software running in an environment that the client can use, not with a document describing what was done.
Every change passes code review and an automated test suite before merging. Environments are provisioned from the same definitions, so behaviour in staging is a reliable indicator of behaviour in production. Architectural decisions are captured as short records that stay with the codebase.
06Project process
From first email to steady operation
- 01
Enquiry
We read your description of the situation and reply with clarifying questions and an outline of how we would approach it.
- 02
Discovery
Structured sessions with domain experts and a review of existing systems, data and constraints.
- 03
Scope and architecture
A written scope, a target architecture, an environment plan and a delivery sequence with review points.
- 04
Build increments
Implementation in reviewable slices with automated tests, continuous integration and deployment to shared environments.
- 05
Verification
Functional, integration and performance checks against the agreed criteria, plus accessibility review for user-facing work.
- 06
Release
Staged rollout with monitoring in place, a rollback path, and release notes recorded for the operating team.
- 07
Handover or support
Documentation, knowledge transfer, and either a clean handover or an agreed maintenance arrangement.
07Business benefits
Process encoded once
Rules that live in people's heads or in parallel spreadsheets are implemented in one place, versioned and testable.
Shorter change cycles
Automated pipelines and test coverage reduce the effort required to release a change safely.
Fewer manual transfers
Integrations replace repeated exports and re-keying, and record ownership becomes explicit.
Predictable operations
Monitoring, alerting and runbooks turn incidents into a defined procedure instead of an improvisation.
Transferable knowledge
Documented architecture and decision records reduce dependence on any single individual.
Controlled cost of change
Modular boundaries mean future work touches a defined area rather than the whole system.
08Security and quality principles
Controls that are part of the build
- LEAST PRIVILEGE
Access to environments, data and secrets is granted per role and reviewed when an engagement changes shape.
- DEPENDENCY HYGIENE
Third-party packages are pinned, scanned for known vulnerabilities and updated on a regular schedule rather than in emergencies.
- DATA MINIMISATION
Systems store what they need for a stated purpose, with retention and deletion paths designed alongside the feature.
- VERIFIED CHANGE
Peer review, automated tests and reproducible builds apply to every change, including small fixes made under time pressure.
- TRACEABILITY
Deployments, configuration changes and access events are logged so that an incident can be reconstructed accurately.
09Why work with us
What working with Calla Flower GmbH looks like in practice
Engineers you speak to directly
The people writing the code attend the working sessions. Requirements are not relayed through a chain of intermediaries, which removes a common source of misunderstanding and rework. Questions about a trade-off are answered by the person who has to live with it.
Scope that stays legible
Scope is written in terms a non-technical stakeholder can verify, and changes to it are visible in the same backlog everyone reads. When something turns out to be more complex than estimated, we say so at the point we discover it and present the options rather than absorbing the difference quietly.
Systems you can take over
We build so that another team could continue the work: conventional structure, documented interfaces, seeded local environments, and tests that describe intended behaviour. Being replaceable is a design goal, not a risk we hedge against.
No lock-in by obscurity
Source, infrastructure definitions and documentation belong to the client from day one.
No hidden subcontracting
You know which engineers are working on the system and in what capacity.
No unexplained estimates
Every estimate comes with its assumptions and the parts we consider uncertain.
10Frequently asked questions
Questions we are asked before a first project
- What kind of projects does Calla Flower GmbH take on?
- Custom business applications, web platforms and portals, cloud environments, integrations between existing systems, and the modernisation or ongoing maintenance of software that is already in production. Work ranges from a bounded piece of engineering to a long-running delivery team.
- How does an engagement usually start?
- With a discovery phase. We review the current systems, data and constraints, run working sessions with the people who use the software, and produce a written scope with success criteria, an architecture outline and a delivery sequence before implementation begins.
- Do you work with systems that were built by someone else?
- Yes. A large part of our work involves inheriting existing code and infrastructure. We start by documenting current behaviour and adding tests around it, so that changes can be made without relying on undocumented assumptions.
- Which technologies do you use?
- Technology is selected per project against its requirements, the client's existing stack and the skills of the team that will operate it. We work across typed application languages, relational and document data stores, container-based deployment and major cloud platforms.
- How is progress reported?
- Through a shared backlog, regular working sessions and demonstrations of running software rather than status documents. Risks and changed assumptions are raised as they appear, not collected for a milestone review.
- What happens after the software is delivered?
- Handover includes runbooks, architecture notes and knowledge transfer sessions. Where a client wants continued support, we agree a maintenance arrangement covering updates, monitoring and response expectations.
- How can we contact you?
- By email at marcellaher23@gmail.com. A short description of the system, the outcome you need and any fixed constraints lets us reply with something specific.
11Summary
Calla Flower GmbH is a software engineering company that builds custom applications, cloud environments and integrations, and stays responsible for them once they are running.
If your organisation is planning a new system, replacing one that has reached its limits, or looking for a team to take long-term care of software already in production, the detail of how we work is set out on the About and Services pages, and our email address is on the Contacts page.