Sales & Reporting

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.

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.

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.

Marketing teams can now see website traffic, email performance, paid social, and search visibility for a community inside Pipsy, sitting next to the sales those campaigns produced, instead of pulling each platform's numbers separately and stitching them together.

• A reporting section carries a tab per channel, so a month can be read across every source of demand in one place.
• Communities that already have their analytics, email, and CRM accounts connected are picked up automatically, with no separate setup step.
• Marketing form submissions come through as lead counts, so spend behind a campaign can be measured against the inquiries it produced.

Sales managers can now see every on-site salesperson graded against the community's own service standards, with a performance view behind each score showing what drove it, so coaching conversations start from the same numbers everyone can see.

• Grades are built from the traffic, follow-up, and sale records already being kept, so nothing extra has to be logged to produce them.
• The time allowances behind each standard are set per client, so a community with a different cadence is not held to someone else's expectations.
• The grade table sorts, so a portfolio can be scanned for who needs attention without opening each community in turn.

Buyer segmentation now produces a written analysis each month, so owners and executives get a read on who bought and how the buyer mix is shifting, rather than a table they have to interpret on their own.

• The analysis is written per community and kept month over month, so a year of commentary can be read in sequence.
• It sits with the segmentation report itself and falls back to the underlying figures in a month with too little closing volume to say anything meaningful.

Realtor contact details are now kept once and shared everywhere an agent appears, and a contract cannot be written against an agent without a full mailing address, so commission checks and mailings reach the right office the first time.

• Agent records fill in from state license records, and a correction made on one contract or traffic card updates that agent everywhere else.
• Contracts capture whether the agent is local to the market, with each community wording the question in its own terms.
• The realtor report reads that answer back per community, so a team can see how much of its business is coming from agents outside the market.

Sales teams can now see where demand is concentrated by price and homesite type, and where buyers are coming from geographically, out of the reports they already run each week.

• A heatmap plots sales and closings across homesite type and price band, so a pricing decision can be made against where the market is actually clearing.
• The geographics map shades ZIP code boundaries by where buyers came from, which makes a media buy far easier to argue than a scatter of pins.
• Closings and sales analysis carry the traffic source behind each sale, along with buyer phone numbers for follow-up.
• Starts are recorded as spec or dirt with an optional dirt start date, so presold and speculative inventory can be told apart in reporting.

Sales managers now get a daily recap of everything that moved on the lot pool - reservations placed, cancelled, and committed, and homesites taken down - and once a builder commits to a homesite, that builder is the only one that can act on it.

• Cancellations show whether the lot returns to the pool, so it is clear each morning what is genuinely back on the board.
• A reminder goes out when a committal has been pending for 36 hours, so a homesite does not sit claimed but unconfirmed.
• Inventory lists, dashboards, and the lot status map scope to the committing builder once a lot is taken, so builders sharing a pool see only their own.
• A weekly community report can be released by hand rather than waiting for the scheduled send.

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.

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.

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.

Every community's weekly report can now carry a written briefing on the week - what sold, which builders and sections drove it, why contracts cancelled, and how the year is tracking - produced automatically and delivered alongside the report sales teams already receive.

• The briefing is built on figures computed directly from the community's records - gross sales, cancellations, net sales, closings, year-to-date totals, active contracts, and inventory by status - so the narrative and the numbers always agree.
• The briefing is marked beta while it is tuned, and users opt in individually, so it reaches the people who want it without changing anyone else's report.
• The emailed weekly report now opens with a summary block: year-to-date net sales, starts, and closings, plus the week's gross sales, cancellations, net sales, and closings.
• Visitor totals now include group tours and realtor groups, so traffic counts reflect everyone who came through the door.

Communities organized into neighborhoods can now carry that breakdown through reporting. Builder performance, inventory supply, construction status, starts and completes, lot fees, section performance, takedowns, and district reports all show the neighborhood a homesite sits in.

• The weekly report and the inventory health and sellout views break out by neighborhood alongside section, lot type, and builder.
• Floorplans are assigned to the neighborhoods where they are offered, so plan lists reflect what is actually available in each part of the community.
• Approved color and material schemes can be scoped to a neighborhood, so a builder submitting there is offered only the schemes approved for it.
• Neighborhood carries across on homesite imports, so a new section arrives already assigned.

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.

Reserved homesites now appear on the lot status map with the date the hold was placed, and a premium homesite progress table tracks how each premium lot is moving by premium type and amount.

• Communities can add their own fields to a reservation and hide contract fields they never use, either everywhere or for a single community.
• The premium table summarizes how many premium homesites there are and what they carry in premium, next to their current status.
• Homesites sold to custom builders now count as developer lots on the lot status map, so the split between builder and developer inventory is accurate.

Communities can hide homesite fields they never use, and the change history on a homesite now names the person behind every edit with the before and after values side by side.

• Any additional field a community has defined can be charted in buyer analysis, and buyers can be filtered by home type.
• The change log is laid out so an edit and its effect are legible at a glance instead of requiring interpretation.

Sales teams can now set a weekly traffic projection for a community and track actual visitor counts against it all year, the same way sales are tracked against plan. A traffic trend report shows cumulative traffic week over week next to the projection.

• Projections are entered per community and compared to actual traffic on a year-to-date basis, so a shortfall is visible in the week it happens rather than at quarter end.
• A cumulative weekly traffic chart is available for executive reporting alongside the sales projection.
• Traffic, sales, and buyer lists can be sorted and limited on the way out, so a report can be pulled for a single period or a top-performing subset.

Every lot contract and takedown instruction now has an overview screen that shows the economics of the deal in one place - lot counts, pricing, fee structures, and deposit position. Sales managers working in builder mode can submit a takedown request directly instead of sending it by email.

• The instruction overview rolls up the lots, pricing, and fees behind a single takedown so the amount due at closing can be read without rebuilding it in a spreadsheet.
• The contract overview does the same across an entire lot contract, so a facility's position is legible at a glance.
• A takedown requested by a sales manager lands in the same queue the development team already reviews, with the requesting builder attached.

Leads captured in Mailchimp or HubSpot now flow into Pipsy on their own, so the traffic and buyer picture for a community includes online inquiries and not just walk-ins. Leads can be pulled up by community and opened in a rebuilt detail view.

• Existing lists import in full rather than only new activity, so a community starts with its whole history on the first sync.
• Custom fields on a marketing audience map into the traffic record, including the source and campaign that produced the lead.
• Leads can be filtered by community, so a group operator can work one property at a time.

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.

Interactions in the public inventory map are now recorded - lot clicks, filter changes, favorites, brochure and virtual tour opens, and view switches - so marketing teams can see what buyers actually look at before they call. QR codes generated in Pipsy can carry campaign tags so scans trace back to the piece that produced them.

• Tracked activity covers the map, the list, filters, the mobile sheet, and every action on a homesite detail page.
• General QR codes accept a source, medium, and campaign at the time they are generated.

A new data check flags homesites where the square footage shown in marketing does not match the square footage on the approved ARC submission, so listing pages and approval records stop drifting apart.

• The data quality report lists each mismatch with both figures side by side, so the wrong one can be corrected at the source.
• Total square footage now carries across on floorplan imports, giving the comparison a reliable figure to check against.
• ARC screens read square footage from the approved submission rather than the marketing record.

Several standing reports picked up filters, exports, and corrections this month, so the numbers that go into a board package need less hand-editing.

• The home sales trend report filters by lot type and exports to Excel.
• Cumulative net sales now include cancellations that fall in a different year than the original sale, so year-over-year figures reconcile.
• Buyer analysis adds further breakdowns, and closed homes can be tracked from the buyer's first visit through to the sale.
• Weekly community maps can show drone aerial imagery, with navigation between shots.

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

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.