Our philosophy

Tailored to the business.
With the discretion of an atelier.

How we work matters as much as what we build.

A considered approach to craft

Attention to context.
Precision in execution.

For us, an atelier means taking time to understand and maintaining continuity from the first conversation to delivery. What we learn about the business informs the choices we make along the way.

Sometimes a solution calls for simplification; sometimes it takes patience with a detail that changes how it is used. Every choice should have a purpose and be open to explanation.

That care extends to the client relationship: how we handle information, the boundaries of access and our responsibility for what we deliver.

Working principles

The foundations of a working relationship.

01 / INDIVIDUALITY

Made for a particular business.

A bespoke solution may embody commercial rules, processes and knowledge that set a company apart. We respect their confidentiality throughout development.

We use established technologies where they fit. The solution’s configuration, workflows and user experience are designed for the client’s circumstances. Dedicated solutions and confidential business logic do not become products to resell to competitors. Rights to deliverables and terms of use are agreed at the outset.

02 / DISCRETION

Trust is not promotional material.

Working together may give us access to plans, difficulties and decisions that are not public. We use that information solely for the agreed purpose of the project.

Client names, internal products, application screenshots and project results are not used in our communications without explicit consent. A relationship can remain private throughout the engagement and after the project ends.

03 / DATA

Access has a purpose and a limit.

We request the data and access needed for the agreed work. We clarify what information is used, by whom, where it is held and how long it is needed.

For development and testing, we prefer synthetic or anonymised data. The use of real data, access by collaborators and external services are discussed for each project. At completion, we agree the handover, retention or deletion of information and the withdrawal of access that is no longer needed.

04 / SECURITY

Care for data begins with design.

Security is part of the design and development decisions: access appropriate to each role, separate test and production environments, protected credentials and limited exposure of information.

We define safeguards, backups, checks and maintenance responsibilities according to the data and how the solution will be used. We discuss risks and limitations, including what happens when a problem arises and who needs to respond.

05 / JUDGEMENT

Technology must earn its place.

We choose tools for their usefulness to the business, their maintenance cost and the control they offer. The same standard applies to artificial intelligence.

Using an AI service with client data requires clarity on what information is shared, the provider’s terms and consent for that use. We establish where human review is necessary and who is responsible for the final decision.

A shared framework

Principles become
practical decisions.

These principles are reflected in the agreements and working practices of each project. We clarify responsibilities from the outset and revisit them when requirements or circumstances change.

Let’s talk