This section didn't finish loading
Something took too long to respond. Reloading usually fixes it.
— Capability · Revit and BIM export
A configurator with Revit and BIM export.
Architects do not buy from a cart. They place your product in a model, and a PDF does not go into a model.
SBFS builds configurators whose output an architect can drop straight into a BIM model. For NOMI we shipped a public API that turns any configuration into a native Revit family (.rfa) via cloud Revit, so architects place the exact configured piece inside their Revit model instead of working from a specification sheet. The same configurator serves retail buyers and trade designers from one catalog.
02— Fit
Who this is for
Architects specify your product
They are not comparing prices in a cart. They are placing your piece in a model, and what you hand them has to be placeable.
Your catalog is configured, not fixed
Every configuration is a different object, so a hand-built family library goes stale the moment the catalog moves.
One product, three kinds of buyer
The architect wants geometry, the designer wants trade pricing and saved projects, the retail buyer wants checkout. All from the same catalog.
03— Capabilities
What we build
Configuration to native Revit family
A public API turns any NOMI configuration into a native Revit family (.rfa) via cloud Revit, so architects place the exact piece they configured in their BIM model.
Generated on demand, not maintained by hand
The export comes off the live configuration, so it cannot drift from the catalog the way a manually curated family library does.
A trade and designer portal around it
NOMI trade users see Ex-GST designer pricing, team discounts and saved configurations, while retail users see standard pricing, from one configurator.
Specifications that reach the pipeline
NOMI quotes and orders sync two-way with Salesforce, so a specification that starts with an architect lands in the sales pipeline without being re-keyed.
05— Method
How an engagement runs
01
Week 1 · Scope and catalog audit
We model the product family, its parameters and the way your architects actually consume it today, then write the spec. You see it before we start.
02
Weeks 2 to 6 · Build to MVP
Configurator, export pipeline, trade portal, checkout and admin ship in parallel, with a reviewable demo every Friday in your own staging environment.
03
Week 6 · Production handoff
Deployed to your domain on your Vercel team and your Neon database. Your team is trained on the system, and we stay on retainer for tuning, not maintenance.
06— FAQ
Questions buyers ask before they commit.
07— Related
Related solutions
10 — Get in touch
Got a configurable product? Let us talk.
Fastest way to start
Book a 20-minute intro call
Pick a time that suits you — you'll get a Google Meet invite. We look at your product, your catalog, and whether a six-week Forge build is the right fit. No slides, no pressure.
See available times
See available times Rather send details in writing?juan@sbfs.co
Direct to Juan. Twenty-four hour reply, typically. If we cannot take your project on, we will tell you fast.
Product briefemails juan directly