Scope the outcome before asking for a number.
“Build a portal” can mean a file-sharing page or a permissioned workspace connected to several internal systems. Those are different projects. A credible estimate identifies the users, their tasks, the records involved and the definition of a useful first release.
We do not publish a universal price range because it would hide the variables that matter. A smaller release is valuable only if it completes a real task, including errors and handoffs.
The cost drivers that deserve attention.
The visible interface is only one part of delivery. Complex integrations or historical data can cost more effort than a large number of straightforward screens.
| Driver | Questions to answer |
|---|---|
| Workflow complexity | How many roles, states, exceptions and approvals are involved? |
| Integrations | Are supported APIs available? Who owns the records? |
| Data migration | What must move, how clean is it and how will it reconcile? |
| Access and security | Which people can see and change which information? |
| Reliability | What happens when a vendor or background task fails? |
| Adoption | Who tests, trains, supports and owns the change? |
Separate initial delivery from ongoing operation.
Initial work can include discovery, design, implementation, testing, migration and rollout. Ongoing operation can include hosting, email, storage, AI usage, vendor licenses, monitoring and support.
Ask for those categories separately. Usage-based costs need an expected volume and a range, not just a rate per API call. Support should say what is covered and how changes are handled. Source-code ownership does not eliminate service costs.
Reduce uncertainty before reducing quality.
A short investigation of the riskiest integration can make an estimate much more useful. Representative data can reveal cleanup work. Testing a prototype can prevent investment in the wrong workflow.
Cut scope by reducing the number of supported tasks or rollout groups. Do not quietly remove access controls, error handling or the ability to recover just to make an estimate look smaller.
What to bring to an estimating conversation.
A current workflow walkthrough is more useful than a long list of fashionable features. You do not need to solve the technical design first.
- Users, roles and the first task to support
- Current tools and available integration information
- A few redacted examples, including an exception
- Data that needs to migrate
- Who will operate the system and what success means
