March 2026

Developers can now define the fees attached to a lot, stage by stage, and track deposits, invoices, and payments against each one. The money owed on a lot lives on the lot instead of in a side spreadsheet.

• Fees are set per stage, so a deposit taken at contract and a balance due at closing are tracked separately on the same lot.
• A builder fee register lists every fee a builder owes across a community, with what has been paid and what is still outstanding.
• Fee position carries through to the lot record, the lot status map, and the closings report, so it is visible wherever the lot is being worked.
• Fees due on a lot are surfaced in the architectural review workflow, so a builder submitting a home sees what is outstanding on that homesite.

Developers and builders now work the same community map in lot pool mode. Developers see which lots are released to the pool and who is holding them, and builders see what is open to them and can reserve a homesite directly from the map.

• The map runs in a developer view or a builder view, so each side reads the pool from its own position without a separate report.
• A reservation is placed from the map and carries a start and end date, so a hold on a lot has a defined term rather than sitting open indefinitely.
• Lot pricing is carried into the pool view, so a builder can weigh cost while choosing from what is available.

Sales teams can now see the whole path from traffic to closing in one view - visitors and leads at the top, sales at the bottom - and read exactly where a community is losing people.

• Leads and walk-in traffic combine into a single top-of-funnel count, and leads are matched to the sales they turned into.
• The funnel can be narrowed to one builder, so each builder's conversion can be judged on its own rather than against the community average.
• The funnel sits on the main dashboard next to the overview report, and the full breakdown exports to Excel.

Builders and marketing teams can now group floorplans into named collections - a series, a product line, a price band - and manage them alongside the plans themselves, so homes are presented to buyers the way the builder actually sells them.

• Collections are created and edited in the same place as the floorplans, so a plan picks up its collection as it is added to the community.
• Base pricing is published with each plan, so a collection can carry a starting price.
• Collections are available to the public inventory map and widget, ready to drive how buyers browse plans.

Builders running Microsoft Dynamics 365 can now connect it to Pipsy. Lot records sync across on their own, so a community's inventory stays current without anyone re-keying it into two systems.

• Sections and lot types that do not yet exist in Pipsy are created as part of the sync, so a new phase coming out of the builder's system does not stall the run.
• Deals and contacts pushed to HubSpot carry their relationship labels, so a buyer, a co-buyer, and a cooperating agent land on the record in the right role.
• Reminder emails can be switched off for an individual builder contact, so someone who works out of their own system is not chased twice.

Community managers can now maintain the approved color and material schemes for a community and set the defaults on each elevation, so an architectural submittal arrives pre-filled with what the builder actually intends to build.

• Schemes are created and edited in one place, with the colors and materials that make each one up held together.
• Every elevation carries its default colors and materials, and those values fill in automatically when a builder submits a lot, leaving reviewers to check the exceptions rather than re-read the whole submittal.
• The elevation list on a submittal narrows to the elevations that belong to the plan chosen, so a builder cannot submit a combination that does not exist.
• A material outside the approved list can be typed in directly when a builder needs a one-off.

Builders can now open their own lot contracts in Pipsy and read the takedown terms and fee structures that apply to them, instead of asking the developer for a copy every time a question comes up.

• Each builder sees the contracts it is a party to and nothing else, so one portal serves every builder in the community.
• Additional fee structures are supported on a contract, so the view reflects how the deal was actually written rather than a standard template.
• Developers are kept in a single list, so the counterparty on a contract is chosen consistently across land development and lot takedown deals.

Marketing teams can now tune what buyers see on the public inventory site community by community - how resale homes are labeled, which homes carry a featured or premium badge, and whether open houses and driving directions appear at all.

• Featured and premium homes stand out in the listing and on the map, and a community can relabel resale inventory in its own words.
• Open house dates show on a home's detail page, and a directions button opens turn-by-turn routing to the homesite.
• Default sort order and the layout of the listing grid are set per community, and buyers can generate a PDF of a home to save or share.
• Amenities and area features can be assigned to a subdivision, so the map shows the ones that actually belong to that neighborhood.

Sales teams can now read week-by-week traffic performance and see what prospects are actually asking for, broken out by neighborhood, home type, and lot type.

• A weekly analysis table summarizes traffic and conversion week over week, and it is open to every user rather than a handful of executives.
• Prospect charts show demand by neighborhood, home type, and lot type, so product and pricing decisions can be made against what buyers are asking for.

Inventory reporting now separates lots a builder already holds from lots that are genuinely open, and adds sale velocity and move-in timing by home type, so supply conversations with builders start from the same numbers.

• A builder assigned only column runs through the inventory health and sellout reports, so committed lots no longer read as available supply.
• Builder inventory supply adds sale velocity by home type and an expected move-in date on every row.
• Supply and demand charts can be read with direct sales included or excluded, and absorption is calculated the same way in the chart as in the table behind it.
• Homes that have arrived on site are called out and color coded in delivery tracking.

The realtor report now shows each cooperating agent's share of community sales and counts bustouts alongside closings, so sales teams can see which agents actually produce.

• A share-of-sales column ranks agents by the percentage of the community's sales they brought in.
• Bustouts are counted in an agent's statistics, and a sale transferred to another agent no longer inflates the original agent's numbers.
• Agent names fill in automatically from the license number given at registration, so agents entered in a hurry still report by name.

Development teams that run their schedules in SmartSuite can now keep master plans and lot plans in step with Pipsy automatically, so the planning board and the lot record stop drifting apart.

Community managers can now pause a builder's architectural submissions in a specific community, so a builder that is out of compliance cannot keep sending new homes through review until the issue is settled.

• The pause is set community by community, so a builder can keep working where it is in good standing while it is held in one place.
• The block applies at submission, which keeps paused work out of the review queue instead of leaving reviewers to sort it out.

Marketing teams can now search a builder's listing feed by plan name or address to confirm what that builder is publishing to the market, without going to the builder for a list.

• Search results show the plans and addresses a builder currently has live, which makes it quick to spot a home missing from the community's public inventory or priced differently than expected.