Autodesk Construction Cloud pricing depends on the products and licensing arrangement you need. If your proposal uses Autodesk Build, ACC, and Forma names, start by matching them: Autodesk Construction Cloud is now part of Autodesk Forma, and Autodesk Build is now Forma Build. Autodesk explains the changes in its product naming announcement. The name change does not establish what your subscription includes.
Autodesk's current pricing page offers product and bundle options, with user, project, and account-based pricing. It directs buyers to request quotes for the listed bundles. There is no single published amount on that page that can stand in for your whole construction software budget. Product information here was checked on October 13, 2026; use your written quote for the price and contract terms.
Which products are you buying?
A proposal labeled Construction Cloud or Forma needs a product list beneath it. Autodesk lists Model Management, Preconstruction, and Construction Operations bundles on its pricing page. The Construction Operations list includes Forma Build and Forma Data Management, among other products. Have the seller identify the bundle, individual products, and any edition limits on the order form.
Describe the tasks you expect people to complete before reviewing that list. For example, a project manager may need to review a change order while a superintendent needs access to current drawings. Ask for those tasks to be demonstrated with the quoted package. If the demonstration uses another product, record the added subscription and who needs access to it.
Check existing Autodesk subscriptions with your account administrator. Record the product, assigned user, renewal date, and proposed replacement for anything you plan to retire. This gives the seller a specific entitlement question to answer and helps finance avoid budgeting overlapping subscriptions without a reason.
What does the license cover?
Ask which pricing basis applies to each line in the proposal. A user-based offer needs a defined population, while a project-based offer needs a definition of the covered projects. For an account-based agreement, ask the seller to document which teams, legal entities, and outside participants are included. These are questions for your agreement, not assumptions to carry over from another contractor's purchase.
Autodesk's Forma FAQ says some Build subscriptions have sheet-count tiers. For those subscriptions, the count includes sheets accessible across a user's projects and their revisions; files in the Files area do not count toward that limit. Check whether your quoted plan has this restriction and how the seller will size it for your work.
For a hypothetical rollout, suppose a project manager works on several active jobs and a superintendent works on one. Counting their users alone would miss the difference in sheet access if their plan has a sheet limit. Ask for a capacity check using the active drawing sets and expected revisions. Do not use the count from a quiet demonstration project as the purchasing assumption.
Put the unanswered questions beside the price
| Budget item | What to request in writing | What could be missed |
|---|---|---|
| Subscription | Product names, licensing basis, term, and capacity limits | A demonstrated feature belongs to an unquoted product |
| Outside participants | Access requirements for subcontractors, owners, and consultants | An invited collaborator cannot perform the expected task |
| Setup and training | Deliverables, delivery owner, and acceptance criteria | Your team must configure something it expected the seller to handle |
| Existing project records | Records, attachments, references, and validation work | Imported documents lose the context needed for later review |
| Accounting and reporting | Exact data required, transfer method, and exception owner | A report still needs manual exports or matching |
| Renewal and exit | Renewal rules, notice dates, and export arrangements | A first-year comparison omits later costs or retained access |
Put “scope pending” beside an integration that has not been priced. A zero would make it look included. Separate recurring charges from setup work, and assign the internal work to named people so finance can see which costs the vendor quote leaves with your team.
If Procore is also on the shortlist, request the same workflow and rollout assumptions from both sellers. The Procore pricing article explains its published pricing basis. You can compare the total proposed spend once each offer covers the people, projects, and tasks your company expects to support.
Scope the accounting and reporting work
Take a report that your controller already prepares and list its inputs. Which project records does it need, where do accounting actuals come from, and how are the job identifiers matched? Then ask the implementation provider to show how those inputs will be obtained under the proposed subscriptions. A demonstration with sample data does not answer whether your own records are accessible.
Use one corrected record to test the process. If a commitment changes after it appears in a report, identify who updates the source, when the report refreshes, and how a reviewer sees the revision. The Autodesk Build and ERP integration article covers the data handoff in more detail. Keep that work in the implementation scope if the budget depends on it.
Where Permute fits in the reporting budget
Permute sells connected business data and custom applications. We can scope a reporting application around supplied project records and supported accounting sources, keeping the source identifiers available for review. A controller could inspect a cost difference and see which inputs produced it, with access limited to the data they are allowed to use.
The work starts with agreed definitions, such as which commitment status belongs in the report and which date controls the reporting period. Those rules can be reused instead of being changed in a separate spreadsheet each month. Our custom software offering describes this kind of engagement; it needs its own scope and estimate alongside the Autodesk purchase.
Try a report with an available data source
Explore a recurring question and inspect the records behind the answer.
Separate product access from delivery commitments
Permute does not set Autodesk prices or replace its drawing, field, and project-management workflows. This example does not promise a native Autodesk connector, automatic ERP posting, or access that your Autodesk agreement does not grant. Confirm the available extraction method and permissions before pricing a reporting connection.
Your project and accounting owners still approve corrections and decide which records belong in the financial report. A reporting application can expose inconsistent inputs, but it does not settle an accounting treatment or approve a project change. Name the responsible person in the rollout plan.
Approve the scope with the price
A usable Autodesk Construction Cloud budget identifies the products, license coverage, and work required to put them into use. Match older product names to the current proposal, then resolve access limits and delivery responsibilities. Compare offers using the same project requirements and keep unpriced work visible. The subscription amount becomes a useful decision point once you know what your team can do with it.
Review the reporting needs around your Autodesk rollout
Bring a recurring report and the project and accounting records it depends on.
Questions about the Autodesk budget
Does the Forma name change require a data migration?
Autodesk says the branding change does not require a migration for current ACC or Forma customers, and existing subscriptions and permissions remain intact. That is separate from a company deciding to move records from another product. Ask a services provider to identify the actual records being moved before accepting a migration charge.
Is Autodesk cheaper than Procore?
A general answer would hide differences in product scope and contract terms. Compare written proposals for the same participants, projects, and required workflows. The Procore vs Autodesk comparison can help you define those requirements before asking for prices.
Can I carry a quote into next year's budget?
Keep the quote date, expiration, currency, and assumed scope with the budget line. Ask the seller whether the proposed terms remain available for your planned start date. Treat an expired offer as a planning assumption until it is refreshed.
Do invited subcontractors need the same subscription as employees?
An invitation alone does not establish access to every required product or task. Give the seller a list of what subcontractors must do, such as view drawings, respond to an RFI, or review a change, and get the required entitlement for each. Include existing subscriptions in that check to avoid buying overlapping access.