June 2026

Development teams can now run a project in Pipsy from the deal through delivery - acquisition pipeline, entitlements, phase schedules, and pro forma sitting against the same homesites the sales side works from, instead of in a spreadsheet nobody else can see.

• A program dashboard and an action center show every active project, what is due next, and where a phase has slipped, with a schedule view for the milestones behind each phase.
• Engineers, consultants, and contractors can be given their own sign-in to a vendor portal, so they submit and follow their work without an account on the rest of the platform.
• Project and phase boundaries are drawn straight onto the map, with current site imagery and terrain underneath, so acreage and phasing come from one shape rather than a separate exhibit.
• Access is granted from saved permission profiles, so a new development user is set up in one step instead of switch by switch.

A community can now run an open lot pool, where several builders sell from the same set of homesites and a lot is assigned to a builder only when a buyer commits to it. Sales managers approve each commitment, and from that point the lot belongs to the builder that sold it.

• Commitment can be deferred until after the contract is written, so a builder is not forced to claim inventory before it has a buyer for it.
• Cancelling or closing a contract is limited to the builder that holds it, so builders working the same pool cannot act on each other's deals.
• Transfers between builders are turned off on pool communities, because assignment now happens through commitment instead.
• Inventory lists and the lot status map carry pool filters, so a builder can separate the lots it controls from the lots still open to everyone.

Sales teams can now work a homesite from the hold through to a signed contract in one place. Each reservation keeps its own history, active and expired holds are listed separately, and a reservation converts into a contract with the buyer and builder already carried across.

• Placing, extending, expiring, or releasing a hold notifies the people responsible for it and is written to the homesite's activity history, so there is a record of who held what and for how long.
• A converted reservation stays linked to the sale it became, so the path from hold to contract can be followed without matching records by hand.
• An all-reservations table lists every hold with its status, section, and salesperson, and sales managers get the same list narrowed to their builders.
• Administrators choose which alerts each person receives, user by user, so reservation and closing notices reach whoever acts on them.

Buyers can now shop a community by what surrounds it. Selecting an amenity frames the map on it and shows what is nearby, while a live inventory list beside the map keeps the matching homes and homesites in view the whole time.

• The list narrows to whatever filters are set, so a buyer exploring the area never loses track of what is actually for sale in it.
• The map can be colored by homesite type or by availability, and at wider zoom it colors by neighborhood so the shape of the community reads before any single lot does.
• Amenity markers stay in place as a buyer moves around, and the map frames each amenity rather than dropping the buyer at an arbitrary zoom.
• Communities marketing future sections can show them as not yet available, and the homesite finder stays hidden where there is nothing to sell yet.

Anyone driving or walking a community can now record a note on a homesite with photos taken on their phone, and send it on by email before they leave the lot.

• Notes and photos attach to the homesite, so what was seen in the field shows up on the lot record and on the lot status map for everyone else.
• A note goes out by email with its photos attached, which turns a punch item into a message to the builder or contractor on the spot.

Contracts written in Pipsy now flow into the builder's own contract system automatically, and closings, buyer detail, and lot assignments stay aligned on both sides without anyone rekeying them.

• When a homesite is committed, the lot moves out of the pool and the builder's contract is created in order, so both systems agree on which lot the contract covers.
• Approval is requested when a builder-owned lot goes under contract, and the decision is passed back through the sync once it is made.
• Builders are matched on the name they market under, so contracts land against the right builder even where the legal entity differs.
• Closing dates line up with the builder's own closing field, and a sync can be run on demand instead of waiting for the next scheduled pass.

Builders now see the reason an ARC submittal was rejected instead of only its status, and communities can add their own fields to a color and material scheme so a submittal captures what the guidelines actually ask for.

• The approved scheme is tracked on the homesite and drawn on the repetition map, so a reviewer can see where a scheme has already been used before approving it next door.
• Monotony checks show the range being measured on the map, and submittals carry the neighborhood so a review queue can be worked one neighborhood at a time.
• Submittals capture a square footage breakdown, so minimum size rules can be checked against the figures on the plan rather than a single total.
• Brick is handled as its own exterior material, so masonry selections no longer have to be recorded as something else.

Homes under contract now read as sale pending and sold homes stay on the map as sold, so buyers see how fast a community is absorbing instead of a map that empties out as it succeeds.

• Available counts and filters leave out sold and pending homes, so the number a buyer is shown matches the list they get.
• Sold homes and sold homesites are treated separately, and a resale that has closed is marked sold rather than dropping off the map.
• A community with no completed homes opens on homesites, so the first thing a buyer sees is what is genuinely for sale.

Executives running several communities can now read each community month by month in one table, with closings sitting next to sales and traffic instead of in a separate report.

• Every month is broken out per community, so a portfolio can be compared period over period without running each community on its own.
• Weekly executive reporting separates model home traffic from welcome center traffic, so a shared welcome center is not counted twice against the builders.
• Traffic capture records a phone number, and cancellation reasons read as their labels wherever they appear rather than as codes.
• Web leads show who they are assigned to, so a list of leads makes clear who owes the follow-up.

Development and sales teams can now hand out construction status as a formatted document, and see closings summarized by month alongside takedown and district reporting.

• The construction report prints per community with each homesite's stage, so a weekly construction meeting can work from a single document.
• Homes that have arrived on site are called out as their own stage, with the estimated closing date next to them.
• District exports use each client's own column names, so a reimbursement package does not have to be relabeled after it is exported.

Marketing teams can now attach an incentive to a specific floorplan and add a virtual tour to it, and both reach the public site next to the plan and the homesites where the offer applies.

• An incentive tied to a plan shows on the plan card and on the available homes offering it, so a buyer meets the offer where they are already looking.
• Floorplan documents supplied as PDFs render as images across cards and detail views, so plans no longer have to be converted before they can be published.
• Move-in dates that have already passed are hidden, so a listing never advertises a date behind it.

Setting up a facility no longer depends on knowing what each setting does from memory. Community, contract, and takedown instruction forms now carry plain-language help on every field, and a contract can hold a lump sum earnest deposit instead of a per-lot amount.

• Help sits beside each field as it is filled in, so the effect of a term is clear before it is saved and carried into takedown instructions.
• A lump sum earnest override replaces the standard per-lot calculation where a facility was negotiated that way, and released earnest is no longer counted twice against the balance.
• A builder's separate business address can be recorded on the contract and used on the documents generated from it.
• A contract can name the incentive program it runs under, so the terms appear wherever the contract is read.

A salesperson or a buyer can now send a link that opens straight to one home, homesite, or floorplan, and each community controls which view the map opens on and what its filters are called.

• Each community sets its own opening view, so one selling homesites opens on homesites and one selling homes opens on homes.
• Filter labels, status wording, and homesite colors follow the community's own terminology, and additional square footage figures can be surfaced on the cards where buyers compare.
• On a phone the map takes over the screen with a clear way out, and coming back from a home's detail leaves the buyer where they were.
• Contact forms can carry the community's own legal disclaimer, and campaign tracking travels with the lead into the CRM.

Teams running a realtor program can now manage it from Pipsy - events and their check-in codes, who registered and who showed up, and the announcements that go out to agents - and record a realtor on a contract even when that agent is not yet on file.

• Each event counts registrations, check-ins, no-shows, and walk-ups, so turnout can be measured against what was promised to the community.
• Announcements can go to every agent or only to those following a given community, with a start and end date and a limit on how often they are sent.
• A realtor can be entered by hand on a contract or closing, so a sale is attributed to the right agent the first time.
• Realtor office mailing addresses come through on sales reporting, and realtor fields are available when building an email campaign.

The written briefing that has been running with weekly community reports now has a monthly edition, giving owners and executives a narrative on the month's sales, cancellations, and closings next to the figures they already receive.

• The monthly briefing sits on the dashboard as its own card, so it can be read without opening the weekly report.
• Each person chooses whether they receive the weekly briefing, the monthly one, or both.