Founder
Niklas Mencke
Niklas Mencke founded Lucentive. He is a senior engineering leader who currently runs an AI transformation program inside a major US regulated bank, where review, audit, and approval boundaries sit in the same loop as engineering work. The method was earned in that production environment; Lucentive holds and teaches it.
His path to Lucentive runs through enterprise engineering roles where the hardest problem was rarely the core technology. The harder work was the system around delivery: which decision the work serves, who can approve it, what context travels with it, and what evidence remains after the change ships. Those are the constraints Enterprise OS was built against.
Enterprise OS is the firm methodology that carries those patterns forward. Intuitive Agent System (IAS) is the first product family built on it: a governed-action system whose current public proof profile serves engineering teams that need review, approval, context, and evidence in the same workflow.
Standing
Lucentive is 100% founder-owned, with no outside investment. Current openings are on the careers page.
AboutThe problem
Agent initiatives stall on operating-model problems, not model problems.
Most agent initiatives stall before production, and rarely because of the model. The reviews, approvals, and records around the work were never redesigned for agents that can produce code before the surrounding organization can defend it. In regulated industries the gap is sharper, because the compliance stack asks exactly the questions an ungoverned program cannot answer: what ran, who approved it, and what record was kept. The teams that close the gap are the ones that build those controls into the delivery loop, not onto it as cleanup.
- Audit and approval
- Review boundaries and the record of what ran are the core of the work, not an afterthought.
- Reusable context
- What an agent needs to know is written once, checked alongside every run, and reused.
- Operating cadence
- The team rhythm and ownership boundaries that keep the system reliable as models change.
Where the work shows up
The work is inspectable at three layers.
- 01
Founder
Niklas leads AI delivery inside a major US regulated bank, where review, audit, and engineering sit in the same loop. The method was earned there; Lucentive holds and teaches it.
- 02
Partners
7N and Globeteam are active partner relationships for selected enterprise opportunities.
- 03
Product
Intuitive Agent System (IAS) is the first product family built on Enterprise OS: a governed-action system for turning intent into controlled, inspectable work. The current public proof profile is enterprise engineering: Claude Code, Codex CLI, and Gemini CLI run under one repo-local harness with auditability, reusable context, and real control.
Visit ias.dev
Why a neutral firm
The audit trail has to cross model vendors.
When teams use multiple coding agents, regulated enterprises need one approval path across those runs. The brief, approvals, and record of what ran stay in the customer's repo. Lucentive builds from that neutral position: independent of model vendors and repo-native.
How the work compounds
Patterns earned under real constraints compound into product.
Field work earns the pattern.
The methodology is earned by the founder leading AI delivery under strict regulated-production constraints. Every pattern had to survive audit, change control, and approval boundaries before it became part of Enterprise OS.
The harness ships first.
IAS turns the parts of the methodology that belong in software into product: context that travels with every run, review steps inside delivery, and a signed record of what ran. The software ships into the customer's environment; the methodology is taught.
The system travels.
The operating model applies to the next environment without restarting the work. One environment proving the pattern is a result. The same pattern running in many environments is a product company.
Where it goes
The control layer comes first. Everything downstream of it compounds.
On the engagement side, Lucentive takes selected regulated-enterprise work where the operating model is the binding constraint. On the product side, IAS grows from the enterprise-engineering proof profile into a broader family of governed-action variants. Because the harness sits on every run, it accumulates each run's context, cost, and outcome, which makes it the natural place to understand value across models as adoption scales. That part is roadmap, deliberately. Getting the control layer right is what earns the rest.
Open conversations
Three lanes for an introduction.
Direct to founder. niklas@lucentive.io.
- Investor
In conversation with a small set of investors. If the operating-model thesis fits your fund, write directly. The note can be short; the detail is for the meeting.
Write to Niklas - Strategic partner
If you are evaluating a technology partner relationship, bring the constraint your program cannot get past. We work on selected engagements where the operating-model gap is the core constraint.
Open the conversation - Press
Press kit available on request. Briefings on governed AI delivery available for peer-CIO and journalist audiences.
Request the kit