What’s New in Pipsy

Capital partners can now sign in to Pipsy and see the facilities and development projects they have money in, with position, returns, and distribution detail on each one, rather than waiting on a statement from the sponsor.

• Partners get their own logins, scoped to only the facilities and projects they participate in, and sponsors administer those accounts themselves.
• Joint venture waterfalls calculate preferred return and promote tiers, so each partner's share of a distribution is visible on the project it came from.
• Capital statements show contributed capital, returned capital, and outstanding balance per partner, and equity terms can be edited as a deal is restructured.
• Portfolio and returns views summarize positions across every facility and project a partner holds.

Land bankers and their builder partners now run the whole facility lifecycle in Pipsy - lots assigned to a facility, takedown requests raised against it, and approvals recorded with who signed off and when.

• Sales managers request a takedown by picking lots from the facility map or table, and the request carries its obligation math with it.
• Approvers work a queue of pending requests with the facility position behind each one, and every approval or rejection is stamped to a person and a date.
• A facility can be created directly from a development project, so a project that converts to a Lot Trust deal keeps its lot inventory and cost basis.
• Each contract keeps a full history, including earnest money handling and an approved-to-takedown flag that drives the takedown schedule and the accounting journal export.

Development teams can now raise, edit, and track draw requests against a project's budget, with a shared status timeline that the sponsor, the lender, and capital partners all read from the same place.

• Draw requests and takedown requests share one status model and timeline, so anyone can see where a request sits and what moved it there.
• Comments with mentions live on the request itself, which keeps the back and forth about a funding decision attached to the funding decision.
• Pro forma sensitivity tools re-run a project against changed absorption, price, and cost assumptions without rebuilding the model.

Traffic and sales recorded in a builder's own CRM now flow into Pipsy automatically and land on the right lot and the right on-site rep, so a community's numbers are complete without the builder re-keying anything.

• Visits and deals match to lots by address, including addresses that arrive with the street suffix truncated or formatted differently.
• Visitor names and emails resolve from the contact record when the deal itself is missing them, and rows that came across blank earlier are filled in.
• Walk-ins are attributed to an active salesperson at that community, and a record that can only be matched to a manager or a departed rep is flagged rather than quietly dropped.
• Cancellations and closings on the builder's side carry through to the sale already claimed in Pipsy.

Community managers can now see every home that is under or over the square footage its section requires in one report, instead of checking plans lot by lot against the deed restrictions.

• The report reads each section's minimum and maximum and lists the homes that miss it, with the shortfall or overage shown per lot.
• A dashboard widget surfaces current compliance without opening the report, and the same figures carry into the construction report.

Inspectors and field staff can keep working where there is no signal. Compliance inspections and drive mode notes are captured on the device and submitted on their own once the connection comes back.

• A banner shows when work is being held on the device, and a pending list shows exactly what is still waiting to go up.
• A queued submission cannot post twice if the device retries, so reconnecting after a long day in the field does not create duplicate inspections.
• Photos attached to a note are resized on the device, which stops long inspection sessions from crashing phones.

Development teams can bring a recorded plat into Pipsy straight from the engineer's CAD drawing, and the section comes up with its lot geometry already in place instead of being traced by hand.

• A preview map shows exactly which lots will be created before anything is committed.
• Lot lines and map layers can still be drawn and adjusted by hand, with a basemap toggle for tracing against aerial imagery.
• Sellout projection columns on the section view show how the imported inventory absorbs by lot type and builder.

Builders that group their plans into collections can now present them that way on the public site, and buyers can narrow the inventory to a single collection.

• Collections are scoped to the builders a buyer has selected, so the filter only offers plans they can actually buy.
• Dirt homesites show the specs of the plans that fit on them, so a buyer looking at an empty lot still sees beds, baths, and square footage.
• Bed, bath, and square footage filters match against those compatible plans, and full and half baths are listed separately.

Communities that sell finished homesites as well as homes can now present that inventory properly. Developer-owned, resale, premium, and build-on-your-own-lot homesites each get their own treatment on the map and in the list.

• An available homesite filter and a homesites-only view keep dirt lots out of the search when a buyer is shopping for a house.
• Lot size reads in both acres and square feet, from a land area figure kept separately from house square footage.
• Model homes are handled as their own case, so they no longer show as available inventory and their plan detail reads correctly.
• Builder and floorplan detail on a lot stays hidden until the community's release date, so a coming soon section can go up early without exposing what is not ready.

Marketing teams can send a buyer to the community map with the search already set up, and buyers can see and change what they have filtered to without starting over.

• Links can open directly on a specific lot, neighborhood, or builder's inventory, which makes them usable in email campaigns and on builder pages.
• A filter summary shows everything currently applied and lets a buyer clear any part of it in one place.
• Amenity hubs collapse to a single marker until a buyer zooms in, amenities without a photo can show as text-only cards, and trail routes now draw on the map.
• Printed homesite brochures carry the lot number and the sales rep's direct line, and the header bar across the top can be turned off per community.

ARC reviewers get more ways to define what counts as repetition, and builders can attest their way past a soft block instead of calling the community manager.

• A scheme match mode flags repeated color and material schemes even when the plans differ, and a plan-or-scheme mode catches either.
• Fields a community does not treat as part of monotony can be left out of the repetition scan.
• Where a rule is a soft block rather than a hard one, the builder can attest and continue, and the attestation is recorded on the submission.
• The ARC Status report uses the same repetition calculation as the monotony map, so the report and the map cannot disagree.

Competitive data from different market providers now reads as one consistent picture, so sales teams can compare their community against nearby ones without reconciling two formats by hand.

• Overview and resale reporting treat every provider's pricing, absorption, and inventory the same way.
• A competitor attribution map shows which competing communities buyers chose instead, tied back to the sale that was lost.

Executives get a single Overall Stats report covering sales, inventory, and traffic across communities, along with several additions to the weekly report that go out with it.

• The weekly report adds month-to-date sales, buyer demographics, and a toggle to break results out by rep.
• Traffic year over year can be read with Welcome Center traffic included or excluded.
• The lot pool map adds a Not Released to Pool status, so lots deliberately held back read differently from lots that simply have not sold.
• Sales variance can hide the week in progress, so a partial week does not distort the comparison.

Takedown pricing now supports compounding escalation, section-level overrides, and a cap on how far a price can escalate, and fee schedules can be preset per section and locked so they do not drift.

• A compound monthly escalator models price growth that compounds, rather than accruing against the original basis.
• Escalation can be overridden for a single section, and an end cap stops escalation once a set point is reached.
• Fee table presets are scoped to a section or property, so a new lot picks up the right fee schedule as it is created.
• A preset can be locked, which keeps the fees agreed on a contract from being edited after the fact.

Sales teams can verify a cooperating realtor's license in more states at the moment of registration, and get a clear reason back when a license cannot be confirmed.

• Lookups are scoped to the state the community sits in and still match license numbers entered without their state prefix.
• An out-of-state license returns an explanation instead of an empty result, so the rep knows what to ask for.
• Realtor lookup is scoped to the property, and each builder can be given its own assigned closer.