Skip to content

Your company runs because someone is copying data from one place to another. That is fixable.

We study how your company actually works, procedure by procedure, and build the software that does that work without anyone having to remember to do it.

Your peopleTrelew LabsAccountingBankWarehouseEmailSpreadsheetAccountant

Today

With Trelew Labs

  • Accounting
  • Bank
  • Warehouse
  • Email
  • Spreadsheet
  • Accountant

Operational mess has a shape, and it is almost always the same one.

An accounting package that does not quite cover your case. An external accountant who sends files back. The bank on one side and the warehouse on the other. And in the middle, a spreadsheet one person maintains by hand that nobody else can read.

None of it is broken. It simply does not talk to itself, and the glue is people.

We do not replace what already works. We build the line the data travels on, so it is entered once and shows up wherever it is needed.

A supplier invoice, today.

TodayArrives by emailGets printedby handGets keyed intoaccountingby handGets filed in afolderby handGets hunted forat month-endby handWith a systemArrives by emailReads itselfProposes theentryA person confirmsa person decides

Today

  1. Arrives by email
  2. Gets printed by hand
  3. Gets keyed into accounting by hand
  4. Gets filed in a folder by hand
  5. Gets hunted for at month-end by hand

With a system

  1. Arrives by email
  2. Reads itself
  3. Proposes the entry
  4. A person confirms a person decides
A generic example, not any particular company’s. Your real path comes out of the audit.

Put your own numbers in.

We are not going to tell you what you would save, because we do not know your company yet. Type your figures and see it.

1,320 hours a year

€29,040 a year

That is what it costs today to get the data in by hand. Not everything can be automated, but almost none of this has to stay human.

Based on 220 working days a year. The calculation happens in your browser: nothing you type here is sent or stored.

Six things we do.

None of them starts with technology. All of them start by watching how your people work.

Four stations, in this order.

The most expensive mistake in a software project is starting to build before understanding what is done today. We spend the entire first stage looking.

  1. KM 01

    Process audit

    One to three weeks

    We sit down with the people who do the work, not with the org chart. We document it task by task: what comes in, who touches it, how many times the same thing gets typed, where it breaks, and what happens when the person who knows how to do it is away.

  2. KM 02

    Automation design

    One to two weeks

    We decide what disappears, what gets fully automated, what gets half automated, and what has to stay human because someone must answer for it. You see how the system will work before it is built.

  3. KM 03

    Build

    In stages, delivering every two or three weeks

    We build in useful pieces: the first thing we hand over is already in use in your company. No disappearing for six months and coming back with a whole system nobody has tried and that has to be redone.

  4. KM 04

    Operation and improvement

    For as long as the system is alive

    We maintain it, measure it and extend it. When the law changes, when the business changes, or when a new repetitive task appears, the system absorbs it instead of spawning another spreadsheet.

Timeframes are indicative: they depend on the size of your operation and on how many people we can sit down with. Yours is fixed in writing in the proposal.

Why Trelew.

In 1865 a group of Welsh settlers landed on an empty stretch of Patagonian coast. The valley they found, the Chubut river valley, was fertile and completely cut off: whatever it produced reached nobody.

They built the canals that carried the river water to the land, and then the railway that carried what the land gave down to the sea. The station on that line was founded in 1886 and named Trelew: in Welsh, “tre” means town and “Lew” is Lewis, after Lewis Jones, the man who pushed that railway through.

The town of Lewis. They did not invent the valley and they did not invent the sea. They built what connected them.

Let us start by looking at how you work today.

The first conversation is about understanding your operation, not about selling you a project. If what you need is not worth automating, we will say so.