Skip to content
lube

Why we built this

Our story

The people told to keep up with users were never given a way to.

The company would not pay for another seat. So the people asked to stay close to customers never actually could. That is the problem we started with.

What went wrong

A seat you cannot buy is a story you cannot read.

Customer feedback sits in one tool. Pull requests and deploys sit in another. Uptime, tests, and AI spend each get their own tab and their own bill. Every tool sells seats. So the person who most needs to read the work is the first person cut from the licence.

Then someone asks “did that ship?” and the answer is “let me find out and get back to you.” That sentence is the whole problem. We built lube to delete it.

How we work

Three rules we hold ourselves to.

01

Everyone who needs to see the work can see the work.

02

Build each tool from the ground up. Connect the systems of record you keep.

03

Say what the product does. Say what it does not do.

Where we are

Early, and building in the open.

We are a small team. The product is real and you can use it today. We have plans that reach further than what is built, and we keep those two things clearly apart.

Start with one workflow

Create a workspace. Connect one thing.