People ask this before they ask about price, and the honest answer is a range, not a number: a real SaaS dashboard — the kind with authentication, a data table, filters, and at least one chart or timeline view — typically takes four to eight weeks from a fixed scope to a shippable v1. Anything quoted faster is either much smaller than it sounds, or cutting a corner nobody's told you about yet.
What actually takes the time
Three things move the timeline more than anything else: how many distinct states a screen needs (empty, loading, error, populated — most quotes only account for one); whether the data model is settled before design starts, or gets figured out alongside it; and how many roles or permission levels the dashboard needs to support.
A single-role admin panel with one table view can genuinely ship in two to three weeks. The same dashboard with a customer-facing role, an admin role, and different data visibility for each is a different project, even though it looks similar in a mockup.
Why "fixed timeline" only works with fixed scope
The reason FirstRay prices in fixed packages rather than hourly is exactly this: a dashboard's timeline is set by its scope, not by how fast someone types. Once the screens, states, and roles are agreed on paper, the build timeline holds — which is also why our own packages state the scope in writing before a date goes on the calendar.
What to actually ask before you commit to a date
- How many distinct screens, not just "pages," does this need?
- What happens on this screen when there's no data yet, or when something fails?
- Does every user see the same version of this dashboard?
Answer those three honestly before anyone gives you a date, and the number you get back will actually hold.