Lumen Advisory & Technologies is an operations consultancy and software studio in Oranjestad, Aruba, that maps how a business runs, redesigns the process, and builds the internal system that holds it.
Three answers to the same question, depending who you ask.
The report exists. It lives on one laptop.
The process holds, as long as one person is in the building.
Usually sold together, in this order
The order matters. Software applied to an undesigned process just makes the mess faster.
Selected engagements in Aruba and the Dutch Caribbean
These are internal systems. Sector, scope, and scale are accurate; names on request.
Construction and trades, logistics, agencies, and professional services.
What an operations diagnostic involves
Two to three weeks alongside the people who do the work. Interviews, screen shares, a walk through the actual queue. No survey forms and no maturity scores.
The output is a decision document, not a slide deck. If a build is not warranted, that is written down too.
What gets built: custom internal software for Aruba businesses
One system, built around the process the diagnostic produced. Staff open it on a phone in the field and on a desktop in the office, and it is the fastest way to do the job.
Runs in the browser. Installs to a phone home screen and opens like an app.
One database, one source of truth. No parallel spreadsheets.
Roles decide what each person sees. Nothing is hidden by convention alone.
Every change is recorded. You can see who changed what, and when.
Three screens from live systems, reproduced with sample data. They are interactive.
How we work: map, design, build, hand over
Three people, based in Aruba
Lumen is three people in Oranjestad. The person you brief is one of the three who map the process and write the code. There is no account manager and no handoff to an offshore team.
That is the advantage, and it sets the limit: a small number of engagements at a time.
Work is done in your time zone, in English, Spanish, Dutch, or Papiamento.
Tell us where the work stalls
Two or three sentences is enough to know whether there is something here.
Start a diagnosticQuestions we are asked before the first call
How long does a diagnostic take?
Two to three weeks. That time is spent alongside the people who do the work: interviews, screen shares, and a walk through the actual queue, not survey forms or maturity scores. The output is a decision document rather than a slide deck, and if a build is not warranted that is written down too.
Do you work with the systems we already have?
Yes. Accounting, ERP and existing tools are connected to one source of truth rather than replaced for the sake of it. The automation list that comes out of the diagnostic splits every task three ways: build it, buy it, or stop doing it.
What happens if you are not available?
The code, the credentials and the documentation are yours at handover, so the system does not depend on us staying reachable. Support continues only if you want it. Nothing in the build requires our involvement to keep running.
Can you take over a project another developer started?
Yes, and it is a normal way for work to arrive. We clone the repository, run the gates, and separate what is actually done from what the handover document claims. You get that status in writing before any new work is scoped or quoted.
Do you work outside Aruba?
Yes. Work is done in your time zone, across Aruba, Curaçao, Bonaire and the wider Caribbean. Language is not the constraint: the work is done in English, Spanish, Dutch or Papiamento.
What do we own at the end?
Everything: the code, the credentials and the documentation. There is no licence to keep paying and no component held back. Support afterwards is a separate decision, not a dependency.
Get in touch
A short description of how the business runs and where it stalls is enough to start. Four fields, then a reply from the person who would do the work.