New-Home Sales ยท Chapter 02 of 10
The builder's systems, and what you can run yourself
You will never log into most of the software that runs a builder's business. This chapter draws the line between what you touch, what routes to you without your control, and the narrow lane where your own tools, Claude included, are allowed to work.
A builder's technology stack is two businesses running on the same brand. One side builds houses: scheduling, trades, supply chain, cost. The other side sells them: the CRM, the sales-center kiosk, the listing feeds, the buyer's self-serve portal. You live entirely in the second layer, and even inside it you only see a slice. This chapter maps every system a rep is likely to hear named in a training session, sorts what you touch from what you never will, tracks a lead from the click that created it to the moment it reaches you, and sets the one rule that governs any personal AI tool, including Claude, near buyer data.
The two layers
Back office and construction systems run the build. You may hear their names in a sales meeting, but you do not have a login, and nothing in this guide asks you to get one. Sales and marketing systems are the ones you actually work in every day, or that work on your behalf whether you asked or not.
| Layer | Job | Named systems |
|---|---|---|
| Back office and construction | Scheduling, trade coordination, supply chain, cost tracking, executive analytics | Hyphen BuildPro, SupplyPro, and BRIX claim; ECI MarkSystems as the builder's ERP claim; Constellation Stella AI, an executive and operations analytics agent announced 2026-02-10, not sold as a sales-rep tool claim |
| Sales and marketing | Lead capture, registrant records, follow-up, kiosk and site-map tools, listing syndication, the buyer's own self-serve path | Lasso CRM, Hyphen CRM, Sales Simplicity, Sales1440, Anewgo Sales Center App, NterNow, Zillow Promoted Communities, myLennar, MyPulte, AtlasRTX or Verse chat |
Notice what is missing from a public search for either layer: no builder in this research publishes a company-wide AI-use policy for sales staff. NAHB, the industry's own trade group, is actively encouraging adoption rather than restricting it, naming ChatGPT, Claude, and Perplexity by name in a January 2026 beginner's guide as low-risk starting points for clearer emails and plain-language explanations, with no data-handling guardrail attached verified. That gap is covered later in this chapter, and again in Chapter 09.
Every system, in one table
What follows is not a buying guide. It is a map of what a rep touches directly, what routes through a system without a rep's hands on it, and what a rep is structurally locked out of. None of these vendors publish public list pricing; access and configuration are set by the builder, not the individual rep.
| System | What it is | What the rep touches | What the rep never sees |
|---|---|---|---|
| Lasso CRM (ECI) | Builder-side sales CRM used across 500+ builders and developers claim | Registrant records, the lead inbox, follow-up tasks, real-time alerts when a prospect registers, a prospect-rating view for prioritizing hot leads, and a rep-level CSV or Excel export of the rep's own reports claim | The nightly bulk "Lasso Data Export Service" feed used for external reporting, other reps' pipelines, and any manager-level rotation logic report |
| Hyphen CRM | Lead capture and campaign tool from Hyphen Solutions, the same company behind BuildPro/SupplyPro/BRIX claim | Lead capture, drip and newsletter campaigns, open and click reports, and the design-selection handoff into Chameleon Power claim | The BuildPro/SupplyPro construction-scheduling side it sits next to inside the same vendor family claim |
| Sales Simplicity (ECI) | Cloud sales-cycle CRM and automation tool for production builders claim | The sales cycle for the rep's own buyers | Salesperson-performance dashboards and neighborhood trend comparisons built for sales management, not the rep claim |
| Sales1440 (Constellation) | Lead-to-contract workflow tool tracking lots, plans, and options claim | New leads, follow-up tasks, the buyer's lot and option selections, and auto-generated sales contracts for the rep's own deal claim | The ERP and estimating data it integrates with on the back end claim |
| Anewgo Sales Center App | Interactive plan browser and kiosk app running on the sales-office TV, tablet, or the builder's own site claim | The same plan browser a buyer uses; named webhook events fire when a buyer registers, signs in, builds a brochure, or favorites a home, and those signals can land in the rep's CRM in real time via Zapier or a direct Lasso connection verified | The nightly ingestion of pricing and lot data from the builder's own ERP, and the XML feed configuration that pushes availability out to NewHomeSource, Zillow, Realtor.com, Homes.com, BDX, and NoviHome verified |
| NterNow | Self-guided touring and smart-access system for spec and model homes claim | A verified-lead notification once a buyer completes ID scan, background check, and two-factor phone verification, in place of physically unlocking the door claim | The identity-verification and background-check process itself, which runs entirely inside NterNow before a rep is ever notified claim |
| Zillow Promoted Communities | New-construction placement on Zillow-owned sites with a "Contact Builder" lead form claim | Leads routed to a rep-specific email or phone number the builder sets per community, plus spend and performance visible in the Builder Dashboard claim | Builder Boost's native-ad and Facebook-retargeting spend, which is a marketing-team decision, not a rep-level one claim |
| myLennar / MyPulte | Self-serve purchase flows: shop, customize, price, and sign a purchase agreement online claim | A "New Home Consultant" role name attached to buyers even when they start entirely online, and the buyer's completed configuration once they reach that point claim | Nothing structurally hidden here; the point of this system is that a buyer can complete the whole purchase without a rep at all claim |
| AtlasRTX / Verse chat | AI web-chat and SMS assistant answering buyer questions on builder sites, merged under Verse.ai (NiCE) in 2026 claim | Whatever the chat hands off as a qualified lead; KB Home's company-wide "BuilderBot" is the flagship named deployment, and CBH Homes, Smith Douglas Homes, and Eastwood Homes are also named clients with vendor-claimed conversion and response numbers claim | The chat's own conversation logic and any lead-scoring model behind it |
No public builder AI policy for sales staff was found anywhere in this research, and Stella AI, the one named builder-AI product aimed at leadership, is explicitly framed as finance and operations facing, not a sales tool claim. That silence matters more than any single row in this table: assume the builder has not written the rule yet, and ask.
The lead's path, from click to rep
A lead's speed and routing depend entirely on its source. Some sources publish exactly how routing works; most do not, and this table says "not published" rather than guessing.
| Source | Who routes it | How fast it reaches you | What to check first |
|---|---|---|---|
| Builder's own site | The builder's CRM, per its own configuration | Not published in this research; ask your sales manager how your site's lead form is wired | Which community and plan the lead was viewing when they submitted the form |
| NewHomeSource / BDX | Delivered to the builder by email, JSON via API, XML, or text file; internal assignment to a specific rep is set by the builder inside its own CRM, not published by BDX claim | Not published; BDX's own inventory feed imports the next business day, but lead delivery speed is a separate mechanism not stated publicly claim | The lead-comments field, which BDX standardizes to show what the shopper actually asked for: an appointment, design options, or promotions claim |
| Zillow Promoted Communities | The builder explicitly designates routing, down to a specific agent email or phone number per community, inside the Builder Dashboard claim | Not published as a specific speed, but the routing is direct to the named rep, not a shared inbox claim | Which community's Builder Dashboard the lead came through, since routing is set per community, not per builder |
| Realtor.com | Not published in this research | Not published | Whether the lead came through the New Construction division or a general search; ask your manager how the two are handled differently, if at all |
| Homes.com | Not published in this research | Not published | Whether the builder profile page routes to your CRM automatically or to a shared inbox someone forwards from |
| Chat (AtlasRTX / Verse) | The chat qualifies the conversation, then hands off to the builder's CRM; exact routing logic to a specific rep is not published claim | Vendor case studies describe high response and engagement rates but do not publish a lead-to-rep delivery time claim | Read the full chat transcript, if your system surfaces it, before your first call. It tells you what the shopper already asked and was already told. |
| Self-tour (NterNow) | The system itself notifies the rep once identity verification is complete | Real time: the rep gets a verified-lead notification as the tour happens or immediately after, in place of manually opening the door claim | The tour timestamp; about 25% of NterNow tours happen outside standard staffed hours, so this may be your first knowledge of the visit claim |
| Walk-in | You, in person, at the moment of the greeting | Immediate | Whether the visitor has a buyer's agent, asked before anything else, since an unregistered walk-in can permanently affect who is recognized on that deal |
What you may take out of the CRM
Lasso publishes rep-level export in two forms: on-demand reports exportable to CSV or Excel from inside the Sales Center, and a separate nightly "Lasso Data Export Service" that delivers raw CSV files for external reporting tools verified. Neither of the other named CRMs in this chapter, Hyphen CRM, Sales Simplicity, or Sales1440, publishes export specifics on its own marketing pages; that is more likely thin public documentation than a missing feature, so ask your sales manager what your own system allows rather than assuming it matches Lasso.
Registration cards are the other thing you legitimately hold: the buyer's own signed acknowledgment that they registered with you, on that community, on that date. Keep your copy. It is the only proof you have if a co-op position is ever challenged.
The honest rule, stated plainly: buyer PII stays inside builder-approved systems. Your personal AI use, Claude included, runs on your own notes and the community file from Chapter 01, not on exported buyer records, unless your builder's IT policy explicitly says otherwise. No public builder IT policy naming AI tools was found in this research report, which means the safest working assumption is that none exists yet at your builder, not that it is silently permitted. Ask the questions in the checklist below before you paste a single registrant's name, phone number, or email into any tool your builder did not provide.
The sales-center kit
The kiosk, the interactive site map, the Matterport tour, and the lot-availability board are the physical and digital furniture of your sales office, and buyers now expect to interact with all of them before they ever talk to you.
- Kiosk and interactive plan browser (Anewgo). Runs on the sales-office TV, tablet, or website. The same webhook events that notify your CRM when a buyer favorites a plan or builds a brochure are the earliest signal you get that a walk-in was already shopping before they arrived verified.
- Interactive site map and lot reservation. Buyers browse real-time lot status, price, and elevation, and can reserve a lot online with a credit card in systems like ECI's LotVue claim. If your kit includes this, a buyer may arrive already knowing more about current lot status than the printed sheet on your desk.
- Matterport tours. A single scan of a model or quick-move-in home becomes an interactive dollhouse and walkthrough view, used heavily before a physical model even exists claim. Send the link ahead of a visit rather than making a buyer wait for the in-person walk.
- Lot availability. Whatever board, sheet, or screen shows current lot status, it is only as good as its last update. Treat it the same way you treat a price sheet: verify before you quote.
Keeping it current is a discipline, not a system feature. A stale plan browser or an outdated lot board actively works against you, because it can tell a buyer something the phone call you're about to make would contradict.
The builder's own self-serve buying flows
myLennar and MyPulte both let a buyer complete a purchase agreement entirely online: pick a floor plan, choose elevation and interior options, see a total price, generate the agreement, put down a deposit, and finance through the builder's own affiliated lender, without ever visiting in person or speaking to a rep claim. Lennar's flow still attaches a "New Home Consultant" name to the buyer even when they start online, and Pulte's own current pages describe the same end-to-end path first reported in 2021 claim.
This is not a threat to route around; it is a fact about your job. The builder already built the fastest possible path for a buyer who wants zero human contact. Your value has to sit somewhere that flow cannot reach: reading a hesitant buyer's actual objection, walking a lot in person and pointing out what a floor plan on a screen cannot show, negotiating an incentive inside the rules, and being the person a buyer calls when the online flow gives them a number they don't understand. Be the human the flow cannot be, not a slower version of the flow.
Claude workflow: read the lead before you call
Trigger: a new registrant lands in your CRM inbox, or a walk-in registers before you sit down together.
What Claude prepares: a 60-second brief that summarizes the registration card's stated fields (must-haves, budget range, timeline, agent status) alongside the relevant section of the community file from Chapter 01, so you walk into the call or the appointment already knowing the plan inventory and current incentive without having to re-read two documents cold.
What the human checks and does: confirms nothing outside the registration card and the community file made it into the brief, since both of those are documents you control and pasted in yourself, not an export pulled from the CRM's buyer records.
What is never automated: pulling buyer data out of Lasso, Hyphen CRM, or any builder system on Claude's own initiative. Claude reads what you paste; it does not fetch.
Claude workflow: keep the sales-center kit current
Trigger: this week's price sheet or lot-availability update comes down from your sales manager.
What Claude prepares: a draft of the weekly plan-and-lot update note, comparing this week's price sheet against last week's so the changes (price moves, homes gone, new releases) are called out plainly instead of buried in a full re-read of the sheet.
What the human checks and does: verifies every number in the draft against the actual price sheet before it updates the kiosk, the printed lot board, or anything a buyer will see, since the sheet you paste in is only as current as the moment you copied it.
What is never automated: the physical or system update to the kiosk, site map, or lot board. Claude drafts the summary; you make the change.
Claude workflow: ask IT the right questions
Trigger: you want to use Claude, or any personal AI tool, on something closer to buyer data than your own notes and the community file.
What Claude prepares: a short, specific checklist to bring to your builder's IT or compliance lead, built from the gap this chapter documents: no public builder policy on personal AI tools and buyer PII was found anywhere in this research. Sample questions: Does our CRM's terms of use permit any browser assistant or automation tool inside a signed-in session? Is there an approved list of AI tools for sales staff, and does it include a data-handling addendum? Does exporting my own registrant reports to a personal device or personal account violate any policy? If I use an AI tool for drafting only, on data I typed myself rather than exported, is that treated differently?
What the human checks and does: asks these questions in writing, keeps the written answer, and treats "no policy exists yet" as a "no" until it changes, not as an opening.
What is never automated: the decision itself. Claude can draft the questions; only your builder's IT or compliance lead can answer them, and only you can decide to wait for that answer before touching exported buyer data with any personal tool.
What stays human
- Getting your builder's IT or compliance answer in writing before any exported buyer record touches a personal tool, Claude included.
- Verifying every price, incentive, and lot status against the current sheet before it reaches a kiosk, a site map, or a buyer's ears.
- Asking whether a walk-in has a buyer's agent, before anything else, every single time.
- Deciding what actually gets exported from the CRM and where it goes afterward.
- Every phone call, appointment, and negotiation the self-serve online flow was built to replace.
Do this today
- Write down which named systems from the table above your community actually runs, and note which ones you have never been shown a login for.
- Pull your builder's registrant export and confirm exactly what it contains, in CSV or Excel, before you assume you know.
- Draft the IT and compliance checklist above and send it to your sales manager or IT contact this week, even if you don't expect an answer immediately.
Sources
- ECI, Lasso CRM lead management, ecisolutions.com/products/lasso-crm/features/lead-management, retrieved 2026-09-04
- Support Lasso CRM, Lasso Data Export Service and Sales Center Export Registrants help articles, support.lassocrm.com, retrieved 2026-09-04
- Lasso CRM Zapier integration, lasso.io/articles/5-things-you-can-do-with-lasso-zapier; zapier.com/apps/lassocrm, retrieved 2026-09-04
- Hyphen Solutions, Hyphen CRM product page, info.hyphensolutions.com/products/hyphen-crm, retrieved 2026-09-04
- ECI, Sales Simplicity product page, ecisolutions.com/products/sales-simplicity, retrieved 2026-09-04
- Constellation HomeBuilder Systems, Sales1440 product page, constellationhb.com/products/sales1440, retrieved 2026-09-04
- Anewgo, Sales Center App webhooks and XML feeds documentation, docs.dashboard.anewgo.com, fetched 2026-09-04
- NterNow, nternow.com/home-builders; Fine Homebuilding, finehomebuilding.com/2026/04/20/smart-access-for-spec-homes, retrieved 2026-09-04
- Zillow, New Construction Promoted Communities training page, zillow.com/resources/new-construction/training/promoted-communities, retrieved 2026-09-04 (search snippet; direct fetch returned HTTP 403)
- Lennar Resource Center, resourcecenter.lennar.com/homebuying/homebuying-journey; Lennar Mortgage, lennarmortgage.com/digital-mortgage, retrieved 2026-09-04
- Pulte, pulte.com/buying-a-new-home-online; CNBC, cnbc.com/2021/06/24, retrieved 2026-09-04
- AtlasRTX / Verse.ai case studies, atlas.verse.ai/case-studies; AtlasRTX, KB Home partnership press release, atlasrtx.com, fetched 2026-09-04
- NAHB, beginner's guide for builders using AI, nahb.org/blog/2026/01/beginners-guide-for-builders-using-AI, fetched 2026-09-04
- Constellation HomeBuilder Systems, Stella AI announcement, constellationhb.com/our-news, retrieved 2026-09-04
- BDX, thebdx.com; NewHomeSource XML Data Integration Guide, zondalive.com, retrieved 2026-09-04
Starting from zero? Use the field manuals first.
02 · BEFORE YOU BUY SOFTWARE
If you're still choosing the buyer, offer, stack, agents, content, customers, and delivery, don't start with a tool: start with the manuals. These create local worksheets only: no checkout, outreach, or account setup.
Find the first manual
Not sure which guide to open first? Start from your stuck point and let the finder recommend the next manual and the first worksheet question. No personal data is collected: it just points you at the right starting move.
Work the starter pack
Move through buyer, offer, stack, agents, content, customers, and delivery as a sequence of short local worksheet sessions. One artifact at a time, in order, so you build the business instead of browsing for it.
See what "done" looks like
Read a fully worked field manual before writing your own version, so the output feels concrete: a real, numbered workflow with the risky steps gated, not a fake proof claim.