Many teams run important work from a spreadsheet that has grown over years — a quote generator, an inventory tracker, or a budget model that only one person fully understands. Turn the spreadsheet your team already relies on into an application with Aha! Builder — without starting over. Upload the workbook, and Elle (the AI assistant) analyzes its sheets, data, and formulas, then builds a database-backed application that carries the same logic.
You can create an application from a spreadsheet on all Aha! Builder plans: Pro, Team, and Scale. Analyzing the workbook and building the application use AI credits.
In this article, we will turn a real spreadsheet workflow into an application together. Let us say we are on a sales operations team at a software company. We build every customer quote in a shared Excel workbook with four sheets: a quote sheet that looks up list prices, a price book, volume discount tiers, and a log of every quote we have sent. It works, but formulas break when someone edits the wrong cell, and only one person on the team knows how the discount logic fits together. We will upload the workbook to Aha! Builder, confirm that the new application calculates quotes the same way the spreadsheet does, and fix what does not match.
Click any of the following links to skip ahead:
Prepare your spreadsheet
The best candidates support an ongoing process: several people update the spreadsheet, it calculates values the team depends on, and it has been part of the workflow for a long time. A one-time analysis or a simple list rarely needs an application.
A few minutes of cleanup before you upload helps Elle read the workbook the way you intend. Before we upload our quote workbook, we will:
Save it as an XLSX file, or as an XLSM file if it contains macros.
Note: If the spreadsheet lives in another tool, download it as an Excel workbook first.
Give each sheet a single header row with a clear name for every column.
Remove any superfluous worksheets or data. Elle will assume that anything in your workbook is relevant to the application it builds.
Label configuration values, such as a tax rate or the number of days a quote stays valid.
Replace confidential data with sample data. Elle imports the rows in the workbook as the application's starting data.
Upload the spreadsheet
To start, navigate to the Applications page and click Create.
On the Welcome, let's start building screen, click Create from spreadsheet.
Drag the workbook into the upload area, or click Browse files and select it. You can upload one XLSX or XLSM file.
-
In the What do you use this spreadsheet for? field, describe the workflow in a sentence. The field is optional, but a short description helps Elle interpret the workbook.
For our quote workbook, we will type: "Build quotes for software deals: look up list prices, apply volume discounts by seat count, add sales tax, and flag quotes that need approval."
Click Analyze spreadsheet.
Elle reads each sheet and maps the workbook's structure, data, and formulas. The analysis usually takes less than a minute. When it finishes, Elle begins drafting the application's vision, personas, and capabilities from the workbook, and the wizard moves straight to naming the application.
Finish the getting started wizard
The remaining steps match the ones in creating your first business application. Elle has already drafted the hard parts, so each step takes only a few seconds. Click Next after each one.
Name: Elle suggests names based on the workbook. We will select SaaS Quote Manager. If none of the suggestions fit, we could select Custom name and enter our own.
Type: Choose how people will use the application. Everyone on the sales team should see the same quotes, so we will select Team, which requires login and shows every user the same data.
Navigation: Our application will have several areas, including quotes, a price book, and settings, so we will select Vertical for a left sidebar.
Style: Describe how the application should look. We will type: "Clean and professional, like a modern finance tool. Navy primary color on a white background, with green for approved quotes and amber for quotes that need approval." We could also upload design inspiration in PNG, JPEG, or SVG format.
Answer Elle's clarifying questions
On the Elle is almost ready to start building screen, Elle asks a few follow-up questions. When you start from a spreadsheet, these questions often target the logic Elle could not settle from the workbook alone, so they deserve careful answers.
For our quote workbook, Elle asks three questions:
-
What seat-volume thresholds determine whether a quote needs sales manager approval or finance approval?
We will answer from the Discount tiers sheet: quotes under 250 seats need no approval, quotes with 250 to 499 seats need sales manager approval, and quotes with 500 or more seats need finance approval.
-
Should the price book support multiple currencies?
We will answer that all pricing is in US dollars.
-
Should a quote lock when you mark it won?
We will answer that won quotes lock, and only administrators can reopen them.
Click Design my app. If we wanted to leave the decisions to Elle, we could click Skip instead and refine the assumptions later.
Choose a starting design
Before the full build, Elle renders three design variations of the application. For SaaS Quote Master, Elle offers Playful, Professional, and Monochrome, each with a live preview and a short description.
Click the variation that fits your team. We will select Professional, which Elle describes as dense, structured, and optimized for daily operations.
Click Build application.
Elle builds the complete application — front end, back end, and database — in about 10 minutes. We will keep the browser tab open while it runs.
Review what Elle built
When the build finishes, the application opens in Preview. Because we selected the Team type, the preview starts on a sign-in screen. Sign in with your Aha! account to explore the application the way the sales team will.
SaaS Quote Master includes a dashboard, a quote list, a new quote form, a price book, and settings. Elle imported the workbook's rows as starting data, so the price book lists every product from our Price book sheet and the dashboard shows the quotes from our Quote log sheet.
To see exactly how Elle read the spreadsheet:
Click through the application and compare the results with your original spreadsheet.
If you see discrepancies, ask Elle to investigate and explain. Be sure to include your expected behavior when prompting Elle.
Check the calculations
An application built from a spreadsheet earns trust by producing the same numbers. Before anyone uses it, run the same inputs through both and compare the results.
We will rebuild a quote from the spreadsheet: 140 seats of Brightline Pro, 140 single sign-on add-ons, API access, and guided onboarding on a 12-month contract.
In the application, click Create Quote.
Click Add Product... and select each product from the quote.
Enter the same Qty for each line as the spreadsheet.
Compare the Quote summary with the totals in the spreadsheet.
Our spreadsheet calculates a total of $147,730.44 with no approval needed. The application shows $17,084.925 and flags the quote for sales manager approval. This is a significant difference, and a good opportunity for us to investigate further:
Contract term: The spreadsheet multiplies recurring charges by a 12-month term. The new quote form has no contract term field, so the application prices recurring items for a single month.
Seat count: The spreadsheet counts only seat-based subscriptions toward the discount tiers. The application also counts the 140 add-on seats, reaches 280 seats, and triggers an approval.
Volume discount: The application applies no volume discount, even though the quote qualifies for a discount tier.
The tax and total also display three decimal places instead of two. Differences like these are common, because spreadsheets hide rules in cell references and team conventions. Now that we can see these, we can resolve them.
Refine the application with Elle
We will fix each difference from the Elle panel, one request at a time, and rerun the same quote after every change.
When a number looks wrong and the reason is not obvious, ask Elle to explain the calculation before asking for a fix.
Ask Elle how the discount works: "How does the application calculate the volume discount? Walk through the totals for a quote with 280 seats."
Add the missing field: "Add a contract term field to each quote, defaulting to 12 months, and multiply recurring line totals by the term."
Correct the seat rule: "Count only seat-based subscription products, the SKUs that end in -SEAT, toward total seats for discounts and approvals."
Fix the rounding: "Round sales tax and all quote totals to two decimal places."
Aha! Builder records every change in the code history, so we can review a refinement or roll it back. When the application and the spreadsheet agree on several quotes, including at least one in each discount tier, we are ready to trust SaaS Quote Master with real deals.
Go beyond the spreadsheet
SaaS Quote Master now calculates quotes the way our spreadsheet does, and it can do things the spreadsheet never could:
Control access: Give sales representatives, sales managers, and finance reviewers their own roles, so each person sees and changes only what they should.
Connect other tools: Use the integrations catalog to post approved quotes to a Slack channel or pull customer details from a CRM.
Notify the team: On the Aha! Builder Scale plan, send an email when a quote needs approval.
When the application is ready for the whole team, configure and deploy it. Then retire the spreadsheet, so the team stops maintaining two versions of the same process.