The stock list looks fine until you check it lot by lot. A reservation that has been sitting for six weeks with no contract issued still shows as “reserved”. Nothing looks wrong. It sits there next to the healthy reservations, indistinguishable from them, and it quietly falls over. By the time anyone notices, the buyer has bought somewhere else.
Every development sales manager has been bitten by this. It is invisible on a normal stock report because a stalled reservation looks exactly like a good one. This post is about Property Shell reporting that finds those deals before they die, and about what else becomes possible when you can ask your sales book a question in plain English and act on the answer.
Property Shell is development and project marketing software: stock management, the buyer database, reservations, contracts, settlements. The reader we have in mind is a development sales manager or a project marketer, selling apartments or land off the plan across one or more projects, whose day is stock, buyers and contract progression.
The data is good. The difficulty is that a development sale passes through four or five systems between reservation and settlement, and the questions that matter are about movement over time rather than status right now. A stock report tells you what is reserved. It does not tell you what has been reserved for too long. A buyer database tells you who enquired. It does not tell you who enquired and was never called.
So the sales manager builds a spreadsheet, exports into it weekly, and colours cells. Everyone does. It works until the week it does not.
We connect Claude, Anthropic’s AI model, to your Property Shell environment through an open standard called the Model Context Protocol. You ask in plain English, in Microsoft Teams or the Claude app, and Claude answers from the live system as you. With your approval it drafts the follow-up, builds the list, or moves the lot.
Three points about how it is built.
It reads the live system. The reservation taken at the display suite an hour ago is in the answer.
It acts as you. An agent sees their buyers and their lots. A project marketer sees their projects. The sales director sees the book. Permissions follow the person, and every question is logged.
It prepares, and a person confirms. Nothing is recorded or sent without approval.
The managed AI service around it handles the connector, the access model, the logging and the tuning, alongside the IT support we deliver to property businesses in Perth.
“Which reservations have stalled?”
Lots reserved a while ago with no contract issued yet, oldest first. These are the ones that quietly fall through, and they are invisible on a standard stock report because they look exactly like healthy reservations.
If this post has one hero question, it is this one. It is a problem every reader recognises instantly, and the answer is worth real money every time it is asked. A single stalled reservation rescued pays for the connection many times over.
Pair it with the e-signing question further down, which contracts have been out for signature with no movement, and you have the complete picture of every deal that is drifting. That combined view is the single most useful thing you can hand a development sales manager.
“What is still available at West Quarter?”
Filterable by project, status (available, reserved, sold, settled), bedrooms, or a price ceiling.
“Show me every two-bedroom under $750k across all projects.”
“How is stock split across the projects right now?”
Every development with its stock broken down by status.
“Where does the sales book stand?”
Stock, total value, pipeline and contract progress in one answer.
“What is the total value of everything reserved but not contracted?”
That number, and how it moves week to week, is the health of the business.
“Segment the buyer database: hot leads living in Como with a budget over $800k.”
This is the job that takes an hour by hand. Filter by project, lead quality, the suburb a buyer currently lives in, and budget range, combined freely. It tells you how big the segment is as well as listing it, so you know whether the mailout is worth doing before you build it. Buyer database segmentation becomes a sentence rather than a Friday afternoon.
“Find everyone who enquired about West Quarter and has not been contacted.”
“Tell me everything about this buyer and what they are holding.”
“What is the story on lot 412?”
Its purchaser and contract stage.
“Give me the full picture on West Quarter.”
Stock, value, purchasers and contract progress.
“How is James tracking?”
Settlements, stalled reservations and conversion. The numbers behind his KPIs, which matter more when review season arrives, as we will get to.
“Draft the follow-up for every stalled reservation.”
“Build the buyer list for the Como mailout and export it.”
“Move lot 412 to contracted.”
All prepared for review before anything is recorded or sent. The follow-ups come back as drafts. The list comes back for a look before it goes anywhere. The status change is shown before it is written. A sales manager keeps control of the book; they just stop doing the clerical work of running it.
A development sale touches Property Shell, an e-signing platform, a conveyancer or settlement platform, the accounting system, and usually a campaign tool. The gaps between them are where deals quietly die, and the questions worth the most money are the ones that span two of them.
“Which contracts have been out for signature more than a week with no movement?”
“Issue the contract for lot 412 and tell me when it has been signed.”
Combined with the stalled reservations question, this is the drifting-deal report. Reserved but not contracted, plus contracted but not signed, oldest first, in one list.
“Which settlements are due next month and which are at risk?”
“What is outstanding on each of this month’s settlements, and who is waiting on whom?”
Settlement pipeline forecasting is where the developer’s cash flow actually lives, and it is usually maintained in a spreadsheet updated from phone calls to the conveyancer. Being able to ask the question is a different way of running the month.
“Have the deposits for these reservations actually landed?”
“Which lots have settled where the funds have not been reconciled?”
A reservation without a landed deposit is a reservation that may not exist. Checking that across the book weekly is the kind of thing nobody has time for and everyone wishes they had done.
“Build the Como segment for the West Quarter release and push it to the campaign.”
“Who opened the last release email and has not been followed up?”
“This buyer has emailed a question about lot 412. Pull up what they are holding and their budget, and draft the reply.”
“How did James do against his targets this half?”
Property Shell knows his settlements and conversion. The HR system knows his targets. Nobody has ever joined those without a spreadsheet. We wrote about that pairing in our post on running performance reviews from operational data, and it is the demonstration that makes people sit forward.
Property Shell alongside Microsoft 365 (email, Teams, SharePoint), Xero and Employment Hero runs today. E-signing, settlement platforms and campaign tools vary by developer; where yours is not already connected it is a build rather than a blocker.
Connecting an AI model to Property Shell is not the hard part. The hard part is that every sales system has places where the data quietly misleads. A lot released and withdrawn and released again, so its “days reserved” count is wrong. A buyer duplicated across two projects with different budgets. A reservation converted to a contract in the e-signing tool but never updated in the stock list.
Point a generic AI at that and ask which reservations have stalled, and you will get a confident, specific list that is slightly wrong. It will look completely reasonable. Nobody will check, because not checking was the point. And in this business, a wrong “stalled” flag means a sales agent ringing a buyer who signed last week.
Making Property Shell reporting through an AI assistant trustworthy means measuring the data against itself, writing down where it misleads, and building those traps into the answers. When ours flags a stalled reservation, it says whether the e-signing platform has a contract in flight for it. When it reports days reserved, it says which reservation date it counted from. That is what an integration specialist is for, and it is exactly what a self-serve connector cannot give you.
Developers, project marketers and development sales teams running Property Shell across one or more projects, with enough stock that the book cannot be held in one person’s head, and a settlement pipeline that matters to the lender as much as to the sales team.
WA has a lot of developers, and Perth is where we deliver most of our work because we set this up hands-on. Property Shell is national and so is the connector. If you are selling off the plan in Brisbane or Melbourne and these are your questions, talk to us and we will say plainly whether we can deliver it well.
Run the stalled reservations check by hand, once. Export the reservations, sort by date reserved, and look at everything older than your normal contract turnaround with no contract issued. Most sales managers who do this find at least one they did not know about. That single exercise tells you whether the rest of this post is worth your time.
Check who can see what in Property Shell. Agents, marketers, directors. Any AI connection inherits those permissions, and buyer data is personal information under the Privacy Act.
Watch the stalled reservations question answered live. We have a working demonstration against a realistic multi-project portfolio. For this audience, that one question does more selling than a page of copy, so we would rather show you than tell you. Twenty minutes, no commitment. Contact us on 1300 EPIC IT or through the contact page.
Yes. A Property Shell AI assistant connects an AI model such as Claude to your live Property Shell environment so you can ask about stock, buyers, reservations and settlements in plain English. Ours runs in Microsoft Teams, respects each user’s permissions, logs every question, and drafts follow-ups and lists for a person to approve.
Ask “Which reservations have stalled?” The assistant lists lots reserved with no contract issued, oldest first, and checks whether a contract is in flight in your e-signing platform before flagging any of them. A standard stock report cannot show this because a stalled reservation looks identical to a healthy one.
Yes. Combine project, lead quality, the suburb a buyer currently lives in, and budget range in one request, and the assistant returns the segment with its size. It can then build the export or push it to your campaign tool, prepared for review first.
With Property Shell and your settlement or conveyancing platform connected, you can ask which settlements are due next month, which are at risk, and what is outstanding on each. That replaces the spreadsheet most developers maintain from phone calls to the conveyancer.
It depends on how the connection is built. Ours acts as the person asking, so an agent sees their buyers and a director sees the book. Every question is logged, and nothing is recorded or sent without approval. Buyer data is personal information under the Privacy Act and should be treated that way by any provider you speak to.
Perth and WA are where we deliver most of our work, because we set this up hands-on. Property Shell reporting through an AI assistant works anywhere in Australia. If you are interstate, contact us and we will tell you plainly whether we can deliver it well for your projects.
