Article · Software DevelopmentEditor's pick

What Our First 90 Days With a New Client Actually Look Like

Founders ask us this in a roundabout way almost every time — not "what's your onboarding process," but something closer to "what actually happens after I say yes." Fair question.

Jay SomeoneJay Someone
Aug 5, 2026 · 4 min read
What Our First 90 Days With a New Client Actually Look Like

Signing on with an agency is a bit of a leap of faith, and most agencies don't say much about what the first few months look like beyond "we'll be in touch."

So here's the actual shape of it, in three stretches of roughly a month each.

Days 1–30: we spend more time asking than building

This is the part people are sometimes impatient with, and we understand why — you've decided to build something, and the instinct is to want to see it happening immediately. But the first month is mostly discovery, and skipping it is exactly how projects end up rebuilt six months later because nobody asked the right question early.

We're figuring out what the product actually needs to do, not what it should look like — those get confused constantly, and untangling them early saves everyone from arguing about button colors when the real disagreement is about a workflow. We're also figuring out how you make decisions: who signs off on what, how fast you like to move, whether you want to be looped into every small choice or only the ones that matter. That last part sounds minor. It isn't. Half of what makes a project feel smooth or painful comes down to whether we've correctly mapped how you want to communicate before we're three sprints deep and guessing.

By the end of month one, you should have a scoped plan, a rough timeline, and a specific understanding of what the first working version is actually meant to prove — not just "the app," but the thing inside the app we're testing first.

Days 31–60: the first sprint, and the first real friction

This is where building actually starts, and it's also, honestly, where the relationship gets tested a little. The plan from month one meets reality, and reality usually disagrees with the plan in at least one place — a feature turns out more complicated than it looked on paper, or a piece of feedback surfaces that changes what "done" means for a screen we thought was settled.

That friction isn't a bad sign. It's normal, and what matters is how it gets handled. We'd rather tell you in week five that something's going to take longer than originally scoped than quietly absorb it and let the timeline slip without explanation. You'll get a working piece of the product by the end of this stretch — not a mockup, something you can actually click through — and you'll also get our first honest read on whether the original scope needs adjusting.

This is usually the point where clients either relax into the process or start second-guessing it. The ones who relax are almost always the ones we were straight with early, even when the news wasn't great.

Days 61–90: the pattern sets

By month three, something important has usually happened without anyone announcing it: we've stopped treating each other like strangers being careful. You know how we communicate. We know how you make decisions. The team building your product has probably answered a question directly from you a few times by now, without it routing through three layers first.

This is also when we do a real retro — not a formality, an actual look at what worked, what didn't, and what we'd change going into the next stretch. If the original scope needs to shift based on what we've learned in the first two sprints, this is where that conversation happens, out loud, rather than getting silently absorbed into scope creep neither of us named.

By day 90, you should have a working core of the product, a team that knows your business well enough to stop asking basic questions, and a clear sense of what the next 90 days looks like. If any of those three things is missing at this point, something in the relationship needs fixing before the build continues.

Why we lay it out this bluntly

Most of what goes wrong in the first three months of a client relationship isn't a skill problem. It's an expectations problem — someone assumed month one would be building, or assumed the first sprint would be perfect, or assumed friction meant the team was struggling instead of just doing the job honestly. Telling you what actually happens, including the part where things don't go exactly to plan, is cheaper for both of us than letting you find out the hard way.

Ninety days in, you'll know exactly what kind of team you hired. We'd rather you know that by design than by accident.


Curious what your first 90 days would actually look like? Start a project or book a free 30-minute strategy call and we'll walk you through it before you commit to anything.
Image by Petra

#Onboarding#Process#Client Relationship

Was this article helpful?

More articles like this