<Let's Talk/>
Company 5 min read

The client who became a long-term partner — and what we learned from that

Most client relationships end when the project does. One did not. Three years, four products, and a friendship we did not expect to build through a Notion doc.

How it started

The first brief was modest. A redesign for a B2B SaaS product — mainly the onboarding flow and dashboard. Six weeks, fixed scope, clear handoff. We did not think much beyond that. Most projects end when the invoice is paid.

But at the end of that engagement, the founder sent a message that surprised us: "Can we keep a monthly retainer? Not for a specific project. Just so you are there when things come up." That was not something we had offered before. We said yes.

Two people collaborating at a desk with notebooks and a laptop
The first retainer call. No brief, just a conversation.
Whiteboard covered in sticky notes during a product strategy session
By month four, we were shaping briefs, not just executing them.

Retainers are not about money. They are about trust accumulated faster than a one-off project allows.

What changed over time

By month four, we were not executing briefs anymore. We were in the room — or on the call — when the briefs were being formed. The founder would share a half-baked idea on a Tuesday and we would push back, reshape it, and have a rough proposal back by Thursday. The line between vendor and partner had moved.

Four products over three years. Two product pivots, one rebrand, and one failed feature we killed together before it shipped. The failed feature was the moment we knew the relationship had changed — because the founder trusted our "do not build this" more than the pressure to ship.

01
Product 1: Onboarding redesign

The original brief. Six weeks, scope-locked. Activation rate improved from 34% to 61% in the first month after launch.

02
Product 2: Mobile companion app

Proposed during a retainer call. Built in eight weeks. The first version shipped rough — we fixed it together in sprint two.

03
Product 3: Analytics module

The one we nearly killed. Built it anyway. Taught us the difference between "good idea" and "right time for this user base."

04
Product 4: Full rebrand + redesign

Eighteen months in. By then we knew the product better than most people on the founding team. That knowledge is not something you can buy in a brief.

What this taught us

We now structure every new engagement with a quiet goal: to make ourselves useful enough that the client wants to keep talking after the final delivery. Not by making ourselves dependent — but by genuinely understanding their product well enough to have something useful to say when they come back.

The best working relationships are not transactional. They are cumulative. Every project adds context, every conversation adds trust, and after a while you are not a vendor anymore. You are someone they call before they have a brief, not after.

The goal of every project is a second project. Not because we need the revenue — but because it means the first one worked.

Next post
Company

Our work ended up on a Times Square billboard — and I was not even there