Fixed price
The price in your scope is the price. If you ask for something new, we quote it as a change before doing it. Nothing is billed without your OK.
How we work
How we work: scope, pilot, build, support
You know the price, the date and what "done" means before we write a line of code. Here is each step of an Autodesk® Revit® software automation project with us, what we need from you, and our terms in plain English.
The six steps
From first call to a tool your team owns.
Every project follows the same steps, whether it's a $750 pilot or a full add-in. Times are estimates; your written scope sets the dates.
Scoping call
Show us the task. We ask how often it happens, how long it takes and who does it. You get honest advice, even if the answer is "don't automate this yet".
30 min · freeWritten scope
A short scope in plain English: deliverables, a written acceptance test, a fixed price for the pilot or first phase, an estimate range for anything bigger, and a date.
within 2 business daysPilot or build
We build on a copy of your model. You see a short demo every week and can try early versions yourself. You get a working tool on your test model.
est. 1–8 weeksAcceptance
You run the agreed test on your model, with us on the call if you like. Pass, and you sign off. Fail, and we fix and re-deliver.
up to 5 business daysHandover
Source code in your Git repository, an installer for each Revit version, a short user guide, a recorded walkthrough and the build steps. Everything you need to own it.
at acceptanceSupport
A 30-day bug-fix warranty after acceptance. After that, an optional retainer or a quoted fix when you need one.
ongoing
| Offer | Estimated time | What "done" looks like |
|---|---|---|
| Model health check | 3 business days after access | PDF report, Excel issue list, fix list and a 30-minute walkthrough |
| Pilot script | 1–2 weeks | One task automated and passing its written acceptance test |
| Data center kit | 2–4 weeks | Families, shared parameters and template, checked against the QA checklist |
| Custom C# add-in | 2–8 weeks | Installer per Revit version, source code, guide and video, passing its acceptance test |
What "done" means
A written acceptance test, agreed before we start.
The acceptance test is a short list of checks, written in plain English, that the tool must pass on your test model and your Revit version. We agree it with you in the scope, before any code is written. At the end you run it, line by line, and each line passes or fails.
It protects both sides. You know exactly what you're paying for. We know exactly what to build. Nobody argues later about what "finished" meant.
Our pilot guarantee
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.
Example acceptance test
Rack rows and IDs pilot
On the client's test model in Revit 2026:
- the tool places all racks listed in the input table;
- every rack gets an ID in the hall-row-position scheme, such as
DH1-A-03; - there are zero duplicate IDs;
- the clearance report lists every aisle narrower than the 4 ft (1.2 m) minimum the client set;
- one Undo restores the model.
Example for illustration. The clearance value comes from the client's engineer of record.
How we communicate
One person, regular demos, no surprises.
- One point of contact: the person writing your code. No account managers, no hand-offs.
- Written replies within one US business day by email.
- Live calls scheduled within US business hours by arrangement, on Teams, Zoom or Google Meet.
- A short demo every week during projects, live or recorded, so you see progress on real screens.
- A shared task list, so you always know what's done and what's next.
- Changes in writing. Any change is quoted before we do it.
What you provide
What we need from your side.
- A named 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. A detached copy is best for building and testing.
- Your standards: your BIM standard, the owner's naming or ID scheme, title blocks and any rule values the tool must apply.
- Rule values from your engineer of record when a tool checks things like clearances, capacities or redundancy.
- Revit licenses for your users. Full Autodesk Revit or the AEC Collection. Revit LT doesn't run add-ins or Dynamo.
- A workstation for the acceptance test with the agreed Revit version installed.
Working in your cloud models
If the work happens inside your cloud-hosted models, your firm adds us to the project on an account you control, and you can remove our access at any time. Working in those models takes a Revit seat and, for cloud worksharing, an Autodesk Forma Design Collaboration (formerly BIM Collaborate Pro) entitlement on that account. We agree on the scoping call whether you assign them or we bring our own, and the written scope states it, so nothing is assumed.
Capacity & continuity
A founder-led firm, planned for.
You work directly with Shreyansh Shende, who scopes the job, writes the code, runs the acceptance test with you and supports it afterwards.
We take on a limited number of builds at a time so every client gets real attention. If the founder is unavailable, you already hold the source, build steps and a recorded walkthrough.
What you hold from handover onward
- Full source code in your own Git repository
- Build steps, so another developer can compile and change it
- A recorded walkthrough of how the tool works
- A short user guide for your team
- An installer for each Revit version you run
- No license keys and no license server, so nothing stops working
Engagement terms
The terms, in plain English.
These are the terms we work on. Your signed scope, and for larger projects a short master services agreement, put them in writing.
Payment
Fixed-scope work: 50% to start, 50% on acceptance, due in 15 days. Health checks are paid when ordered. Retainers are billed monthly in advance. All prices are in US dollars and exclude any applicable taxes. We accept ACH, wire, and card for smaller items.
Acceptance
You test against the written criteria within 5 business days of delivery. If it fails, we fix and re-deliver.
Pilot guarantee
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.
Warranty
A 30-day bug-fix warranty after acceptance. A bug is anything where the tool doesn't do what the scope says on the agreed Revit versions.
Who owns what
- Work made only for you (your add-ins, scripts, content built to your standard, documentation): assigned to you in writing once paid in full.
- 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.
Confidentiality
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.
Your data and AI
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. Security details.
Close-out
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.
Stopping early
If you stop a fixed-scope project, you pay for work done to date and receive everything built so far. Retainers are month to month with 30 days' notice.
Revit upgrades
Autodesk releases a new Revit version every year. Upgrades of tools we built are included in some retainer tiers, or quoted as a fixed-price update. Because you hold the source, any developer can do it.
Contract and paperwork
Larger projects use a short master services agreement. Liability is capped at fees paid. Tell us your insurance requirements during scoping, and we confirm before signing whether we can meet them. A vendor onboarding pack is available on request: the tax form for our entity, banking details, and a certificate of insurance where required.
Not included
What we don't do, so you can plan for it.
- Engineering design, calculations of record or code-compliance reviews
- Stamped or sealed drawings
- Autodesk licenses for your team
- Autodesk Platform Services (APS) usage fees, which Autodesk bills to your account
- Full project production modeling
- On-site work
Need production modeling? We can make your modeling team, or your outsourcing provider, faster with tools and content.
Engineering responsibility
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.
Process questions
Questions buyers usually ask about the process
What if we need a change halfway through?
Tell us. We write up the change with its price and any effect on the date, and you approve it before we do the work. Nothing is billed without your OK.
What if the tool fails the acceptance test?
We fix it and re-deliver. For a pilot, if it still doesn't pass within 10 business days of your test report, we refund the pilot fee in full.
What if our Revit version changes during the project?
The scope names the Revit versions we build and test for. Moving to a different version after the scope is signed is a change, and we quote it first. If your team runs several versions, tell us on the scoping call and we build and test an installer for each.
Could a tool damage our model?
We build to prevent that. Changes run inside Revit transactions you can undo, bulk edits show a preview first, and tools log what they changed. We test on sample models and on a copy of yours. As with any new tool, work on a detached copy the first time.
Can we see a scope before we commit?
Yes. Read our sample scope for a fictional pilot. Your own scope arrives within 2 business days of the scoping call, and there's no obligation to sign it.
Free 30-minute scoping call
Have a Revit task your team repeats every week?
Tell us about it. 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. No obligation.