> For the complete documentation index, see [llms.txt](https://enercalc.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://enercalc.com/docs/efr-faq/overview-and-value/ive-tried-revit-connected-design-software-before-what-makes.md).

# What Makes EFR Different

I’ve tried Revit-connected design software before. What makes ENERCALC for Revit© different?

For most modern structural engineering firms, Revit is the nerve center of the entire production workflow. Revit is the home for all the information you receive from other design disciplines and the home for all the structural systems and sheets that you create. But most Revit-connected products create a fork in the road by pulling you out of Revit and forcing you to walk a tightrope to a secondary model which then needs to be managed. ENERCALC for Revit© is different because the entire focus is keeping you inside Revit to let you do what you do. One model and one intuitive linear workflow.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://enercalc.com/docs/efr-faq/overview-and-value/ive-tried-revit-connected-design-software-before-what-makes.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
