·
00 Statement

We build from understanding.

Complex systems start with understanding the work itself.

Domains in which we develop.

01. Point clouds

From scan to structure

Scans produce billions of points but rarely usable structure. We build pipelines that move from raw scan to object model. Automated, reproducible, auditable.

02. Digital twins

Models that move with reality

A model is only a twin if it moves with reality. We build systems where design, scan and actual state stay in sync, so decisions are made on what is, not on what once was.

03. 3D native platforms

3D as data model

Most software is 2D with 3D bolted on top. We build the other way around: 3D as data model, not as visualisation. That changes what you can do with it.

04. Engineering & as-built

Design into reality

Between design and reality is where most information is lost. We structure that handover so what gets built remains traceable, verifiable and transferable.

05. AI development

AI where processes stall

We apply AI where processes stall on manual work. Document handling, case analysis, decision-making in domains where the rules are complex and the volumes are large: notarial practice, asset management, engineering.

06. Process automation

Process as system

A large share of our work sits here: process automation for contractors and the (semi-)public sector. Standardised work that piles up across many parallel cases. We build systems that move that flow on their own, so people are left with the parts that actually need a person.

Three ways something comes into being.

Mode 01

On commission

We build software for organisations running into the limits of their existing systems. Not as a project with an end date, but as a system that stays in place.

Mode 02

As a venture

Sometimes a solution turns out to be more broadly applicable than the original problem. Then we set up a standalone company together with domain partners, with its own direction and its own future.

Mode 03

On our own initiative

Part of what we build comes from our own observation. Problems we keep seeing return and want to solve ourselves, from the conviction that it can be done differently.

We innovate from the content outward.

We bring two things that rarely sit in one team: the capacity to innovate and the discipline to execute. We absorb the subject matter quickly and work alongside the people who have spent years inside it. Where they hold the operational logic, we open technological doors they did not know existed. What comes out is automation neither side could have conceived alone.

They bring
Operational logic.
We bring
Technological reach.
Together
Systems that could not exist otherwise.

You can only build what you have first understood.

We start inside the work itself. With the people who have spent years there. Long enough to understand it as it actually is. Not as it is described. Not as it should be.

A system is only finished when it can continue without us.

We build for what comes next. For the user we never met, who finds the system already running and uses it as if it has always been there.

Built with the practice.

Cursor develops software in collaboration with parties from the field. What we build starts with a concrete problem and ends with a system that stands on its own.

For interest or questions.

info@cursoram.com

A short note is enough. We read everything that comes in.