01
Buyer
Enquiry
Property, configuration, budget range and source are recorded.
Industry · Real estate
Real estate systems that preserve context from first enquiry to final document.
Thalenor builds property websites, lead and inventory systems, broker and client portals, document workflows and follow-up automation for developers, agencies and property-service businesses.
INVENTORY · RELATIONSHIP · DOCUMENT03
A clear answer
What does Thalenor build for real estate organisations?
Thalenor helps real-estate teams connect the public property experience to the internal commercial workflow. That can mean structured inventory and search, source-aware lead capture, qualification, property matching, visit coordination, document exchange and reporting. The objective is not to automate the relationship; it is to make sure agents, managers and clients act from current, shared context.
Operating landscape
One connected operation. Six places where context can break.
The system should carry meaning across these hand-offs, not leave users to rebuild it in messages and spreadsheets.
01
Property discovery
Search, comparison, availability, location context, plans, media and enquiry journeys built around buyer intent.
02
Lead qualification
Source, budget, property type, location, timing, finance readiness and consent captured without turning the first interaction into an interrogation.
03
Inventory and matching
A current view of units, attributes, status, price rules and alternatives available to authorised teams.
04
Site visits
Scheduling, assignment, reminders, directions, attendance, notes and the next action after a visit.
05
Client and broker portals
Selected properties, documents, questions, status and commission or referral context behind appropriate access.
06
Documents and reporting
Controlled templates, checklist states, approval, secure exchange, pipeline definitions and exception-led management views.
Workflow in view
A credible product should make the work visible before it tries to make it fast.
Follow the record, the responsible role and the decision that must remain human.
ILLUSTRATIVE MODEL · FICTIONAL RECORDS
A property enquiry arrives with enough context for a useful first response.
The workflow keeps the buyer’s intent attached while giving the sales team a clear owner and next action.
INTENT → INVENTORY → NEXT ACTION
ILLUSTRATIVE OPERATING MODEL · 06 STATES02
Sales system
Ownership
The lead is assigned with a response target and duplicate check.
03
Advisor
Conversation
Requirements are confirmed and unsuitable inventory is ruled out.
04
Inventory
Match
Current options and alternatives are shared from controlled inventory.
05
Advisor
Visit
A slot, host and reminders are confirmed.
06
Sales system
Outcome
Interest, objections and next step are recorded immediately.
Illustrative commercial workflow. Pricing, representation, consent and document requirements depend on the business and market.
Where design judgement matters
The hard part is rarely the screen someone asks for first.
01
A lead record should preserve why the person enquired.
Campaign source alone is not context. The property viewed, price seen, location, device, stated requirement and prior conversation should arrive together so the first response can be relevant.
- ACarry property context into the CRM
- BSeparate duplicate people from distinct requirements
- CDefine response ownership and reassignment
- DRecord consent and channel preference
02
Availability is a controlled fact, not brochure copy.
Marketing pages, sales teams and partner channels lose trust when they show conflicting availability or pricing. Inventory needs a named authority, update rules and clear provisional states.
- AModel unit status and reservation expiry
- BSeparate public, broker and internal fields
- CKeep price revisions and approvals traceable
- DDefine behaviour when sync is delayed
03
The site visit is a handoff between digital intent and human selling.
Good software prepares both sides, confirms attendance and captures an outcome while the context is fresh. It should not bury agents in forms during the conversation.
- AOffer realistic slots and travel context
- BAssign an accountable host
- CUse short, structured outcome capture
- DTrigger a relevant next action, not a generic sequence
04
A document room needs states, permissions and expiry—not just uploads.
Identity, booking, finance and property documents move through review. Each item should show who supplied it, which version is current, who may view it and what is still missing.
- AUse purpose-specific requests
- BTrack review and rejection reasons
- CRestrict highly sensitive documents
- DSeparate generated drafts from executed documents
Relevant capabilities
The engineering disciplines this work usually touches.
Boundaries built into the product
Responsible software states what it will not decide.
A disclaimer cannot compensate for a workflow that hides uncertainty or lets sensitive actions happen without ownership.
01
Availability authority
Name the system and role that determine whether a property or unit is available.
02
Fair presentation
Search and recommendation logic should not quietly misrepresent sponsored or preferential inventory.
03
Sensitive documents
Identity and financial documents require purpose-limited access, retention and secure sharing.
04
Consent and messaging
Follow-up cadence and channels should reflect consent and genuine buyer context.
05
Human negotiation
Pricing exceptions, commitments and advice remain visible to authorised people rather than hidden in automation.
Decision guide
Design the property data model before designing the property card.
Real-estate interfaces become brittle when the project, building, unit, listing and availability concepts are treated as one object.
A credible first release often connects current inventory, contextual enquiries and site-visit outcomes before attempting a complete sales ERP.
01
Separate the entities
A development contains buildings; buildings contain units; listings present an offer; availability and price change over time. Model them deliberately.
02
Name the source of truth
Decide who updates status and what downstream surfaces must change. Add provisional and stale states where certainty is not possible.
03
Preserve enquiry context
The internal record should retain the page, property, campaign, price and requirement that caused the enquiry.
04
Define pipeline language
‘Interested’, ‘qualified’ and ‘hot’ are not operational states. Use definitions tied to evidence and next action.
05
Design partner access separately
Brokers may need inventory, collateral and referral status without seeing internal notes or another partner’s relationship.
06
Treat documents as workflows
Requests, versions, review, rejection and execution are more important than a folder of files.
Practical questions about real estate software.
Yes, if there is a dependable source and update process. We design explicit status, sync and fallback behaviour so ‘live’ does not become an unsupported marketing claim.
Connect the property experience to the sales reality.
Show us how inventory changes, where enquiries arrive and what happens after a visit. We will identify the handoff that deserves fixing first.