Water & Wood AtelierSoftware engineering studio

Contacts

Written enquiries, answered in plain language

All correspondence with WATER AND WOOD ATELIER LIMITED is handled by email. Writing tends to produce better first conversations than a call, because it forces the problem to be described and leaves a record both sides can refer back to.

Company

WATER AND WOOD ATELIER LIMITED

Email

heidibrooks198461@gmail.com

The address above is plain text. Copy it into your email client to write to the studio.

Quiet meeting corner in a technology studio with an open laptop showing an email client

Before you write

What to include in an enquiry

None of these are required. Each one, however, shortens the distance between the first message and a useful answer.

  1. 01

    The problem in your own words

    A few sentences about what is not working today and who it affects is more useful than a feature list.

  2. 02

    Systems already in use

    Names of the applications, databases or services involved, and which of them cannot be replaced.

  3. 03

    Who will use the result

    Roles, approximate number of people, and whether they are internal staff, customers or both.

  4. 04

    Constraints that are fixed

    Deadlines tied to external events, budget boundaries, regulatory rules, hosting requirements or existing contracts.

  5. 05

    What already exists

    Documents, designs, prototypes, a live system or a repository — anything that shows the current state.

  6. 06

    How you prefer to work

    Whether you want a defined build, continuous work alongside your team, or an advisory review only.

Subjects

Topics that can be discussed by email

A new system

Feasibility, likely shape, sequencing and the questions that need answering before any estimate is meaningful.

An existing codebase

Review options, modernisation paths, dependency and platform upgrades, or taking over maintenance.

Integration work

Connecting applications, moving data between them reliably, and handling failures and reconciliation.

Design and accessibility

Interface structure, design systems, and meeting WCAG 2.1 AA principles in an existing product.

Cloud and deployment

Environment definition, release automation, monitoring, backup strategy and infrastructure review.

Performance concerns

Slow pages, slow queries, growing infrastructure cost, and how these would be measured before changes.

Ways of working

Engagement models, communication cadence, documentation expectations and handover arrangements.

General questions

Anything about the studio's approach that this website does not already answer clearly.

Process

How the conversation usually proceeds

No timescale is promised here, because a commitment of that kind would only be meaningful once agreed with you directly.

  1. 01

    Your message arrives

    The enquiry is read in full, together with any material you attach or link to.

  2. 02

    Clarifying questions

    A written reply confirms what has been understood and asks about anything ambiguous or missing.

  3. 03

    Shared understanding

    The problem, the constraints and the desired outcome are restated in writing so both sides agree on the subject.

  4. 04

    Proposed approach

    Where the work is a fit, an outline of a first stage is described, including assumptions and what would fall outside it.

  5. 05

    Decision

    You decide whether to proceed. If the work is not a good fit, that is said plainly rather than shaped into an offer.

A note on privacy

Information you send by email is used only to respond to your enquiry and to discuss possible work. Please avoid including sensitive personal data, credentials or confidential documents in a first message; secure arrangements can be agreed once the conversation is underway.

Details of how personal data is handled are set out in the Privacy Policy. The terms that apply to the Application operated by the Service Provider are set out in the Terms of Service.

Email

heidibrooks198461@gmail.com