Autodesk Construction Cloud pricing includes published per-user offers and quoted bundles. Autodesk’s Build pricing comparison lists $117 per user per month for an annual plan and $175 per user per month for monthly billing. Match the product, billing term, and user role before multiplying a price by your headcount.
Autodesk Construction Cloud is now part of Autodesk Forma, and Autodesk Build is now Forma Build, as Autodesk explains in its naming announcement. The prices below were checked against official US product and licensing pages on November 2, 2026 (no paid account or checkout was tested). Use a written order for your currency, tax, payment schedule, and full commitment.
Which products are you buying?
Autodesk publishes these dollar amounts in its Build and Build Essentials comparison, updated April 24, 2026. The annual column is a monthly equivalent for an annual plan. It does not establish the payment schedule or exact annual checkout total, so do not multiply a rounded display price by twelve to calculate an annual order.
| Product | Per user, monthly plan | Per user, annual plan monthly equivalent | Unlimited users |
|---|---|---|---|
| Forma Build Essentials | $100/month | $67/month | Not listed as available |
| Forma Build | $175/month | $117/month | Contact sales |
Autodesk lists issues, forms, photos, sheets, and files for Essentials, while RFIs, submittals, and cost management require Build. Demonstrate the proposed license for each role: a superintendent logging daily activity may need different tools from a project manager reviewing a change.
Autodesk confirms on the Build purchase page that Essentials and Build users can share a project, with available tools governed by license type. Sharing the project does not give an Essentials user the full Build toolset. Test the handoff between those users, including who must open, review, or approve the next record.
For broader coverage, Autodesk lists Model Management, Preconstruction, and Construction Operations bundles on its pricing page, with quotes rather than a published bundle total. Construction Operations includes Forma Build and Forma Data Management, among other products. Have the seller identify the products and editions on the order form; leave the bundle amount unknown until quoted.
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.
For estimating teams, the Autodesk Takeoff pricing evaluation narrows the quote to takeoff access, quantity outputs, and the estimating handoff. Use it to define that product scope before requesting a broader bundle.
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.
For a named-user purchase, Autodesk distinguishes project access from subscription assignment. Inviting a member to a project does not provide a subscription. Record whether each employee or outside participant receives an assigned subscription, brings an eligible one, or is using a trial that will expire.
Autodesk supports eligible bring-your-own-subscription arrangements, but its subscription usage policy can restrict use on another team’s projects. Before removing subcontractor seats from your budget, verify the product entitlement and the assigning team’s policy with that subcontractor. Then test access on your project; possession of a subscription alone does not settle the question.
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
- Tie every demonstrated task to a quoted product and assigned role, including outside participants whose subscriptions cannot be used on your project.
- Confirm the annual contract total, amount due upfront, renewal terms, and treatment of midyear additions; keep the monthly display rate separate from the payment schedule.
- Assign setup and training deliverables to a delivery owner, with acceptance criteria for the configuration your team expects the provider to complete.
- Name the old project records, attachments, and references that must remain usable, then specify how the imported relationships will be validated.
- Price the accounting and reporting data transfer, including manual work and the owner of records that fail to match.
- Document renewal notice dates and exit exports, including the access needed to review retained project evidence after the subscription changes.
Build a first-year budget from the confirmed subscription commitment, any additional products, implementation fees, and internal delivery work. Show taxes and any overlap with subscriptions you cannot yet retire as separate lines. Build the renewal-year view alongside it so that a one-time setup charge and a recurring reporting service do not disappear into the same number.
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.
For each reporting service, request the recurring charge, refresh schedule, correction process, and delivery owner. Leave the total open if the provider has not confirmed access to the required records. A subscription proposal and a reporting estimate can be approved together once those dependencies are explicit.
Where Permute fits in the reporting budget
Permute sells connected business data and custom applications, so this evaluation has a commercial interest. We can scope a reporting application around supplied project records and supported accounting sources, matching job identifiers while retaining source references. Access stays limited to the data each user is 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. A controller could inspect a cost difference and see the inputs behind it; our custom software offering 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. Use the published seat rates with their billing terms, then obtain exact annual totals and bundle quotes for the roles you need. Verify access limits and delivery responsibilities against the same project requirements. Keep unpriced work visible until it has an owner and an agreed cost.
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’s naming announcement says the branding change does not require a migration for current ACC or Forma customers, and existing subscriptions and permissions remain intact. Moving records from another product is a separate implementation task. 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.
What if a subcontractor changes firms during the project?
Recheck the subscription assignment and the new firm’s policy before relying on continued access. Include that review in the person’s project handoff, along with their open tasks and replacement owner. Budget for a replacement entitlement only after establishing what access the new arrangement provides.