@maordp
Data / AI / AI Economy / Technology
TECHNOLOGY · DATA · AI EXECUTIVE

Between the customer conversation
and the architecture diagram.

I’m Maor David-Pur. I’ve built my career moving between technology, customers and business - from software and product to presales, data, AI and technology leadership. I like turning a real problem into something that can be understood, built, adopted and scaled.

MY VIEW ON AIThe AI demo is becoming a commodity. Everything around it isn’t.

LinkedIn ↗
Maor David-Pur portrait
Maor David-Pur
01 / Career in one view

Build. Customers. Lead.

I started in software and kept moving toward the places where technology has to meet reality: product decisions, customer conversations, presales, data platforms, AI and eventually the challenge of building teams and organizational capabilities around all of it.

BUILD

Technology with enough depth to make decisions.

Software, architecture, platforms, data and AI - not as isolated domains, but as parts of a system that has to work.

CUSTOMERS

Start with the problem, not the product.

Discovery, presales and solution shaping taught me to ask what someone is actually trying to achieve before deciding what to build.

LEAD

Build the organization, not only the solution.

As my roles became more senior, the question shifted from “what should we build?” to “how do we build the organization that can keep doing this well?”

02 / The work

From fragmented technology to capabilities that last.

I care less about launching another project than about leaving behind something an organization can reuse, operate and improve.

Build multidisciplinary capabilities

I lead a technology organization of approximately 50 people, connecting multidisciplinary capabilities around shared outcomes.

Move from use case to production

Turning an interesting idea into a capability with real data, architecture, ownership, security, measurable value and a path to adoption.

Translate across the table

Moving between customer needs, executive priorities and technical trade-offs without losing the substance in translation.

03 / What I’m learning

One argument, three consequences.

Models are becoming easier to replace. Organizational context is not. That shift changes what we should build, what we should govern and how we should think about the cost of intelligence.

01
MODEL CHURN

Stop designing around today’s best model.

The winner of this month’s benchmark is not a durable architectural dependency. Models will improve, prices will fall, capabilities will converge and the best choice will vary by task.

THE IMPLICATION

A replaceable model layer. Keep business logic, organizational context, evaluation and security outside the model. The durable asset is the system around it.

02
MACHINE CONTEXT

The catalog is becoming infrastructure for humans and machines.

A catalog used to help people find data. Agents need more: meaning, ownership, quality, permissions, lineage and a reliable way to discover what organizational data they can use.

THE IMPLICATION

Metadata stops being housekeeping and becomes machine context. The catalog may become part of how an organization tells AI what its data means - and what it is allowed to do with it.

03
ECONOMICS OF INTELLIGENCE

Architecture now determines the bill.

In AI systems, model choice, context, routing, frequency and agent loops create cost while the system runs. More intelligence is not automatically more value.

THE QUESTION I KEEP COMING BACK TO

How much intelligence is this decision worth?

The goal is not to minimize tokens. It is to spend intelligence where it changes the outcome - and use smaller models, less context or deterministic software where it does not.

THE CONNECTION

Replaceable models. Proprietary context. Deliberate intelligence.

If models become increasingly interchangeable, competitive advantage moves outward: into the context an organization owns, the architecture that can use it safely, and the ability to apply the right amount of intelligence to each decision.

04 / Writing & Ideas

Turning the theses into writing.

AI Weekly is where I interpret what is changing now. These are the longer arguments I’m developing from the ideas above.

PUBLISHED WEEKLY · HEBREW

AI Weekly

A weekly briefing focused on the developments that may actually change architecture, economics, products and management decisions.

Read AI Weekly ↗
IDEAS I’M WORKING THROUGH
01The Catalog Is Becoming Runtime InfrastructureFrom metadata for humans to context for agents.
02How Much Intelligence Is This Decision Worth?A way to think about AI architecture and economics together.
03Stop Designing Around Today’s Best ModelWhy model churn should be an architectural assumption.
05 / A bit more personal
I like technology, but I also like understanding how things work - whether that means an AI architecture, a home network, something I’m building myself, or a piece of history.

I’m based in Herzliya, Israel. Outside work, I’m usually experimenting with some piece of technology, doing a DIY project at home, reading about history, or trying to make something work a little better than it did before.

A GOOD CONVERSATION

Technology, AI, leadership
and what comes next.

I’m always interested in a thoughtful conversation with people building ambitious things.

Start on LinkedIn ↗