WorkFlow Brief

Melbourne, Australia

Menu

WorkFlow Brief · Melbourne

Reduce repetitive work.Organise information.Make better decisions.

We analyse inefficient workflows and build practical software — custom tools, automation, and AI-assisted information processing — that actually fits the work.

Founded by engineers.

See selected projects How a project works

WorkFlow Brief signature process A tangled workflow on the left resolves across a brass datum into a four-step brief: understand, analyse, build, test.
A tangled workflow resolving across a brass datum into understand, analyse, build, and test.

01 Problems

Where the work gets stuck

We take on work where the process is getting in the way. If the brief is something else, we are probably not the right fit.

  1. 01

    Inefficient workflows

    Work that depends on memory, workarounds, and ‘that’s just how we do it’. Handovers are messy, and nobody is quite sure which step is the bottleneck.

  2. 02

    Repetitive admin

    The same updates, copy-paste, and checking — every week. People are busy, but the busywork is not the valuable work.

  3. 03

    Scattered information

    Decisions wait because the facts live in inboxes, spreadsheets, and separate systems. You cannot see the picture in one place.

  4. 04

    Software that actually fits

    Off-the-shelf products are close, but not close enough. You need a tool that will actually get used: something shaped around the work, not the other way around.

02 What we do

Four kinds of work

We stay inside this brief rather than offering a little of everything.

  1. 01

    Workflow analysis and automation

    We map how work actually moves — people, steps, and information — then automate the parts that should not need a person every time.

  2. 02

    Custom software and internal tools

    Software shaped around your process. Built to be used on ordinary days, not only to look convincing in a demonstration.

  3. 03

    AI-assisted information processing

    Where a large volume of information has to be read, sorted, compared, or prepared, we use AI as an assistant. The workflow stays in charge, not the model.

  4. 04

    Practical prototypes and integrations

    A working prototype can answer a question faster than a long specification. Where existing systems should talk to each other, connecting them can be the suitable solution.

A mapped tangle of people, steps, and information, reduced to a rail that keeps judgement and automates the rest.
Margin notes for reading, sorting, comparing, and preparing fold into a single brief. The workflow stays in charge.

03 Selected projects

Studies of a workflow

Our own prototypes and work in development — not commercial products, and not client case studies. They show the kind of problems we like to work on.

  • HideAnalyzer conceptual preview: a leather hide with usable-area contour and nested cutting pieces. Not a product screenshot.

    Prototype · in development

    HideAnalyzer

    Software for leather-hide analysis: identifying usable area on a hide and preparing that information for cutting.

  • YouTube video automation conceptual preview: production notes resolving into a timed programme. Not a product screenshot.

    Prototype · in development

    YouTube video automation

    A workflow from idea and research through production and publishing, so a repeatable video process is less manual from brief to published video.

  • Job search engine conceptual preview: a candidate brief compared with roles, then a shortlist. Not a product screenshot.

    Prototype · in development

    Job search engine

    A way to organise job opportunities and compare them with a candidate’s skills and experience, so search and comparison are clearer. It does not replace judgement about whether a role is a fit.

04 Engineering approach

An engineering-led approach

Founded by engineers. Software is a response to a real problem, not a catalogue of features.

Understand the problem. Analyse the workflow. Build a suitable solution. Test its behaviour.

Four stations on a brass rail: understand, analyse, build, test.

  1. 01

    Understand the problem

    What is actually going wrong, for whom, and what better would look like. We stay with the problem until it is specific enough to build against.

  2. 02

    Analyse the workflow

    How the work happens today: the steps, the handovers, the information, and the exceptions. The workflow is the design brief.

  3. 03

    Build a suitable solution

    Only as much software as the problem needs — a prototype, an internal tool, an automation, or an integration.

  4. 04

    Test its behaviour

    Does it behave correctly on real work? We test the thing that was built, not the idea of it.

05 How we work

How a project works

Every brief is different. The shape of the work stays consistent. Prices, timelines, and guarantees belong in a real conversation, once enquiries are open.

  1. 01

    You describe the problem

    What is repetitive, unclear, or stuck — and what you have already tried.

  2. 02

    We analyse the workflow together

    We look at the current way of working and the information it depends on, then say what we think is worth building, and what is not.

  3. 03

    We build a suitable solution

    A prototype or tool you can actually try, shaped around that workflow — not a larger piece of work than the problem needs.

  4. 04

    We test and adjust

    We check behaviour against real cases and refine it. If it is not helping, that is a finding, not something to paper over.

When online enquiries are available, this is the path a new brief would follow. Contact

06 FAQ

Frequently asked questions

What kinds of problems do you work on?

Inefficient workflows, repetitive admin, scattered information, and briefs that need useful custom software. We analyse the workflow, then build a suitable tool — including automation, internal software, AI-assisted information processing, prototypes, and integrations.

Do you work with every industry?

No. We are not a general digital agency, and we do not take every kind of software brief. The fit is the problem: a workflow that is inefficient, repetitive, or poorly served by the tools already in place.

Are the projects on this site client case studies?

No. They are our own prototypes and work in development. They are not commercial products, and they are not presented as client results.

What does AI-assisted mean here?

It means using AI where it helps process information — reading, sorting, comparing, or preparing material — inside a designed workflow. It does not mean handing decisions to a model, or dressing ordinary software up as innovation.

What does an engineering-led approach mean in practice?

Founded by engineers: we start with the problem, analyse the workflow, build a suitable solution, and test its behaviour. We do not start with a template, a stack, or a pitch deck.

Do you sell ready-made products?

The projects shown here are prototypes and work in development, not products you can buy from this site. Engagements are about a specific workflow and a suitable solution for it.

Where are you based?

Melbourne, Australia. How we work with people elsewhere is something we would discuss once enquiries are open.

How do I get in touch?

Online enquiries are not available yet. There is no form on this page, and we are not publishing an email address until a contact path is working. This site will be updated when that changes.

07 Contact

Online enquiries are not available yet.

Status
Closed
Based in
Melbourne, Australia

There is no enquiry form on this page, and we are not publishing an email address or phone number until a contact path is working.

This section will be updated when a working way to enquire is ready. In the meantime, you can see the kind of work we take on and how a project is structured.