Affordable array size from a budget

Reading a budget as capacity: what the money-first direction changes

The division treats money as a unit of capacity. At a given market rate, a budget simply IS a certain number of watts, and expressing it that way makes the budget commensurable with everything else in this cluster: the size the load demands, the size the roof permits and the size the money affords are three numbers in the same currency, and the smallest of the three wins.

Everything therefore hangs on the cost-per-watt figure, and that figure is local in every sense — it moves with the market, the country, the installer and the size of the job itself. The default here is illustrative only. A real budget deserves a real local quote, expressed turnkey and before incentives, because a subsidised or hardware-only rate quietly inflates what the money appears to buy.

The relation is a reciprocal, and reciprocals punish optimism asymmetrically. Halving the assumed cost per watt doubles the affordable array; the same error in the other direction only trims it. An optimistic rate therefore produces a paper array the quotes cannot match — which is why this page pairs naturally with the cost-per-watt page, where a real quotation is reduced to the very rate assumed here.

The pack also declares the reverse direction: fix a target size — the one the load page demanded, say — and the engine returns the budget it requires at the going rate. Run both ways, the page becomes a negotiation table: what the money buys, and what the wish costs.

When this calculation is used

• Opening a solar conversation from the only number many households actually start with: what they are prepared to spend.
• Setting expectations before quotations arrive, so a proposal can be judged against what the local rate says the money should buy.
• Reconciling the three constraints — comparing the affordable size against the load-demanded and roof-permitted sizes from this cluster’s sibling pages.
• Running the declared reverse workflow to price a target: the budget a chosen array size requires at the local cost per watt.

Worked example

Take the pack’s own anchor: a budget of six thousand dollars — the installed cost the cluster’s payback arithmetic also uses — at the illustrative default rate of ninety cents per installed watt.

What returns is the array size that budget affords at that rate, in kilowatts-peak. Set it beside the size the daily-load page demanded and the size the roof check permitted: if the affordable size is the smallest of the three, the budget is the binding constraint and the design conversation becomes one about phasing, financing or a sharper quote. It is a screening size at an assumed rate — the quotes themselves, not this division, set the real price.

The figure is computed by the verified engine at load, and the scenario is one of the signed pack’s declared test vectors. Because the rate sits in the denominator, the affordable size moves inversely with it — a cheaper market stretches the same money into a larger array, which is exactly the sensitivity the declared vectors exercise at several different rates.

What each input represents

Assumptions and limits

• One flat cost per watt covers the whole system, although real pricing steps with system size and the fixed costs of a small job fall harder per watt.
• The budget buys capacity only: batteries, monitoring, structural work and future maintenance sit outside this division.
• The rate and the budget are on the same incentive basis; mixing a post-incentive rate with a pre-incentive budget flatters the answer.
• Affordability is not viability — whether the affordable array fits the roof, meets the load or pays back is what the sibling pages decide.

What the guards protect against

• A zero cost per watt is refused, and the pack declares that refusal as a test vector — free installation would make every budget buy an infinite array, and the engine declines the division rather than reporting one.
• The rate is bounded to a plausible market band, from a fraction of a dollar to a few dollars per watt; a per-kilowatt price or a whole-system price typed into the rate field lands far outside it and is refused as a unit slip.
• The budget must be positive and sits under a very high ceiling — zero money buys no array, and a figure beyond the cap suggests a currency or magnitude error rather than a real project.

Provenance

Algebraic rearrangement of the standard cost-per-watt pricing metric, affordable size = budget ÷ installed cost per watt expressed at array scale

Division of the available budget by the installed cost per watt, converted to array scale, returning the affordable nameplate size in kilowatts-peak; the declared reverse workflow solves the same relation for the budget a target size requires.

Screening and reference material, to be checked against real quotations and a qualified installer or engineer; not a design determination and not financial advice. The signed pack carries its own citation, and the page reports the verification state of the release it mounted.