Measure first, then fix.

We show where your company’s work gets lost and fix what is worth fixing — with what you already pay for, or with software built for you.

Process consulting and software development

  1. Observe As long as it takes, inside the operation.
  2. Measure The starting point is fixed before any work begins.
  3. Assess We separate what is secondary from what is a real risk.
  4. Fix Biggest impact first. Not everything needs software.
  5. Follow up We measure again on the agreed date, from the same source.

Is this you?

If you recognise yourself in one or two, it is worth looking at the process before looking at the budget.

  • We live in Excel — and nobody trusts the numbers.
  • Our information sits in systems that do not talk to each other.
  • It is done by hand because it has always been done that way.
  • If one person is out for a week, nobody quite knows how it gets done.
  • Before a meeting, someone spends the morning gathering numbers from different places.

How we work

Five phases, in an order that is not skipped

Observe, measure, assess, fix, follow up. None of them starts by choosing software.

What comes out at the end is called a Process Map: a report that says how the work happens today, where it gets lost and where to start.

Every number says where it comes from

The starting measurement is fixed before any work begins. In the Map, every number carries its origin beside it, and what we do not yet know is written in an annex of open questions.

We do not promise numbers before we measure them.

At least one recommendation we do not carry out

We build software, so we tell you upfront: every Map carries at least one recommendation that brings us no work. It may be making better use of a tool you already pay for.

A map that always ends in “and now we build it” is a quote with a cover.

The four possible origins of a number in the Map

  • verified
  • estimated
  • set by management
  • to be confirmed

What we build when the Map recommends building

Software is not our way in. It is what we do after the Map, when building really is the answer — starting from the process that was observed and measured, not from a feature list.

What we build from a Map is quoted in writing, once the scope is defined, case by case.

We maintain open-source packages, listed at /packages.

Thirty minutes to see if it makes sense.

Online, no strings attached. We talk about the process that bothers you. If it makes sense to go on, we agree the scope and the quote comes in writing.

Book thirty minutes to talk

Quote in writing, once the scope is defined.

Email: geral@digitaldev.pt
Phone: +351 961 546 227