Independent loan officers and small mortgage shops are stuck between two bad options for their website. Build it on Squarespace or WordPress and spend the next year integrating forms, tracking, and the 1003 application by hand. Or skip the website entirely and lose to the lender across town who has one.
The BNTouch Website Builder is the third option. A mortgage-specific website module that lives inside the CRM, drops your forms and CTAs in natively, supports per-LO landing variants on the same domain, and integrates with the rest of the platform without third-party stitching. The setup happens “on the fly” per the team’s framing, and the most useful version of the tool is the one most loan officers do not configure.
From the demo: “Website builder, the website manager we’re actually going to create a website on the fly, I’ll do it live.” The Website Builder is a paid add-on module, not in the base subscription: “This doesn’t come with BNTouch when you have a basic subscription. If you want to add websites to your account that’s gonna be up here in the top right from the module section.”
Three pieces matter:
A visual editor with template support.
Native integration with every other BNTouch feature (1003, forms, CTAs, Property Sites).
Multi-LO support on the same domain.
Setup, step by step
Step 1: domain
From the demo: “Enter a domain name. This you can get from a website like GoDaddy.” The Builder does not register domains for you. You buy a domain elsewhere and point it at the BNTouch Website Builder’s DNS records.
Practical note. If you already have a site on WordPress or Squarespace, you have a decision to make: keep the existing site and use the Website Builder for landing pages only, or migrate the full site. We have seen both work. The “landing pages only” approach is the lower-risk option for shops with established SEO.
Step 2: pick a template
The Builder ships with mortgage-specific templates. Each template is a reasonable starting point. From the demo: “Templates and editing” cover the standard mortgage shop pages: home, loan products, about, contact, application.
Step 3: native CTAs and forms
This is the part that earns the module. From the demo: “All of your sort of features, forms, call to actions, anything, are native.” The 1003 application, the contact form, the rate alert opt-in, the live chat widget, the Property Sites integration. All of them drop into pages without third-party plugins.
Compare this to the WordPress version of the same setup. WordPress means a contact form plugin, a CRM integration plugin to get the leads into BNTouch, a separate plugin for the live chat, a manual link to the 1003 application, and an ongoing maintenance burden when any of those plugins update incompatibly with each other. The native Builder skips all of that.
Step 4: configure pages and navigation
From the demo: “We can actually add things to our dropdowns as well.” And: “Set pages up here as well for conversion.” The editor supports standard CMS operations: add page, add to navigation, add to dropdown, set as conversion page.
The multi-LO mechanic most teams under-use
This is the feature that justifies the module for a multi-LO shop. From the demo: “Same domain would actually switch up the website a little bit so that this has all of my user-specific information.”
What this means in practice. Your shop’s domain is, say, ourmortgage.com. Each LO gets a per-LO URL on the same domain, with their headshot, their bio, their phone number, and their 1003 application link. So:
ourmortgage.com/john shows John’s branding and routes leads to John’s pipeline.
ourmortgage.com/sarah shows Sarah’s branding and routes leads to Sarah’s pipeline.
ourmortgage.com shows the generic shop version.
The LOs hand out their personalized URL on business cards, in email signatures, in social media bios. Every lead from that URL is attributed automatically.
The HTML and source-code access
For shops with a developer or design preference, the Builder exposes source-code access. From the demo: “You can get into the source code if you wanted to do this with HTML, you have a developer, you can get in there, you can add tables, change the formatting.” This matters for shops that want to extend beyond the template defaults without abandoning the platform.
The Google-Maps auto-embed
One small detail with disproportionate value. From the demo: “If you have your business address in BNTouch connected with your BNTouch account, this will auto create automatically put in your address here for the Google Maps.” The site auto-embeds the location map without you typing your address into a maps widget. Address changes propagate everywhere the address appears.
Site analytics, GA-like
The Builder ships with native analytics. From the demo: “If you’ve ever used Google Analytics, it pulls information from there so it’ll look familiar.” This is about UI resemblance, not GA integration. The analytics show visitor traffic, page views, form completions, and conversion paths inside the BNTouch interface.
If you want true GA4 integration, you add the GA4 snippet through the source-code editor. Most shops we work with run both: the native BNTouch analytics for the daily view, GA4 for the long-tail analysis.
Multi-domain support
From the demo: “Any domain name that you own [can be aimed at the same BNTouch content].” Useful for shops running multiple brands, multiple geographic micro-sites, or A/B testing different domain experiences.
The Website Builder vs WordPress decision
Two reasonable answers to the question “should I run my mortgage website on the BNTouch Website Builder or on WordPress”:
Use the Website Builder if: you are a solo LO or small shop, you do not have a developer on retainer, you want zero plugin maintenance, you need per-LO landing variants, and you want the 1003 and forms to work natively without integration work.
Use WordPress if: you have existing SEO authority you cannot afford to migrate, you have a developer on retainer, you need a specific design or content management workflow the Builder does not support, and you are comfortable maintaining the plugin stack.
The hybrid path also works. Keep your existing WordPress site for the content marketing and SEO. Use the Website Builder for landing pages tied to your campaigns. The per-LO URLs especially work well as campaign landing pages.
What to set up first
Configure the domain DNS to point at the BNTouch Website Builder.
Pick a template that matches your shop’s brand.
Add the loan officer pages with per-LO URLs.
Drop in the 1003 application CTA on every product page.
Configure the BNTouch Connect chat widget on high-intent pages.
Turn on the auto-Google-Maps location embed.
What the Website Builder does not do
Two honest limits. The Builder is mortgage-specific. If you want to run a non-mortgage business on the same domain, the Builder is the wrong tool. And the Builder is not as customizable as a custom-developed site. If your brand has very specific design requirements that go beyond what the templates and source-code editing support, build elsewhere.
See the Website Builder live
The clearest evaluation is to see an already-built Website Builder site populated with real content and multi-LO URLs. Request a demo and ask the team to show you a live Website Builder site from a multi-LO shop.
