Endra Power Studio Launches With Planlabs Deal After $50M Raise

Endra launched Endra Power Studio on September 16, just over three months after securing a $50 million Series A. The company also acquired Planlabs, adding mechanical engineering research to its plan for a unified building-systems design platform.

The announcement packages three developments into one move. Endra now has an electrical product, a mechanical engineering team, and a stated path toward plumbing software in 2027. Acquisition terms were not disclosed.

That combination matters more than another AI feature inside design software. Endra wants to move calculations, routing, simulation, modeling, and documentation into one system controlled by engineering firms. It is challenging the fragmented workflow built around Autodesk Revit, spreadsheets, coordination software, and specialized calculation tools.

The Endra Power Studio Launch Combines Product and Acquisition

Endra is using Power Studio and the Planlabs acquisition to assemble the three disciplines covered by MEP engineering.

MEP stands for mechanical, electrical, and plumbing engineering. These disciplines determine how buildings receive power, ventilation, water, fire protection, communications, and other essential services.

Endra Power Studio starts with electrical design. According to the company’s Power Studio details, engineers can load a building model, define requirements, and assign specific tasks to software agents.

The engineer remains responsible for reviewing and approving the output. That qualification is important because electrical design affects safety, code compliance, project costs, and construction sequencing.

Endra divides the product into several connected functions. Playbooks store a firm’s standards, calculation methods, code interpretations, and placement rules. Agents apply those instructions to defined design tasks.

A simulation layer evaluates the proposed system against physical constraints and building rules. The document engine then produces connected project materials, including Revit models, single-line diagrams, panelboard schedules, shop drawings, and bills of materials.

Endra says Power Studio can complete the electrical design for a 500,000-square-foot commercial building in less than one day. The company compares that result with a conventional process lasting about two months.

That claim has not received independent validation across multiple firms or building types. Project complexity, jurisdiction, model quality, and approval requirements can all affect the comparison.

The announcement therefore establishes a performance target, not an industry benchmark. Customers will need repeatable project results before the promised time reduction becomes a reliable planning assumption.

Planlabs supplies another part of the strategy. The Swiss company was founded in 2024 and employed five researchers with doctoral training in mathematics and computer science, according to Endra.

Its software uses geometry, data, and physics engines to generate mechanical systems while checking physical constraints. The entire team will join Endra through what the company describes as a technology and talent acquisition.

Mechanical capabilities will not appear immediately. Endra says they will reach its platform after the acquired technology has been integrated. A plumbing module is scheduled to follow in 2027.

The deal creates a clear sequence. Electrical engineering is the available entry point, mechanical engineering is the acquired expansion, and plumbing is the remaining roadmap commitment.

Endra is not merely buying revenue or regional distribution. It is buying specialized technical work that would take time to reproduce internally.

The acquisition also indicates how Endra intends to spend its recent financing. The company is combining product development, recruitment, geographic expansion, and selective consolidation instead of pursuing organic growth alone.

That approach can accelerate coverage across disciplines. It can also create integration risk, especially when separate geometry and simulation engines must operate through one data model.

Why Endra Is Moving Beyond Another Revit Add-On

The central bet is that meaningful engineering automation requires a shared model of the building, not a collection of disconnected shortcuts.

Most MEP projects already use digital tools. The problem is that those tools often divide one engineering process across separate files, applications, and handoffs.

An engineer might model geometry in Revit, maintain calculations in spreadsheets, and coordinate conflicts in Navisworks. Other specialized applications may handle equipment selection, code checks, schedules, or manufacturer data.

People connect those systems through manual review. They transfer values, resolve inconsistencies, interpret design intent, and update related documents when the architectural model changes.

Endra wants to place those steps inside a single computational environment. Its product must understand the relationship between equipment, circuits, cables, rooms, loads, routes, and documentation.

That is different from asking a language model to generate explanatory text. Building design requires spatial reasoning, deterministic calculations, and persistent relationships among thousands of components.

A language model can interpret an instruction, but it cannot independently establish whether every cable is correctly sized. It also cannot guarantee that a route avoids structural elements or satisfies a local electrical code.

Endra’s proposed answer combines agents with geometry and physics engines. The agents receive tasks, while the specialized engines handle constraints that require calculation or spatial evaluation.

CEO Niklas Lindgren described the product as a way to remove repetition while preserving engineering judgment. The company’s position is that engineers define requirements, review each stage, and retain final approval.

That human control is not a minor interface choice. It is the condition that makes automation plausible inside a profession carrying contractual and safety responsibilities.

Endra previously explained that its software uses a granular 3D data model instead of relying entirely on Revit’s internal representation. Lindgren told an AEC design interview that the platform models electrical systems from individual receptacles through transformers.

Revit still remains part of the workflow. Endra generates Revit models and other familiar deliverables, allowing firms to exchange work with architects, contractors, and clients.

This creates an important distinction. Endra is not trying to eliminate the dominant building information modeling format immediately. It is trying to become the engineering layer that determines what goes into that model.

In that arrangement, Revit becomes an orchestration and delivery environment. Endra carries more of the system logic, automation, and validation.

The difference matters for adoption. A conventional add-on can fit into established processes with limited organizational change. An end-to-end engineering platform asks a firm to move standards and project knowledge into a new system.

That migration can produce deeper automation, but it raises the stakes. Firms must trust how the platform represents their calculations, applies their rules, and responds to design revisions.

The Playbooks feature addresses part of that problem. It lets each firm encode its own standards instead of accepting a universal design method.

Stored standards could also preserve knowledge when senior engineers retire. A playbook might capture preferred layouts, calculation practices, or interpretations previously carried through mentoring and internal documents.

However, converting judgment into structured rules requires careful work. Standards contain exceptions, local practices, client preferences, and lessons that teams do not always document explicitly.

A playbook is only useful when it remains current. Firms will need governance for reviewing rules, recording exceptions, and ensuring that one project’s workaround does not become a permanent standard.

This resembles the challenge of building a searchable engineering knowledge base. The software matters, but information ownership and maintenance determine whether teams can rely on it.

Endra’s model therefore shifts some work rather than simply removing it. Engineers spend less time placing repeated objects, but more time defining reusable requirements and checking automated results.

That change could be valuable. It also means productivity depends on process design, not only model performance.

A $50 Million Raise Increases the Pressure to Prove Repeatability

Endra now has enough capital and customer access to test its thesis, but its financing also raises expectations for measurable deployment.

Andreessen Horowitz led Endra’s $50 million Series A in June 2026. Existing investors Notion Capital and Norrsken VC also participated.

The financing followed earlier rounds and arrived less than two years after Endra’s 2024 founding. The company has since expanded beyond Stockholm into New York, San Francisco, and London.

Endra says it works with consulting firms including AtkinsRéalis, Ramboll, Buro Happold, Hoare Lea, and AFRY. These names give the startup access to large projects and experienced engineering teams.

The funding case rests on a recognizable constraint. Data centers, industrial facilities, electrification projects, and complex commercial buildings require extensive mechanical and electrical design.

Axios linked the round to growing construction demand for facilities with complicated power and water requirements. Its funding coverage highlighted data centers and manufacturing sites as representative workloads.

Investors also see MEP engineering as a large services market limited by available specialists. Andreessen Horowitz describes it as exceeding $150 billion globally.

That estimate comes from an investor in the company, so readers should treat it as part of the financing thesis. It does not establish the amount that software vendors can capture.

The investor’s Endra thesis focuses on automating repeated tasks such as device placement, circuit routing, and rule checking. Those tasks can consume substantial time across large, repetitive buildings.

The strongest business case is not replacing every engineering decision. It is increasing the number of projects each experienced team can supervise without lowering quality.

Endra’s launch places that proposition into a product that customers can evaluate. The company must now prove that the workflow transfers across offices, jurisdictions, building types, and project stages.

One impressive demonstration cannot establish that repeatability. A hotel, hospital, data center, office tower, and laboratory impose different constraints.

Local building rules also complicate scale. Electrical codes share common structures, but authorities, utilities, clients, and engineering firms apply additional requirements.

Model quality varies as well. Automated output depends on the architectural information supplied to the system. Missing room data or inconsistent equipment names can introduce problems before an agent begins designing.

Changes during a project create another test. Architecture rarely remains fixed while engineering proceeds. Rooms move, equipment changes, and structural elements appear in previously available routes.

Power Studio must update connected calculations and documents without hiding downstream effects. A fast initial design loses value if each revision requires extensive manual reconstruction.

The company must also show that its review interface helps engineers find meaningful errors. A system can produce thousands of connected outputs, making superficial approval dangerous.

Traceability will matter as much as generation speed. Reviewers need to understand which requirements shaped a result and what changed between versions.

They also need confidence that automated decisions can survive peer review, permitting, construction, and professional liability discussions.

The funding gives Endra time to address those issues. It also creates pressure to expand quickly across disciplines and regions.

Buying Planlabs answers the mechanical engineering staffing question faster than building an equivalent team from scratch. Yet the acquisition introduces another milestone investors and customers can monitor.

Endra must integrate the team’s technology without weakening the electrical product. It must also avoid presenting future mechanical capability as if it were already available.

The distinction between roadmap and production software should remain visible. Power Studio covers electrical work today, while mechanical and plumbing coverage depend on later delivery.

Endra Faces an Automation Race, Not Just Legacy Software

Endra’s primary opponent is the fragmented engineering workflow, but competing automation platforms are pursuing the same opening.

Autodesk remains the central software provider in much of building design. Revit gives architects and engineers a shared building information model, while related products support coordination and construction management.

Autodesk also continues adding artificial intelligence across its portfolio. Its construction AI tools already target document processing, risk analysis, specifications, and repetitive design tasks.

The incumbent possesses distribution, file compatibility, and customer relationships. It does not need to reproduce Endra’s entire architecture to create competitive pressure.

Autodesk can embed automation into products firms already license and understand. That lowers switching costs, even if specialized platforms offer deeper engineering capabilities.

Endra’s relationship with Revit is therefore cooperative and competitive. It relies on Revit-compatible deliverables while trying to move important design intelligence into its own platform.

Augmenta provides a more direct comparison. Its platform automates electrical raceway modeling and coordination for virtual design and construction teams.

The company says users can import Revit models, set routing areas and project constraints, generate clash-free paths, and return conduit systems to Revit. Its electrical workflow emphasizes complex projects such as data centers, hospitals, and schools.

Both companies use spatial computation to reduce repetitive electrical work. However, they enter the market from different positions.

Augmenta focuses heavily on constructable routing and coordination. Endra presents Power Studio as a broader engineering environment spanning requirements, calculations, simulation, system design, and documentation.

Those descriptions come from the vendors. Buyers will need project evidence to determine how far each system extends and where manual work remains.

The competition is also wider than two startups. Engineering firms already use scripts, Revit extensions, Dynamo workflows, calculation packages, and internal templates.

A collection of smaller tools can be difficult to maintain. It can still win when it reflects a firm’s established process and avoids a major platform migration.

Endra must therefore outperform more than legacy software. It must outperform the customized workflow that experienced firms have assembled around that software.

That requirement changes the adoption calculation. Faster object placement matters, but firms will also examine interoperability, audit history, model ownership, security, and staff training.

Endra says it does not train models on customer data. It also reports SOC 2 Type II and ISO 27001 certification, regional hosting, GDPR compliance, and a Cyber Essentials Plus assessment.

Those controls help with enterprise procurement. They do not answer every question about project confidentiality, subcontractor access, retention policies, or intellectual property.

Customers will need contract-specific answers. Sensitive building models can expose security systems, infrastructure layouts, equipment locations, and operational requirements.

Professional responsibility creates another competitive barrier. An engineer can delegate a task, but accountability does not automatically transfer to the software vendor.

That reality favors systems designed around review rather than autonomous approval. Endra’s emphasis on engineers signing off at each stage fits that requirement.

Still, review can become a bottleneck if automated output grows faster than human verification capacity. The product must help reviewers focus on exceptions and high-impact decisions.

Otherwise, a firm could exchange drafting labor for a new burden: checking a large volume of machine-generated work without sufficient context.

The central question is not whether Power Studio can produce a model. It is whether engineers can trust, inspect, revise, and defend that model efficiently.

That is why independent project evidence matters. Endra’s speed claim attracts attention, but traceability and revision performance will determine durable adoption.

What to Watch as Endra Integrates Planlabs

The next evidence should come from deployed projects, mechanical integration, and customer behavior rather than broader automation claims.

The first signal is repeatable Power Studio performance across different building types. Endra’s 500,000-square-foot example provides a concrete claim, but not a representative sample.

Useful evidence would compare input quality, engineering hours, review time, revision cycles, and final documentation. It should also identify the building type and project stage.

A successful result would strengthen Endra’s claim that one platform can compress electrical design without sacrificing oversight. Wide variation would show that benefits depend heavily on project conditions.

The second signal is Planlabs integration. Endra acquired a specialized team and technical engines, but mechanical capability remains on the roadmap.

Customers should watch for a working mechanical module, not only a demonstration. The important test is whether electrical and mechanical systems share constraints and coordinate inside one model.

Mechanical and electrical designs compete for limited space. Ductwork, cable trays, piping, equipment, access zones, and structural elements cannot occupy the same location.

A unified system becomes valuable when it resolves those relationships earlier. Separate automated modules would reproduce part of the fragmentation Endra says it wants to remove.

Progress toward the planned plumbing module will provide another check. Delivering it during 2027 would complete Endra’s stated MEP coverage, although completeness will still depend on workflow depth.

The third signal is customer expansion from trials into standard production. Named consulting firms create credibility, but adoption depth matters more than logos.

Buyers should look for firms using Power Studio on repeated projects, across multiple offices, and with documented review processes. Renewals and expanded deployment would indicate that the product survives real project pressure.

Customer behavior can also reveal whether Endra becomes a system of record or remains a specialized generation tool. The difference affects its strategic position against Autodesk and other automation vendors.

If firms store standards in Playbooks and use Endra throughout revisions, switching becomes harder. If they export a model after one automated task, established software retains more control.

Endra’s expansion into North America also raises a specific test. The platform must handle local codes, firm standards, and utility requirements without turning every new market into a bespoke implementation.

The company does not need identical automation everywhere. It does need a repeatable method for representing regional differences and validating updates.

Readers should also separate engineering assistance from autonomous engineering. Endra describes agents performing defined tasks while engineers control requirements and approval.

That model is credible because it reflects professional accountability. Claims that imply complete replacement would require a much higher level of evidence.

For engineering firms, the immediate decision is whether Power Studio can remove a meaningful block of repetitive work while fitting existing review practices. The answer will vary by project portfolio and internal standardization.

For software buyers, the most useful evaluation starts with a constrained workflow. Teams can compare model preparation, automated output, correction effort, and documentation quality against their existing process.

They should also test a substantial architectural revision. Revision handling will expose whether the system maintains connected engineering logic or merely accelerates initial generation.

For technical leaders, knowledge capture deserves equal attention. Playbooks only become an advantage when firms know who owns each rule and how changes receive approval.

Teams evaluating the Endra Power Studio launch should now follow the evidence, not the size of the funding round. Ask which projects reached delivery, how much expert review remained, and whether mechanical integration works across shared constraints.

Those answers will show whether Endra has built a durable engineering platform or an impressive automation layer. The Planlabs deal gives it more technical reach, while the Series A gives it time to prove that reach in production.