Automating the steps that depend on someone remembering

Many processes don't fail for lack of software, but because a step depends on someone remembering to send a message, copy a value or tell another team. We automate those steps from the data you already capture, and keep a visible record of what fired and when.

When it makes sense

  • Someone spends hours a week copying data from one system to another.
  • Customers find out late because the update depends on one person.
  • Reminders are kept in a notebook or in someone's head.
  • The same WhatsApp message is typed dozens of times a day.
  • When that person goes on holiday, the process stops.

What we build

Event notifications
Email, WhatsApp or push when something changes state, with no manual step.
Scheduled reminders
Appointments, due dates, doses or payments that remind the right person on their own.
Data hand-offs
What comes in through a form reaches the right system without being re-entered.
Automatic reports
The daily or weekly summary that's assembled by hand today, sent on time.
Run log
A record of every automation run, so you know what happened when something breaks.

When not to build

Building isn't always the answer. If that's your case, we'll tell you before the proposal.

  • If the people doing the process can't describe it clearly, automating it only speeds up the mess.
  • If a tool like Zapier or n8n solves it without code, start there.

Related concepts

Studio concepts for fictional businesses. They show how we work; they aren't client projects.

How it starts

  1. 01What you needWhat the software must do and who will use it.
  2. 02What exists todayIf something is running, what it's built with and what stays.
  3. 03Scope and timingWhat goes into the first version and what can wait.
  4. 04Written proposalScope, deliverables and cost. No commitment.

What stays in your name

  • The code repository, in your account from the first commit.
  • The deployment and database, in your cloud accounts.
  • No proprietary platform or licence: if you work with another team tomorrow, they take everything.

Other services

Tell us which process doesn't fit the software you have.

Message on WhatsAppcontacto@liffeylabs.comA message with your project's name and what it needs to do. Reply within 24 h.
  • Repository in your name
  • Deployed to your accounts
  • No proprietary platform