You've signed the contract. Development is starting. Now what?
The first month sets the tone for everything that follows. Here's what a healthy project looks like in those early weeks.
Week 1: Discovery Deep Dive
This week is about understanding, not building.
What happens:
- Stakeholder interviews
- Process documentation
- Requirements clarification
- Technical environment assessment
Your role:
- Be available for questions
- Provide access to systems and documentation
- Introduce the team to key people
- Don't expect code yet
Warning sign: If they start coding on day one, they're skipping crucial understanding.
Week 2: Design and Planning
Translation of business needs into technical approach.
What happens:
- Wireframes or mockups for key screens
- Technical architecture decisions
- Development environment setup
- Sprint planning
Your role:
- Review and provide feedback on designs
- Approve the technical approach (or ask questions until you understand it)
- Make decisions when asked — delays here compound
Deliverables: You should see something visual by end of week 2.
Week 3: First Code
Development begins, but don't expect magic.
What happens:
- Core infrastructure setup
- First features in development
- Initial database design
- Authentication and basic framework
Your role:
- Stay engaged but don't hover
- Respond to questions promptly
- Start thinking about testing resources
What you'll see: Probably a working login screen and some basic navigation. Not impressive yet — that's normal.
Week 4: First Demo
Time to see something real.
What happens:
- End-to-end flow of at least one core feature
- First sprint review/demo
- Feedback incorporation planning
- Next sprint planning
Your role:
- Actually use what they built (not just watch)
- Provide specific, actionable feedback
- Prioritize feedback — what matters most?
Key question: "Does this feel like it's heading in the right direction?"
What Good Communication Looks Like
By end of month one, you should have established:
- Regular updates: You know what's happening without asking
- Predictable demos: Weekly or bi-weekly, on schedule
- Quick responses: Questions don't sit for days
- Clear escalation: You know who to contact for what
If you're constantly wondering "what are they doing?", something's wrong.
Normal Frustrations (Not Red Flags)
- "It doesn't look finished yet" → Correct, it's week 4
- "They keep asking questions" → Good, that means they're being thorough
- "The demo had bugs" → Normal for early development
- "We had to change something from the original plan" → Learning is working
Actual Red Flags
🚩 No demo by end of month one 🚩 They've stopped asking questions (they're guessing) 🚩 Major technical decisions made without consulting you 🚩 Scope creep already happening 🚩 Communication has degraded from week one
Your Checklist for Month One
End of month one, you should be able to say:
- [ ] I understand the development process
- [ ] I've seen working software (even if basic)
- [ ] I know who to contact for what
- [ ] I've received regular updates
- [ ] My questions get answered promptly
- [ ] I trust the direction we're heading
If you can't check these boxes, address it now. It doesn't get easier later.
Starting a project with us? Here's exactly what to expect. Get in touch