Land Development

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 LotTrust 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.

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.

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.

Development teams running several projects can now read the deal pipeline, entitlements, action center, and program dashboard across the whole portfolio at once, instead of switching community by community to assemble the picture.

• Every development report reads across projects regardless of which community is currently selected, so the portfolio view is the default rather than an assembly job.
• Debt draws are capped at the committed facility amount and financing carry is counted once, so a pro forma no longer overstates what a project will draw.

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.

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.

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.

Lot contracts, their takedown schedules, and the instructions behind them are now managed in one place, and each contract carries its earnest money position next to its pricing and fee terms. A contract's economics can be read without assembling them from separate screens.

• Earnest money is recorded on the contract and on each section, so deposits held are visible alongside the pricing and fees they offset.
• Sections carry the county they sit in, which flows through district and fee reporting.
• Takedown reports show the community behind each contract, so an operator running several communities can work from a single list.
• Sales managers get their own view of sections, and a takedown schedule no longer has to match a fixed lot count to be saved.

District reimbursement reporting now breaks out by builder and by lot type, and every table can be run on either the contract sale price or the final closing price.

• The builder and lot type table sits alongside the existing district totals, so a reimbursement package can be assembled builder by builder.
• Switching to closing price uses the figure actually recorded at closing rather than the price written at contract.

Sales teams can now reserve several homesites at once for the same builder and extend an existing hold instead of releasing and rewriting it. A reservations report shows what is held, who holds it, and when each hold runs out.

• A reservation records the builder it is held for, so lot status reporting reflects who is sitting on inventory.
• Expiring reservations are extended in place, keeping the original terms and history intact.
• Opening a homesite on the community map in buyer mode now shows a floorplan gallery and photo carousel for that lot.

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.

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.