Spacemaker

Name: Spacemaker
Brand: Spacemaker

Spacemaker (now Autodesk Forma) is a cloud-based AI software, empowering teams to analyze and design real estate sites.

Est 2016|Valuation $252M|Raised $32M|4 Ref Customers

LinkedIn 21K|Website|FTEs 13|HQ Oslo, Oslo, NO

Published Aug 18, 2026

01Common complaints

1. If view-based unit valuation is central and immediate access to specific view-analysis features is required - Community feedback indicates view analysis was valued in Spacemaker and may not be available or prioritized in Forma at present. 2. If a fully transparent, auditable optimization pipeline is required - Some organizations prefer open parametric scripting (for example, Grasshopper) where objective functions and constraints are fully auditable. 3. If low-cost, broad deployment for massing feasibility is the primary objective - TestFit and other alternatives may offer lower entry price points and licensing models designed for wider distribution across deal teams. 4. If strict data residency or deletion controls are mandatory and cannot be validated - Historical reports exist of project deletion/archiving issues; buyers with strict governance requirements should validate lifecycle controls during evaluation. 5. If projects are located in geographies with limited context datasets - Environmental and zoning/context utility can degrade materially where local data coverage is sparse. - Feature gaps compared with legacy Spacemaker: community feedback highlights missing view analysis and related prioritization concerns. - Cloud dependency: limits offline usage and can introduce IT/security friction. - Project lifecycle controls: historical reports indicated issues with hub settings persistence and project archiving/deletion behavior (Autodesk staff reported the issue was resolved in one example). - Vendor-published metrics not independently validated: claimed ROI, density, and value uplift figures should be treated as vendor-reported unless independently corroborated.

Deal disqualifiers (poor fit)

- Organizations that require offline workflows, air-gapped environments, or strict on-premises-only deployments. - Organizations that depend on specific legacy Spacemaker features that are not currently available in Forma (for example, certain view analysis capabilities) and require those capabilities immediately. - Teams primarily focused on cost/QTO feasibility rather than environmental or qualitative analyses; alternative tools may provide stronger cost-modeling features.

02Why they buy

Unique selling points with supporting evidence

Autodesk ecosystem integration: Forma provides workflow connections to Revit and Autodesk Docs/ACC, which supports handoff to later design stages.
Embedded environmental feedback loop: Autodesk materials and product descriptions indicate integration of sun, wind, and other environmental analyses into early-stage iteration.

Where the unique selling point is weaker or competitors have advantage

Economic feasibility and cost certainty: competitors such as TestFit emphasize cost models and quantity takeoffs more directly.
Feature continuity across product transitions: some users have reported missing legacy analyses after the transition from Spacemaker to Forma.

03Field reports

Review-platform reality check

Spacemaker has a limited presence on mainstream B2B review platforms: it appears on listings such as G2 but lacks a substantive review corpus, and some directory listings are either unrelated or ambiguous. This creates a data gap: the absence of reviews should not be interpreted as an indicator of product quality without further investigation; it may reflect low review capture in AEC tooling.

Community / forum quotes (Forma/Spacemaker lineage)

Because third-party review volume is low, Autodesk’s Forma community forum is a key source of user feedback. Negative / feature-related feedback: - A forum thread noted that a particular view analysis feature from the earlier product was highly valued by users and questioned why it was not present in Forma; the comment surfaced repeatedly as a top complaint. - Autodesk product staff responded in forum discussion that the feature was deprioritized relative to other work and could not promise a timeline for reinstatement. Operational bug report (resolved): - Users reported issues updating hub settings and difficulties deleting or archiving old projects; Autodesk engineering acknowledged the synchronization/bug issue and applied a resolution.

Vendor case-study statements (vendor-published; not independent)

Vendor-published customer stories highlight speed and communication benefits:

A large firm’s customer story emphasizes Forma Site Design as useful for validating performance under tight deadlines.
Vendor blog/customer stories describe reduced iteration times and smaller pursuit teams (methodology and sample sizes are not independently audited).

Inferred reasons customers chose the product

Faster generation of massing alternatives with integrated environmental analysis
Early performance and sustainability narratives for stakeholders
Integration pathway to Revit and the broader Autodesk ecosystem

Inferred reasons some customers might leave or hesitate

Feature regressions compared with legacy Spacemaker (for example, view analysis)
Cloud-only constraints
Dependency on Autodesk subscriptions and procurement practices

Vendor-reported outcomes (vendor-published)

Autodesk’s vendor materials list outcomes such as: - Saved time on the planning phase for certain projects - Increases in density and changes in unit counts with estimated economic value - Productivity improvements for architecture firms Critical evaluation: - No methodology is disclosed (for example, how measurements were taken, what baselines were used, what controls were applied). - Customers are often unnamed or only partially identified, limiting verification. - The metrics mix operational outcomes (time saved) and economic outcomes (value uplift) that are sensitive to assumptions.

Large design firm — healthcare project in the Gulf region (vendor-published story)

A vendor-published customer story describes a large design firm using Forma Site Design for an advanced healthcare facility, emphasizing tight deadlines, climate constraints, stakeholder communication via visuals, and workflow connection to Revit.

Critical evaluation:

The story is useful for understanding workflows but is light on quantitative, independently verifiable metrics.
It aligns with firms already standardized on Autodesk tooling.

Regional architecture practice — pursuits efficiency (vendor blog)

A vendor blog post reports that Forma helped reduce analysis time for some workflows and suggested smaller pursuit teams were required in certain examples.

Critical evaluation:

The account is directional and vendor-published; it likely highlights successful usage and may not represent average results.

04Best fit

Company sizes

Best-fit organizations tend to be mid-sized to large AEC firms and enterprise developers with recurring project pipelines where repeated feasibility cycles and standardization provide measurable benefits.

Industries / verticals

Architecture firms focused on urban, multi-family, hospitality, or commercial feasibility
Real estate developers operating in urban contexts
Urban planning and municipal design teams where procurement permits use of cloud tools

Roles and personas

Decision makers: Head of Design Technology, BIM/VDC leadership, CIO/IT procurement, Development Director (owner-side)
Daily users: architects, urban designers, computational designers, sustainability analysts

Pain points addressed

Slow feasibility cycles and limited iteration bandwidth
Difficulty quantifying environmental tradeoffs early in the design process
Challenges in stakeholder communication that require data-driven narratives
Rework between concept and BIM design development

Qualification criteria (good fit)

Organizations already using Revit/AEC Collection/ACC that seek earlier-stage workflow cohesion with downstream BIM.
Teams that need fast iteration with embedded analyses and can accept a cloud-first deployment model.
Groups with repeatable project types where standardized exploration yields measurable efficiencies.

05The pitch

What the product does (objective core value proposition)

Spacemaker was a cloud-based AI/generative-design product for early-stage site planning and urban massing. It enabled architects, urban designers, and real estate developers to generate and evaluate site proposals against constraints and quantitative "quality" criteria (for example, sun/daylight, wind, noise, zoning/context data) and then iterate toward higher-performing schemes. Important recent reality: Spacemaker as a standalone product has been integrated into Autodesk Forma. Autodesk marketing and product updates position Forma Site Design as the in-market offering for feasibility and concept design.

Target market and market positioning

- Primary users: architects and urban designers conducting feasibility studies, schematic massing, and early site analytics. - Economic buyer: frequently the developer/owner or large architecture firm leadership (budgets typically higher than individual architects; this was referenced in Spacemaker’s go-to-market learning). - Positioning: a data-informed early-stage design tool intended to reduce iteration time (minutes/hours vs. days/weeks in many legacy processes) and integrate into downstream BIM workflows (notably Revit) via Autodesk’s ecosystem.

Get a comprehensive analysis of Spacemaker including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →

Published Aug 18, 2026

01Common complaints

If view-based unit valuation is central and immediate access to specific view-analysis features is required
- Community feedback indicates view analysis was valued in Spacemaker and may not be available or prioritized in Forma at present.
If a fully transparent, auditable optimization pipeline is required
- Some organizations prefer open parametric scripting (for example, Grasshopper) where objective functions and constraints are fully auditable.
If low-cost, broad deployment for massing feasibility is the primary objective
- TestFit and other alternatives may offer lower entry price points and licensing models designed for wider distribution across deal teams.
If strict data residency or deletion controls are mandatory and cannot be validated
- Historical reports exist of project deletion/archiving issues; buyers with strict governance requirements should validate lifecycle controls during evaluation.
If projects are located in geographies with limited context datasets
- Environmental and zoning/context utility can degrade materially where local data coverage is sparse.

Feature gaps compared with legacy Spacemaker: community feedback highlights missing view analysis and related prioritization concerns.
Cloud dependency: limits offline usage and can introduce IT/security friction.
Project lifecycle controls: historical reports indicated issues with hub settings persistence and project archiving/deletion behavior (Autodesk staff reported the issue was resolved in one example).
Vendor-published metrics not independently validated: claimed ROI, density, and value uplift figures should be treated as vendor-reported unless independently corroborated.

Deal disqualifiers (poor fit)

Organizations that require offline workflows, air-gapped environments, or strict on-premises-only deployments.
Organizations that depend on specific legacy Spacemaker features that are not currently available in Forma (for example, certain view analysis capabilities) and require those capabilities immediately.
Teams primarily focused on cost/QTO feasibility rather than environmental or qualitative analyses; alternative tools may provide stronger cost-modeling features.

02Why they buy

Unique selling points with supporting evidence

Autodesk ecosystem integration: Forma provides workflow connections to Revit and Autodesk Docs/ACC, which supports handoff to later design stages.
Embedded environmental feedback loop: Autodesk materials and product descriptions indicate integration of sun, wind, and other environmental analyses into early-stage iteration.

Where the unique selling point is weaker or competitors have advantage

Economic feasibility and cost certainty: competitors such as TestFit emphasize cost models and quantity takeoffs more directly.
Feature continuity across product transitions: some users have reported missing legacy analyses after the transition from Spacemaker to Forma.

03Field reports

Review-platform reality check

Community / forum quotes (Forma/Spacemaker lineage)

Because third-party review volume is low, Autodesk’s Forma community forum is a key source of user feedback.

Negative / feature-related feedback:

A forum thread noted that a particular view analysis feature from the earlier product was highly valued by users and questioned why it was not present in Forma; the comment surfaced repeatedly as a top complaint.
Autodesk product staff responded in forum discussion that the feature was deprioritized relative to other work and could not promise a timeline for reinstatement.

Operational bug report (resolved):

Users reported issues updating hub settings and difficulties deleting or archiving old projects; Autodesk engineering acknowledged the synchronization/bug issue and applied a resolution.

Vendor case-study statements (vendor-published; not independent)

Vendor-published customer stories highlight speed and communication benefits:

A large firm’s customer story emphasizes Forma Site Design as useful for validating performance under tight deadlines.
Vendor blog/customer stories describe reduced iteration times and smaller pursuit teams (methodology and sample sizes are not independently audited).

Inferred reasons customers chose the product

Faster generation of massing alternatives with integrated environmental analysis
Early performance and sustainability narratives for stakeholders
Integration pathway to Revit and the broader Autodesk ecosystem

Inferred reasons some customers might leave or hesitate

Feature regressions compared with legacy Spacemaker (for example, view analysis)
Cloud-only constraints
Dependency on Autodesk subscriptions and procurement practices

Vendor-reported outcomes (vendor-published)

Autodesk’s vendor materials list outcomes such as:

Saved time on the planning phase for certain projects
Increases in density and changes in unit counts with estimated economic value
Productivity improvements for architecture firms

Critical evaluation:

No methodology is disclosed (for example, how measurements were taken, what baselines were used, what controls were applied).
Customers are often unnamed or only partially identified, limiting verification.
The metrics mix operational outcomes (time saved) and economic outcomes (value uplift) that are sensitive to assumptions.

Large design firm — healthcare project in the Gulf region (vendor-published story)

Critical evaluation:

The story is useful for understanding workflows but is light on quantitative, independently verifiable metrics.
It aligns with firms already standardized on Autodesk tooling.

Regional architecture practice — pursuits efficiency (vendor blog)

A vendor blog post reports that Forma helped reduce analysis time for some workflows and suggested smaller pursuit teams were required in certain examples.

Critical evaluation:

The account is directional and vendor-published; it likely highlights successful usage and may not represent average results.

04Best fit

Company sizes

Industries / verticals

Architecture firms focused on urban, multi-family, hospitality, or commercial feasibility
Real estate developers operating in urban contexts
Urban planning and municipal design teams where procurement permits use of cloud tools

Roles and personas

Decision makers: Head of Design Technology, BIM/VDC leadership, CIO/IT procurement, Development Director (owner-side)
Daily users: architects, urban designers, computational designers, sustainability analysts

Pain points addressed

Slow feasibility cycles and limited iteration bandwidth
Difficulty quantifying environmental tradeoffs early in the design process
Challenges in stakeholder communication that require data-driven narratives
Rework between concept and BIM design development

Qualification criteria (good fit)

Organizations already using Revit/AEC Collection/ACC that seek earlier-stage workflow cohesion with downstream BIM.
Teams that need fast iteration with embedded analyses and can accept a cloud-first deployment model.
Groups with repeatable project types where standardized exploration yields measurable efficiencies.

05The pitch

What the product does (objective core value proposition)

Important recent reality: Spacemaker as a standalone product has been integrated into Autodesk Forma. Autodesk marketing and product updates position Forma Site Design as the in-market offering for feasibility and concept design.

Target market and market positioning

Primary users: architects and urban designers conducting feasibility studies, schematic massing, and early site analytics.
Economic buyer: frequently the developer/owner or large architecture firm leadership (budgets typically higher than individual architects; this was referenced in Spacemaker’s go-to-market learning).
Positioning: a data-informed early-stage design tool intended to reduce iteration time (minutes/hours vs. days/weeks in many legacy processes) and integrate into downstream BIM workflows (notably Revit) via Autodesk’s ecosystem.

Get a comprehensive analysis of Spacemaker including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →