• DESIGN
  • ENGINEERING
  • OPERATIONS
  • AI

Where a person thinks,and the system works.

Relay Atelier is an independent studio that understands how a business runs and turns that understanding into a working system.

SCROLL
[ APPROACH ]

First we understand the work. Then we build the system.

Most software asks the organisation to fit around it. We do the opposite: we map where a request comes in, whose hands it waits in, and at which step it closes, and build the system on top of that flow. Automation is a decision taken after the work is understood — not the place you start.

— Relay Atelier

[ PROCESS ]

Six steps

Each step uses the output of the one before it. None is skipped, and none happens only once.

  1. 01

    Discovery

    We talk to the people doing the work. Which channel a request arrives through, where it waits and who closes it, heard first-hand.

  2. 02

    Mapping

    We set the flow out step by step. Which part runs by hand and which part can move to a system becomes visible on that map.

  3. 03

    Design

    Interface and flow are designed together. Whatever a team will use twenty times a day, we make fast first.

  4. 04

    Build

    We build the system. It starts as one small working piece and is tested against real data at every step.

  5. 05

    Integration

    We connect it to what already exists. The new system runs inside the tools the organisation uses, not beside them.

  6. 06

    Improvement

    We watch it once it is live. Where it sticks, what it misses and what has changed goes back into the system itself.

[ WHAT WE BUILD ]

Five kinds of system

  • AI agents and reception

    The layer that answers an incoming request, qualifies it, and hands it to a person where it should.

  • Operations and workflow automation

    Repeated manual steps become a defined, traceable flow.

  • CRM and request management

    Requests from scattered channels visible, routed and closed in one place.

  • Bespoke web applications

    Software written for the business logic an off-the-shelf product does not cover.

  • Internal tools and integrations

    The panels a team runs its day on, and the connections between systems.

[ DISCIPLINE ]

How we build a system

Design

Systems with a defined scope

A system is built by defining what it will not do as carefully as what it will. Behaviour left undefined turns into a surprise in production.

Named handover points

Every step that calls for a decision is marked and passed to whoever owns it. Automation does not stand in for professional judgement.

Data minimisation

We do not collect data the process does not need. Which field is kept, and why, is settled while the scope is being written.

Build

Never failing silently

When a step fails the system does not quietly stop; it records what happened and makes it visible to the person who needs to see it.

Reversibility

Wherever it is possible a change is built so it can be undone, and a system is brought into use in stages.

Validation and handover

Validation against real scenarios

The happy path is not enough. Missing information, the wrong channel, a repeated request, a cancellation — all of it is tried before delivery.

A written way of working

The flow we build is documented with its rules and its connections. How the system works does not live in one person's memory.

These are how we work; they are not a certification or a statement of compliance. In regulated fields the legal framework is settled with your own legal adviser while the scope is being written.

[ COMMERCIAL TERMS ]

The rules of working together

  1. Discovery is a step of its own

    A process analysis is worth something on its own and can be bought on its own. You end up with a map of your process; you are not obliged to continue.

  2. No development before the scope is written

    What will be built, what is out of scope, which data will be used and how success will be measured are all written down before anything is signed.

  3. Price is tied to scope

    We do not sell hours. We give a fixed quote for a defined scope; if the scope changes, we discuss that separately.

  4. The system we build is yours

    Accounts, code and documentation are set up in your name. If you stop working with the studio, the system stays with you.

  5. Support is not compulsory

    Maintenance after delivery is optional. We do not impose a binding subscription.

A woman in dark clothing looking straight at the camera, holding a cream board printed with the words Relay Atelier.
[ START WITH A CONVERSATION ]

Good ideas start with a conversation.

Tell us where the time goes, which step jams, or what you want to change. We'll work out together where to start.

[ STUDIO ]

An independent practice

Relay Atelier is a small, independent studio. Design, engineering and operations run at the same table, so what a decision means in the interface and in the database is discussed at the same moment. The team that takes a project on is the team that built it.

Experience in healthcare pointed our first focus at clinics; the systems we build are not limited to healthcare.

Company
Relay Atelier Ltd
Company no.
17549626
Registered
England and Wales
Working languages
Turkish · English