Project operations intelligence
LumenSpark connects delivery, capacity, time, cost and operational performance in one system, giving leaders the clarity to identify risk, protect margins and act earlier.
Built for project-driven companies that need more than task tracking.
Scroll to see the operating model
One operating model for the work, the people and the financial reality behind every project.
Positioning
Most tools tell teams what was assigned and what was completed. LumenSpark connects that activity with capacity, time, cost, revenue, utilization and delivery risk.
Getting there takes implementation work.
Connected operating model
LumenSpark keeps one chain of records. A client becomes an opportunity, an opportunity becomes a project, a project consumes people and time, time becomes cost, cost becomes margin, and margin informs a decision that stays traceable.
Capabilities at a glance
Nine capability areas run on one data model, so a change in one place is visible everywhere it matters.
Revenue against real labour cost, expenses and billing phases. Cost rates per member make margin a measured number, not an estimate.
One capacity source: the company work calendar defines a full day, each member contract defines their share of it.
Allocated against available, next four weeks
Spark
The platform computes the numbers, Spark explains what changed and where attention is needed.
margin 18.4% · min 24% · labour €41,200 · revenue €50,500
margin 34.1% · spent 410 h · plan 460 h
From plan to delivered work to the financial result, in one continuous record.
Timer, manual entry, imports and reconciliation, with billable and non-billable separated.
A hash-linked change log, role-based access and GDPR retention rules.
-
Schedule view: phases, milestones and the current date marker on one timeline.
-
Absence and leave balances
Allocation against available capacity, plus approved absence for the same period.
-
Daily log: project, task, billable flag and duration, recorded once.
-
Cash flow across the period, with the break-even line and monthly result.
-
Funnel by stage, with the expected value carried into the project on conversion.
-
Portfolio view: revenue, cost and margin per project against the minimum threshold.
How a project moves through the platform
Nothing is re-entered between stages. The plan, the delivered work, the cost and the decision all live on the same project.
An opportunity converts into a project with a team structure, planned hours, expected cost and expected revenue. Milestones and phases are defined before work starts.
Kanban and schedule carry the active work. Time is tracked by timer or entered manually, dependencies and progress stay visible on the same project.
Actual cost, utilization, billable ratio, delivery status and project profitability are derived from the same records, with no separate reporting spreadsheet.
Spark Insights flags margins below threshold, exceeded hour budgets, approaching deadlines and overloaded members, then explains the finding in plain language.
Actions get an owner and a due date, approvals are recorded, and every change stays in the audit trail for later review.
Opportunity funnel
Planned frame
Schedule and Gantt view
Plan vs actual
Project health
3 findings · 2 need attention
Margin pressure is concentrated in one project rather than spread across the portfolio.
Delivery Portal — labour cost exceeds plan, margin has dropped below the threshold.
margin 18.4%
More hours have been spent than planned.
spent 892 h
The system computes the numbers from your data, Spark only interprets them. Verify before deciding.
Change log, hash-linked
Spark Insights and AI Narrative
LumenSpark combines structured project, team, time and financial signals to surface patterns, explain operational changes and help management focus attention where it matters.
The platform computes every number deterministically. The model interprets and describes those numbers; it does not calculate margin and it does not decide.
3 findings · 2 need attention
Margin pressure is concentrated in one project rather than spread across the portfolio.
Delivery Portal — labour cost exceeds plan, margin has dropped below the threshold.
margin 18.4% · min 24%
More hours have been spent than planned.
spent 892 h · plan 800 h
Healthy margin with hours below plan.
margin 34.1%
The system computes the numbers from your data, Spark only interprets them. Verify before deciding.
Role-based value
Navigation and permissions follow the role, so people see the level of detail they are accountable for.
A single portfolio view of health, margin and utilization, with the underlying detail one level away when a number needs explaining.
Workload and dependencies read from the same schedule the teams work in, with process health visible instead of inferred.
Cost rates, expenses and billing phases connect to recorded work, so financial figures reconcile with delivery rather than diverge from it.
Schedules, milestones and allocation in one place, so portfolio reporting is a view of the work rather than a weekly collection exercise.
Availability, absence and allocation for the team, with time trends used to plan rather than to police.
Project health, work logs, cost and open risks on one screen, with actions that carry an owner and a date.
See operational reality before it becomes a board-level surprise.
Connect delivery, capacity and accountability across the operation.
Trace project activity to cost, margin and cash impact.
Replace fragmented project status with one operating view.
Understand capacity without reducing people to timesheets.
See what changed, why it matters and what requires action.
Governance, security and system health
Access, changes and system state are all recorded. Governance is part of the product rather than a separate spreadsheet maintained after the fact.
Designed with role-based access. Navigation and permissions follow the role, and permission changes take effect on the next sign-in.
The change log records who changed what and when, with records hash-linked so a gap in the chain is detectable.
Password hashing, sign-in throttling, session regeneration and TOTP two-factor authentication for accounts that enable it.
Built for GDPR-conscious workflows: retention rules, export of a person’s data and a documented deletion path.
Sign-in history and active sessions are reviewable, so access questions can be answered from the record.
Built-in system health and diagnostics surface migration state, integration status and configuration problems.
LumenSpark makes no certification claims.
Where work already happens in another system, LumenSpark reads it in and reconciles it.
Connect delivery, people, time, cost and profitability in one operating model, and give every important decision reliable context.
A demo is a working session on your own operating questions, not a slide deck.
LumenSpark is developed and maintained by Lumen Spei d.o.o. in Osijek, Croatia. The platform started as the operating system for our own project work, which is still how it is used every day.