Client portals, CRMs and internal tools for companies that have outgrown spreadsheets and can no longer bend an off-the-shelf SaaS into shape. Fourteen engineers, two-week increments, and source code you own on day one.
We don't do everything. We do the software your staff and customers open every morning — the operational core, not the marketing site.
A branded workspace where your clients see exactly what they're allowed to see, and act without a phone call.
When your sales process has three approval branches and a bespoke quote calculator, configuring someone else's CRM costs more than owning one.
Back-office software that replaces the shared spreadsheet, the WhatsApp thread and the person who "just knows how it works".
Most of the work in a portal is not the screens — it's the plumbing behind them, and the honest handling of what happens when it fails.
Same data model, two audiences: the customer sees their own shipments; the sales team sees the pipeline behind them. Details are anonymised, the layout is not.
| Shipment | Route | ETA | Amount | Status |
|---|---|---|---|---|
| NL-40217 | Gdańsk → Rotterdam | 08 Sep, 14:20 | €4,120.00 | In transit |
| NL-40216 | Poznań → Hamburg | 09 Sep, 09:05 | €2,860.00 | In transit |
| NL-40209 | Łódź → Antwerp | Delivered 04 Sep | €3,540.00 | Invoice due |
| NL-40204 | Kraków → Lyon | Delivered 02 Sep | €1,960.00 | Docs to sign |
The portal and the CRM read the same shipment records. One source of truth, two permission sets — which is the entire reason we build them together.
Each stage ends with something you keep, whether or not you continue with us. No stage depends on a promise about the next one.
We interview the people who do the work, map the process as it really runs, and write down where it leaks. Ends with a scope document and a fixed price band, not a range with a shrug.
Data model, permission matrix and integration contracts on paper first; a clickable prototype of the main screens in parallel. Your team clicks through it before a single endpoint is written.
Staging environment from day one, a demo every second Thursday, and a working release at the end of every increment. You see the burn-down and the backlog in the same tool we do.
Deployment pipeline, infrastructure as code and written runbooks go to your team. Then either we support it under a 4-hour SLA, or we spend a month training your engineers to.
Indicative figures for a European team, quoted per project after discovery. Whatever the shape, the code and infrastructure are yours.
Every choice here has a hiring pool in Europe and documentation older than we are. You should never be locked to us by a framework nobody else writes.
Your cloud account, ours, or on-premise. We deploy to EU regions by default and can keep personal data inside your own perimeter.
GDPR-shaped data handling, encrypted backups tested by restore, dependency and secret scanning in CI, annual penetration test on request.
You do, from the first commit. We work in your repository where you have one, and transfer ownership of everything — source, infrastructure definitions, domain and cloud accounts — where you don't. There is no licence to renew and no runtime we host on your behalf unless you ask us to.
Often, yes. We start with a two-week audit: architecture, dependency health, test coverage, deployment path and the three riskiest places in the codebase. You get the written findings whether or not you continue — about a third of audits end with us recommending you keep your current team and fix a specific list.
On a fixed-scope build, changes are quoted against the signed scope and go in or out by your decision at the increment boundary. On a dedicated team, priorities simply move in the backlog — you re-order, we build what's on top. Either way nothing changes silently.
Development and staging run on anonymised copies; production credentials stay with your team. Access is per-person and time-boxed, every environment is logged, and we sign your DPA or use ours. If your sector requires it, the whole engagement can run inside your infrastructure.
Thirty minutes, no deck. Bring the process that hurts most and we'll tell you plainly whether it's a two-week fix, a three-month build, or something you shouldn't build at all.
Avalux Systems Ltd, Reg. No. HE 479663
Fellachoglou 35, Mouttallos, 8016 Paphos, Cyprus