You can sell Revit models online as digital products, but a useful offer is more than a family file or a download button. The buyer needs to know the Revit version, category, units, dependencies, permitted use and exactly what has been tested. Prepare a versioned release bundle, open it in a clean project, then deliver the approved archive after payment.
This workflow is for architects, BIM content creators and manufacturers selling Revit families, detail components or model libraries directly. It is narrower than a general CAD-file guide because Revit buyers need host-version compatibility, nested families, shared parameters and a clear distinction between a native editable model and a rendered preview.
Define the Revit deliverable before setting a price
Decide whether the customer receives one family, a category pack, a project template or a library subscription. State the Revit release, metric or imperial units, family category, detail level and whether the file is native, exported or only a reference image.
| Release field | Record before checkout | Why it matters |
|---|---|---|
| File identity | Family or library name, version and exact extension | Prevents a buyer opening the wrong release |
| Compatibility | Revit version, templates and required add-ins | A newer file may not open in an older release |
| Geometry | Host category, detail levels, visibility and types | A preview does not prove the family behaves correctly |
| Data | Shared parameters, schedules and type catalog | Buyers need to know what can be tagged or scheduled |
| Licence | Personal, project, studio or commercial reuse | A download does not automatically transfer ownership |
Autodesk describes Revit as a BIM application for design, documentation and coordination; that broad capability does not mean every family works in every project. Check the actual version and host context you advertise in the official Revit product documentation.
Build a clean-project compatibility test
Keep the working library private and create a buyer-facing release folder. Include the tested family files, a start-here PDF, a parameter map, a licence, a version note and a preview image. Remove client information, internal project geometry and unpublished source files.
Use this release test for each advertised family:
- Open a blank project in every Revit version you claim to support.
- Load the family and place it in the declared host category.
- Check type names, dimensions, visibility settings and detail levels in plan, elevation and 3D views.
- Test the parameters that a buyer is expected to edit, including units and type changes.
- Run a small schedule or tag test where the family promises shared parameters.
- Save a copy, reopen it and compare the filename and release note with the listing.
The checklist is an original planning asset for this article. It is not evidence that any particular family works until you run the test on that family and record the result.
Make the licence and preview agree
Separate the right to use a family in a project from the right to redistribute the family itself. A customer may be allowed to use a component in a project but not upload the original RFA to a public library or pass it to another studio. State whether project deliverables, client work, internal reuse and resale of the source file are allowed.
Show a rendered view or a screenshot of the family in a sample project, but label it as a preview. A render cannot prove parameter behavior, file version or schedule compatibility. If you have only inspected a file and have not tested it in a clean project, say so.
Deliver the model through PayRequest
Create a PayRequest digital product for the exact release bundle and attach the RFA files, ZIP archive or instructions that the buyer should receive. Use a payment link when you share one fixed family or library from a portfolio, newsletter or professional community. Put the Revit version, units, dependencies and licence scope on the product page before the checkout.
Rehearse four states: abandoned checkout, confirmed payment, download opened and a superseded release. PayRequest can collect the payment and deliver the configured file; it cannot validate a family, convert a Revit version, supply a missing add-in or enforce a licence against redistribution.
For an illustrative €29 library, PayRequest's Free plan has no monthly charge and applies 2% per successful payment, capped at €25 per transaction; provider fees remain separate. The amount is an example, not a market-price recommendation. Review current pricing and your connected provider's terms before publishing.
Measure completed payments, correct-version downloads, compatibility questions, support time, refunds and release corrections. The useful outcome is a buyer who knows what they received and can reproduce the advertised test—not a promise that one family will suit every project.
Editorial note: AI assisted with this article and its illustrative cover. The release checklist, compatibility matrix and €29 example are original planning tools; no live Revit-family test, customer result or legal conclusion is claimed.
