Discuss a Project
myer / how-we-workHow we work

The work is only real when people can rely on it.

We combine workflow discovery, product design, software engineering, and AI evaluation. The goal is not a striking demo. It is a system people can understand, use, supervise, and improve.

One accountable path from problem to operation.

  1. 01

    Understand the work

    We identify the user, the decision, the input, the current tools, the handoffs, and the cost of error. We agree what a first useful result would be.

  2. 02

    Define the system

    We specify interfaces, data access, permissions, integration points, exceptions, human approvals, and success measures before expanding the build.

  3. 03

    Build a narrow release

    We implement the core workflow and put it in front of the people who will use or supervise it. The first release should answer a concrete operational question.

  4. 04

    Validate in context

    We test for useful output, failure handling, latency, security expectations, and user understanding. AI components are evaluated against the task they serve.

  5. 05

    Handover and improve

    We document the system, its limits, and its operating responsibilities. Subsequent work follows evidence from use and agreed priorities.

The controls are part of the product.

Access

Access and permissions appropriate to each role.

Review

Human review where a decision carries material consequence.

Traceability

Clear source and action records where traceability matters.

Failure

Failure paths, retries, and safe fallback behavior.

Evaluation

Evaluations against representative real-world tasks.

Ownership

Documentation and ownership for ongoing operations.

The exact controls depend on the use case and engagement. We discuss those boundaries before promising autonomous behavior.

Clear ownership on both sides.

A strong project has a named business owner, access to users and current workflows, timely decisions on scope, and clear ownership of data and approvals. Myer provides a defined engineering team and transparent delivery communication appropriate to the engagement.

A useful first conversation starts with one workflow.

Describe where it begins, where it stalls, what systems are involved, and what a better outcome would mean.