Resources and answers

Fair question. SS Technologies started in October 2026, so we don't have client references yet, and we won't invent them. Here's what you can check instead:

• browser demos of the rules our tools apply, on sample data
• a sample written scope and acceptance test
• published prices
• a written security and IP policy you can hold us to

You don't have to take a big risk to find out. We recommend starting with a $500 health check or a fixed-price pilot with a written acceptance test.

Yes. We recommend starting with a model health check ($500 per model) or a pilot ($750–$1,500). Both have fixed prices and clear deliverables, and the scoping call is free.

A small, fixed-price project that automates one task. We agree in writing what "done" means. For example: "creates all sheets for one data hall from the Excel list, with correct names and title block, and undoes cleanly." You test it on your own model against that written acceptance test.

If the pilot doesn't pass the written acceptance test on the agreed Revit version, we fix it at no charge. If it still doesn't pass within 10 business days of your test report, we refund the pilot fee in full. This doesn't cover changes to the scope, the test model or the Revit version after the scope is signed.

• A person who knows the task and can test the tool, for about 1–2 hours a week
• A sample model or access to one, after the NDA is signed
• Your standards documents, and any rule values your engineer of record sets
• Revit licenses for your users

More detail: what you provide.

Full Autodesk Revit or the AEC Collection. Revit LT doesn't run add-ins or Dynamo. Clash automation needs Navisworks® Manage, because Navisworks Simulate has no Clash Detective. Shared dashboards need Power BI licenses for viewers. Cloud jobs may use Autodesk Platform Services (APS) usage billed by Autodesk to your account.

Estimated times:

• Model health check: 3 business days after we get access
• Pilot: 1–2 weeks
• Data center family and template kit: 2–4 weeks
• Custom C# add-in: 2–8 weeks

Your written scope includes the date.

Written questions get a reply within one US business day. Live calls are scheduled within US business hours by arrangement, on Teams, Zoom or Google Meet. During a project you get a short demo every week, and one point of contact: the person writing your code.

We focus on US design and construction teams today. If you're in the UK, Europe or Australia, get in touch and we'll tell you honestly whether we can help.

• Model health check: $500 per model
• Pilot script: $750–$1,500
• Data center family and template kit: $2,500–$6,000
• Custom C# add-in: $4,000–$15,000
• Monthly retainer: $2,000–$4,000 a month

Within 2 business days of the call you get a written scope with a fixed price for a pilot or first phase, and an estimate range for anything bigger. The price changes only if you ask for changes, and we quote every change first. Prices exclude any applicable taxes. See pricing.

Because a big tool is easier to price well once the first phase is done and you've seen it work. You get a fixed price for the pilot or first phase, and an estimate range for the rest. Each later phase gets its own fixed price before work starts.

• We invoice in US dollars.
• Fixed-scope work is billed 50% to start and 50% on acceptance, due in 15 days.
• Health checks are paid when ordered.
• Retainers are billed monthly in advance.
• We accept ACH, wire, and card for smaller items.

On request we send a vendor onboarding pack: the tax form for our entity, banking details, and a certificate of insurance where required.

Tell us your contract's insurance requirements during scoping. We'll confirm before signing whether we can meet them.

Yes, with a monthly retainer:

• Essentials, $2,000 a month: 20 hours, first response within 1 business day
• Standard, $3,000 a month: 30 hours, first response within 1 business day from a priority queue
• Priority, $4,000 a month: 40 hours, first response within 1 business day, first in queue, plus a weekly live call

Unused hours roll over one month. Each tier includes model health checks, which are separate from the hours bank. Retainers are month to month with 30 days' notice. Retainer details.

Since December 8, 2025, some Autodesk Platform Services APIs (the Automation API, the Model Derivative API and others) are metered, with a free monthly tier. Paid use is by Autodesk Flex tokens, bought in a minimum of 100 and valid for one year (APS). AEC Data Model API "Data Out" pricing started October 6, 2026 (APS blog). Autodesk bills usage to your account, not ours. We estimate usage before we build.

Already have Model Analytics Essentials? Use it. It's included with Autodesk Forma Design Collaboration and automatically tracks Revit cloud models: sync times, file growth, version alignment, CAD imports, in-place families and unapproved content (Autodesk). Our check covers what a dashboard doesn't: models that aren't in the cloud, checks against your BIM standard and your owner's data center rules (asset IDs, A/B feed fields, schedules vs placed equipment), a person's read on root causes, and a fix list in priority order with a walkthrough.

• Work made only for you (your add-ins, scripts, content built to your standard, documentation): assigned to you in writing once paid in full. You get the full source code in your own Git repository, installers and documentation.
• Our reusable components, including the data center Revit kit: a permanent, firm-wide, royalty-free license to use and change them on any project. We keep ownership so we can keep improving them.
• Open-source parts (for example pyRevit, GPL-3.0): stay under their own licenses, listed in your handover.

There are no license keys and no license server.

Before any file changes hands, we sign an NDA: yours, after a quick review, or our mutual one. We never name your company or project publicly without written permission.

Where possible we work inside your environment, on an account you control: a project in Autodesk Forma (formerly Autodesk Construction Cloud), your SharePoint or your virtual desktop. We use multi-factor authentication on every account, take only the access the work needs, use separate credentials for each client, and store files encrypted, only for the project.

We delete your files from our systems within 30 days of close-out and confirm in writing. We keep only what the contract requires (the signed scope and invoices) and anything you ask us to keep for warranty work.

We don't put your models, drawings or project data into AI tools. We may use AI coding assistants on our own code, and a person reviews and tests every line before delivery. AI is used on your data only with your written approval, in tools you approve.

SS Technologies is a remote company. Before any file changes hands, we confirm in writing our registered entity and where your data would be accessed from, so you can check it against your contract (for example, US-persons-only access, background checks or CUI). If your project restricts who can see files, tell us on the scoping call.

No, and we say so plainly. What we do instead is written down on our security page: multi-factor authentication on every account we use, least access, separate credentials for each client, and files stored encrypted only for the project. Security questionnaires are welcome.

We build to prevent that. Our code-quality standard:

• Changes run inside Revit transactions you can undo.
• Bulk edits show a preview first.
• Tools log what they changed.
• We test on sample models and on a copy of yours.

As with any new tool, keep a backup or work on a detached copy the first time.

No. We never name your company or project publicly without written permission.

Revit 2024 through 2027, and 2023 on request:

• Revit 2024 (and 2023): .NET Framework 4.8, so we ship a net48 build.
• Revit 2025.0–.4 and 2026.0–.4: .NET 8, so we ship a .NET 8 build.
• Revit 2025.5+ and 2026.5+: the .NET 10 runtime. We ship the same .NET 8 build, which Autodesk expects to load but doesn't guarantee, so we test on both.
• Revit 2027: .NET 10, so we ship a .NET 10 build installed to Program Files.

If your team runs several versions, we build and test an installer for each. Microsoft ends .NET 8 support in November 2026. What that means for your add-ins.

Autodesk releases a new Revit version every year, and recent releases changed the runtime add-ins load into. Upgrades of tools we built are included in some retainer tiers, or we quote them as a fixed-price update. Because you own the source, any developer can do it too.

• Dynamo suits visual scripts your team may want to edit.
• pyRevit is quick for a company toolbar of small tools.
• A C# add-in is best for tools many people use daily, that need a real interface or speed, or that must handle Revit upgrades cleanly.

We'll recommend one on the scoping call, and sometimes the answer is a mix. Read the full comparison.

Some will, some won't. Dynamo 4.0 made PythonNet3 the default Python engine, replacing CPython3 (Dynamo release notes). Graphs written for the IronPython2 or CPython3 engines may need changes, especially where they use Excel or COM interop, WPF, collections or enums (DynamoBIM). We can review your library, list which graphs need work, and migrate them with tests.

Yes. We start with a free code review, then tell you plainly whether to port it or rebuild it, and give you a fixed quote. See add-in upgrades and migration.

Yes. You get an installer for each Revit version, and we document what it installs and where, so your IT team can roll it out with the tools they already use. For Revit 2027, all-user add-ins install to Program Files, which usually needs administrator rights.

Yes, with access you grant. We can work in a project in Autodesk Forma (formerly Autodesk Construction Cloud). On the scoping call we agree who supplies the Revit seat and the Autodesk Forma Design Collaboration entitlement for that work, and you can remove our access at any time.

Yes. For batch work across many cloud models we lead with Design Automation for Revit, part of the APS Automation API, with usage estimated before we build. Dynamo Switchboard, which runs graphs in the cloud, is an early-access beta (DynamoBIM), so we don't recommend it for production work yet.

No. We build software and Revit content. Our tools apply rules and values that your engineer of record provides. Their outputs are drafting and data aids, not engineering calculations, code-compliance reviews or sealed documents. Your licensed professionals review the results and remain responsible for the design.

We build tools, checks and Revit content rather than take on full project modeling. If you need production modeling, our tools can make your in-house team, or your outsourcing provider, faster at it.

No. Data centers are our specialty because they repeat so much, but the same tools work on any building type with repeated floors, rooms, equipment or whole buildings. See who we help.

No. SS Technologies is an independent company. We build tools for Autodesk software, but we're not an Autodesk partner and Autodesk doesn't endorse our services. See our trademark notice.

You'll have everything you need to carry on without us: full source in your repository, build instructions, documentation and a recorded walkthrough. There's no license server and nothing that stops working. We also take on a limited number of builds at a time. See how we work.