What Does a Climate Data Dashboard Cost to Build?

The chart is the cheapest part of a climate data dashboard. The price is set by what sits behind it: how many sources feed it, how messy they are, how often they change and who is allowed to see the result. Depending on the question behind it, a climate dashboard can cost nothing with FEMA's National Risk Index, which rates 18 natural hazards for every U.S. county and census tract, $14 a user a month in Power BI Pro, or $4,000 to $12,000 a month on Microsoft's Sustainability Manager.

At CF Labs' published prices, a working prototype on one data source costs $12,500 and takes two to three weeks. A production dashboard starts from a base of $18,000 to $45,000 over four to eight weeks, then rises with more sources, a public audience, integrations and add-ons such as maps. Running it adds a bill every year.

That yearly bill deserves its own line in the budget. U.S. federal agencies report spending about 80% of their IT budgets on operating and maintaining systems they already have. For a small dashboard, a $20-a-month application host and a $25-a-month managed database cover the hosting; the hours someone spends keeping the data current cost several times as much.

CF Labs is Council Fire's software studio, and Council Fire has been a certified B Corp since 2010. We publish our prices along with a project estimator that shows how each range is built, and this guide walks through that arithmetic so you can treat one studio's published pricing as a yardstick for any quote, ours included. We build these tools for clients and for ourselves, and the hard part is usually the data. Our communications work starts from the same place: the iMPAct Report series for the Maryland Port Administration and Maryland Environmental Service began as existing but disparate data points from five jurisdictions.

How does one studio price a climate data dashboard?

CF Labs prices a climate data dashboard as two pieces of work: the view your board, staff or residents read, and the pipeline that keeps it current. The estimator starts from a base range for the kind of build, multiplies it for scope, adds fixed ranges for extras and rounds the result. What comes back is a planning range; the scope and a fixed price are settled on a 20-minute call.

The base then moves with four answers and up to four add-ons:

The multipliers compound. A public dashboard fed by four or more sources and complex systems, needed within six weeks, carries about 2.3 times the base before any add-on, and with every box ticked the estimator tops out at $65,000 to $159,000. Totals of $20,000 or more round to the nearest $1,000, and smaller ones to the nearest $500. The schedule stretches with the square root of the combined multiplier, plus 8% of the base timeline for each add-on.

Worked example: a county's public flood-risk dashboard

A county resilience office wants one public page showing flood and storm risk by neighborhood, alongside the projects funded to reduce it. It draws on three sources: FEMA's National Risk Index, the county's asset inventory and its capital plan, the last two kept in spreadsheets. It needs a map and data that refreshes on a schedule, and it should launch this quarter.

• Base: $18,000–$45,000 over four to eight weeks.
• Scope: two or three sources (×1.15), the public (×1.2) and a few spreadsheets (×1.1) multiply to ×1.518, giving $27,324–$68,310.
• Add-ons: maps and GIS ($6,000–$15,000) and data that updates on its own ($4,000–$10,000), giving $37,324–$93,310.
• Planning range: $37,000–$93,000 over six to 11 weeks.

The same dashboard for staff only comes to $33,000–$82,000, so the public audience adds $4,000 to $11,000. If a grant will pay for it, the estimator points first to the $4,500 Grant-Ready Tool Scope.

Worked example: a university's internal emissions dashboard

A university sustainability office wants Scope 1 and 2 emissions by building, with business travel and purchasing alongside, for leaders who review it monthly. That is four or more sources: utility bills, fleet fuel, travel and purchasing records, two of them held in enterprise systems with their own interfaces. Draft figures should stay with the sustainability team and facilities staff, so it needs sign-in and roles.

• Base: $18,000–$45,000 over four to eight weeks.
• Scope: four or more sources (×1.35), your team (×1.0) and complex systems (×1.3) multiply to ×1.755, giving $31,590–$78,975.
• Add-ons: sign-in and roles ($5,000–$10,000) and data that updates on its own ($4,000–$10,000), giving $40,590–$98,975.
• Planning range: $41,000–$99,000 over six to 12 weeks.

Both examples start the same way in the estimator: a $12,500 Tool Sprint that puts one source into a working prototype in two to three weeks. If the prototype earns its keep, the production build is scoped at a fixed price; if it does not, you have spent $12,500 and a few weeks finding out. Where a project lands inside its range depends on what the sources look like once someone opens them.

Who this is for: sustainability, resilience and program leads who need a defensible number for a budget request or a board memo. To compare quotes line by line, use the blank worksheet in our custom software budget brief; to define the first release before anyone prices it, write a one-workflow build brief.

What drives the cost up or down?

None of the estimator's questions is about the chart. The drivers below are what move the number.

How many sources, and how messy

Two or three sources multiply the base by 1.15 and four or more by 1.35, and each source brings its own definitions and its own update schedule. The count misses the mess.

When we joined FEMA's risk index to OpenFEMA's plan records for our Climate Risk Lookup, two datasets from the same agency disagreed about what to call a county. OpenFEMA's county names predate Connecticut's nine planning regions, which the Census Bureau adopted as county equivalents starting with 2022 data; its plan records file Baltimore City and Baltimore County under one county name; and Alaska's census areas carry school district names. FEMA itself describes the plan status data as raw and unedited, with possible human error or delayed entries. Problems like these decide whether a project lands at the low or the high end of its range.

Find out which sources can carry the dashboard before paying for the chart. Give every metric an owner and a definition, as our ESG data management guide recommends, or buy the check: CF Labs' Data & AI Readiness Review tests your sources in two weeks for $6,500. In our experience, most dashboard problems are data problems, and a chart only makes a disagreement look official.

How often the data changes

Data that updates on its own adds $4,000 to $10,000, and the right schedule is the slower of two clocks: how often the source changes and how often anyone decides anything. FEMA's advice for its own API is blunt: your refresh interval should not be more frequent than the dataset's.

Federal sources run on very different clocks. FEMA's risk index is a versioned release, December 2025 v1.20 at its last update; NOAA's high tide flooding outlook is issued once a year; OpenFEMA's plan statuses refresh daily; and USGS streamflow is typically recorded every 15 minutes. A board that meets quarterly gains nothing from a 15-minute feed, and paying to keep one running is over-buying. Decide what you will track first; our guide to measuring climate resilience progress honestly covers which indicators earn a place.

Who will see it

A public audience multiplies the base by 1.2, and partners by 1.1. Public numbers need things internal ones can skip: a review of which fields are safe to publish, and pages that hold up under traffic nobody can predict. Internal views can carry draft figures and working notes; a public view shows only what you have approved.

Accessibility

If your county, port or university is a public body, accessibility has a deadline. The Justice Department's ADA Title II rule requires web content, including content governments provide through contractors, to meet WCAG 2.1 Level AA from April 26, 2027 for governments serving 50,000 people or more, and from April 26, 2028 for smaller ones and special districts. The department's guidance lists public universities and transit agencies among the entities covered.

Most of the web still falls short. In WebAIM's 2026 scan of the top million home pages, 95.9% had detectable WCAG failures, with an average of 56.1 detected errors per page. Charts need text alternatives and a table view of the same numbers, colors need enough contrast, and maps and filters need to work from a keyboard. Build that in from the first sprint.

Sign-in, maps and AI

Sign-in and roles add $5,000 to $10,000, and the design question is who sees what: draft figures for staff, approved ones for the board. Running sign-in costs little; Supabase's published plans include 50,000 monthly active users free and 100,000 on Pro. A page everyone may see needs none of it.

Maps and GIS add $6,000 to $15,000, and connecting to an existing GIS counts among the complex integrations (×1.3). Serving web maps can be cheap: Mapbox's published pricing includes 50,000 web map loads a month free, then $5 per 1,000. If you already license ArcGIS, look before you buy, because Esri lists ArcGIS Dashboards among the apps included with every ArcGIS Online user type. Our guides to cloud platforms for spatial disaster data and vulnerability and equity maps for government cover which layers earn their place.

AI features add $8,000 to $20,000. Hold them to the standard of any other source of numbers, with a named reviewer and a trail back to the data, as our AI reporting pilot checklist sets out.

Who this is for: whoever writes the scope. Every source, schedule, login or map layer you can drop comes off the estimate.

What does a dashboard cost to run each year?

Plan for two lines: infrastructure, which is small and published, and upkeep, which is larger and depends on your sources. For a small dashboard on a common modern stack, published prices look like this:

The hourly figure is the BLS median wage for software developers, quality assurance analysts and testers, $64.44 in May 2025, before benefits. The upkeep hours are illustrations: each hour a month adds about $770 a year, so list each source with its schedule and the person who checks it, then multiply. The free tiers will not carry a production dashboard, because Vercel's Hobby plan is for personal, non-commercial use and Supabase pauses free projects after a week of inactivity.

Custom builds also carry tail risk. In a peer-reviewed analysis of 5,392 IT projects, cost overruns followed a power law: most were small, a few extreme. Scope small, ship early and price the second year before you sign the first.

Free data has a maintenance cost of its own, because sources change under you. NOAA retired its billion-dollar disasters product with no updates beyond 2024. EPA's GHG Emission Factors Hub, an annual release, still listed its January 2025 edition as the latest when we checked in October 2026. We learned it ourselves when a third-party widget service behind the free tools on our site stopped loading, and we rebuilt the few worth keeping on our own code.

Who this is for: finance and budget staff, and anyone whose dashboard will outlive the person who commissioned it. Ask every bidder, us included, for the second-year cost in writing.

Should you build a dashboard or subscribe to one?

For an internal dashboard a staff analyst can build, a subscription usually costs less, and we would tell you so. Power BI Pro is $14 a user a month and is included in Microsoft 365 E5, so 25 seats come to $4,200 a year. Tableau's Standard edition charges $75 per Creator, $42 per Explorer and $15 per Viewer a month, billed annually. Google's Data Studio, formerly Looker Studio, is free for creators and viewers, with a Pro tier at $9 per user per project a month.

The subscription replaces hosting; it does not replace upkeep. Someone still models the data and explains to the board why a number moved.

Per-seat pricing stops fitting when the audience is the public. Power BI needs a capacity of F64 or larger before people without a paid per-user license can view content, and its Publish to web option, which needs no viewer licenses, lets anyone on the internet reach the underlying data, including detail the report does not display. Everything published to Tableau Public is freely accessible to anyone, and Tableau Cloud's broad-viewer option is capacity pricing by quote.

Sustainability platforms are a different purchase: calculation engines and audit trails, with a dashboard on top. Where the vendor publishes a price, it is below; where it does not, we say so.

• Microsoft Sustainability Manager: $4,000 a month for Essentials and $12,000 for Premium, per tenant, and some features need other Microsoft licenses.
• Salesforce Net Zero Cloud: "Contact us for pricing" on every edition.
• Watershed: no published prices; the site offers a demo.
• Persefoni: the Pro tier is free; the Advanced tier is priced on request.
• Esri ArcGIS Online: sold through annual user-type licenses with no prices on its buy page.

If you report under a standard such as California's SB 253, buy the calculation engine and build only the view your board needs on top. Our guide to building or buying sustainability software explains where that line sits, and our GHG Protocol guide covers the accounting. Local governments managing a portfolio of projects should read build or buy climate resilience planning tools.

Who this is for: teams with a BI license and an analyst who can use it, and teams weighing a platform contract. Run the arithmetic over three years: seats times price, plus staff hours to build and maintain, against a build price plus its run cost. For the wider decision, see how to choose sustainability software.

Which free data sources cut the cost?

Federal data can carry much of a climate risk dashboard at no license cost. These are the sources we reach for first, and each should be treated as a versioned input you can swap:

• FEMA National Risk Index: 18 natural hazards for every U.S. county and census tract, currently the December 2025 v1.20 release, as tables, shapefiles or geodatabases. Our Climate Risk Lookup and Maryland climate risk profiles are built on it.
• OpenFEMA: an API that is free and needs no subscription or API key, with datasets such as hazard mitigation plan statuses.
• NOAA: water level stations and the annual high tide flooding outlook, which predicts a record national median of 7 to 12 high tide flood days from May 2026 to April 2027, and a national average of 55 to 85 a year by 2050.
• USGS: real-time streamflow, typically recorded every 15 minutes, for dashboards that support flood operations.
• EPA: the GHG Emission Factors Hub for default emission factors, and eGRID, whose latest edition covers 2023 power-sector emissions and emission rates, for location-based Scope 2 estimates.
• Census Bureau: the geography everything else joins to, with relationship files that bridge changes such as Connecticut's.

Free data removes the license fee and leaves the upkeep. Someone still records which release each figure rests on and notices when a product changes or ends, which is why our Climate Risk Lookup names the FEMA release it reads.

Who this is for: local governments, ports and nonprofits whose question is about hazards and exposure. If your question is emissions, EPA's factors help, but your own activity data carries the inventory; our community greenhouse gas inventory RFP guide covers what to collect.

Can a grant pay for a climate data dashboard?

Often, for the build. Many grants that fund planning, data or capacity can cover a digital tool, depending on the program, and your grant manager confirms eligibility. EPA's Exchange Network grants, in their 23rd year of competitive funding in fiscal 2025, help states, tribes and territories improve the quality and accessibility of environmental data, with awards expected at $200,000 to $600,000. For universities, NSF's biology directorate treats the costs of carrying out a data management and sharing plan, including personnel time, as allowable during the award.

Federal money brings federal buying rules, set out in 2 CFR 200.320:

• Below the micro-purchase threshold, $15,000 at the federal level, you can buy without competitive quotes when the price is documented as reasonable, and a recipient may self-certify a threshold of up to $50,000.
• Up to the simplified acquisition threshold, no more than $350,000, you need price quotes from an adequate number of qualified sources.
• Above it, formal procurement with public notice applies.

The $12,500 Tool Sprint sits under the federal micro-purchase threshold, though state and local rules can be stricter.

Plan for the years after the grant. Under 2 CFR 200.403, costs other than closeout must be incurred during the approved budget period, so hosting and upkeep after the award ends need another budget line. Under 2 CFR 200.315, you may copyright software developed under the award, but the awarding agency keeps a royalty-free, nonexclusive and irrevocable right to use it for federal purposes. Write ownership of the code and the data into your contract with the builder.

If the application itself is the bottleneck, CF Labs' Grant-Ready Tool Scope writes the scope, line-item budget, technical approach, data management plan and milestone timeline reviewers expect, in one to two weeks for $4,500. Our 2026 federal climate funding playbook tracks the programs, and funding resilience without federal grants covers the recurring sources that keep a tool running.

Who this is for: grant managers and program leads writing a budget that includes a tool. Council Fire works with local governments and universities on the program behind the application.

Which option fits your situation?

Match the build to the decision it serves, and read the last column first.

Many organizations land on two rows at once: a free or subscribed layer for the standard work, and a small build for the part that is theirs.

Related Resources

Price and scope the build

• How to write an RFP for a climate and sustainability data dashboard: requirements, weights and budgets from public contracts.
• Start a build with CF Labs: the Tool Sprint, Readiness Review and Grant-Ready Tool Scope, with prices.
• What drives the cost of custom sustainability software?: a blank budget worksheet for comparing quotes.
• Before you commission sustainability software, write a brief: define the first release before anyone prices it.
• Build or buy sustainability software?: where buying the ledger ends and building the edge begins.
• How to choose sustainability software: buy, configure or build?: the wider decision matrix.
• Free sustainability and climate tools: what CF Labs has built and published.

The data behind the dashboard

• Climate Risk Lookup: FEMA risk ratings and plan status for any U.S. county.
• Maryland climate risk by county: county profiles built on FEMA data.
• ESG Data Management Guide: owners, definitions and controls for every metric.
• GHG Protocol guide: the accounting standard behind emissions dashboards.
• Sustainability data and technology guides: the library's data and tooling guides.
• How to measure climate resilience progress, honestly: choosing indicators worth a dashboard.

Fund it and keep it running

• Federal climate funding in 2026: a municipal playbook: programs that can pay for the build.
• Funding resilience without federal grants: recurring sources for the years after.
• Resilience funding guides: the programs and funding tools we track.
• Grant reporting: which questions can you stop asking?: cut the reporting burden before you build for it.
• Build or buy climate resilience planning tools?: when the need is a project portfolio.
• iMPAct Reports: port data from five jurisdictions, made usable.

Bring your source list to a 20-minute call

Before you ask anyone for a quote, list every source the dashboard would draw on, how often each one changes, who owns it and who needs to see the result. Bring that list to a 20-minute call and we will turn it into a fixed scope and price, or tell you when a free tool or the BI license you already pay for will do the job. Talk to us on our contact page and choose Software & AI (CF Labs).

About the Author

George Chmael II is Council Fire's Founder & CEO. He has led the firm since its founding and through its B Corp certification in 2010. Council Fire's climate resilience practice works with cities, counties, ports and authorities on planning, funding and delivery, and CF Labs builds the software that puts that work to use.

Written by

George Chmael II

Founder & CEO

Corporate lawyer turned social entrepreneur, guiding organizations toward three bottom lines for 25+ years.

Full bio →All 85 articles by George →

From the library

• Topic hubSustainability Data & Technology→
• GuideESG Data Management Guide→
• CF LabsThe tools we build→

Around The Fire, in your inbox.

New articles on climate resilience, sustainable business and the end of extraction, sent when they publish.

Email addressSubscribe