← Back to the homepage

Work with us

Bring us a product idea, a process that needs automation, or a problem in an existing system. Together, we will work through the business goal, the technical constraints, and the scope of the first stage.

01

You can start without a specification.

Describe what happens today, who is affected, and what you want to change. Existing documentation helps, but the conversation can start with a few sentences.

For example
“An order passes through three systems. Staff copy data by hand, and errors cause requests to get lost. We want to connect the systems and see each order’s status in one place.”
02

Where we get involved.

We can develop a new product, work alongside your team, or focus on a difficult part of an existing system.

A new product

Define user scenarios, architecture, the data model, and a first release with a clear scope.

An evolving product

Add capabilities, connect systems, and improve performance while accounting for the current product and its dependencies.

A problem in a running system

Reproduce the problem, trace it through the code and data, identify the cause, and agree a plan to fix it.

03

Agree what success looks like.

Before defining the scope, we agree what needs to change and how the result will be checked.

Business goal
The process or user capability to improve, and the benefit the business expects from that change.
Constraints
Timeline, budget, system availability, data requirements, and integrations that must keep working.
Acceptance criteria
Specific scenarios, data checks, and agreed indicators used to assess the work.

For automation, this could mean fewer manual steps; for data, a report reconciled against its sources; for an integration, a complete flow from an event to the required business action.

04

What to include in your first email.

A short description is enough. These five questions help us understand the task and prepare a useful first discussion.

  1. What does your product do, or which process needs to change?
  2. What exists today: a system, a team, documentation?
  3. Which problem needs solving, and what outcome do you want?
  4. Which deadlines and constraints should we account for?
  5. What is your name, and how can we reach you?