Two modules are live today, and they share one index of your project data:

1. NimbleFaçade, for ETTV reporting and envelope compliance.
2. DocuMentor, for automated audits across document sets.
3. Both read the files your team already produces.
4. Further modules build on the same data layer.

You can start with one and add the other without re-indexing anything.

Sid reads the model and document set you already produce. There is no migration:

1. Point Sid at a collection and it indexes the files.
2. It runs the audits you choose.
3. Results trace back to the source document.
4. Your data stays in your environment.

Nothing about how your team models or documents has to change.

Work that used to take a fortnight of someone's time now runs in an afternoon:

1. ETTV computed per orientation.
2. Every facade module carries a value.
3. One assembly library across studies.
4. Output formatted ready for submission.

The time saved goes back into the design rather than the paperwork.

You do. Sid processes your project data, it does not acquire it:

1. Files stay inside your environment.
2. Nothing is used to train shared models.
3. Access follows your existing permissions.
4. Results are exportable at any time.

If you stop using Sid, your data and your outputs remain yours.

Placeholder answer. Most teams are running their first audit inside a day, because Sid indexes the files where they already sit.

Placeholder answer. No. Sid reads the model and document set your team already produces.

Placeholder answer. Envelope compliance is computed to the code set for the project market.

Placeholder answer. Inside your own environment. Sid processes your project data, it does not take custody of it.

Placeholder answer. Pricing is per project, and scales with the number of modules you run.

Placeholder answer. Yes. We run a pilot on one of your live projects before any commitment.