The Scenario
You are a cloud finance analyst. It is the last week of the month and the VP of Engineering wants cost allocation broken down by team before the budget meeting. You have thirty Neon projects — each owned by a different engineering team — and you need compute hours, written bytes, and storage size for each one in an Excel workbook.
The workbook already has project IDs in column A and team names in column B. Columns C through E are empty.
The bad version of the next two days:
- Open the Neon billing dashboard
- Navigate to each project's usage details
- Read the compute hours, written bytes, and storage numbers
- Copy them into the workbook row by row
- Thirty projects × three metrics = ninety manual lookups
- You finish the day before the meeting and realize you read one metric in the wrong unit for six projects.
The fast version is one prompt.
The Easy Way: One Prompt in SheetXAI
SheetXAI reads the project list and pulls consumption data from the Neon API for each one.
Open the SheetXAI sidebar and type:
Pull Neon project consumption metrics for all project IDs listed in column A of my workbook and fill in monthly compute hours, storage used, and total written bytes in the adjacent columns.
SheetXAI calls the Neon consumption API, structures the output, and writes the metrics into the workbook. Thirty rows, all populated, consistent units.
What You Get
A complete cost allocation workbook with:
- Compute hours — billable compute duration per project
- Storage used — current storage size per project
- Written bytes — storage write volume per project
- Consistent units — all metrics in the same format, no conversion errors
The workbook reflects actual usage for the period, not an estimate or a dashboard screenshot.
What If the Data Is Not Quite Ready
Cost reports need additional processing before they are useful in a budget meeting. SheetXAI adds the analysis in the same prompt.
When the VP wants human-readable units
Pull Neon consumption metrics for the past 30 days for all projects. Write compute time in hours (not seconds) and storage in gigabytes (not bytes) into columns C and D. Round to two decimal places.
When you need team-level rollups alongside project-level detail
Pull Neon consumption metrics for the past 30 days for all projects and write compute hours and storage GB into columns C and D. Then add a 'Team Totals' tab that sums compute hours and storage GB by team name from column B.
When some project IDs are stale
Pull Neon consumption metrics for each project ID in column A. If a project no longer exists, write 'PROJECT NOT FOUND' into column C. For all active projects, write compute time seconds and written bytes into columns C and D.
When the VP wants month-over-month comparison
Pull Neon consumption metrics for the past 30 days and the 30 days before that for all projects. Write this month's compute hours into column C and last month's into column D. Add a 'Change' column E showing the percentage change. Flag any project with more than 25% increase.
The pattern: one prompt pulls the data, converts the units, and builds the cost allocation table.
Try It
Get the 7-day free trial of SheetXAI and open any Excel workbook with Neon project IDs, then ask it to pull the consumption data. The Neon integration is included in every plan. See also how to export your full Neon infrastructure inventory to Excel or the Neon in Excel overview.