Month One With a Development Agency: What Should Actually Happen
You have signed. The kickoff call is booked. Four weeks from now you will either have a product taking shape or a folder of documents and a vague feeling that not much happened.
Month one sets the entire trajectory of a build, and it is the period clients have the least visibility into. Here is what should actually be happening, week by week, and the specific artefact you should be able to point at each Friday. If you have not sent your brief yet, start with how to brief an app development agency — everything below assumes that document exists.
1. Week One — Alignment and Access
Week one is not “getting to know each other.” It is a controlled information transfer, and it should feel slightly intense.
An assumptions log. A plain list of everything the team currently believes to be true and has not verified. If your agency cannot produce one by Friday of week one, they are not thinking about risk — and every unverified assumption is a candidate for a change request in week six.
The most common week-one failure is on your side, not theirs: access takes eight days instead of two. Chase credentials before kickoff, not after. Idle senior engineers still bill.
2. Week Two — Narrowing
Week two is where a good team starts telling you no. The feature list gets cut, the architecture gets a decision attached, and the first real estimate replaces the sales estimate.
3. Week Three — First Working Software
This is the week that separates agencies. By the end of week three there should be something running that you can open in a browser or on a device — deployed, not on someone’s laptop.
It will be ugly and it will do almost nothing. That is correct. The point is that the pipeline is real: a commit goes to a repo, CI runs, a build lands in a staging environment you can reach. Teams that defer this until “when there’s something to show” routinely discover deployment problems in the final week, which is the most expensive possible time to find them.
4. Week Four — Rhythm and the Honest Conversation
By week four the project should have a heartbeat: a fixed demo slot, a visible board, a change-request process that has been used at least once. The delivery cadence matters more than the delivery speed — predictable teams let you plan around them.
Week four is also when a good agency has the uncomfortable conversation. They have now seen your codebase, your stakeholders and your constraints, and they know something the proposal did not. Maybe the timeline needs another three weeks. Maybe a feature you love is technically disproportionate. Hearing it in week four is a gift; hearing it in week eleven is a crisis.
5. The Month-One Scorecard
Print this. At the end of week four you should be able to tick every line.
If you are still weighing whether to run this in-house instead, our honest comparison of in-house teams and agencies covers the trade-offs — and if you are arriving with a prototype that is nearly there, the MVP gap describes the month-one that situation actually needs.
Month one should produce software.
Tell us what you are building and we will show you exactly what your first four weeks would look like — deliverable by deliverable, with the uncomfortable conversation scheduled up front.