The First Three Months Make or Break the Project
You’ve signed the contract. Now what? If you’ve never worked with a development agency before, the first 90 days can feel opaque. What’s happening behind the scenes? When should you see something? How involved do you need to be?
Here’s a realistic walkthrough of what to expect, when to contribute, and when to worry.
Weeks 1-4: Discovery and Alignment
This is the most important phase. It’s also the one clients most want to rush through. Don’t.
Your agency will run workshops to understand your business, your users, your workflows, and your pain points. They’ll interview stakeholders, map existing processes, and ask questions that feel obvious but have answers that aren’t.
Your role: be available. Block time for workshops. Be honest about what’s broken and what’s working. The faster you provide context, the faster discovery produces results.
What you should see by week 4: a requirements document, a technical architecture proposal, wireframes or prototypes, and a project timeline with milestones.
Red flag: if four weeks pass and you haven’t seen any of these deliverables, ask why.
Weeks 5-8: Building Begins
Development starts. Your agency works in 2-week sprints, each ending with a demo of working software. Not slides. Not mockups. Actual software you can click through.
Your role shifts from “define the problem” to “validate the solution.” Attend sprint demos. Give feedback immediately. Questions you take a week to answer cost the team three.
What you should see: working features, even if rough around the edges. A login screen, a basic workflow, data flowing from point A to point B. Ugly is fine. Broken is not.
Red flag: the agency goes quiet for three weeks and then shows you a polished demo. That means they weren’t building iteratively. They were building in a black box.
Weeks 9-12: First Usable Version
By week 9, you should have something testable. Not launch-ready. Testable.
Put it in front of real users (even just 3-5 colleagues). Watch them use it. Where do they get confused? What’s missing? What did you assume was obvious but wasn’t?
This feedback loop is gold. The best development teams incorporate it quickly. They’ll adjust, refine, and ship a noticeably better version within a sprint.
Your role: champion internal testing. Collect feedback systematically. Prioritize what needs to change before launch versus what can wait for version 2.
What you should see by week 12: a feature-complete first version, preliminary testing results, and a clear path to launch.
Communication Patterns That Work
The agencies that deliver consistently share a communication pattern.
Weekly status emails or messages. Not lengthy reports. A short update: what was done, what’s in progress, what’s blocked, and what needs your input.
Biweekly sprint demos. Live walkthroughs of new features with time for questions and feedback.
A shared project board (Linear, Jira, Asana). You should be able to see what’s being worked on at any time without asking.
An escalation process. When something goes wrong (it will), how is it communicated? A good agency tells you about problems early, not after they’ve become crises.
When to Worry
Not every bump is a crisis. Software development is messy. Bugs happen. Scope evolves. Timelines shift by days or weeks.
But some patterns warrant serious concern.
Radio silence. If your agency doesn’t communicate for more than a week without explanation, something is wrong. Good teams communicate especially when things are hard.
No working software after 6 weeks. If you haven’t seen a demo of functioning software by sprint 3, the project is in trouble.
Scope surprises. “We didn’t realize this would be so complex” is acceptable once, in good faith. If every sprint brings a new surprise, requirements weren’t properly defined.
Rotating team members. If a different developer attends every meeting, your project isn’t getting dedicated attention.
What Good Looks Like at Day 90
By day 90, a well-run project has produced a testable first version that handles the core workflow, a shared understanding of what’s in version 1 and what’s in version 2, a realistic launch timeline (typically 2-6 weeks from here), and a documented maintenance plan.
You should feel informed, not anxious. If you’re regularly surprised by what the team is doing, communication has broken down.
For help choosing the right partner, read how to evaluate a software development partner. And for the full development lifecycle, see our complete guide to custom software development.
About to start a project with a dev agency? Let’s set you up for success. We’ll walk you through our process, timeline expectations, and exactly what you’ll see at each milestone.
