Skip to content

Studio

Three people.
One connected practice.

Design, direction and engineering. Close to the work from the first conversation.

Team

The people behind the work.

The same three people from the first call to launch.

Edward Salvatierra

Founder & CEO Vision, intelligent systems and engineering

Holds product direction and builds the technical systems behind the experience.

LinkedIn
About Edward

Edward holds the product vision and builds the systems on every engagement: the AI workflows, the data layer and the engineering that keeps them running after launch.

Alexander Koch

Co-founder Strategy, scope and oversight

Shapes engagement direction, scope and timeline and supports governance.

About Alexander

Alexander sets the direction of each engagement and signs off its scope and timeline before work starts. He also owns the studio's governance and how it grows.

Kevin Silva

Design director Design and visual systems

Leads the interface, visual consistency and reusable design language.

About Kevin

Kevin designs the interface and the visual system. He owns UI and brand consistency on Incontro Bar and Dreilokale, from the first layout to the last component.

Remote-first. Working globally.

On site when it helps.

English · German · Spanish

Our approach

How we stay close to the work.

Six working principles.

  1. Systems over screens.

    We start with workflows, users, data and decisions, then design the surface.

  2. Clarity before complexity.

    Whoever uses the system should see at once what matters and what to do next.

  3. Measure, do not guess.

    Where intelligent systems are involved we define what a good answer is and test against it before anything goes live.

  4. Working previews early.

    You get something real to review throughout the engagement, not slides about what is coming.

  5. Code you can inherit.

    We document and structure the implementation so the next team can understand it.

  6. Small by design.

    Three people, deliberately, so the decision-makers stay close to delivery.

Internal R&D

Inside the studio.

Research, concepts and tools we build for ourselves.

Internal R&D, not client work
  • Morvion AI Sentinel

    System direction

    An operating-layer concept for running a business day to day, explored in a self-funded Discovery Sprint.

    Morvion AI Sentinel

    Internal R&D, not client work
    What we explore
    CRM intelligence, tasks, multi-agent workflows, sales pipelines and decision support in one operating layer.
    Current status
    A Morvion product direction explored in internal research. Not launched, no customers.
    How it informs our work
    The review and routing patterns we test here shape how we design intelligent workflows for clients.
  • Atlas Intelligence

    Internal tool

    A CRM with enrichment, signal scoring and lead prioritisation, used for the studio's own pipeline.

    Atlas Intelligence

    Internal R&D, not client work
    What we explore
    Enrichment, signal scoring and prioritisation on top of a plain CRM.
    Current status
    In use for the studio's own pipeline. Not offered as a product.
    How it informs our work
    It shows us where automation helps a small team and where a person still has to decide.
  • Platform prototypes

    Experiments

    Internal experiments with marketplaces, client portals and workflow tools.

    Platform prototypes

    Internal R&D, not client work
    What we explore
    Two-sided matching, portal and workflow patterns, tested in Atelier, an internal marketplace probe.
    Current status
    Ongoing experiments inside the studio. None is a client project.
    How it informs our work
    Patterns are proven here before they go into a client platform.
  • Studio knowledge layer

    Internal tool

    A structured record of decisions, references and technical patterns.

    Studio knowledge layer

    Internal R&D, not client work
    What we explore
    How a small studio keeps what it has learned findable: decisions, references, patterns.
    Current status
    In use inside the studio.
    How it informs our work
    A new engagement starts with what the studio has already learned.

Work directly with the people building your system.

One conversation to start. Scope, timeline and price in writing before you commit.

Start a project