“How many months?” is the wrong first question. Ask which workflow must go live, which roles, whether legacy data moves, and which systems integrate. Plan by stages.
Define phase-1 must-haves
- Which roles cannot work without the system?
- Which process stops the business if broken?
- Which reports can wait for phase 2?
Education example: training admin system case. Service: web admin system development.
Typical stages
- Discovery & prototype (days to weeks)
- Core modules (weeks+)
- Integration & data import (often underestimated)
- Training, pilot, go-live
- Ops iteration — software maintenance services
What stretches the calendar
- Unbounded mid-build changes — requirement change control
- Dirty legacy data
- Missing API docs
- Unclear acceptance — custom software contract tips
Keep timelines honest
- Sign off prototype before the build plan
- Tie payments to demos
- Ship the critical path first
- List integration risks separately
FAQ
Months for a mid-size admin?
Often weeks to a few months when phase 1 is sharp; “everything in v1” takes longer.
Can we change while using it?
Yes, with a change process — otherwise the schedule becomes fiction.
Build app in parallel?
Risky if admin is unstable. Stabilize web first, then mobile (custom app development).
Takeaway
Separate must-ship from nice-to-have. Share your industry and main workflow for a staged plan.
contact for software projects