How-To

What the first month of a project actually looks like

Most people who've worked with a software agency before have experienced the moment where the first sprint looks very different from what they'd imagined. The first month is real work — but it mostly isn't code.

Most people who've worked with a software agency before have experienced the moment where the first sprint of work looks very different from what they'd imagined would be happening. It can feel like things aren't moving fast enough, or that weeks have passed and there's not much to show yet.

It's one of the things we try to be upfront about: the first month of a project is real work, but it mostly isn't code.

It starts with what we call a discovery phase — a few weeks of structured conversation and documentation that's designed to answer one question before anything else: are we solving the right problem in the right way?

This means going through the workflows that currently exist (even the informal, spreadsheet-based ones), understanding who uses what and when, mapping out the integrations that will be needed, and pressure-testing the assumptions that came in with the brief.

The output at the end of this phase isn't a product. It's a document — a specification that all of us, including the client, have signed off on. It describes what we're building, what's out of scope, how we'll know it's working, and what happens when edge cases occur.

That document does something important. It means that when a developer is writing a particular function three months in, they don't have to guess what the intended behaviour is. It's in the spec. When we're reviewing work in a sprint, we're checking it against something agreed — not against a half-remembered conversation from the kick-off call.

It also means that changes to scope are visible. If something comes up mid-project that wasn't in the spec, that's a conversation, not an assumption. We've found that clients who understand the spec process are usually much more confident through the build phase, because they know exactly what's been agreed and why.

The discovery phase takes time. For a complex project, it can be three to four weeks. That can feel frustrating when you want to see momentum. But it's the part of the project that, if done properly, makes everything else move faster.

Let's find where you're losing money

The discovery call is free. We'll talk about what's slowing your business down — whether that's outdated software, no visibility into your numbers, or too much manual work. Yuvati will give you an honest view of what would help, and whether we're the right fit to build it.

[email protected]
Please enter your name
Please enter a valid email address

Message sent

We'll be in touch within one business day.