Web platforms
Multi-tenant systems, portals and the sites in front of them.
Service lines
They stack. Discovery decides what to build, the seven between build it, support keeps it running. Take one, or take the sequence.
Discovery & scoping
Workshops, a review of the systems you already run, and a technical spike on whatever looks riskiest. It ends in a scoped backlog, an architecture, and a fixed price to build it.
Custom platforms & SaaS
Multi-tenant systems, internal tools and customer portals shaped around your process rather than a template's. The bulk of what we do, and where a discovery pays for itself.
Web & mobile products
iOS in Swift, Android in Kotlin and the web alongside, from the first screen through to the store listing. Native by default, so the product feels like the phone it ships on.
ERP, POS & operations
Inventory, sales, finance and HR, plus point of sale that clears the tax authority before it ships, rather than in a hurry after a customer is handed a receipt nobody accepts.
ELV & building systems
Structured cabling, IP CCTV, access control and public address, specified and commissioned as one system. The half of a project most software houses hand to somebody else.
Data & integrations
Reporting, pipelines, and the integrations that make two systems built a decade apart agree on one number. The least glamorous line, and often the one that unblocks the rest.
AI & automation
Assistants, document extraction, forecasting and search, built into the system that already holds your data. We will also say where a model is the wrong tool for the job.
Cybersecurity
Hardening, review and incident readiness: identity, secrets, dependencies, penetration testing and the evidence an audit asks for. Against what you run, not only what we build.
Support & evolution
Monitoring, upgrades and a roadmap, on a retainer that ends when you say so. We stay after go-live, which is the only reason a first version is worth writing carefully.
What we build it with
Daleenda is a software house and IT solutions company. Everything in our sector is in scope: software, data, cloud, infrastructure and the systems in the building, carried by one team that owns the outcome. What that looks like in practice:
Native mobile
iOS in Swift, Android in Kotlin, through review and into the stores.
AI & automation
Models put to work inside your systems, and an honest no where they don't belong.
Backend, APIs & data
Services and the databases under them: ours, or the ones you already run.
Cloud & DevOps
Accounts you own, pipelines that deploy themselves, dashboards that phone first.
On-site & building systems
The low-voltage systems a site runs on: cabling, cameras, access, audio.
Business & commerce
ERP, point of sale, payments and the reporting that sits on top.
How we choose
Two questions asked before anything enters a stack of ours.
We do not adopt a technology for one project.
If we could not support it in five years, we do not start it.
A model, a framework or a rewrite has to earn its place.
Where the honest answer is that you do not need one, that is the answer you get.
What you own
Three things that are yours from the day the work starts.
You own the repository, the pipeline and the cloud account from day one.
Nothing runs on an account you cannot log into.
No licence you have to keep paying us for.
Where a product is ours, it is named as ours.
The documentation and the tests ship with the system.
A team that was not there when it was written can still keep it running.
How we engage
Three shapes. What separates them is how settled the work is.
When the scope is settled
Project build
Fixed scope, fixed price, delivered in phases, each with something you can see and use.
- Billed
- By phase, against a fixed price
- Runs
- Six weeks to two years
When the scope keeps moving
Dedicated team
Senior engineers embedded with your team, working to priorities you set each cycle.
- Billed
- Per engineer, per month
- Runs
- Three months and up, rolling
When it is already live
Retainer
Support, iteration and growth for a live product: the work that starts after launch.
- Billed
- Per month
- Runs
- Rolling, ends with notice
What happens next
The same four steps whichever line and model you land on.
- You are here
30-minute meeting
You talk to an engineer. We listen, ask, and tell you honestly if we're the right fit.
- You are here
A proposal scoped to the work
Fixed scope and price for a defined build; a phased plan for a larger programme. In writing, without obligation, and small asks come back in days.
- You are here
Delivery in the rhythm the work needs
Short cycles with a demo at each for product work; staged milestones for large programmes. Either way you own the code and the repo from day one.
- You are here
Launch, run, improve
Monitoring, support and a roadmap. We stay after go-live.