Insight · Project Development
Costing versus feasibility
Feasibility asks whether the site, grid, building or use case can support the project. Costing asks what it would cost to deliver a defined scope. They are sequential more often than they are interchangeable.
WattFund Editorial Team · Published 17 Sept 2026 · 4 min read
Feasibility
Early technical and commercial testing: roof or land, connection, heat demand, power for chargers, planning constraints. The output is whether the idea holds, and what would have to be true. It is not an install price.
Costing
A delivery estimate from people who can do the work, based on a stated scope. WattFund does not generate that price. A costing can still carry exclusions and validity dates.
When you need which
If the technical questions are open, feasibility or a design envelope comes first. If the idea is clear enough to brief, costing is the useful next step. High-level budgets can sit in between if they are labelled as budgets.
Which request to make
| Situation | Usual request |
|---|---|
| Site idea, constraints unknown | Feasibility or review |
| Building heat demand not modelled | System assessment, then costing |
| Design envelope exists | Delivery costing / quotation |
| Quote exists, capital does not | Funding review — not another feasibility |
Funding sits after the right one
Construction capital needs a costing it can point at. Development support may fund feasibility. Asking investors to price an untested idea, or asking an EPC to “feasibility” a number, wastes both.
Questions
RELATED GUIDES
RELATED INSIGHTS
EXPLORE THIS TECHNOLOGY
SIMILAR PROJECT EXAMPLES