One platform to run real estate sales & operations — connecting leads, sales, site visits, inventory, bookings, customers, operations, collections and management reporting. Reos, your AI assistant, suggests the next move. Your team decides.
Leads arrive from different channels. Sales teams coordinate through calls and messages. Site visits happen every day. Inventory changes continuously. Bookings create payment schedules. Channel partners need attribution. Operations manage what happens after the sale — and management needs accurate MIS across all of it.
When these workflows live in disconnected tools, context gets lost, follow-ups are missed, inventory becomes hard to control, and management spends time asking for updates instead of acting on them. PREOS connects the operational chain so teams work from shared context and leaders see the business through one operating layer.
PREOS stands for Platform for Real Estate Operations & Sales. Instead of treating every department as a separate system, it connects the journey from first enquiry to booking, customer servicing, collections and management reporting.
Capture, assign, qualify and follow up with complete lead context.
Opportunities, activities, negotiations, site visits and conversion progress.
Project, tower, floor and unit availability through a controlled workflow.
Connect customer, unit, booking and downstream processes.
Registrations, attribution and partner performance.
A connected customer history across every interaction.
Structure internal tasks, ownership, processes and escalations.
Track payment milestones, dues, ageing, follow-ups and escalation.
Bring operational data into management-level visibility.
From the first lead to final collection, PREOS keeps every part of your business connected around one core.
Visibility into what needs attention and what has already happened.
Keep activities, visits, opportunities and customer context connected.
A shared view of unit status and controlled inventory workflows.
Assign ownership, track processes and surface exceptions.
Connect payment schedules to actionable follow-up.
Project, sales, inventory and collections in management reporting.
Reos is the AI assistance layer inside PREOS. It analyses supported business activity, identifies signals, prioritises opportunities and suggests what your team should consider next — while important operational and commercial decisions remain with authorised people. Meet Reos →
An AI-integrated operating system for real estate developers, connecting sales and operational workflows in one platform.
No. PREOS extends beyond lead management into sales, site visits, inventory, bookings, customers, operations, collections and MIS.
Real estate developers and the teams in sales, channel partnerships, operations, collections and management.
PREOS's AI assistant. It suggests next actions and surfaces signals while keeping important decisions with authorised users.
Yes. Request a demo and walk through your projects, teams and current operating process with the PREOS team.
See PREOS using a real project scenario — your leads, inventory, sales, customer journey and reporting.
PREOS connects leads, customers, sales, inventory, projects, channel partners, collections and post-sales operations into one connected platform — giving every team the workflow they need and leadership a single source of truth. One platform. One workflow. One operational view.
Traditional CRM systems primarily focus on customer and lead management. But a real estate developer operates far beyond the CRM. A lead becomes a site visit. A site visit becomes a negotiation. A negotiation becomes a booking. A booking changes inventory and creates a payment schedule. Collections follow the milestones. The customer continues into post-sales. At the same time, channel partners, marketing teams, sales managers, project teams and leadership are all interacting with the same business. PREOS connects these activities into one operating environment.
Each stage creates information that becomes useful to the next. PREOS keeps that information connected rather than forcing teams to recreate it in separate systems.
When information is spread across WhatsApp conversations, spreadsheets, individual CRM records and disconnected systems, teams spend time asking “What’s the latest status?”, “Who is handling this customer?”, “Is this unit available?” PREOS creates a central operational record so authorised users can access the information relevant to their role.
Who is the customer and what is their journey?
Where did the enquiry come from and what has happened since?
What is the current status of the property?
What has been booked and by whom?
What has been paid and what remains?
What has happened and what needs to happen next?
PREOS brings together the major operational functions required to run a modern real estate development business.
Capture, assign, qualify and manage enquiries throughout the sales journey.
Manage customer interactions, follow-ups, site visits, negotiations and conversions.
Maintain live visibility of projects, towers, floors and individual units.
Organise project-level information, teams, workflows and operational visibility.
Manage channel partners, lead attribution, deal progress and performance.
Maintain a connected customer record throughout the buying journey.
Track payment schedules, milestones, outstanding amounts and collection activity.
Continue the customer workflow after booking — documentation, communication and post-booking processes.
Connect marketing activities and lead generation with downstream sales operations.
Bring relevant customer and team communication into the operational context.
Turn operational activity into dashboards, reports, performance views and management information.
Use AI-assisted intelligence to identify signals, prioritise activity and suggest next actions.
Real estate has operational requirements generic CRM platforms are not designed to handle deeply: projects have towers, towers have floors, floors have units, units have availability states, customers move through sales stages, channel partners influence the journey, bookings affect inventory and create payment schedules. PREOS is designed around these relationships.
Organise projects and their operational context.
Track towers, floors, units and availability.
Manage enquiries and customer intent.
Track physical customer interactions.
Maintain the complete customer relationship.
Connect customers, units and transactions.
Track financial milestones after booking.
Manage external sales networks.
A sales executive doesn’t need the same interface as a CEO. PREOS uses role-based access and workflows so every team can work within the same platform while focusing on the information relevant to their responsibilities.
Business performance, projects, MIS and exceptions.
Pipeline, team performance, bookings and conversion.
Team activity, leads, site visits and inventory movement.
Leads, customers, follow-ups and daily tasks.
Campaigns, sources, leads and performance.
Unit availability, holds and bookings.
Partners, attribution and deals.
Payment schedules, dues and follow-ups.
Customer journey after booking.
A real estate developer doesn’t manage abstract inventory — it manages projects. Within those projects are towers, blocks, floors, units, customers, sales teams and transactions. PREOS maintains this hierarchy so information can be viewed at the appropriate level.
From portfolio-level visibility to individual unit-level detail.
Inventory is not simply a list of available units. It is an operational system that must reflect availability, holds, bookings and ownership of actions. PREOS provides a central view so authorised teams work from the same status, with controlled permissions around inventory actions.
Unit can be offered according to business rules.
Unit is temporarily reserved under an authorised hold workflow.
Unit has been converted into a confirmed booking.
PREOS maintains continuity throughout — teams understand not only the current stage, but the activity and context that brought the customer there.
What happened today?
What changed this week?
How is the business performing?
Where does management need to intervene?
Reos uses relevant operational context within PREOS to help teams identify priorities and make faster decisions. Instead of requiring users to move information into a separate AI tool, PREOS brings intelligence closer to the workflow.
Sales shouldn’t have to call operations to understand inventory. Collections shouldn’t have to search spreadsheets to understand a booking. Management shouldn’t have to wait for separate reports. PREOS connects the underlying information so authorised teams work from the same operational context.
Real estate operations involve commercially sensitive customer, inventory, financial and business information. PREOS is designed around controlled access and role-based workflows.
PREOS is designed for developers at different stages of operational maturity. Whether running one project or managing multiple developments, the platform provides a common operating layer while preserving project-level workflows and access.
Multiple developments.
Multiple departments and roles.
Thousands of units.
Across the entire portfolio.
Growing channel networks.
More complexity without more fragmentation.
Designed around projects, inventory, customers, bookings and collections.
Connects departments that traditionally work in separate systems.
Create ownership around critical workflows and actions.
Reos helps teams understand activity and prioritise what matters.
Give leadership a connected view of business performance.
Designed to support growing project portfolios and teams.
PREOS connects every stage of the real estate sales and operations journey — giving your team one continuous view of every lead, customer, unit and transaction.
Leads enter PREOS from your connected channels and are automatically organised into a central pipeline.
Sales teams get a complete view of every active opportunity and know exactly what needs attention.
Once a buyer is ready for a site visit, PREOS keeps the activity connected to the same customer journey.
After the site visit, the buyer’s requirement can be matched against live inventory.
Once a buyer is interested in a particular unit, PREOS connects Buyer → Requirement → Unit → Price → Negotiation → Approval.
Once commercial terms are agreed, the unit moves through the appropriate hold/booking process — PREOS maintains its status (Available → Held → Booked) with the relevant ownership and timestamps.
After booking, the customer does not disappear from the sales system — PREOS continues the customer journey into post-sales.
Every booking can be connected to its payment schedule.
PREOS connects operational workflows across departments.
All operational activity ultimately feeds management reporting.
A site visit shouldn’t create another disconnected activity. PREOS brings together everything that matters into one view:
So your sales manager can immediately understand:
Across everything: customers, teams, projects, channel partners, reporting & MIS, and Reos AI — all connected through PREOS.
See how PREOS can bring your real estate operation into one connected system. We’ll walk through the platform using workflows relevant to your business.
PREOS connects the core workflows of a real estate development business — from the first lead to booking, inventory, collections and post-sales — in one connected platform. Give every team the tools they need to execute their work, while giving leadership a unified view of the business.
A real estate developer doesn't operate through one workflow. Marketing generates demand, sales converts it, inventory controls availability, channel partners extend the network, operations coordinate, collections bring revenue in, and post-sales continues the relationship. PREOS connects these workflows so information doesn't fragment between departments.
Capture, assign, qualify and track every enquiry.
Turn enquiries into structured sales workflows with clear ownership and follow-ups.
Schedule, track and analyse site visits from one place.
Manage project inventory with real-time availability, holds and bookings.
Maintain a complete customer record throughout the buying journey.
Manage channel-partner leads, attribution, performance and deal progress.
Track payment schedules, outstanding amounts, milestones and follow-ups.
Continue managing the customer journey after booking.
Bring customer communication and operational interactions into the workflow.
Connect campaigns, lead sources and marketing activity with sales outcomes.
Standardise operational workflows, responsibilities and approvals.
Give management visibility across projects, teams, sales and collections.
Use AI to analyse activity, identify priorities and recommend next actions.
Real estate leads arrive from multiple sources — portals, digital campaigns, websites, calls, walk-ins, referrals and channel partners. PREOS brings these enquiries into one structured lead environment. Teams can assign leads, track activity, manage follow-ups and understand where every prospect sits in the buying journey.
Sales performance shouldn't depend entirely on individual memory and personal spreadsheets. PREOS gives sales teams a structured workflow from enquiry through site visit, negotiation and booking. Managers can see what is happening across the team while executives have a clear view of their own priorities.
A site visit can be one of the strongest indicators of purchase intent. PREOS connects site visits with the lead and sales journey, helping teams know who is visiting, when they are visiting, what happened and what needs to happen next.
Project inventory changes constantly. A unit can be available in the morning, held during a negotiation and booked later that day. PREOS gives teams a central inventory view across projects, towers, floors and units.
Customers interact with multiple teams throughout a property transaction. PREOS keeps the customer journey connected so teams can access the relevant information without rebuilding the history from conversations, spreadsheets and separate systems.
Channel partners can be an important part of a developer's sales ecosystem. PREOS provides a structured environment to manage partner leads, attribution, deal progress and performance.
A booking doesn't end at the booking form. Payment milestones continue throughout the customer's journey. PREOS connects bookings with payment schedules so teams can identify upcoming milestones, overdue amounts and required follow-ups.
Once a customer books a property, a new operational journey begins. PREOS extends the customer record beyond sales and supports post-booking workflows, communication and follow-up.
Marketing shouldn't operate in isolation from sales. PREOS helps developers connect lead sources and campaign activity with the resulting sales pipeline.
Real estate conversations happen across calls, messages, emails and other channels. PREOS is designed to bring relevant communication into the operational context of the lead or customer.
As organisations grow, processes become harder to manage consistently. PREOS helps developers define workflows, assign responsibilities and create accountability across operational activities.
Payment activity and operational workflows should not exist as disconnected processes. PREOS can connect relevant payment events, customer records and operational activities within the broader transaction lifecycle.
Leadership shouldn't have to wait for someone to compile spreadsheets before understanding what is happening. PREOS brings operational data into dashboards and management reporting.
Reos is PREOS's AI assistant. It analyses operational activity and helps teams identify priorities, risks and opportunities. Reos is designed as an assistant — not an autonomous decision-maker.
PREOS is designed around role-specific workflows so every team member sees the information and actions relevant to their responsibility.
Business-wide visibility and decision support.
Team performance, pipeline, inventory and bookings.
Lead allocation, executive activity, site visits and conversions.
Daily leads, tasks, follow-ups and customer activity.
Project inventory, holds, bookings and availability.
Partner leads, attribution and performance.
Payment milestones, overdue amounts and follow-ups.
Customer servicing and post-booking workflows.
A lead becomes a site visit. A site visit becomes a negotiation. A negotiation becomes a booking. A booking changes inventory and creates payment milestones. Payment activity becomes collection data. Customer information continues into post-sales. PREOS connects these events instead of treating them as separate records.
See how PREOS brings your real estate workflows together in one operating system. Bring your project, inventory and team into the conversation.
PREOS connects the people, processes and information behind a real estate business — giving every team the tools they need and leadership the visibility to run the organisation with confidence.
A real estate developer may have strong teams across sales, marketing, inventory, channel partners, collections and customer operations. But when every team works through different tools and disconnected processes, the organisation loses context — leads get handed over, inventory is updated manually, site visits are tracked separately, channel-partner information sits elsewhere, collections depend on follow-up lists, and management waits for reports. PREOS connects these workflows so every department can operate within the same business context.
Run the business with a complete operational view — project performance, pipeline, inventory, bookings, collections and team activity without waiting for consolidated reports.
Give your sales organisation a system, not a collection of spreadsheets — leads, site visits, negotiations, bookings, team activity and performance in one connected workflow.
Make every lead and every follow-up count — a clear daily workflow for enquiries, calls, site visits, follow-ups and customer interactions.
Know exactly what is available, held and booked — unit-level visibility, hold management and booking status.
Bring your channel network into the same operating environment — partner leads, attribution, customer progress, deals and performance.
Turn payment schedules into proactive collection workflows — milestones, outstanding amounts, overdue payments and follow-ups.
Continue the customer journey after booking — information, communication, documentation and post-booking workflows kept connected.
Leadership needs more than isolated departmental numbers. A CEO needs to understand what is happening across projects, teams, inventory, sales and collections — and where attention is required. PREOS brings operational data into a unified management view.
Sales managers shouldn’t have to chase executives for updates or consolidate activity manually. PREOS gives sales leadership a live view of the pipeline and the activities driving it.
Sales executives deal with dozens of customers and activities every day. PREOS turns that activity into a structured workflow so important follow-ups don’t depend on memory. Every stage carries its relevant information, tasks and activity history.
Inventory is one of the most sensitive parts of a real estate business. Availability changes constantly and multiple teams may interact with the same units. A lack of control can lead to incorrect commitments, customer dissatisfaction and revenue leakage. PREOS creates a central inventory environment across projects, towers, floors and units.
Channel partners can generate significant business, but managing a large partner network can create complexity around lead attribution, deal status and performance. PREOS brings channel-partner activity into the same operational system.
Collections should begin with the booking, not after a payment becomes overdue. PREOS connects customer bookings with their payment schedules and collection workflows.
The booking is not the end of the customer journey. Customers continue to interact with the developer through documentation, payments, communication, requests and handover-related processes. PREOS keeps this information connected to the customer’s record.
As developers grow, complexity grows with them — more projects, more inventory, more teams, more customers, more channel partners and more operational data. PREOS provides a connected operating environment that gives leadership a portfolio-level view while allowing individual projects to maintain their own operational context.
Instead of treating each stage as a separate system, PREOS connects the information moving through the entire transaction.
Know what is happening across projects, teams and customers.
Create ownership and accountability around critical workflows.
Reduce manual coordination and unnecessary information searching.
Give teams and leadership the information they need at the right time.
See how PREOS can fit your projects, teams, workflows and business processes. Bring your real operation into the conversation.
Meet Reos — the AI assistant built into PREOS to help real estate developers understand activity, identify priorities and decide what deserves attention next.
Every day, sales teams create thousands of interactions — calls, messages, follow-ups, site visits, negotiations, bookings, payment updates, customer requests and management decisions. The challenge isn’t simply collecting this information; it’s understanding it quickly enough to act. PREOS uses AI to help turn operational activity into useful signals — helping teams identify what matters, what changed and what should happen next.
Reos is the intelligence layer within PREOS. It works with the operational context available within the platform to help teams identify priorities and reduce the amount of manual analysis required. Reos doesn’t replace the team’s workflow — it works alongside it.
Not every lead has the same level of intent. Reos analyses available customer and activity signals to help teams prioritise their pipeline, and can suggest which prospects should receive attention and why.
High-intent customer with recent engagement.
Customer showing relevant buying signals but requiring follow-up.
Low recent engagement or limited buying activity.
Important information is often buried inside calls — customer requirements, budget, preferred configuration, objections, timeline, family decision-making and next steps. Reos can analyse supported conversations and help surface relevant information for the sales team.
A CRM can show that a customer hasn’t been contacted. AI can help explain why that matters and suggest what the salesperson should consider doing next. Reos can surface operational signals such as:
Reos can help sales and customer-facing teams draft follow-up communication based on the relevant customer context. Teams remain in control: the AI prepares the suggestion, the authorised user reviews it, and the user decides whether to send it.
Dashboards tell leadership what the numbers are. AI can help identify what deserves attention within those numbers. Reos can help surface patterns and exceptions across operational activity.
AI can be powerful. But in real estate, some actions have significant financial and operational consequences. PREOS therefore follows a human-in-the-loop approach: Reos can recommend; authorised users decide.
A generic AI assistant may know how to write a message. But an AI assistant operating inside PREOS can work with relevant business context — which makes its recommendations more relevant to the actual workflow. For example:
PREOS is designed with the principle that AI should improve human decision-making rather than remove accountability from it. It should make important information easier to understand, surface relevant signals and reduce repetitive analysis — while critical business decisions remain traceable to authorised users and defined workflows.
People remain accountable for critical decisions.
AI recommendations should be grounded in relevant operational information.
Users should understand when AI is providing a recommendation.
AI should not silently perform critical operational actions.
Our vision for Reos goes beyond answering questions. We are building toward an AI layer that can help teams understand the state of their operation continuously: What needs attention? Where is a process slowing down? Which opportunities are being missed? What changed since yesterday? Which customers require action? Where is revenue at risk? The objective is not to automate people out of the business — it is to give every person better information at the moment they need it.
See how Reos works inside PREOS and how AI can support your real estate operation without taking control away from your team.
Every real estate organization operates differently. The number of projects, users, teams, workflows, integrations, automation requirements and deployment complexity can vary significantly. That’s why PREOS uses a flexible pricing model rather than a one-size-fits-all public price.
One operating system, configured to where your business is today — and ready for where it’s going.
Your PREOS subscription is designed around your operation. Pricing may be determined by factors such as:
Number of active and upcoming projects managed through PREOS.
Number of users, departments and organizational roles.
The PREOS capabilities required by your organization.
Level of workflow automation, communication and AI usage.
Third-party systems, APIs, communication platforms and other integrations.
Data migration, configuration, onboarding and deployment requirements.
Custom workflows, multiple entities, advanced permissions and organization-wide deployment.
Every PREOS deployment includes structured onboarding designed to help your teams transition successfully.
Configure PREOS around your organization’s structure, projects, teams and workflows.
Assist with relevant data preparation, configuration and migration requirements.
Introduce your teams to the workflows relevant to their roles.
Map your existing sales and operational processes into PREOS.
Role-based training helps teams understand how to use PREOS effectively.
Support your team during the transition to live operations.
Your commercial proposal will clearly outline:
Every proposal is tailored to your requirements before you commit.
Large organizations may have different project structures, sales hierarchies, approval processes and operational requirements. Our enterprise team can work with you to understand:
…and structure the appropriate PREOS deployment.
Experience PREOS with your team and understand how an integrated operating system can change the way your organization manages sales and operations.
During your trial, your team can experience selected PREOS workflows and understand how the platform fits into your operating model.
Trial eligibility, included modules, user limits and onboarding requirements may vary based on the selected deployment.
Manage leads.
Connect the lead to the customer journey, sales process, inventory, booking, collections and management intelligence.
PREOS is designed for businesses handling sensitive customer, sales, inventory and operational information. Access to information can be managed through organisational roles and permissions, helping businesses maintain appropriate control over their data.
Commercial terms are governed by our Subscription & Billing Policy, and your data is handled per our Privacy Policy.
PREOS uses a flexible pricing model because implementation requirements vary by organization, project count, users, modules and integrations. Contact our team for a customized quotation.
Pricing can depend on the selected deployment model and organizational requirements. Our team will recommend the most appropriate commercial structure based on your business.
Yes. PREOS can be deployed for an individual project as well as across multiple projects.
Yes. PREOS is designed to support multi-project real estate operations, with centralized visibility and role-based access.
Yes. Enterprise deployments can include organization-level configuration, advanced workflows, integrations, permissions, MIS and dedicated onboarding.
Implementation requirements are assessed as part of your proposal. Your quotation will clearly specify the applicable setup, onboarding and deployment components.
PREOS can support integrations depending on the systems, APIs and technical requirements involved. Discuss your existing technology stack with our team.
A 14-day trial may be available based on eligibility and the selected PREOS deployment. Contact our team to discuss your requirements.
PREOS is designed with configurable workflows, roles, permissions and processes. Enterprise requirements can be evaluated for additional configuration or integration.
Tell us about your projects, team and workflow — we’ll recommend the appropriate PREOS configuration.
Ideas for the people building the next generation of real estate — practical perspectives on operations, sales systems, inventory, AI, collections, channel partners and business technology.
A CRM can organize leads. A real estate operating system connects the workflows that turn those leads into bookings, collections and business outcomes.
Read the article →WhatsApp and spreadsheets are useful tools. The problem begins when they become the operating system for a growing real estate sales organization.
Read the article →Inventory is the product. When availability is unclear, the sales process becomes vulnerable to conflict, delays and poor customer experience.
Read the article →A strong sales process does more than capture leads. It creates a visible journey from enquiry to site visit, negotiation and booking.
Read the article →The most useful AI for real estate sales may not be the AI that makes decisions. It may be the AI that helps salespeople make better decisions faster.
Read the article →Collections should begin with the booking and continue through every payment milestone, with clear ownership and escalation.
Read the article →Choosing real estate software should start with the developer's operating workflow — not a generic feature checklist.
Read the article →A modern developer's technology stack should connect the complete project lifecycle instead of creating separate islands of information.
Read the article →Connected operating models, fewer process gaps and better visibility across teams.
Lead management, follow-up discipline, site-visit conversion and sales productivity.
Unit status, hold management, booking control and fragmented-inventory risks.
Onboarding, lead registration, attribution and partner performance.
Payment milestones, ageing, follow-up, escalation and collection visibility.
Conversation intelligence, lead prioritisation and human-in-the-loop systems.
Guides explaining how PREOS workflows operate.
Research-backed perspectives on Indian real estate and technology adoption.
PREOS content should teach something useful, explain operational reality and distinguish opinion from fact. Statistics, market claims, customer results and regulatory statements are sourced or clearly attributed.
Subscribe for new PREOS insights, product education and real estate operating perspectives.
Whether you’re exploring PREOS, setting up your account, managing your team’s workflows, or need help with an existing account, we’re here to help. Find answers, explore resources, or connect directly with the PREOS team.
Search our help resources to find answers about PREOS, account setup, modules, workflows, AI, billing and more.
Everything you need to get started with PREOS.
Manage and track your leads throughout the sales journey.
Manage your sales process from lead to site visit and beyond.
Manage project inventory with greater visibility.
Keep the customer journey organised in one place.
Track payment-related workflows and outstanding amounts.
Manage your channel partner ecosystem.
Turn operational data into management visibility.
Get help understanding and using PREOS AI.
Manage your PREOS users, access and account settings.
Getting started with a new operating platform should not be complicated. Our onboarding process is designed to help your team understand PREOS, configure your workflows and move toward effective day-to-day usage.
Have a question about a PREOS feature, workflow or module? Our support team can help you understand how to use the platform effectively.
Contact support@preos.tech →Need help with your account, users, access or configuration? Contact our team and we’ll guide you through the next steps.
Contact Support →Need help setting up PREOS for your organisation? Our team can guide you through onboarding, configuration and team enablement.
Talk to the PREOS Team →Experiencing a technical issue? Share the details with our support team so we can investigate and assist you.
Report an Issue →When contacting support, please include:
Tell us what you need help with.
Once you submit a support request, our team will review the information provided and contact you regarding the next steps. For urgent issues, please include “Urgent” in the subject line and provide enough information for our team to understand the issue.
Once your PREOS account is set up, our onboarding process helps you configure your workspace, projects, users and relevant workflows. Your team can then be trained and guided through the platform.
Click Request a Demo and submit your business details. Our team will contact you to schedule a walkthrough.
PREOS may offer a 14-Day Guided Trial, subject to eligibility and applicable commercial terms.
Submit a support request with your registered email, company/project details, description of the issue and, where possible, a screenshot or screen recording.
Yes. PREOS follows a structured onboarding approach covering setup, configuration, team onboarding, training and go-live.
Account administrators can manage users and access based on the capabilities available in their PREOS configuration.
Visit the Trust & Security information on the website or contact our team for questions about data handling, privacy and security.
Find answers to common questions about PREOS.
Explore FAQs →Read insights about real-estate operations, sales, technology and business management.
Read the Blog →Explore information about PREOS features, modules and workflows.
Explore Product →Learn how PREOS approaches data protection, privacy and security.
Explore Trust & Security →If you couldn’t find the answer you were looking for, we’re happy to help. Whether you’re evaluating PREOS, getting started, or already using the platform, our team is available to help you move forward.
Submit a support request any time and our team will review it. For detailed information about support scope, priorities and escalation, see our Support Policy.
Get answers, resolve issues and keep your PREOS workflows moving.
Common questions about PREOS — the platform, users and access, inventory, AI and getting started with a demo or trial.
PREOS is the AI-integrated operating system for real estate developers. It connects leads, sales, site visits, inventory, bookings, customers, channel partners, operations, collections and management reporting in one platform.
PREOS is built specifically for real estate developers and their teams — including sales, marketing, operations, inventory, channel partner, collections, post-sales and management teams.
PREOS connects workflows that usually live in separate spreadsheets, messaging apps and systems — reducing lost context, missed follow-ups, inventory confusion and the delay between operational activity and management visibility.
No. PREOS can be deployed for a single project as well as across multiple projects, and is designed to scale as your projects, teams and operations grow.
PREOS covers lead management, sales, site visits, inventory, bookings, customers, channel partners, collections, operations, and reporting & MIS, with AI assistance through Reos.
Yes. PREOS is designed around role-based workflows so each team accesses the information and functions relevant to their responsibilities.
Yes. PREOS is designed to support multi-project real estate operations, with centralised visibility and role-based access.
PREOS can support integrations depending on the systems, APIs and technical requirements involved. Discuss your existing technology stack with our team.
Reos is the AI assistant built into PREOS. It helps teams understand operational activity, prioritise opportunities and identify what deserves attention next.
Reos analyses the operational context available within the platform to surface insights, prioritise leads, suggest next actions and draft follow-ups for approval.
Reos works within the access controls and permissions configured for your organisation. Access to information follows the same role-based rules that apply to users.
Reos suggests; people decide. It does not independently confirm bookings, change prices, control inventory or override authorised users. See our AI Usage Policy for details.
PREOS uses a flexible pricing model based on your projects, users, modules, integrations and implementation needs, rather than a one-size-fits-all public price. Contact our team for a customised quotation.
PREOS may offer a 14-Day Guided Trial, subject to eligibility and applicable commercial terms.
Yes. Plans can be tailored to your organisation, and enterprise requirements can be evaluated for additional configuration or integration.
PREOS is designed for businesses handling sensitive customer, sales, inventory and operational information, consistent with our Privacy Policy and Data Processing Addendum.
Access is managed through organisational roles and permissions, helping businesses provide the right information to the right people.
Account administrators can manage users and access based on the role-based capabilities available in their PREOS configuration.
Data retention and deletion are handled per our Data Retention & Deletion Policy. See the Legal Center for details.
Contact PREOS Support, or request a demo to see the platform for your workflow.
Have a question about PREOS? Want to understand how it can fit your organisation? Our team would be happy to connect.
See PREOS in action and explore how it can connect your real estate operations, sales, inventory, customers and teams.
Get answers, resolve issues and keep your PREOS workflows moving.
Tell us a little about your business and our team will get in touch to schedule a personalised demo.
During the walkthrough, we’ll show you how PREOS can handle:
How enquiries are captured, assigned, tracked and followed up.
How teams manage customers, site visits, negotiations and bookings.
How your teams see available, held and booked units.
How partner-generated business can be tracked and attributed.
How payment schedules, dues and follow-ups are managed.
How leadership gets project and organisation-level visibility.
How AI can analyse activity and suggest what deserves attention next.
Interested in trying PREOS for 14 days? Submit your details and our team will connect with you to understand your requirements and guide you through the trial process.
Trial eligibility, included modules, user limits and onboarding requirements may vary based on the selected deployment.
Share your project, team structure and operational requirements.
We set up the relevant PREOS environment and workflows.
Invite the relevant users and assign role-based access.
Experience your sales, inventory and operational workflows inside PREOS.
At the end of the trial, we review your experience and discuss the right plan.
A software trial is most useful when you can evaluate it against the problems your team actually faces. Our guided trial helps your organisation understand how PREOS fits into existing workflows, roles and operational requirements.
Evaluate PREOS against your actual processes.
Bring the people who will actually use the platform.
Get help understanding the system.
Assess PREOS based on operational outcomes, not just features.
Every real estate business operates differently. PREOS plans and implementation can be tailored based on your projects, team size, modules and requirements. Tell us about your organisation and we’ll prepare a proposal designed around it.
Welcome to PREOS.
These Terms of Service ("Terms") constitute a legally binding agreement between AVREOS Technologies Private Limited, a company incorporated under the laws of the Republic of India ("AVREOS", "PREOS", "Company", "we", "our", or "us"), and every individual, organization, partnership, corporation, builder, developer, construction company, real estate firm, channel partner, consultant, contractor, employee, representative, or any other legal entity ("Subscriber", "Customer", "Organization", "you", or "your") that accesses, registers for, subscribes to, purchases, integrates with, or otherwise uses PREOS.
PREOS is an enterprise Software-as-a-Service (SaaS) platform developed to assist organizations in managing operational workflows relating to real estate development, sales, inventory management, customer relationship management (CRM), lead management, bookings, collections, analytics, artificial intelligence, workflow automation, reporting, integrations, and other business operations offered by PREOS from time to time.
These Terms govern every aspect of your relationship with PREOS, including use of the website, software platform, APIs, artificial intelligence services, mobile applications, documentation, integrations, customer support, trial services, paid subscriptions, and services introduced under the PREOS brand from time to time.
By creating an account, accepting these Terms electronically, beginning a free trial, purchasing a subscription, inviting Authorized Users, accessing any portion of PREOS, or otherwise using the Services, you acknowledge that you have carefully read, understood, and agreed to be legally bound by these Terms and applicable policies.
If you do not agree with these Terms, you must discontinue use of PREOS and refrain from accessing the Services.
PREOS is provided as a licensed Software-as-a-Service platform.
Nothing contained in these Terms shall be interpreted as creating any partnership, joint venture, agency, franchise, employment relationship, fiduciary relationship, reseller arrangement, or other legal association between AVREOS and any Subscriber.
Each Subscriber remains an independent legal entity solely responsible for management of its business, employees, customers, vendors, contractors, channel partners, and regulatory obligations.
PREOS provides software tools designed to assist organizations in conducting business operations efficiently.
AVREOS does not participate in, supervise, approve, guarantee, or assume responsibility for commercial transactions, contractual negotiations, pricing decisions, legal documentation, financial arrangements, customer relationships, construction activities, regulatory filings, sales commitments, or operational decisions made by Subscribers through PREOS.
All business decisions remain the responsibility of the Subscriber.
By using PREOS, you expressly represent and warrant that:
Electronic acceptance of these Terms shall have the same legal force and effect as a handwritten signature to the extent permitted by applicable law.
PREOS is intended for commercial and professional use.
To access or use PREOS, you must:
Organizations must ensure that every Authorized User accessing PREOS on their behalf complies with these Terms.
PREOS is not intended for consumer, household, or personal use.
AVREOS may refuse registration or restrict access where eligibility requirements are not satisfied.
Account — The digital account established within PREOS for an Organization.
Administrator — An Authorized User designated by the Organization with authority to manage subscriptions, users, permissions, billing information, integrations, and organizational settings.
AI Features — Artificial intelligence capabilities provided by PREOS, including AI Lead Scoring, AI Assistant, AI Search, AI Recommendations, AI Forecasting, AI Analytics, AI Reports, AI-generated summaries, intelligent workflow suggestions, predictive insights, natural language search, and future AI-powered services introduced by AVREOS.
Authorized User — An individual authorized by the Organization to access PREOS through a licensed user account.
Customer Data — Information uploaded, entered, imported, created, generated, processed, transmitted, stored, or otherwise made available within PREOS by the Organization or its Authorized Users, including customer records, leads, inventory information, pricing data, booking details, financial information, communications, reports, documents, media files, configuration settings, analytics, and operational data.
Documentation — User guides, manuals, knowledge base articles, technical documentation, API references, onboarding materials, tutorials, support resources, and other informational content published by AVREOS relating to PREOS.
Organization — The legal business entity subscribing to PREOS.
Organization Administrator — The primary administrator appointed by the Organization to represent it in matters relating to PREOS.
Platform — The PREOS software platform, including web applications, mobile applications, APIs, artificial intelligence services, dashboards, integrations, automation capabilities, documentation, and associated services.
Project — A development, community, property, construction project, township, commercial project, or other operational entity managed by an Organization within PREOS.
Services — Products, features, functionality, software, AI capabilities, APIs, integrations, customer support, professional services, documentation, websites, applications, updates, upgrades, enhancements, and future offerings provided under the PREOS brand.
Subscriber — The Organization purchasing or otherwise authorized to use PREOS.
Subscription — The commercial license granted by AVREOS permitting an Organization and its licensed Authorized Users to access PREOS for the applicable Subscription Term.
Subscription Term — The period for which a Subscription remains active following successful payment and activation.
Trial — A limited evaluation period that may be offered by AVREOS to eligible Organizations, subject to these Terms and any applicable trial conditions.
User License — The right granted to one named Authorized User to access PREOS under an active Subscription.
PREOS is licensed on an organizational basis. Each subscription is intended for use by a single legal business entity ("Organization"), including builders, developers, construction companies, real estate firms, channel partner organizations, or other approved commercial entities.
The Organization shall designate at least one Organization Administrator responsible for subscription management, billing, security, user administration, permissions, integrations, and communications with AVREOS.
Subject to the applicable subscription plan, an Organization may create and manage multiple projects, departments, business units, teams, locations, developments, or operational entities within a single PREOS account.
The Organization is responsible for ensuring that only authorized personnel are granted access and that information maintained within the Organization Account remains accurate and current.
AVREOS may rely upon instructions provided by the Organization Administrator concerning account management, subscription modifications, user administration, integrations, billing matters, and security settings unless otherwise required by law.
The Organization shall promptly notify AVREOS of unauthorized access, compromised credentials, suspected misuse, or other security incidents affecting its PREOS account.
PREOS may be licensed on a named-user basis. Every individual accessing PREOS must have an assigned User License where required by the applicable subscription plan.
User Licenses are personal to the assigned Authorized User and may not be simultaneously shared among multiple individuals. Generic or shared credentials may constitute a violation where they undermine security, accountability, or licensing requirements.
The Organization is responsible for maintaining sufficient User Licenses for individuals requiring access.
Authorized Users may include employees, directors, officers, consultants, contractors, sales representatives, channel partner personnel, or other individuals authorized by the Organization.
Organizations may reassign User Licenses when personnel leave or no longer require access, subject to applicable licensing policies.
AVREOS may implement reasonable technical controls to detect excessive credential sharing or suspicious authentication activity.
AVREOS may introduce additional licensing models, enterprise licensing programs, or volume licensing arrangements in the future.
PREOS provides configurable Role-Based Access Control ("RBAC") to enable Organizations to manage operational responsibilities securely.
Organizations may create, modify, assign, revoke, or customize user roles according to their requirements.
Depending on subscription and configuration, roles may include Organization Administrator, Managing Director / CEO, Sales Manager, Sales Executive, Pre-Sales Executive, CRM Executive, Marketing Executive, Accounts Executive, Channel Partner Manager, Site Manager, and custom organizational roles.
Organizations remain responsible for determining access permissions, segregation of duties, approval workflows, and internal governance.
AVREOS is not responsible for actions performed by Authorized Users acting within permissions assigned by the Organization.
Organizations should periodically review permissions and promptly revoke access when individuals no longer require it.
PREOS is offered through commercial subscription plans.
Plans may differ based upon licensing quantities, supported features, storage allocations, AI usage, API access, integrations, support entitlements, enterprise capabilities, or other commercial criteria established by AVREOS.
Plans, pricing, entitlements, and commercial offerings are published separately on the PREOS Pricing page or communicated through an authorized commercial proposal.
Unless otherwise agreed in writing, subscriptions are billed according to the applicable commercial terms.
Subscription plans may evolve as PREOS introduces functionality, infrastructure improvements, AI capabilities, enterprise services, compliance features, security enhancements, and other offerings.
Nothing guarantees that a subscription plan, feature, integration, promotional offer, or commercial arrangement will remain available indefinitely.
AVREOS may introduce, modify, discontinue, replace, or rename plans, provided changes do not adversely affect active subscriptions during the then-current Subscription Term except where required by law, security considerations, or technical necessity.
Eligible Organizations may receive one fourteen (14) day free trial of PREOS.
A trial is intended to enable prospective Subscribers to evaluate functionality, suitability, and compatibility before purchasing a commercial subscription.
AVREOS may require valid registration information and, where applicable, a payment method for trial activation.
A trial does not automatically convert to a paid subscription unless the applicable conversion terms are expressly disclosed before activation and accepted by the Organization.
The Organization may cancel the trial according to the applicable trial or account procedures.
AVREOS may modify, suspend, refuse, limit, or discontinue free trials, including where multiple trial accounts are created to circumvent licensing requirements or where fraudulent or abusive conduct is suspected.
A free trial for one Organization does not create an obligation to provide trials to other Organizations.
Subscription fees are payable according to the applicable commercial terms.
Fees are exclusive of applicable taxes, duties, levies, governmental charges, payment processing fees where applicable, and other statutory obligations unless expressly stated otherwise.
The Organization shall maintain valid, current, and complete billing information.
Payments may be processed through payment service providers approved by AVREOS.
Invoices, payment confirmations, renewal notices, tax invoices, and billing communications may be delivered electronically.
Failure to maintain a valid payment method may result in suspension of renewals or interruption of Services.
Subscription fees are generally non-refundable except where expressly provided in applicable commercial terms or required by law.
Where a Subscription is configured for automatic renewal, it will renew at the end of the applicable Subscription Term unless cancelled before the renewal date.
The Organization authorizes AVREOS or its payment processor to charge applicable renewal fees according to the commercial terms.
The Organization may disable automatic renewal before the renewal date through applicable account settings or by contacting PREOS Support.
If renewal payment cannot be processed, AVREOS may provide a reasonable grace period. AVREOS may suspend or terminate access where payment remains outstanding beyond that period.
AVREOS may modify subscription pricing for future Subscription Terms upon reasonable prior notice.
Subject to these Terms and payment of applicable fees, AVREOS grants the Subscriber a limited, non-exclusive, non-transferable, non-sublicensable, revocable license to access and use PREOS solely for its internal business operations during the applicable Subscription Term.
The license permits the Organization to:
No ownership rights are transferred. AVREOS retains all rights, title, and interest in PREOS and its intellectual property.
The Subscriber shall not, directly or indirectly, and shall ensure that Authorized Users do not:
Any use beyond the granted license may constitute a material breach.
The Organization retains ownership of Customer Data submitted to PREOS.
Nothing in these Terms transfers ownership of Customer Data to AVREOS.
The Organization grants AVREOS a limited, worldwide, non-exclusive license to host, process, transmit, store, index, back up, analyze, and otherwise use Customer Data solely as necessary to provide, operate, maintain, secure, support, and administer the Services; deliver requested features, including AI Features; perform backups and disaster recovery; prevent fraud and detect security threats; comply with legal obligations; provide customer support; and fulfil contractual obligations. AVREOS may use aggregated or de-identified information that does not identify the Organization or an individual for service analytics, security, reliability, and product or service improvement, subject to applicable law. Nothing in this clause authorizes AVREOS to use Customer Data to train or fine-tune AI models except where expressly agreed in writing and permitted by applicable law.
AVREOS shall not sell Customer Data to advertisers or unrelated third parties.
Customer Data shall be processed in accordance with the PREOS Privacy Policy and applicable data-protection laws.
The Organization remains responsible for the accuracy, legality, completeness, and integrity of Customer Data.
AVREOS is not responsible for verifying the authenticity or legal validity of Customer Data.
The Subscriber agrees to:
PREOS supports business operations but does not replace the Subscriber's responsibility for governance, internal controls, legal compliance, accounting practices, regulatory obligations, or professional judgment.
PREOS may include AI capabilities designed to assist Organizations with operational efficiency, decision-making, productivity, reporting, forecasting, and business analysis.
AI Features may include AI Lead Scoring, AI Assistant, AI Search, AI Recommendations, AI Forecasting, AI Analytics, AI Reports, intelligent summaries, natural language queries, workflow suggestions, and future AI capabilities introduced by AVREOS.
AI generates probabilistic outputs and may produce incomplete, inaccurate, outdated, inconsistent, or unexpected results.
Accordingly:
AVREOS does not warrant that AI-generated outputs will always be accurate, complete, suitable, error-free, or fit for a particular purpose.
AVREOS may improve, replace, modify, suspend, limit, or discontinue AI Features as technology evolves, subject to applicable law and applicable subscription entitlements.
AVREOS implements administrative, technical, and organizational safeguards designed to protect the confidentiality, integrity, and availability of Customer Data.
Measures may include:
No technology platform can guarantee absolute security. AVREOS does not warrant that PREOS will be immune from cyberattacks, unauthorized access, malware, service interruptions, telecommunications failures, internet disruptions, or other incidents beyond reasonable control.
Security is a shared responsibility. Organizations are responsible for protecting credentials, managing permissions, using strong authentication practices, and maintaining secure devices and networks.
Each party may obtain confidential or proprietary information belonging to the other.
Confidential Information includes business strategies, software architecture, product roadmaps, technical documentation, source code, algorithms, AI models, pricing proposals, customer information, security procedures, infrastructure details, financial information, non-public operational information, commercial agreements, product demonstrations, training materials, and trade secrets.
Each party agrees to maintain confidentiality, use Confidential Information solely for purposes related to these Terms, restrict disclosure to persons with a legitimate need to know, and protect it using reasonable care.
These obligations do not apply to information that becomes public without breach, was lawfully known before disclosure, is independently developed, is lawfully obtained from another source without confidentiality obligations, or must be disclosed by law or lawful authority.
Confidentiality obligations survive termination.
PREOS may integrate with or facilitate connections to third-party products, services, platforms, APIs, communication providers, payment gateways, productivity tools, business applications, and other external technologies.
Such integrations may include messaging platforms, email and SMS providers, telephony providers, Meta platforms, Google services, Microsoft services, payment gateways, accounting software, calendar services, document storage providers, identity providers, analytics platforms, and future third-party integrations.
Third-party services are operated independently from PREOS.
AVREOS does not control and is not responsible for their availability, interruptions, pricing, security practices, privacy practices, data handling, API changes, functional limitations, or business decisions.
Use of third-party services remains subject to their terms and privacy policies.
Where an integration becomes unavailable due to circumstances beyond AVREOS's reasonable control, AVREOS will use commercially reasonable efforts to restore compatibility or provide an alternative where feasible, but will not be liable for interruptions arising solely from the third-party provider.
PREOS may provide APIs for integrations with other software systems.
API access may be subject to subscription entitlements, authentication requirements, usage limitations, documentation, security requirements, fair-use policies, and commercial agreements.
Subscribers shall keep API credentials confidential.
Subscribers shall not use APIs to circumvent licensing restrictions, access unauthorized data, overload infrastructure, interfere with other Subscribers, perform unauthorized scraping, conduct malicious activities, or reverse engineer PREOS functionality.
AVREOS may modify, enhance, replace, version, deprecate, suspend, or discontinue APIs where necessary to improve security, performance, or functionality.
Reasonable efforts will be made to communicate material API changes in advance where practicable.
Subscribers shall use PREOS responsibly, ethically, and lawfully.
Subscribers shall not use PREOS to:
AVREOS may investigate suspected violations and take appropriate action, including suspension or termination where necessary.
Nothing limits AVREOS's ability to cooperate with law enforcement or governmental authorities where legally required.
AVREOS is committed to providing a reliable, secure, and continuously improving software platform.
PREOS is designed with the objective of achieving high service availability; however, uninterrupted access cannot be guaranteed.
Interruptions may occur due to scheduled or emergency maintenance, infrastructure upgrades, internet service disruptions, cloud provider incidents, telecommunications failures, security events, software defects, force majeure events, or circumstances beyond AVREOS's reasonable control.
AVREOS may provide service availability objectives or an SLA where applicable.
Nothing guarantees uninterrupted, error-free, or continuous availability.
AVREOS may make experimental, preview, beta, early-access, or evaluation features available.
Beta Features may be incomplete, contain defects, produce inaccurate outputs, change without notice, be discontinued, be replaced, or never become generally available.
Unless otherwise expressly stated, Beta Features are provided "AS IS" and may be excluded from service availability commitments, warranties, and service-level guarantees.
Subscribers use Beta Features at their discretion.
Feedback regarding Beta Features may be used by AVREOS to improve PREOS.
AVREOS may temporarily suspend, restrict, or limit access to PREOS where reasonably necessary to protect security, integrity, availability, lawful operation, or the interests of PREOS, Subscribers, or third parties.
AVREOS may suspend access where:
Where reasonably practicable, advance notice will be provided. Immediate action may be taken where necessary.
Suspension does not relieve the Subscriber of payment obligations accrued before or during suspension.
These Terms remain effective until terminated.
The Subscriber may terminate its Subscription by disabling automatic renewal before the renewal date, providing notice according to applicable subscription procedures, or following applicable cancellation procedures.
Termination by the Subscriber does not entitle it to refunds except where expressly provided in applicable commercial terms or required by law.
AVREOS may terminate these Terms or access where:
Upon termination:
Termination does not affect rights or obligations accrued before termination.
PREOS recognizes that Customer Data represents valuable business information belonging to the Subscriber.
Subject to an active Subscription or applicable post-termination retention period, Subscribers may export Customer Data using available platform functionality or methods supported by AVREOS.
Following expiration or termination, Customer Data is retained and deleted in accordance with the PREOS Data Retention & Deletion Policy, including its 90-day wind-down and applicable backup-retention periods.
During that period, the Subscriber may request export, subject to verification, outstanding obligations, and technical feasibility.
After the applicable retention period, AVREOS may permanently delete Customer Data from production systems in accordance with operational procedures and backup retention schedules.
Recovery may not be possible after permanent deletion.
PREOS, including software, source code, object code, architecture, databases, AI models, workflows, documentation, designs, graphics, interfaces, dashboards, APIs, trademarks, logos, branding, inventions, know-how, methodologies, reports, templates, and related intellectual property are and remain the property of AVREOS Technologies Private Limited or its licensors.
Nothing transfers ownership of PREOS or its intellectual property to the Subscriber.
Subscribers acquire only the limited right to access and use PREOS during an active Subscription Term.
Subscribers shall not claim ownership, copy substantial portions, create derivative works, reverse engineer proprietary technologies, remove copyright notices, misappropriate trade secrets, or register confusingly similar trademarks, domains, or branding.
All rights not expressly granted are reserved by AVREOS.
PREOS welcomes suggestions, ideas, recommendations, comments, enhancement requests, usability feedback, feature proposals, bug reports, and other communications relating to the Services ("Feedback").
By voluntarily submitting Feedback, the Subscriber grants AVREOS a perpetual, worldwide, irrevocable, royalty-free, transferable, sublicensable right to use, modify, commercialize, publish, incorporate, reproduce, and otherwise exploit such Feedback without restriction or compensation.
Nothing obligates AVREOS to implement Feedback.
PREOS is provided on an "AS IS" and "AS AVAILABLE" basis.
To the maximum extent permitted by applicable law, AVREOS disclaims warranties, whether express, implied, statutory, or otherwise, including warranties relating to merchantability, satisfactory quality, fitness for a particular purpose, non-infringement, uninterrupted operation, accuracy, reliability, availability, or compatibility.
AVREOS does not warrant that:
Subscribers acknowledge that software services have technological limitations and commercial decisions should not rely solely upon automated outputs.
To the fullest extent permitted by applicable law, AVREOS, its directors, officers, employees, affiliates, licensors, contractors, suppliers, and representatives shall not be liable for indirect, incidental, consequential, exemplary, special, punitive, or similar damages arising from or relating to PREOS.
Without limitation, AVREOS shall not be liable for loss of profits, business opportunities, revenue, goodwill, anticipated savings, loss or corruption of Customer Data, business interruption, regulatory penalties arising from Subscriber conduct, decisions made using AI-generated outputs, third-party service failures, or cyber incidents beyond reasonable control.
Except where liability cannot legally be excluded, AVREOS's aggregate liability arising out of these Terms shall not exceed the total subscription fees actually paid by the Subscriber to AVREOS during the twelve (12) months immediately preceding the event giving rise to the claim.
Nothing excludes liability that cannot legally be limited.
The Subscriber agrees to defend, indemnify, and hold harmless AVREOS Technologies Private Limited, its affiliates, directors, officers, employees, licensors, contractors, successors, and assigns from and against claims, demands, proceedings, damages, liabilities, losses, penalties, fines, costs, and expenses, including reasonable legal fees, arising from or relating to:
AVREOS shall notify the Subscriber of an indemnifiable claim where practicable.
Neither party shall be liable for delays or failures resulting from circumstances beyond its reasonable control, including natural disasters, floods, earthquakes, fire, epidemics, pandemics, government actions, war, terrorism, civil unrest, internet outages, cloud infrastructure failures, telecommunications disruptions, power failures, labour disputes, or extraordinary cyberattacks.
The affected party shall use commercially reasonable efforts to resume performance as soon as reasonably practicable.
Subject to mandatory local law that cannot lawfully be excluded, these Terms shall be governed by and construed in accordance with the laws of the Republic of India, without regard to conflict-of-law principles.
The parties shall first attempt to resolve disputes through good-faith negotiations.
Where a dispute cannot be resolved amicably, the parties agree to refer the matter to arbitration in accordance with the Arbitration and Conciliation Act, 1996, as amended.
The seat and venue of arbitration shall be Hyderabad, Telangana, India.
Subject to arbitration, courts located in Hyderabad, Telangana shall have exclusive jurisdiction over matters requiring judicial intervention.
Nothing in this Section prevents a party from seeking urgent interim or injunctive relief from a court of competent jurisdiction where permitted by law.
Nothing in these Terms excludes or limits rights, remedies, or protections that cannot lawfully be excluded or limited under mandatory applicable law. If a mandatory local legal requirement conflicts with these Terms, that requirement will prevail to the extent of the conflict.
Where required by applicable law or contract, additional terms, data-processing agreements, transfer mechanisms, disclosures, consent mechanisms, or other safeguards may apply.
Subscribers are responsible for ensuring that their use of PREOS and the Customer Data they process through PREOS complies with laws applicable to them, including applicable privacy, data protection, consumer, communications, tax, sanctions, employment, and sector-specific requirements.
AVREOS's primary legal framework is the law applicable to AVREOS as an Indian company. Where PREOS is offered or used in another jurisdiction and mandatory local law imposes additional or different requirements, AVREOS will comply with those requirements to the extent applicable.
PREOS may be made available to Subscribers and Authorized Users in India and other jurisdictions. These Terms are intended to apply globally, subject to mandatory laws applicable to the relevant Subscriber, Authorized User, transaction, processing activity, or service.
AVREOS may revise these Terms from time to time to reflect changes in law, technology, business operations, security practices, or PREOS Services.
Material changes will become effective upon publication or as otherwise communicated to Subscribers.
Where required by applicable law, AVREOS will provide advance notice of material amendments.
Continued use of PREOS after the effective date of revised Terms constitutes acceptance of the updated Terms to the extent permitted by applicable law.
Questions regarding these Terms may be directed to AVREOS Technologies Private Limited through the contact channels published on preos.tech.
AVREOS may designate specific communication channels for legal notices, billing matters, privacy inquiries, security reporting, and customer support.
Official communications issued through designated channels shall constitute valid notice under these Terms where permitted by applicable law.
These Terms, together with policies expressly incorporated by reference, including the Privacy Policy, Cookie Policy, Subscription & Billing Policy, Refund & Cancellation Policy, Acceptable Use Policy, AI Usage Policy, Data Processing Addendum (DPA), Service Level Agreement (SLA), Support Policy, Data Retention & Deletion Policy, and other applicable PREOS policies, constitute the agreement between the Subscriber and AVREOS regarding use of PREOS and supersede prior understandings, communications, proposals, or agreements relating to the Services, except for separately executed agreements that expressly govern the relationship.
Questions about this document? Contact support@preos.tech.
AVREOS may act in different capacities depending on the data and processing activity.
Processor / Data Processor. This applies to Customer Data that a Subscriber uploads to or generates within PREOS, including records concerning leads, homebuyers, channel partners, employees, site visits, calls, bookings, payments and related documents. The Subscriber generally determines the purposes and means of processing this Customer Data. The PREOS Data Processing Addendum governs this processing.
Controller / Data Fiduciary. This applies to data AVREOS processes for its own purposes, such as account administration, website visitors, support, billing, security and direct marketing where applicable.
If a builder recorded your enquiry in PREOS and you want your data corrected or deleted, the relevant Subscriber is generally the party responsible for that Customer Data. Where AVREOS acts as a Processor, we will assist the Subscriber in accordance with our agreement and applicable law. Where AVREOS acts as Controller/Data Fiduciary, Sections 7 and 8 apply directly.
Identity: name, job title and organisation, where provided, to create and administer an account.
Contact: work email and phone number for authentication, service notices and support.
Authentication: password credentials, OTP/verification information, session tokens and related security information. Passwords are stored in protected form and are not recoverable by us.
Billing: billing name, address, GSTIN or other tax identifiers, invoice information and transaction history as required for billing and legal compliance.
Usage: features used, timestamps, diagnostics and error information to operate, secure and improve the Platform.
Technical: IP address, browser, device and similar technical information for security, fraud prevention and diagnostics.
Support: correspondence with our team and information necessary to resolve support requests.
Payment card details are not intended to be stored by PREOS where payment processing is handled by a third-party payment provider through a third-party payment provider.
Subscribers use PREOS to manage their own real-estate sales and operations. Customer Data may include prospective buyer names and contact details, requirements and budget information, site-visit records, call records or recordings where enabled, booking and payment schedules, and documents such as agreements or identity documents.
We process Customer Data to provide, operate, secure and support the Platform and as otherwise instructed or agreed with the Subscriber. We do not independently determine the Subscriber's purposes for collecting Customer Data. We do not sell, rent or license Customer Data to advertisers or data brokers, and we do not use Customer Data for unrelated purposes.
Depending on the context and applicable law, we may process personal data to:
Where we rely on consent, you may withdraw it in accordance with applicable law. Withdrawal does not affect processing lawfully carried out before withdrawal.
Sub-processors. We may use service providers that process data on our behalf under contractual arrangements and subject to applicable requirements. Our current Subprocessor List identifies relevant providers, their functions and, where available, applicable processing locations.
The Subscriber's organisation. Customer Data may be visible to Authorized Users permitted by the Subscriber according to its configured roles and permissions.
Legal and regulatory requests. We may disclose data where required by applicable law or a valid order, warrant, notice or other legally enforceable request from a court, regulator or law-enforcement authority. We may take reasonable steps to verify the request and, where legally permitted, limit disclosure to the information required or reasonably relevant to the request. Where legally permitted, we may notify the affected Subscriber or person before or after disclosure. We will not provide notice where prohibited by law, where a lawful order requires secrecy, or where notice could reasonably compromise an investigation, security measure or other lawful process. We may preserve relevant records where required by law or a valid legal process. In an emergency, we may disclose information where permitted or required by applicable law to address an imminent risk of serious harm or other legally recognised emergency.
Corporate transactions. If AVREOS is involved in a merger, acquisition, financing, reorganisation or sale of assets, relevant data may transfer as part of that transaction subject to applicable law and appropriate protections.
We do not share personal data with advertisers or data brokers for their own marketing purposes.
PREOS application services are hosted through our cloud hosting provider. The production database for structured application data is hosted using MongoDB Atlas on AWS infrastructure in the Hyderabad region (AWS ap-south-2), as currently configured.
Structured application data may include leads, visitors, inventory, calls, site visits and other operational records.
Files such as brochures, images, master plans and legal documents are not stored as binary files inside MongoDB documents and PREOS does not use MongoDB GridFS for these files. Where file storage is enabled, the binary files are intended to be stored through a separate object-storage service, while MongoDB stores related metadata and file references. The applicable storage provider and processing location may be identified in
Data may be processed in India or other jurisdictions where AVREOS or its service providers operate or where processing is required to provide PREOS. Where personal data is transferred across borders, AVREOS will apply safeguards and transfer mechanisms required by applicable law. Where another jurisdiction imposes mandatory requirements that differ from this Policy, those requirements will apply to the extent applicable.
We retain personal data only for as long as reasonably necessary for the purposes described in this Policy, to provide PREOS, meet contractual and legal obligations, resolve disputes, maintain security, and enforce agreements.
Customer Data after a subscription ends: retained for the period specified in the applicable agreement and Data Retention & Deletion Policy, followed by deletion or return subject to legal obligations and backup-cycle requirements.
Application and access logs: retained for the period reasonably necessary for security, operational and legal requirements.
Support correspondence: retained for the period reasonably necessary to manage the support relationship and legal obligations.
Invoices and tax records: retained for the period required by applicable accounting and tax laws.
Marketing contacts: retained until consent is withdrawn where consent is the applicable basis, or for a reasonable period of inactivity subject to applicable law.
Backup copies may remain for the configured backup-retention period before being overwritten or deleted as part of the normal backup lifecycle. Current MongoDB Atlas backup configuration includes automated hourly/daily backups and longer weekly/monthly retention schedules; these settings may change as our infrastructure evolves.
The Data Retention & Deletion Policy provides additional operational detail.
Where AVREOS acts as Controller/Data Fiduciary, you may have rights under applicable law, which may include access, correction, completion, updating, deletion/erasure, withdrawal of consent, objection or restriction where applicable, data portability where applicable, and the right to raise a grievance.
For Customer Data processed by AVREOS as a Processor, requests concerning that data should generally be directed to the relevant Subscriber. We will assist the Subscriber as required by the applicable agreement and law.
To exercise a right concerning data for which AVREOS is responsible, contact grievance@avreos.in. We may request reasonable information to verify identity and protect personal data from unauthorised disclosure. We will respond within the period required by applicable law or, where no specific period applies, within a reasonable period.
Grievance Officer: Sumalatha G
Designation: Grievance Officer, AVREOS Technologies Private Limited
Email: grievance@avreos.in
How to raise a grievance: Write to the Grievance Officer at the email or postal address above. Describe the concern, the data involved and the outcome you are seeking. No particular form is required.
Where applicable under Indian law, individuals may pursue escalation to the competent data-protection authority after using the applicable grievance mechanism. Individuals in other jurisdictions may have additional rights or complaint routes under local law.
We use technical and organisational measures designed to protect personal data against unauthorised access, alteration, disclosure, loss and misuse.
Our security controls and technical and organisational measures are described in greater detail in the PREOS Security Policy. No platform can guarantee absolute security.
AVREOS maintains incident-response processes designed to identify, contain, investigate and remediate security incidents.
Where AVREOS acts as a Processor, AVREOS will notify the affected Subscriber without undue delay and, where required under the PREOS Data Processing Addendum, within 72 hours after becoming aware of the relevant Personal Data Breach. AVREOS will provide information reasonably available to help the Subscriber meet its own obligations.
Where AVREOS acts as Controller/Data Fiduciary, AVREOS will assess the incident and make notifications to individuals and authorities where required by applicable law and within the applicable legal timelines.
For incidents subject to applicable cyber-security reporting requirements, AVREOS will comply with the reporting obligations and timelines applicable to the incident.
PREOS and the PREOS website may use cookies or similar technologies that are necessary for authentication, security, session management and core functionality.
We do not currently use advertising cookies or third-party tracking cookies for behavioural advertising.
If we introduce analytics, advertising or other non-essential cookies or similar technologies, we will update the applicable Cookie Policy and obtain consent where required by law.
PREOS includes AI-enabled features that may generate suggestions, scores, summaries, drafts and other assistive outputs.
The PREOS AI Usage Policy provides additional information.
PREOS is a business platform and is not intended to be used directly by children. We do not knowingly collect personal data directly from children for the purpose of providing PREOS accounts.
Where a Subscriber processes information concerning a minor in PREOS, the Subscriber is responsible for complying with the applicable law governing that processing, including requirements concerning parental or guardian consent where applicable.
We may send product updates, event invitations, educational information and offers to existing Subscribers and to people who request or permit marketing communications, subject to applicable law.
Marketing communications will provide an appropriate unsubscribe or opt-out mechanism where required. Service communications, including security alerts, billing notices and material changes to legal documents, are not marketing communications and may continue where necessary to provide the service or comply with law.
If you use PREOS to process other people's personal data, you are responsible for determining and documenting the lawful basis and purposes for that processing and for complying with applicable privacy and data-protection laws.
Subscribers must not use PREOS to process personal data in a manner that violates applicable law, the Terms of Service or the Acceptable Use Policy.
The current Policy will be published on the PREOS website, with the effective date shown at the top.
AVREOS Technologies Private Limited
CIN: U74102TS2025PTC205165
Grievance Officer (data protection): grievance@avreos.in
Privacy and data protection: privacy@avreos.in
Legal notices, copyright, trademark, security reports: legal@avreos.in
Customer support (PREOS): support@preos.tech
AVREOS Technologies Private Limited. CIN U74102TS2025PTC205165.
Questions about this document? Contact support@preos.tech.
A cookie is a small text file a website stores on your device. It allows the site to recognise your browser between requests — for example, to keep you signed in as you move between pages. This Policy applies to cookies used on PREOS websites and web-based services. It is intended to operate globally; mandatory local privacy and cookie requirements will apply where applicable.
| Cookie type | Purpose | Duration | Essential |
|---|---|---|---|
| Session cookie | Maintains your signed-in session as you move between pages of the application. | Deleted when you close your browser or sign out | Yes |
| Authentication token | Confirms your identity on each request so that others cannot access your account. | Expires on sign-out or after inactivity | Yes |
| Security cookie | Protects against cross-site request forgery. | Session | Yes |
Based on the current PREOS configuration covered by this Policy, these cookies are set by AVREOS and are not used for advertising, retargeting or cross-site profiling. If a third-party cookie is introduced in the future, it will be disclosed and handled in accordance with applicable law.
Strictly necessary cookies may be used without consent where permitted by applicable law because the service cannot function without them. Disabling them will prevent you from signing in. If we introduce any non-essential cookie — for example product analytics — we will update this Policy, provide appropriate notice, and obtain consent where required by applicable law. We will not set a non-essential cookie where applicable law requires prior consent unless that consent has been obtained.
If we introduce any non-essential cookie in future — for example product analytics — we will update this Policy, tell you before it takes effect, and ask for your consent where the law requires it. We will not set a non-essential cookie without doing so.
Most browsers allow you to view, delete and block cookies through their settings. Blocking the cookies listed in section 2 will prevent PREOS from working, because you will not be able to remain signed in.
Signing out of PREOS clears your session cookie and invalidates your authentication token.
We will update this Policy if the cookies we use change. The effective date at the top shows when it was last revised. Where a change introduces a non-essential cookie, we will provide appropriate notice before it takes effect. Information collected through cookies, where it constitutes personal data, is handled in accordance with the PREOS Privacy Policy and applicable law.
We will update this Policy if the cookies we use change. The effective date at the top shows when it was last revised. Where a change introduces a non-essential cookie, we will give notice before it takes effect.
AVREOS Technologies Private Limited
CIN: U74102TS2025PTC205165
Manjeera Trinity Corporate, JNTU–HITECH Road, Near Lulu Mall,
KPHB Phase 3, Kukatpally, Hyderabad, Telangana – 500072, India
| Purpose | Contact |
|---|---|
| Grievance Officer (data protection) | grievance@avreos.in |
| Privacy and data protection | privacy@avreos.in |
| Legal notices, copyright, trademark, security reports | legal@avreos.in |
| Customer support (PREOS) | support@preos.tech |
AVREOS Technologies Private Limited. CIN U74102TS2025PTC205165.
Questions about this document? Contact support@preos.tech.
PREOS is licensed on a per-user basis. Fees are stated in the Order Form and depend on the plan, the number of User Licences and the Subscription Term.
| Element | Basis |
|---|---|
| User Licence | One named Authorized User. Licences are not shared between individuals. |
| Plan | Determines the modules, limits and support arrangements available. |
| Subscription Term | As stated in the Order Form. Annual by default; monthly available on request. |
| Project fees | Where applicable, charged per project configured in the Platform. |
2.1 Annual is the default. Subscriptions are invoiced annually in advance unless the Order Form states otherwise.
2.2 Monthly billing. Monthly billing is available on request at the same per-user rate, invoiced monthly in advance.
2.3 Mid-term changes. Additions during a term are invoiced pro rata and co-terminate with the current Subscription Term, so that all charges align to a single renewal date.
An eligible Subscriber may receive one fourteen (14) day free trial of PREOS. No fee is charged during the 14-day Trial.
At the end of the Trial, access ends or may be converted to a paid Subscription only on the terms disclosed and accepted before conversion. If no paid Subscription is activated, the account enters the wind-down described in the Data Retention & Deletion Policy.
4.1 Indirect taxes. All fees are exclusive of applicable indirect taxes unless the Order Form states otherwise. AVREOS will charge and show applicable taxes on invoices as required by law, and the Subscriber shall pay them in addition to the fees.
4.2 Tax invoices. AVREOS will issue invoices containing the information required by applicable law, including tax registration and tax details where applicable.
4.3 Tax information. The Subscriber shall provide any tax registration or exemption information reasonably required for accurate invoicing. AVREOS may be unable to amend invoices retrospectively where prohibited by applicable tax law.
4.4 Withholding taxes. Where the Subscriber is required by applicable law to withhold tax, it shall provide the required withholding certificate or other evidence within the applicable statutory period. Amounts properly withheld and remitted will be treated as paid to AVREOS to the extent supported by the required documentation.
4.5 Other taxes. Fees are exclusive of other taxes, duties or levies that may apply, except taxes imposed on AVREOS's net income. The Subscriber shall bear taxes properly chargeable to it under applicable law.
5.1 Invoicing. AVREOS issues a tax invoice at the start of each Subscription Term, or at the start of each month where monthly billing has been agreed.
5.2 Payment term. Invoices are payable within 15 days of the invoice date unless the Order Form states otherwise.
5.3 Payment methods. Payments may be processed through third-party payment service providers. AVREOS does not store payment card details.
5.4 Currency. Fees are payable in the currency stated in the Order Form. If no currency is stated, fees are payable in Indian Rupees.
6.1 AVREOS may charge interest at 1.5% per month on overdue amounts, or the maximum permitted by law if lower.
6.2 Where an invoice remains unpaid 30 days after its due date, AVREOS may suspend the Services on 7 days’ written notice. Suspension does not relieve the Subscriber of the obligation to pay.
6.3 AVREOS will restore access promptly on payment.
6.4 AVREOS will not suspend access in respect of an amount genuinely disputed under section 9.
7.1 Adding users. User Licences may be added at any time, charged pro rata for the remainder of the Subscription Term.
7.2 Reducing users. User Licences may not be reduced mid-term. A reduction takes effect at renewal, on notice given at least 30 days before the end of the current term.
7.3 Upgrading a plan. A plan may be upgraded at any time. The difference is charged pro rata.
7.4 Downgrading a plan. A downgrade takes effect at renewal. Functionality available only on the higher plan ceases at that point, and the Subscriber should export any data held in those modules beforehand.
8.1 Renewal. Subscriptions renew automatically for successive terms of the same length unless either party gives written notice of non-renewal at least 30 days before the end of the current term.
8.2 Reminder. AVREOS will send a renewal reminder to the Subscriber’s billing contact at least 30 days before an annual term renews.
8.3 Price changes. AVREOS may change fees with effect from a renewal, on at least 60 days’ written notice before the end of the then-current term. Fees do not change during a term. A Subscriber that does not accept a change may give notice of non-renewal within the notice period.
A Subscriber disputing an invoice should notify support@preos.tech within 15 days of the invoice date, stating the amount disputed and the reason. AVREOS will investigate and respond within 15 business days. Undisputed amounts remain payable on the due date.
AVREOS retains invoices and billing records for 8 financial years, or longer where required by applicable law. This applies notwithstanding deletion of Customer Data under the Data Retention & Deletion Policy, and covers billing records only — not Customer Data.
AVREOS Technologies Private Limited
CIN: U74102TS2025PTC205165
Office Space No. 1204, Plot No. 52, Sy. No. 1050P,
Manjeera Trinity Corporate, JNTU–HITECH Road, Near Lulu Mall,
KPHB Phase 3, Kukatpally, Hyderabad, Telangana – 500072, India
| Purpose | Contact |
|---|---|
| Grievance Officer (data protection) | grievance@avreos.in |
| Privacy and data protection | privacy@avreos.in |
| Legal notices, copyright, trademark, security reports | legal@avreos.in |
| Customer support (PREOS) | support@preos.tech |
AVREOS Technologies Private Limited. CIN U74102TS2025PTC205165.
Office Space No. 1204, Plot No. 52, Sy. No. 1050P, Manjeera Trinity Corporate, JNTU–HITECH Road, Near Lulu Mall, KPHB Phase 3, Kukatpally, Hyderabad, Telangana – 500072, India
Questions about this document? Contact support@preos.tech.
A Subscriber may cancel by giving written notice to support@preos.tech at least 30 days before the end of the current Subscription Term. Cancellation takes effect at the end of that term. Access continues, and fees remain payable, until then.
Cancellation does not delete data immediately. The account enters the wind-down described in the Data Retention & Deletion Policy: the 90-day wind-down described in the Data Retention & Deletion Policy: 30 days of read-only access with full export, followed by 60 days of suspension during which export is available on request.
Subscription Fees, User Licence fees, project fees, AI add-on fees, onboarding fees and professional services fees are non-refundable once the relevant Service has been provisioned or delivered.
Provisioning of an Organization Account, activation of User Licences, or commencement of onboarding constitutes delivery for the purposes of this Policy.
| Circumstance | Refund |
|---|---|
| Payment taken but the Subscription could not be provisioned due to a fault of AVREOS that cannot be resolved | Full refund of the amount paid |
| Duplicate payment, or an amount charged in excess of the Order Form | Refund of the excess |
| AVREOS terminates the Subscription other than for the Subscriber’s breach | Pro rata refund of prepaid fees |
| The Subscriber terminates for AVREOS’ material breach under clause 13.2 of the Terms of Service | Pro rata refund of prepaid fees |
| Chronic failure to meet the availability commitment, as defined in section 5 of the SLA | Pro rata refund of prepaid fees |
| A material adverse change to the Terms of Service that the Subscriber does not accept | Pro rata refund of prepaid fees |
| Objection to a new sub-processor that is not resolved, under clause 7.4 of the DPA | Pro rata refund for the affected Services |
| Where a refund is required by applicable law | As required by law |
Refunds are not available where:
Send a request to support@preos.tech within 30 days of the event giving rise to it, stating the invoice number, the amount and the ground relied on. AVREOS will respond within 15 business days.
Approved refunds are made to the original payment method within 15 business days of approval. Bank processing times may add to that.
AVREOS may, at its discretion, offer a credit or other commercial accommodation in circumstances not covered by section 3. Any such accommodation is made without admission and does not establish a precedent or an ongoing entitlement.
Refunds are net of any taxes already remitted to the authorities where those taxes cannot be recovered. Where GST has been charged, a credit note will be issued in accordance with applicable law.
AVREOS Technologies Private Limited
CIN: U74102TS2025PTC205165
Office Space No. 1204, Plot No. 52, Sy. No. 1050P,
Manjeera Trinity Corporate, JNTU–HITECH Road, Near Lulu Mall,
KPHB Phase 3, Kukatpally, Hyderabad, Telangana – 500072, India
| Purpose | Contact |
|---|---|
| Grievance Officer (data protection) | grievance@avreos.in |
| Privacy and data protection | privacy@avreos.in |
| Legal notices, copyright, trademark, security reports | legal@avreos.in |
| Customer support (PREOS) | support@preos.tech |
AVREOS Technologies Private Limited. CIN U74102TS2025PTC205165.
Office Space No. 1204, Plot No. 52, Sy. No. 1050P, Manjeera Trinity Corporate, JNTU–HITECH Road, Near Lulu Mall, KPHB Phase 3, Kukatpally, Hyderabad, Telangana – 500072, India
Questions about this document? Contact support@preos.tech.
PREOS is a business platform for real estate sales and operations. It must be used lawfully, for the Subscriber’s own business purposes, and in accordance with the Documentation. PREOS may be made available globally. India is AVREOS's primary legal framework, and mandatory privacy, communications, cybersecurity and other local laws applicable to a Subscriber or use of PREOS will apply to the extent required.
You must not upload, store, transmit or generate content that:
You must not:
PREOS may be used to contact buyers and prospects in the ordinary course of the Subscriber’s business. You must not use it to send unsolicited bulk communications, and you must comply with applicable law on telemarketing, electronic communications and the National Do Not Call registry, and with the terms of any communications provider integrated with PREOS.
You are responsible for having a lawful basis to contact the individuals whose details you upload.
Where the Subscriber uses call recording functionality, the Subscriber is responsible for obtaining any consent or other lawful basis required by applicable law, providing any required notice, and respecting applicable recording and privacy requirements. AVREOS provides the functionality; the Subscriber decides how and when to use it.
Use of AI features is additionally governed by the PREOS AI Usage Policy. AI output is advisory and must be reviewed by an authorised human before it is relied upon for a decision producing a legal, similarly significant, or otherwise materially consequential effect on an individual, where applicable law requires such review.
Subscriptions are subject to fair-use limits appropriate to the applicable plan, including limits on storage, API calls and AI usage. Where usage materially exceeds normal levels or threatens the stability, security or availability of PREOS, AVREOS will contact the Subscriber to discuss the issue before applying a non-emergency limit, except where immediate action is reasonably necessary to protect PREOS or other Subscribers.
Suspected breaches of this Policy should be reported to legal@avreos.in. Security incidents or vulnerabilities may also be reported through the security contact published by AVREOS.
9.1 AVREOS may investigate a suspected breach, and may remove or disable access to content that breaches this Policy.
9.2 AVREOS may suspend or restrict access in accordance with the Terms of Service. Except where an imminent risk to security, law, PREOS or another user makes prior notice impracticable, AVREOS will give notice and a reasonable opportunity to remedy the breach before suspension.
9.3 A material breach that is not remedied may lead to termination under clause 13.2 of the Terms of Service.
9.4 AVREOS will report to the appropriate authority where required by law.
AVREOS Technologies Private Limited
CIN: U74102TS2025PTC205165
Manjeera Trinity Corporate, JNTU–HITECH Road, Near Lulu Mall,
KPHB Phase 3, Kukatpally, Hyderabad, Telangana – 500072, India
| Purpose | Contact |
|---|---|
| Grievance Officer (data protection) | grievance@avreos.in |
| Privacy and data protection | privacy@avreos.in |
| Legal notices, copyright, trademark, security reports | legal@avreos.in |
| Customer support (PREOS) | support@preos.tech |
Questions about this document? Contact support@preos.tech.
| Feature | What it produces |
|---|---|
| Lead scoring | A score and the reasons behind it |
| Call analysis | Transcription, summary, intent and objections identified |
| Inventory intelligence | Observations on ageing, demand and pricing |
| Price recommendations | A suggested price with the basis for it |
| Demand intelligence | Patterns in buyer requirements |
| Drafting assistance | Draft messages and summaries |
| Copilot | Answers to questions asked over the Subscriber’s own data |
2.1 Advisory fields only. The PREOS AI assistant ("Reo") writes only to advisory fields: suggestions, scores, reasons and drafts. Reo does not directly write to operational state.
2.2 What AI cannot do. No AI feature within PREOS will, of its own operation and without an affirmative action by an authorised human user, make or execute any of the following operational decisions:
2.3 Audit trail. Where a user acts on an AI recommendation, the action is recorded against that user. The audit trail records the person who acted, not the feature that suggested it.
2.4 Reasoning. AI recommendations are presented with the basis on which they were generated, so that the reviewing user can evaluate and reject them.
2.5 Why this matters. Pricing and inventory decisions carry commercial and regulatory consequences. Automating them would move accountability from a named person to a model. AVREOS has chosen not to do that.
3.1 Customer Data and outputs. Customer Data remains the Subscriber’s as provided in the PREOS Terms of Service and DPA. As between AVREOS and the Subscriber, AI outputs generated from the Subscriber’s Customer Data are made available to the Subscriber for its use, subject to applicable law, third-party rights and the Terms of Service. AVREOS does not claim ownership of the Subscriber’s Customer Data.
3.2 No training. AVREOS does not use Customer Data to train, fine-tune, re-train or otherwise improve any general-purpose artificial intelligence or machine-learning model, whether developed by AVREOS or operated by a third party.
3.3 Provider commitments. AVREOS uses paid, billing-enabled tiers of its AI providers under service terms appropriate to the relevant feature. Where an enterprise or zero-retention configuration is available and appropriate, AVREOS may use it. A provider may retain limited submitted content for security, abuse monitoring or policy-enforcement purposes where its applicable terms permit; such retention does not authorise model training. Applicable AI providers and processing locations are maintained in the PREOS sub-processor information.
3.4 Permitted processing. Content submitted to AI features is processed only to generate the requested output and for the operational purposes necessary to deliver it — routing, abuse prevention, security monitoring, error diagnosis and billing.
3.5 Aggregated statistics. AVREOS may compile aggregated, de-identified statistics about feature usage, provided they do not identify and cannot reasonably be used to identify any Subscriber, user, individual or item of Customer Data.
3.6 No sale. AVREOS does not sell, rent or licence Customer Data to any third party.
The AI providers AVREOS uses, the function each performs and applicable processing locations are maintained in the current PREOS sub-processor information. AI processing may occur in India or other jurisdictions where the relevant provider operates. AVREOS applies the safeguards required by applicable law for such processing.
AVREOS will give at least 30 days’ notice before adding or replacing an AI sub-processor that processes Customer Data, subject to the procedure and exceptions in the PREOS Data Processing Addendum. A Subscriber may object within that period on reasonable, documented data-protection grounds. If the objection cannot reasonably be resolved, the remedies set out in the DPA apply.
5.1 AI output may be incomplete, outdated or incorrect. It is a starting point for a decision, not the decision.
5.2 The Subscriber is responsible for reviewing AI output before relying on it and for all decisions taken by its Authorized Users, including decisions informed by AI. Where applicable law requires human review or prohibits solely automated decision-making, the Subscriber must ensure those requirements are met.
5.3 AI output is not legal, financial, tax, valuation, engineering or other professional advice.
5.4 AVREOS does not warrant the accuracy of AI output. Clause 14.3 of the Terms of Service applies.
The Subscriber must not use AI features to:
AI features are subject to fair use limits appropriate to the Subscription plan. Where usage materially exceeds normal levels, AVREOS will contact the Subscriber to discuss it before applying any limit, except where immediate action is necessary to protect the Platform.
AVREOS may update, replace or retire the models and providers used in PREOS to improve quality, reliability, cost or safety, subject to applicable law and contractual commitments. Where a change materially alters the behaviour of an AI feature on which the Subscriber reasonably relies, AVREOS will provide at least 30 days’ notice where reasonably practicable, unless a shorter period is necessary for security, legal, provider or safety reasons.
AVREOS Technologies Private Limited
CIN: U74102TS2025PTC205165
Manjeera Trinity Corporate, JNTU–HITECH Road, Near Lulu Mall,
KPHB Phase 3, Kukatpally, Hyderabad, Telangana – 500072, India
| Purpose | Contact |
|---|---|
| Grievance Officer (data protection) | grievance@avreos.in |
| Privacy and data protection | privacy@avreos.in |
| Legal notices, copyright, trademark, security reports | legal@avreos.in |
| Customer support (PREOS) | support@preos.tech |
AVREOS Technologies Private Limited. CIN U74102TS2025PTC205165.
Questions about this document? Contact support@preos.tech.
This Policy states how long AVREOS keeps data processed through PREOS, what happens to that data when a Subscription ends, and how deletion is carried out. It sets out specific periods rather than general principles, so that a Subscriber can plan against it.
This Policy applies to Customer Data, Account Data, operational records and backups. It forms part of the PREOS Legal Center and is incorporated into the PREOS Terms of Service and the PREOS Data Processing Addendum.
This Policy applies to PREOS Subscribers and users in India and outside India. Where mandatory law in an applicable jurisdiction requires a different retention period, deletion procedure, legal hold, or other mandatory requirement, AVREOS will comply with that requirement to the extent applicable.
The following periods apply. Where a period is expressed as a maximum, AVREOS may delete earlier.
| Data category | Retention period | Trigger |
|---|---|---|
| Customer Data (leads, units, bookings, documents, media) | 90 days | From termination or expiry of the Subscription |
| Call recordings and transcripts | 90 days, or the period configured by the Subscriber if shorter | From termination, or from the configured period during an active Subscription |
| Account Data (administrator and user records) | 90 days | From termination |
| AI prompts and outputs | Not retained beyond the request, save where stored as Customer Data | — |
| Application and access logs | 180 days | Rolling, as required by the CERT-In Directions |
| Audit trail (status, price and ownership changes) | Retained with Customer Data; deleted at the same time | From termination |
| Support tickets and correspondence | 24 months | From closure of the ticket |
| Invoices, billing records and tax records | 8 financial years | As required by the Companies Act, 2013 |
| Marketing contact records | Until consent is withdrawn, or 24 months of inactivity | From last engagement |
| Aggregated, de-identified statistics | Indefinite | Contains no personal data |
Termination does not delete Customer Data immediately. The account moves through three defined stages over 90 days. This is deliberate: a substantial proportion of cancellations arise from a failed payment or an administrative error, and immediate deletion would destroy a Subscriber’s business records without recourse.
| Stage | Period | Subscriber access | Data status |
|---|---|---|---|
| Grace | Days 0–30 | Read-only sign-in. Full export available. Subscription may be reactivated with no loss of data. | Intact |
| Suspended | Days 31–90 | No sign-in. Reactivation on request, restored within 1 business day. Export provided within 5 business days. | Intact |
| Deletion | From day 91 | No access. | Deleted from production within 30 days of the end of day 90 |
AVREOS will notify the Subscriber’s designated administrator by email on entry to the grace period, on entry to suspension, and not less than 14 days before deletion begins.
4.1 During an active Subscription. Authorized Users may export Customer Data at any time using the export functions within PREOS, in commonly used machine-readable formats.
4.2 During the grace period. The same export functions remain available in read-only mode.
4.3 During suspension. AVREOS will provide a complete export on written request to support@preos.tech, within 5 business days of a verified request, at no charge.
4.4 After deletion. Export is not possible. AVREOS cannot recover deleted Customer Data, and the notice given under section 3 is the Subscriber’s opportunity to act.
5.1 Production systems. Customer Data is deleted from the production database and file storage. Deletion is irreversible.
5.2 Backups. Backups are snapshots of the entire database taken at a point in time. It is not technically possible to remove an individual Subscriber’s records from an existing snapshot. Deleted data therefore remains within backup snapshots until those snapshots expire on their normal rotation, which is within 35 days of production deletion. During that period the data is not accessible through the Platform, is not processed, and remains subject to the same encryption and access controls as production data.
AVREOS states this openly because it is true of every platform that maintains backups. A policy claiming instantaneous deletion from all systems would be inaccurate.
5.3 Certification. On written request made within 30 days of deletion, AVREOS will provide the Subscriber with written confirmation that Customer Data has been deleted, stating the date of production deletion and the date on which the final backup containing that data expired.
6.1 Subscriber request. A Subscriber may request deletion of its Customer Data at any time, including before the end of the 90-day period. AVREOS will action a verified request within 30 days and will confirm in writing when deletion is complete.
6.2 Data Principal requests. Where an individual asks AVREOS to delete personal data held within a Subscriber’s account, AVREOS will direct the request to that Subscriber, who is the Data Fiduciary for that data, and will inform the individual that it has done so. AVREOS will assist the Subscriber in giving effect to the request.
6.3 Where deletion is refused. AVREOS will not delete data where retention is required by law, necessary for the establishment or defence of legal claims, or subject to a legal hold. Where AVREOS declines a deletion request on any of these grounds, it will state which ground applies.
Where AVREOS becomes aware of actual or reasonably anticipated litigation, a regulatory investigation, or a lawful order requiring preservation, the relevant data is placed under legal hold and is exempt from the schedule in section 2 until the hold is lifted.
AVREOS will notify the affected Subscriber that a hold has been applied, unless prohibited from doing so by law or by the terms of the order.
Content submitted to AI features is processed to generate the requested output and is not retained by AVREOS beyond that request, except where the output is stored within the Platform as Customer Data at the user’s direction. AVREOS does not use Customer Data to train, fine-tune or improve any AI model. AI providers may retain submitted content for a limited period for abuse monitoring and policy enforcement, which does not involve model training.
The Subscriber is the Data Fiduciary for Customer Data and is responsible for:
AVREOS may update this Policy. Where a change shortens a retention period in a way that adversely affects a Subscriber, AVREOS will give at least 30 days’ notice before the change takes effect.
AVREOS Technologies Private Limited
CIN: U74102TS2025PTC205165
| Purpose | Contact |
|---|---|
| Grievance Officer (data protection) | grievance@avreos.in |
| Privacy and data protection | privacy@avreos.in |
| Legal notices, copyright, trademark, security reports | legal@avreos.in |
| Customer support (PREOS) | support@preos.tech |
Questions about this document? Contact support@preos.tech.
| Term | Meaning |
|---|---|
| Customer Data | Personal data and other information uploaded to, imported into, or generated within PREOS by or on behalf of the Subscriber. |
| Data Fiduciary | As defined in the DPDP Act. In respect of Customer Data, the Subscriber. |
| Data Processor | As defined in the DPDP Act. In respect of Customer Data, AVREOS. |
| Data Principal | The individual to whom personal data relates. |
| Personal Data Breach | Any unauthorised processing of personal data, or accidental disclosure, acquisition, sharing, use, alteration, destruction or loss of access to personal data, that compromises its confidentiality, integrity or availability. |
| Sub-processor | A third party engaged by AVREOS to process Customer Data. |
2.1 In respect of Customer Data, the Subscriber is the Data Fiduciary and AVREOS is a Data Processor. The Subscriber determines the purpose and means of processing.
2.2 The Subscriber is responsible for issuing notices to Data Principals, obtaining and managing consent where consent is the basis of processing, responding to requests from Data Principals, notifying the Data Protection Board of India and affected Data Principals of a Personal Data Breach affecting Customer Data, and maintaining its own grievance redressal mechanism.
2.3 The Subscriber warrants that it has a lawful basis for the processing it instructs, and that any notice or consent required under the DPDP Act has been given or obtained.
2.4 AVREOS is the Data Fiduciary in respect of Account Data — the personal data of Subscriber administrators and Authorized Users collected for account creation, authentication, billing and support. That processing is governed by the PREOS Privacy Policy and not by this DPA.
| Element | Detail |
|---|---|
| Subject matter | Provision of the PREOS platform under the Terms of Service. |
| Duration | For the term of the Subscription, and thereafter for the period set out in the PREOS Data Retention & Deletion Policy. |
| Nature and purpose | Hosting, storage, organisation, retrieval, analysis, transmission and deletion of Customer Data, in order to provide customer relationship management, inventory management, sales operations, communications, reporting, automation and AI features. |
| Categories of Data Principal | The Subscriber’s prospective and actual customers and homebuyers; the Subscriber’s employees and Authorized Users; channel partners and their representatives. |
| Categories of personal data | Name, contact details, requirement and budget information, correspondence and call recordings, booking and payment schedule information, identifiers, and any other data the Subscriber chooses to upload. |
| Special categories | PREOS is not designed for, and the Subscriber must not upload, health data, biometric data, or financial account credentials. |
4.1 AVREOS shall process Customer Data only on the documented instructions of the Subscriber. The Terms of Service, this DPA, and the Subscriber’s use of the configuration options within PREOS constitute the Subscriber’s documented instructions.
4.2 AVREOS shall not process Customer Data for its own independent purposes, and shall not sell, rent or license Customer Data to any third party. AVREOS may process Customer Data only as necessary to provide, operate, secure, support and administer PREOS, comply with applicable law, prevent fraud and security incidents, provide requested features, including AI-assisted features, and perform the documented instructions of the Subscriber.
4.3 AVREOS shall not use Customer Data to train or fine-tune artificial intelligence or machine-learning models. AI-assisted features may process Customer Data only to provide the requested feature and in accordance with this DPA, the Terms of Service and applicable law.
4.4 Where AVREOS is required by law to process Customer Data otherwise than on the Subscriber’s instructions, AVREOS shall inform the Subscriber before processing unless prohibited from doing so by that law.
4.5 If AVREOS considers that an instruction infringes applicable law, it shall inform the Subscriber without undue delay and may suspend performance of that instruction until it is withdrawn or amended. 4.6 Where permitted or required by applicable law, AVREOS may disclose Customer Data in an emergency to address an imminent risk of serious harm or other legally recognised emergency. AVREOS shall provide reasonable assistance to the Subscriber in relation to a legal request concerning Customer Data where such assistance is reasonably available and required by applicable law or this DPA, but AVREOS is not required to provide legal advice or assume the Subscriber's obligations as Data Fiduciary. 4.6 Where permitted or required by applicable law, AVREOS may disclose Customer Data in an emergency to address an imminent risk of serious harm or other legally recognised emergency. AVREOS shall provide reasonable assistance to the Subscriber in relation to a legal request concerning Customer Data where such assistance is reasonably available and required by applicable law or this DPA, but AVREOS is not required to provide legal advice or assume the Subscriber's obligations as Data Fiduciary.
AVREOS shall ensure that every person authorised to process Customer Data is bound by a written obligation of confidentiality that survives the end of their engagement, and has access only to the Customer Data necessary for their role.
6.1 AVREOS shall implement and maintain the technical and organisational measures set out in the PREOS Security Policy, which is incorporated into this DPA by reference. Those measures include encryption in transit and at rest, role-based access control, logging and audit trails, backup and recovery, and an incident response process.
6.2 AVREOS shall not materially reduce the overall level of security provided under this DPA during the term of a Subscription.
6.3 The Subscriber is responsible for the security of its own systems and credentials, for configuring roles and permissions within its Organization Account, and for revoking access promptly when an Authorized User leaves.
7.1 Authorisation. The Subscriber gives AVREOS general authorisation to engage Sub-processors, subject to this section.
7.2 Current list. The current Sub-processors, with the function performed and the location of processing for each, are
7.3 Notice of change. AVREOS shall give at least 30 days’ notice before appointing or replacing a Sub-processor that processes Customer Data. Notice shall be given by email to the Subscriber’s designated administrator and by publication on the Sub-processor page.
7.4 Objection. Within the notice period, the Subscriber may object to a new Sub-processor on reasonable, documented data protection grounds. The parties shall discuss the objection in good faith. If the objection is not resolved within 30 days, the Subscriber may terminate the affected Services on written notice and AVREOS shall refund any prepaid fees for the unexpired term.
7.5 Flow-down. AVREOS shall impose on each Sub-processor data protection obligations no less protective than those in this DPA.
7.6 Liability. AVREOS remains liable to the Subscriber for the acts and omissions of its Sub-processors as if they were its own.
8.1 PREOS may process Customer Data in India and, where required to provide the Services, in other jurisdictions through AVREOS or its authorised Sub-processors. AVREOS will maintain appropriate safeguards for such processing.
8.2 Where a Sub-processor processes Customer Data outside India, the applicable processing location is disclosed in the current Sub-processor list, subject to lawful and reasonable updates.
8.3 AVREOS shall not make a transfer that is prohibited or restricted under applicable law, including any restriction imposed by the Central Government under applicable Indian data-protection law.
8.4 Where Customer Data is transferred across national borders, AVREOS shall apply the safeguards and contractual transfer mechanisms required by applicable law and appropriate to the transfer.
9.1 Data Principal requests. Where AVREOS receives a request from a Data Principal relating to Customer Data, it shall not respond to the substance of the request but shall forward it to the Subscriber within 5 business days and inform the Data Principal that it has done so.
9.2 Technical assistance. AVREOS shall provide, within the Platform, the functionality necessary for the Subscriber to access, correct, export and delete Customer Data in order to give effect to Data Principal rights. Where a Subscriber cannot give effect to a request using that functionality, AVREOS shall assist on written request within 10 business days.
9.3 Regulatory enquiries. AVREOS shall provide the information reasonably necessary to enable the Subscriber to respond to an enquiry from the Data Protection Board of India or another competent authority concerning processing performed by AVREOS.
9.4 Limits. AVREOS is not obliged to provide legal advice, to conduct a compliance assessment on the Subscriber’s behalf, or to assume the Subscriber’s obligations as Data Fiduciary.
10.1 Notification to the Subscriber. AVREOS shall notify the affected Subscriber of a Personal Data Breach affecting Customer Data without undue delay and in any event within 72 hours of becoming aware of it.
10.2 Contents of notification. The notification shall describe, so far as known at the time: the nature of the breach; the categories and approximate volume of Customer Data and Data Principals affected; the likely consequences; the measures taken or proposed to address it; and a point of contact at AVREOS. Where the full information is not available within 72 hours, AVREOS shall provide it in phases as it becomes available.
10.3 Regulatory notification. The Subscriber, as Data Fiduciary/Controller where applicable, is responsible for regulatory and Data Principal notifications concerning Customer Data to the extent required by applicable law. AVREOS shall provide information reasonably necessary for the Subscriber to meet those obligations.
10.4 Mandatory incident reporting. AVREOS will report cyber security incidents to competent authorities where and to the extent required by applicable law, including applicable CERT-In requirements in India.
10.5 Remediation. AVREOS shall take reasonable steps to contain and remediate the breach and to prevent recurrence, and shall keep the Subscriber informed of material developments.
10.6 No admission. Notification under this section is not an admission of fault or liability by either party.
11.1 Documentation. On written request, and not more than once in any 12-month period, AVREOS shall provide the Subscriber with the then-current PREOS Security Policy, the Sub-processor list, and its responses to a reasonable security questionnaire, together with any independent certification or audit report it holds.
11.2 Audit right. Where the documentation provided under clause 11.1 is not sufficient for the Subscriber to demonstrate compliance with its own obligations as Data Fiduciary, the Subscriber may audit AVREOS’ processing of Customer Data, subject to clauses 11.3 to 11.6.
11.3 Conditions. An audit shall be: on at least 30 days’ written notice; not more than once in any 12-month period, except following a Personal Data Breach affecting the Subscriber or where required by a competent authority; during business hours; conducted so as not to disrupt AVREOS’ operations; and limited to systems and records relating to the processing of that Subscriber’s Customer Data.
11.4 Auditor. The audit may be conducted by the Subscriber or by an independent auditor appointed by the Subscriber, provided the auditor is not a competitor of AVREOS and enters into a confidentiality undertaking with AVREOS before the audit begins.
11.5 Exclusions. AVREOS is not required to disclose information relating to other Subscribers, to provide access to shared infrastructure in a manner that would compromise the security of other Subscribers, or to disclose commercially sensitive proprietary information not relevant to the processing of Customer Data.
11.6 Costs. Each party bears its own costs of an audit, save that where an audit reveals a material breach of this DPA by AVREOS, AVREOS shall reimburse the Subscriber’s reasonable costs of that audit.
11.7 Findings. AVREOS shall remedy any material non-compliance identified by an audit within a reasonable period agreed between the parties.
12.1 During the Subscription. The Subscriber may export Customer Data at any time using the export functions within PREOS.
12.2 On termination. Customer Data is retained and deleted in accordance with the PREOS Data Retention & Deletion Policy, which provides a 90-day period comprising a 30-day grace period during which the Subscriber retains read-only access and full export, followed by a 60-day suspension during which export is provided on request.
12.3 Deletion. AVREOS shall delete Customer Data from production systems within 30 days after the end of the 90-day period, or earlier on the Subscriber’s written request.
12.4 Backups. Customer Data deleted from production remains within backup snapshots until those snapshots expire on their normal rotation, being within 35 days of production deletion. During that period the data is not accessible through the Platform, is not processed, and remains subject to the security measures in this DPA.
12.5 Certification of deletion. On written request made within 30 days after deletion, AVREOS shall provide the Subscriber with written certification of deletion, stating the date of production deletion and the date on which the final backup containing that data expired.
12.6 Retention required by law. AVREOS may retain Customer Data to the extent required by applicable law, or where necessary for the establishment, exercise or defence of legal claims, and shall inform the Subscriber which of these applies. Data so retained shall be processed only for that purpose and shall remain subject to this DPA.
The limitations and exclusions of liability in the PREOS Terms of Service apply to this DPA. Nothing in this DPA excludes or limits either party’s liability where such exclusion or limitation is not permitted by applicable law, including liability for a penalty imposed under the DPDP Act arising from that party’s own act or omission.
This DPA takes effect on the effective date of the Subscription and continues for so long as AVREOS processes Customer Data. Clauses 5, 10, 12 and 13 survive termination.
Subject to mandatory local law that cannot lawfully be excluded, this DPA is governed by the laws of the Republic of India. Disputes are subject to the dispute resolution provisions of the PREOS Terms of Service.
AVREOS may update this DPA to reflect changes in law, regulation or the Services. Where a change materially reduces the protections afforded to the Subscriber, AVREOS shall give at least 30 days’ notice before the change takes effect, and the Subscriber may terminate the affected Services within that period if it does not accept the change.
AVREOS Technologies Private Limited
CIN: U74102TS2025PTC205165
Manjeera Trinity Corporate, JNTU–HITECH Road, Near Lulu Mall,
KPHB Phase 3, Kukatpally, Hyderabad, Telangana – 500072, India
| Purpose | Contact |
|---|---|
| Grievance Officer (data protection) | grievance@avreos.in |
| Privacy and data protection | privacy@avreos.in |
| Legal notices, copyright, trademark, security reports | legal@avreos.in |
| Customer support (PREOS) | support@preos.tech |
Questions about this document? Contact support@preos.tech.
AVREOS commits to a Monthly Uptime Percentage of at least 99.5% for the PREOS production environment.
AVREOS operates to an internal target of 99.9%. The 99.5% figure is the level at which service credits become payable, and is set deliberately below the internal target so that the commitment is one AVREOS can meet consistently rather than one that looks impressive on paper.
2.1 Definition. Monthly Uptime Percentage means: total minutes in the calendar month, less Unavailable Minutes, divided by total minutes in the month, expressed as a percentage.
2.2 Unavailable Minutes. A minute is Unavailable if all attempts by the Subscriber to authenticate to, or retrieve data from, the production environment fail during that minute, and the failure is attributable to AVREOS or its infrastructure providers.
2.3 Exclusions. The following are not Unavailable Minutes:
3.1 Scheduled maintenance. AVREOS will give at least 48 hours’ notice of scheduled maintenance, by email to account administrators and by notice in the Platform. Scheduled maintenance will ordinarily be performed between 23:00 and 05:00 IST.
3.2 Limit. Scheduled maintenance will not exceed 8 hours in any calendar month.
3.3 Emergency maintenance. Where maintenance is necessary to address a security vulnerability or preserve data integrity, AVREOS may act without notice and will inform Subscribers as soon as practicable.
4.1 Entitlement. Where Monthly Uptime Percentage falls below 99.5%, the Subscriber is entitled on request to a service credit calculated as a percentage of the Subscription Fees for the affected month:
| Monthly Uptime Percentage | Service credit |
|---|---|
| Below 99.5% but at or above 99.0% | 10% |
| Below 99.0% but at or above 95.0% | 25% |
| Below 95.0% | 50% |
4.2 Claiming. The Subscriber must request the credit in writing to support@preos.tech within 30 days after the end of the affected month, identifying the dates and approximate times of unavailability. AVREOS will respond within 30 days.
4.3 Form. Credits are applied to the next invoice, or refunded within 30 days where no further invoice will be issued. Credits in any month shall not exceed 50% of that month’s Subscription Fees.
4.4 Sole remedy. Service credits are the Subscriber’s sole and exclusive remedy for failure to meet the availability commitment. This does not limit the Subscriber’s right to terminate for material breach under the Terms of Service.
If Monthly Uptime Percentage falls below 99.0% in any three consecutive months, or below 95.0% in any single month, the Subscriber may terminate the Subscription on 30 days’ written notice given within 30 days of the end of the final affected month, and AVREOS shall refund prepaid fees for the unexpired term.
Database performance and availability are monitored through the production database monitoring service.
AVREOS will notify account administrators of any Priority 1 incident affecting the production environment, and will provide a written summary of cause and remediation within 5 business days of resolution on request.
Response times to reported incidents are set out in the PREOS Support Policy. An emergency telephone line is available to Subscribers 24 hours a day for total outages and confirmed security incidents.
AVREOS is not in breach of this SLA where unavailability results from an event beyond its reasonable control, including natural disaster, war, civil unrest, government action, failure of public telecommunications, or a widespread failure of infrastructure operated by a third party. AVREOS will use reasonable efforts to restore service and will keep Subscribers informed.
Subscribers requiring a higher availability commitment, a shorter recovery objective, dedicated infrastructure or a documented disaster recovery test schedule may agree enterprise-specific terms with AVREOS in writing.
AVREOS Technologies Private Limited
CIN: U74102TS2025PTC205165
Office Space No. 1204, Plot No. 52, Sy. No. 1050P,
Manjeera Trinity Corporate, JNTU–HITECH Road, Near Lulu Mall,
KPHB Phase 3, Kukatpally, Hyderabad, Telangana – 500072, India
| Purpose | Contact |
|---|---|
| Grievance Officer (data protection) | grievance@avreos.in |
| Privacy and data protection | privacy@avreos.in |
| Legal notices, copyright, trademark, security reports | legal@avreos.in |
| Customer support (PREOS) | support@preos.tech |
AVREOS Technologies Private Limited. CIN U74102TS2025PTC205165.
Office Space No. 1204, Plot No. 52, Sy. No. 1050P, Manjeera Trinity Corporate, JNTU–HITECH Road, Near Lulu Mall, KPHB Phase 3, Kukatpally, Hyderabad, Telangana – 500072, India
Questions about this document? Contact support@preos.tech.
Support covers the operation of PREOS as documented: access and authentication, defects, configuration questions, and guidance on standard functionality.
Support does not cover the Subscriber’s own hardware, network or third-party software; data entry or data cleansing; custom development; or issues arising from use contrary to the Documentation.
Database performance and availability are monitored through the production database monitoring service. Application and server availability are monitored through the hosting provider.
Monitoring is distinct from human response. Section 4 sets out when a person will respond to a reported issue.
| Channel | Use | Availability |
|---|---|---|
| support@preos.tech | All support requests | Monitored during support hours |
| Emergency telephone line | Total outage or confirmed security incident only | 24 hours a day, every day |
The emergency telephone number is provided to each Subscriber at onboarding. It is for genuine emergencies — the Platform being wholly unavailable, or a confirmed security incident. Routine issues raised by telephone will be redirected to email.
Support hours are 09:30 to 18:30 IST, Monday to Saturday, excluding public holidays in Telangana.
Please include the Organization Account name, the affected user, a description of the issue, steps to reproduce it, and any error message.
| Priority | Definition | Support hours | Outside hours |
|---|---|---|---|
| P1 — Critical | The Platform is wholly unavailable to all users, or a confirmed security incident is in progress. | 1 hour | 4 hours |
| P2 — High | A core function is unavailable or materially degraded for multiple users, with no workaround. | 4 hours | Next business day |
| P3 — Medium | A function does not work as documented, but a workaround exists. | 1 business day | Next business day |
| P4 — Low | A question, a cosmetic issue, or a feature request. | 2 business days | Next business day |
4.1 Response, not resolution. The times above are for first response by a person. They are not resolution times. Resolution depends on the nature of the issue; AVREOS will provide an estimate once the issue is diagnosed.
4.2 Updates during a P1. While a P1 incident is open, AVREOS will provide an update at least every 2 hours during support hours, and at least every 4 hours outside them, until the Platform is restored.
4.3 Resolution. AVREOS works to restore service as quickly as possible. AVREOS does not commit to a fixed resolution time, because the time required depends on the cause, which is not known in advance.
4.4 Priority assignment. AVREOS assigns priority using the definitions above. A Subscriber that disagrees may ask for the priority to be reviewed, and AVREOS will respond within one business day.
If a Subscriber is not satisfied with how a request is being handled, it may escalate by replying to the ticket with "Escalation" in the subject line. Escalated tickets are reviewed by the technical co-founder within one business day.
A P1 incident is escalated automatically and does not require the Subscriber to request it.
Onboarding is included with every Subscription and covers account setup, configuration of the Subscriber’s first project, import of existing inventory and lead data where the Subscriber provides it in a usable format, role and permission setup, and a walkthrough for the Subscriber’s team.
Onboarding sessions are scheduled during support hours by agreement. Additional training beyond initial onboarding may be arranged separately.
The response times in section 4 do not apply to features identified as beta or other experimental/preview features, to requests raised by anyone other than a nominated contact, or while an account is suspended for non-payment.
Subscribers requiring shorter response times, extended support hours, or dedicated support arrangements may agree enterprise-specific terms with AVREOS in writing.
AVREOS Technologies Private Limited
CIN: U74102TS2025PTC205165
Office Space No. 1204, Plot No. 52, Sy. No. 1050P,
Manjeera Trinity Corporate, JNTU–HITECH Road, Near Lulu Mall,
KPHB Phase 3, Kukatpally, Hyderabad, Telangana – 500072, India
| Purpose | Contact |
|---|---|
| Grievance Officer (data protection) | grievance@avreos.in |
| Privacy and data protection | privacy@avreos.in |
| Legal notices, copyright, trademark, security reports | legal@avreos.in |
| Customer support (PREOS) | support@preos.tech |
AVREOS Technologies Private Limited. CIN U74102TS2025PTC205165.
Office Space No. 1204, Plot No. 52, Sy. No. 1050P, Manjeera Trinity Corporate, JNTU–HITECH Road, Near Lulu Mall, KPHB Phase 3, Kukatpally, Hyderabad, Telangana – 500072, India
Questions about this document? Contact support@preos.tech.
Send a takedown notice to legal@avreos.in. If applicable law requires or permits postal delivery, a notice may also be sent to AVREOS's registered office address set out in the Contact section.
A notice must include:
An incomplete notice may delay action. If we cannot identify the material from your notice, we will tell you what is missing.
2.1 Acknowledgement. AVREOS will aim to acknowledge a complete notice within 24 hours of receipt.
2.2 Action. Where the notice is complete and the complaint appears well-founded, AVREOS will remove or disable access to the material within 36 hours where reasonably practicable and where that timeframe is consistent with applicable law and the circumstances of the complaint. Where applicable law requires a different timeframe or process, that requirement prevails.
2.3 Notification to the Subscriber. We will inform the Subscriber whose account held the material that it has been removed, and provide a copy of the notice, unless we are prohibited from doing so.
2.4 Records. We retain a record of every notice and the action taken for the period required by law.
A Subscriber who believes material was removed in error may send a counter-notice to legal@avreos.in containing:
On receiving a valid counter-notice we will forward it to the complainant. If the complainant does not notify us within 10 business days that it has commenced legal proceedings, we may restore the material.
AVREOS may suspend or terminate the account of a Subscriber that is the subject of repeated well-founded infringement notices. What counts as repeated depends on the circumstances, including the seriousness of the infringement and the Subscriber’s response.
A person who knowingly makes a materially false statement in a notice or counter-notice may be liable for the resulting loss. AVREOS may decline to act on notices from a person who has repeatedly submitted unfounded complaints.
5A. Subscriber responsibility for uploaded content
The Subscriber represents and warrants that it has the necessary rights, licences, permissions or other lawful authority to upload, store, reproduce, display, distribute or otherwise use content through PREOS. The Subscriber is responsible for ensuring that its use of third-party content does not infringe copyright, trademark, privacy, publicity or other applicable rights.
5B. Subscriber content and limited platform rights
Subscriber-uploaded content remains the property of the Subscriber or its applicable licensors. Merely uploading or storing content through PREOS does not transfer ownership of that content to AVREOS. The Subscriber grants AVREOS the limited rights necessary to host, store, reproduce, transmit, display, process, secure, back up and otherwise use the content solely to provide, maintain, secure and improve the PREOS service, and as otherwise permitted by the Terms of Service or applicable law.
The PREOS software, interface, documentation and brand are owned by AVREOS. Use of them is governed by the Terms of Service and the Trademark Guidelines. This Policy concerns content uploaded by Subscribers, not the Platform itself.
Complaints about content that is unlawful for reasons other than copyright, including defamatory, obscene, fraudulent, threatening or otherwise prohibited content, should also be sent to legal@avreos.in. AVREOS will handle such complaints under applicable law and its platform rules.
AVREOS Technologies Private Limited
CIN: U74102TS2025PTC205165
Manjeera Trinity Corporate, JNTU–HITECH Road, Near Lulu Mall,
KPHB Phase 3, Kukatpally, Hyderabad, Telangana – 500072, India
| Purpose | Contact |
|---|---|
| Grievance Officer (data protection) | grievance@avreos.in |
| Privacy and data protection | privacy@avreos.in |
| Legal notices, copyright, trademark, security reports | legal@avreos.in |
| Customer support (PREOS) | support@preos.tech |
Questions about this document? Contact support@preos.tech.
The PREOS application runs on managed cloud infrastructure in Hyderabad, India. The production database is a MongoDB Atlas M10 dedicated cluster on AWS infrastructure in the Hyderabad region (ap-south-2). Files uploaded by Subscribers are stored through separate object-storage infrastructure, while MongoDB stores related metadata and file references.
| Component | Provider | Region |
|---|---|---|
| Application hosting | Hostinger Cloud | Hyderabad, India |
| Production database | MongoDB Atlas M10 dedicated cluster | Hyderabad, India (AWS ap-south-2) |
| File storage | MongoDB Atlas | Hyderabad, India |
| AI inference | Google (Gemini, paid tier) | See sub-processor list |
| Transcription | AssemblyAI | See sub-processor list |
| Payments | Razorpay | India |
| Google Workspace | See sub-processor list |
The current sub-processor list, with the processing location for each, is maintained in the current PREOS Subprocessor List.
| Data state | Control |
|---|---|
| In transit | TLS 1.2 or higher for all connections, including to sub-processors. |
| At rest | AES-256 or equivalent, provided by the managed database and storage services. |
| Passwords | Stored as salted one-way hashes. Not recoverable by AVREOS. |
| Secrets | API keys and service credentials held in environment configuration, not committed to source control. |
Access to Customer Data is governed by role-based access control. Each Authorized User holds a role, and the role determines what they can see and do.
PREOS enforces separation of authority in the sales workflow. Holding, releasing, pricing and discount approval are restricted to the Sales Manager role. A Sales Executive may view inventory and may mark a unit reserved or booked when a buyer commits, but cannot return a unit to the market or change its price.
Organization Administrators assign roles, review permissions and revoke access when a user leaves.
Access to production systems is limited to personnel who require it to operate and support the Platform. At AVREOS’ current size that is a small, named group. Access is granted on the principle of least privilege and removed when no longer required.
AVREOS does not access Customer Data except to provide support at the Subscriber’s request, to investigate a security incident, to maintain the Platform, or where required by law.
AI features process Customer Data only to generate the requested output. AVREOS does not use Customer Data to train any model and uses only the paid tiers of its AI providers, under terms which provide that submitted content is not used to train their models.
The PREOS AI assistant operates within a governance boundary enforced in the product: it writes only to suggestion, score, reason and draft fields, and cannot change inventory status, prices, lead ownership or approvals, or send customer communications. The AI Usage Policy sets this out in full.
| Measure | Position |
|---|---|
| Method | MongoDB Atlas Cloud Backup with automated snapshots. |
| Frequency | Daily automated snapshots. |
| Retention | 30 days. |
| Point-in-time recovery | Available on the dedicated cluster tier. |
| Encryption | Snapshots encrypted at rest by the managed database service. |
| Location | Hyderabad, India — the same region as the production cluster. |
| Recovery Point Objective | 24 hours, or shorter where point-in-time recovery is used. |
| Recovery Time Objective | 24 hours for full restoration of the production environment. |
| Restoration testing | On any change to database configuration, and at least annually. |
AVREOS maintains an incident response process covering detection, triage, containment, eradication, recovery and post-incident review. The escalation path is short and defined: any person noticing a suspected incident escalates immediately to the technical co-founder, who owns the response.
| Recipient | Timeline | Basis |
|---|---|---|
| CERT-In | Within the timelines prescribed by the CERT-In Directions | Section 70B(6), Information Technology Act, 2000 |
| Affected Subscribers | Within 72 hours of becoming aware | PREOS Data Processing Addendum, clause 10 |
| Data Protection Board of India | Within 72 hours, where AVREOS is Data Fiduciary | DPDP Act, 2023 and DPDP Rules, 2025 |
| Affected Data Principals | Within 72 hours, where AVREOS is Data Fiduciary | DPDP Act, 2023 and DPDP Rules, 2025 |
Where AVREOS acts as Data Processor, the Subscriber is the Data Fiduciary and notifies the Board and affected individuals. AVREOS provides the information necessary for it to do so.
Reports of suspected vulnerabilities should be sent to legal@avreos.in with enough detail to reproduce the issue.
AVREOS will acknowledge within 3 business days and provide an assessment within 10 business days. AVREOS will not pursue legal action against a researcher who reports in good faith, does not access or modify data belonging to others, does not degrade the service, and allows a reasonable period to remediate before disclosure.
All AVREOS personnel and contractors are bound by written confidentiality obligations covering Customer Data. Access to production is granted only where the role requires it and is revoked on departure.
AVREOS does not currently operate a formal security awareness training programme. This is planned as the team grows.
The current sub-processors, the function each performs and the location of processing are maintained in the current PREOS Subprocessor List.
AVREOS gives at least 30 days’ notice before appointing or replacing a sub-processor that processes Customer Data. A Subscriber may object on reasonable, documented data protection grounds within that period, and the parties will discuss the objection in good faith.
AVREOS does not hold ISO 27001 certification, a SOC 2 attestation, or any other independent security certification.
AVREOS states this plainly. A prospective customer is better served by an accurate description of the controls in place than by an implication of certifications not obtained. AVREOS will evaluate formal certification as the Platform and customer base mature, and will publish any attestation obtained.
Subscribers may request this Policy, the sub-processor list and responses to a reasonable security questionnaire, once in any 12-month period. Audit rights, including the circumstances in which an on-site audit may be conducted, are set out in clause 11 of the Data Processing Addendum.
Security is shared. The Subscriber is responsible for:
AVREOS may update this Policy to reflect changes in infrastructure, controls or regulation. Where a change materially reduces the protections described, AVREOS will give at least 30 days’ notice.
AVREOS Technologies Private Limited
CIN: U74102TS2025PTC205165
Manjeera Trinity Corporate, JNTU–HITECH Road, Near Lulu Mall,
KPHB Phase 3, Kukatpally, Hyderabad, Telangana – 500072, India
| Purpose | Contact |
|---|---|
| Grievance Officer (data protection) | grievance@avreos.in |
| Privacy and data protection | privacy@avreos.in |
| Legal notices, copyright, trademark, security reports | legal@avreos.in |
| Customer support (PREOS) | support@preos.tech |
AVREOS Technologies Private Limited. CIN U74102TS2025PTC205165.
Questions about this document? Contact support@preos.tech.
Legal documents and policies governing the use of PREOS and the services provided by AVREOS Technologies Private Limited.
Enterprise customers can request the DPA, SLA and related documents during contracting. Talk to our team.
Trust is part of the product. This centre brings together how PREOS approaches data protection, privacy, availability and responsible AI — with links to the detailed policies.
Access controls, audit trails, backups and incident response.
Read Security Policy →How customer and personal data is handled.
Read Privacy Policy →How AVREOS processes customer data on behalf of subscribers.
View DPA →Platform availability and service commitments.
View SLA →How Reos works — and what it cannot do.
Read AI Usage Policy →How business data is retained and deleted.
Read Policy →The providers involved in delivering PREOS services. The finalised subprocessor list will be published here.
Published once finalised| Item | Position |
|---|---|
| Application hosting | Mumbai, India |
| Production database | MongoDB Atlas M10 dedicated cluster, Mumbai (ap-south-1) |
| File storage | Within the MongoDB Atlas cluster, Mumbai |
| Logs | Retained 180 days, held within India, per the CERT-In Directions |
| Sub-processors | Published at preos.tech/subprocessors with the location of each |
PREOS is AI-integrated, not AI-operated. The distinction is enforced in the product.
AI suggests. People decide.
AVREOS commits to 99.5% monthly uptime, with service credits of 10%, 25% or 50% of monthly fees where that is not met, and a right to terminate on chronic failure. The internal target is 99.9%. The commitment is deliberately set at a level AVREOS can meet consistently rather than one that reads well.
The Service Level Agreement sets out the measurement method, exclusions and how to claim.
AVREOS does not hold ISO 27001, SOC 2 or any other independent security certification.
We state this plainly rather than implying otherwise. What we can offer instead is a Security Policy describing the controls actually in operation, audit rights under the Data Processing Addendum, and a sub-processor list naming every third party that touches Customer Data. We will evaluate formal certification as the platform matures, and will publish any attestation obtained.
Subscribers and prospective Subscribers may request the Security Policy, the current sub-processor list, and responses to a security questionnaire, by writing to legal@avreos.in. Audit rights are set out in clause 11 of the Data Processing Addendum.
Send reports to legal@avreos.in. We acknowledge within 3 business days and assess within 10. We will not pursue legal action against a researcher who reports in good faith, does not access data belonging to others, does not degrade the service, and allows a reasonable period to remediate.
AVREOS Technologies Private Limited
CIN: U74102TS2025PTC205165
Office Space No. 1204, Plot No. 52, Sy. No. 1050P,
Manjeera Trinity Corporate, JNTU–HITECH Road, Near Lulu Mall,
KPHB Phase 3, Kukatpally, Hyderabad, Telangana – 500072, India
| Purpose | Contact |
|---|---|
| Grievance Officer (data protection) | grievance@avreos.in |
| Privacy and data protection | privacy@avreos.in |
| Legal notices, copyright, trademark, security reports | legal@avreos.in |
| Customer support (PREOS) | support@preos.tech |
AVREOS Technologies Private Limited. CIN U74102TS2025PTC205165.
Office Space No. 1204, Plot No. 52, Sy. No. 1050P, Manjeera Trinity Corporate, JNTU–HITECH Road, Near Lulu Mall, KPHB Phase 3, Kukatpally, Hyderabad, Telangana – 500072, India
Contact the PREOS team — we’re happy to help enterprise teams with security and data questions.
Help us build the operating system for real estate developers. PREOS is building technology that connects real estate sales and operations into one operating system. We’re looking for curious, driven people who want to solve real business problems and grow with an early-stage technology company.
PREOS is solving real operational problems faced by real estate developers.
Take responsibility and turn ideas into action.
Work directly with customers, decision-makers and the product team.
Your work can directly influence our product and growth.
Build experience across real estate, SaaS, AI and B2B technology.
We believe great products come from staying close to the people who use them.
You’ll have the opportunity to work across teams, interact with customers and contribute beyond a predefined job description.
We value people who are:
Always willing to learn.
Take initiative and follow through.
Can work comfortably in a changing environment.
Understand the problem before proposing the solution.
Work well with people across different functions.
Help take PREOS to real estate developers, understand their business challenges, demonstrate the platform and build long-term customer relationships.
We’re building PREOS for the people who build real estate.
Help take PREOS to the developers who need it. PREOS is building an AI-integrated operating system for real estate developers, connecting leads, sales, inventory, customers, collections and operations in one platform. We’re looking for a Business Development Executive who can understand real estate businesses, build relationships with decision-makers, demonstrate PREOS and help us grow across the market.
This is a customer-facing business development role. You’ll work directly with real estate developers, builders, sales teams and decision-makers to understand how they currently manage their sales and operations, identify gaps and demonstrate how PREOS can help.
You’ll be involved throughout the early sales journey — from identifying potential customers and initiating conversations to conducting meetings, demonstrating the product, following up and developing business opportunities. You’ll also bring what you learn from the market back to the PREOS team.
Research and identify real estate developers, builders and relevant decision-makers who could benefit from PREOS.
Connect with developers, sales heads, business heads and other stakeholders through calls, meetings, networking and field visits.
Learn how each organisation manages leads, inventory, sales teams, site visits, bookings, customers, collections and reporting.
Conduct product walkthroughs and explain how PREOS can address specific business and operational challenges.
Qualify prospects, maintain the sales pipeline, coordinate follow-ups and move qualified opportunities toward adoption.
Visit developer offices, project sites and other relevant locations when required.
Maintain consistent communication with prospects and ensure opportunities don’t get lost due to missed follow-ups.
Capture customer feedback, objections, competitive insights and feature requirements and communicate them to the PREOS team.
We’re looking for someone who can understand business, communicate with people and learn technology quickly. You may come from:
Experience with builders, developers, projects, property sales, channel partners or real estate business development.
Experience with SaaS, CRM, ERP, PropTech or B2B technology products — you can understand and demonstrate software.
Experience identifying prospects, conducting client meetings, presenting solutions, managing pipelines and building relationships.
You may not have direct real estate or SaaS experience, but you have strong communication, sales ability, curiosity and the confidence to learn.
Working with PREOS will give you hands-on exposure to:
You’ll work close to the customers, product and founding team — understanding both the business and technology sides of what we’re building.
Business Development Executive
AVREOS Technologies Pvt. Ltd.
PREOS
Hyderabad, Telangana
Full-time
1–4 years preferred
Client meetings + field visits + office work
Real Estate Technology / SaaS
Competitive and based on experience
You don’t need to meet every requirement. If you understand people, business or technology and believe you can learn the rest, apply below.
PREOS is the operating system for real estate developers — connecting people, processes, data and decisions on one intelligent platform. From lead capture and sales to inventory, bookings, customer management, operations, collections and management intelligence, PREOS brings the entire business together.
Real estate businesses often operate across multiple teams, spreadsheets, communication channels and disconnected systems. PREOS brings these workflows together into one connected platform built specifically for real estate developers.
It helps teams manage the complete customer and business journey — from the first lead to sales, site visits, inventory, booking, post-sales, collections and management reporting.
PREOS is not another tool added to your technology stack. It is designed to become the operating layer that connects it.
As real estate businesses grow, managing leads, sales teams, inventory, customers, channel partners, collections and projects becomes increasingly difficult. Information gets distributed across spreadsheets, messaging applications, portals and individual teams. Follow-ups get missed. Inventory becomes difficult to track. Management lacks a real-time view of what is happening across the business.
PREOS was created to solve this problem.
Designed specifically around the way real estate developers operate — from project and inventory management to sales, customer journeys, channel partners and collections.
Departments don’t operate in isolation. PREOS connects workflows across the organisation so information can move with the business.
Teams work with connected information instead of maintaining separate versions across spreadsheets and disconnected systems.
PREOS uses AI-assisted capabilities to help teams analyse information, identify patterns and make faster, better-informed decisions.
As your projects, teams and operations grow, PREOS is designed to grow with your business.
PREOS is developed by AVREOS Technologies Private Limited, a technology company focused on building intelligent business platforms that simplify complex operations and help organisations work with greater clarity, control and efficiency.
We believe technology should do more than digitise existing processes. It should connect them. It should make information easier to understand. It should reduce operational friction. And it should help people make better decisions. PREOS represents this philosophy for real estate developers — bringing together the systems, workflows and intelligence required to operate a modern real estate business.
PREOS is built by AVREOS Technologies, part of WE Hub — the Government of Telangana’s initiative supporting women entrepreneurs and startups — giving the team mentorship, networks and a structured environment to build.
We envision a future where businesses don’t have to fight through disconnected systems, scattered information and repetitive processes to understand what is happening. Technology should make complexity manageable. It should give teams clarity, give leaders visibility and give organisations the ability to move faster.
Our mission is to build technology that connects people, processes, data and intelligence — helping businesses operate more efficiently and make better decisions.
PREOS is designed for businesses that manage sensitive customer, sales, inventory and operational information. User access can be controlled according to organisational roles and responsibilities, helping businesses provide the right information to the right people.
We take privacy and responsible handling of business information seriously and continue to strengthen the security and protection practices supporting the PREOS platform.
PREOS began with a simple observation: real estate businesses have plenty of software. What they need is better-connected software.
The platform evolved around the real operational challenges faced by developers — connecting lead management, sales, inventory, customer journeys, operations, collections, channel partners and management intelligence. Today, PREOS is being built as a unified operating system designed around the realities of modern real estate businesses.
PREOS is being built to evolve with the industry. As businesses become more data-driven and AI becomes increasingly integrated into everyday operations, PREOS will continue bringing intelligence closer to the teams and decisions that matter.
Our goal is not simply to build more features. Our goal is to build a better way to operate.
Discover how PREOS can connect your real estate operations, sales, inventory, customers and teams on one intelligent platform.
A CRM can organize leads. A real estate operating system connects the workflows that turn those leads into bookings, collections and business outcomes.
Real estate developers rarely have only one operational problem. A project can generate enquiries through portals, digital campaigns, walk-ins, referrals and channel partners. Those enquiries then move through calls, site visits, negotiations, inventory selection, holds, bookings, payment schedules and collections. Management needs visibility across the entire journey while individual teams need tools that fit their daily work.
Yet the technology used to manage this journey is often fragmented. A CRM may contain lead information, an Excel file may contain inventory, WhatsApp may contain conversations, a salesperson's phone may contain follow-up reminders, and management reports may be prepared separately. Each tool can work reasonably well on its own, but the business process becomes difficult to control when the tools do not share the same context.
The result is operational leakage. A lead can be contacted but not followed up. A unit can be discussed with two prospects. A hold can remain active after the underlying opportunity has changed. A payment milestone can become overdue without a clear escalation path. Management may receive a report, but not have a live view of what is happening underneath it.
A CRM is generally designed around customer and lead relationships. That is important, but a developer's operating environment extends beyond relationships. The business also has physical inventory, project structures, sales authorities, booking workflows, payment schedules, channel partners, post-sales activities and management controls.
An operating system brings these connected workflows into a common operating layer. The goal is not simply to store more information. The goal is to preserve context as work moves from one role to another.
For example, a lead should not exist as an isolated record. The organization should be able to understand where the lead came from, who owns it, what communication has happened, whether a site visit occurred, what unit or project is relevant, what stage the opportunity has reached and what action should happen next. Similarly, a unit should not exist only as a row in an inventory spreadsheet. Its availability, hold status, ownership and booking status should be connected to the sales process.
A modern developer needs a shared operating model across roles. Reception may capture an enquiry. A sales executive may qualify it. A manager may review the pipeline. A site team may complete a visit. A sales manager may control a hold. The booking team may complete documentation. Collections may track payment milestones. Senior management may monitor performance.
Each role has a different job, but the underlying business context is shared. An operating system is valuable when it allows these roles to work from the same source of truth without forcing everyone into the same screen or process.
This is particularly important as a developer grows. Informal coordination can work when a project has a small team. As projects, towers, sales executives and channels increase, the number of handoffs increases as well. Software needs to reduce the dependence on memory and individual communication.
Real estate is unusual because the product being sold is finite, structured and location-specific. A sales process therefore cannot be separated completely from inventory.
A developer may need to know which units are available, which are held, which are booked, who has authority to place a hold, how long the hold remains valid and what happens when it expires. If inventory status is maintained separately from sales activity, the organization can end up with conflicting information.
Connecting inventory with the sales workflow creates a stronger control layer. Teams can see availability in context, management can understand movement, and defined authorities can reduce unnecessary ambiguity around holds and releases.
The customer journey does not end at booking. Payment schedules, milestone tracking, reminders and escalation are part of the commercial operation.
When booking information and payment schedules are connected, collections teams can work proactively instead of reconstructing information manually. A milestone can trigger a reminder, a task or a management escalation according to the organization's process.
This also gives management a better view of the relationship between bookings and collections. Instead of looking at sales and cash as two unrelated reports, the organization can see them as connected parts of the project lifecycle.
AI can add another layer of intelligence, but it should not remove business authority from the people responsible for decisions.
PREOS positions Reos as an AI assistant that can listen to calls, score and rank leads, suggest next actions, draft follow-up messages and flag risks such as silent leads or expiring holds. The decision remains with the team.
This distinction matters in real estate. An AI assistant can surface information and recommendations, while sensitive actions such as holding a unit, confirming a booking or changing a price remain under defined human control.
A practical real estate operating system should help a developer achieve several things at once: a shared source of truth, connected workflows, clear ownership, controlled authorities, real-time operational visibility and useful intelligence.
It should also be deployable without forcing the organization to rebuild its entire business around software. Structured onboarding, role-based workflows and a clear implementation process matter as much as the feature list.
PREOS is positioned as an AI-integrated operating system for Indian real estate developers. Its operating model brings leads, inventory, sales teams and collections into a connected platform, while Reos provides AI-assisted recommendations.
The central idea is simple: instead of adding another disconnected tool, build one operational layer around the way a real estate project actually runs.
For developers evaluating software, the key question should therefore not be "Does this system have a CRM?" It should be "Can this system connect the workflows that run my project, preserve context between teams, and give management a reliable source of truth?"
See how PREOS can work for your project. Request a demo and explore a connected operating system for real estate sales and operations. Request a demo →
Publishing note: verify any customer/project names, numerical claims, regulatory statements, awards or performance statistics before publishing.
Request a demo and explore a connected operating system for real estate sales and operations.
WhatsApp and spreadsheets are useful tools. The problem begins when they become the operating system for a growing real estate sales organization.
Sales teams move quickly. They need to call prospects, share brochures, coordinate site visits, discuss availability and update managers. WhatsApp is fast and familiar. Excel is flexible. Phone calls are immediate. When a team is small, this combination can appear sufficient.
The problem is not that WhatsApp or Excel are bad tools. The problem is that neither is designed to provide a complete, controlled operating workflow for a growing real estate organization.
As the number of leads, salespeople, projects and inventory units grows, informal coordination creates hidden dependencies. Information may exist, but the organization may not know where the latest version lives, who owns the next action or whether the information is still accurate.
A lead rarely disappears because someone intentionally ignores it. Leakage often happens between activities. An enquiry arrives, a salesperson calls, the prospect asks for information, a site visit is discussed, another conversation happens, and then the follow-up is delayed.
When the process depends primarily on personal reminders or chat history, management may not know which leads have stalled until the opportunity is already cold.
A structured lead workflow creates ownership, stages, follow-up tasks and visibility. It turns the question from "Did someone remember this lead?" into "What is the current status and what is the next action?"
Spreadsheets are excellent for analysis and structured data. But inventory operations require more than a list of unit numbers.
A project may have towers, floors, unit types, pricing structures and changing availability. Teams may need to distinguish between available, held and booked units. Holds may have owners, expiry times and authority rules.
When several people edit or reference different versions of a spreadsheet, the organization can lose confidence in the data. A live inventory workflow reduces this dependency by giving authorized users a shared operational view.
WhatsApp can preserve a message history, but a conversation is not the same as a workflow. A manager needs to know which leads require action, which site visits are pending, which holds are expiring and which tasks are overdue.
Important operational information can also become buried under unrelated messages. Searching for a conversation is not the same as having a structured record of the business process.
Communication tools should support the workflow rather than become the only place where the workflow exists.
When information is fragmented, management reporting often becomes manual. A manager asks for sales numbers, inventory status or follow-up information, and teams collect data from different sources.
This creates a delay between what is happening and what management can see. It can also create disagreements about whose number is correct.
A connected operating platform can make reporting a by-product of daily operations rather than a separate administrative exercise.
The cost of fragmented tools is not limited to software licenses. There is also the time spent searching for information, reconciling records, asking for updates, correcting mistakes and following up on work that should have been visible.
More importantly, fragmented processes can affect customer experience. A buyer does not care which internal spreadsheet contains the answer. They expect the organization to know the status of their enquiry, site visit, unit and booking process.
The objective should not be to eliminate every familiar tool overnight. The objective is to establish a reliable system of record and a defined workflow, then use communication tools around that foundation.
PREOS is designed around this principle: leads, inventory, sales operations and collections should operate as connected workflows, while teams can use communication and AI assistance within that structure.
The transformation is therefore less about replacing WhatsApp with another app and more about replacing fragmented operating practices with a controlled system.
If managers frequently ask for manual updates, if multiple people maintain lead sheets, if unit availability is confirmed through chat, if follow-up depends on individual reminders, if reports require significant reconciliation, or if teams cannot quickly answer "what happens next?", the organization may need a stronger operating layer.
WhatsApp and Excel will continue to have a place in business. The question is whether they should carry the responsibility of running a complex real estate sales operation.
As projects and teams grow, the value of a connected operating system increases because it creates one place where work, ownership, inventory and management visibility come together.
See how PREOS can work for your project. Request a demo and explore a connected operating system for real estate sales and operations. Request a demo →
Publishing note: verify any customer/project names, numerical claims, regulatory statements, awards or performance statistics before publishing.
Request a demo and explore a connected operating system for real estate sales and operations.
Inventory is the product. When availability is unclear, the sales process becomes vulnerable to conflict, delays and poor customer experience.
In real estate development, the sales team is not selling an abstract product. It is selling specific units with specific attributes: project, tower, floor, unit type, area, price and availability.
That makes inventory management inseparable from sales operations. Every conversation eventually needs an answer to a basic question: what can actually be sold?
If the answer depends on several spreadsheets, calls or messages, the sales process carries unnecessary uncertainty.
A unit can appear available in a list while another salesperson is discussing it with a buyer. A unit can be temporarily held while documentation is pending. A booking can be initiated while another record has not yet been updated.
Operational availability therefore needs defined states and clear authority. A common model is to distinguish at least available, held and booked. Organizations may add additional states based on their business process.
The important principle is consistency: every team should understand what each state means and who can change it.
A hold is not simply a status change. It can affect the sales pipeline, pricing, customer expectations and the availability presented to other buyers.
Without clear authority, multiple team members may attempt to hold or promise the same unit. A controlled workflow gives one defined authority for holds and records the owner and timing of the hold.
PREOS uses the concept of a Sales Manager as the sole hold authority in the described workflow. The intention is to make responsibility explicit rather than allowing inventory status to change informally.
A hold that remains indefinitely can make a unit appear unavailable even when the underlying opportunity is no longer active.
Expiry rules create a defined lifecycle. When a hold expires, the organization can release the unit according to its process, potentially making it available again or moving a relevant opportunity to a waitlist.
The exact duration and conditions should always be configured according to the developer's commercial policy rather than assumed as a universal rule.
Knowing that Unit A-802 is held is useful. Knowing why it is held, which opportunity is associated with it and what the next action is is much more useful.
Connecting inventory with lead and sales records creates context. Managers can understand which units are attracting demand, which prospects are progressing, and where inventory is becoming constrained.
This can also improve internal coordination because the team does not need to reconstruct the relationship between a buyer and a unit from messages.
Senior management may not need to work inside every transaction, but they need reliable visibility into project inventory. They may want to understand how many units are available, held or booked, where demand is concentrated, and how inventory is moving over time.
A live operational view can support these questions more effectively than a report assembled after the fact.
PREOS positions inventory as part of the operating workflow rather than a separate spreadsheet. The described product experience includes live available, held and booked states, a defined Sales Manager hold authority, automatic release after expiry and waitlist handling.
By connecting inventory with leads, sales activity and management reporting, the goal is to make unit status a reliable part of the organization's source of truth.
For developers, inventory accuracy is not merely an administrative concern. It affects sales confidence, customer experience and management control.
A connected inventory workflow creates a stronger foundation for every conversation that follows — from enquiry to site visit, negotiation and booking.
See how PREOS can work for your project. Request a demo and explore a connected operating system for real estate sales and operations. Request a demo →
Publishing note: verify any customer/project names, numerical claims, regulatory statements, awards or performance statistics before publishing.
Request a demo and explore a connected operating system for real estate sales and operations.
A strong sales process does more than capture leads. It creates a visible journey from enquiry to site visit, negotiation and booking.
Generating enquiries is important, but an enquiry has no commercial value until the organization can move it through a disciplined sales journey.
Real estate sales involve multiple stages and handoffs. The prospect may need qualification, project information, a site visit, unit selection, pricing discussion, negotiation and booking support. Each stage creates information that should remain available to the next person.
Leads can come from digital campaigns, property portals, calls, walk-ins, referrals and channel partners. The first requirement is a reliable capture mechanism so that enquiries do not depend on manual forwarding.
Every lead should have basic context: source, contact details, project interest, assigned owner and current status. The exact fields should reflect the developer's process.
Not every enquiry has the same level of intent. Sales teams can qualify prospects based on requirements, budget fit, preferred configuration, location, timeline and other relevant criteria.
The objective is not to reject people prematurely. It is to prioritize attention and ensure that sales effort is aligned with the buyer's current position.
Follow-up is where many sales processes become inconsistent. A lead may receive a call, a message, a brochure or an invitation to visit. Without a structured task and activity history, the next step can become dependent on memory.
A strong workflow records communication and creates a visible next action. This makes the pipeline actionable rather than merely descriptive.
For many property buyers, the site visit is a major transition point. The organization should be able to see whether a visit was scheduled, completed, rescheduled or missed.
The sales process should not stop at marking "site visit done". The next action matters. A completed visit without a follow-up can become a missed opportunity.
Once the buyer becomes more specific, the sales workflow connects with inventory. The buyer may be considering a particular tower, floor, configuration or unit.
At this stage, inventory accuracy becomes critical. The sales team needs confidence that the unit discussed is genuinely available or that its current status is visible.
Booking is a major transition in the customer lifecycle. The process should capture the relevant unit, buyer information, commercial terms and booking status according to the organization's policies.
The more connected the booking process is to inventory and collections, the less manual reconciliation is required later.
Management needs more than the total number of leads. Useful visibility includes pipeline by stage, site visits, negotiations, booking activity, inventory movement, salesperson performance and exceptions requiring attention.
The purpose of a dashboard is not to create more charts. It is to make decisions faster by exposing the information that matters.
AI can support the workflow by identifying patterns and recommending next actions. Reos, the PREOS AI assistant, is positioned to score and rank leads after calls, suggest next best actions, draft follow-up messages and flag risks.
The sales team remains responsible for decisions. AI should help the team focus attention, not make uncontrolled commercial decisions.
A strong sales workflow should answer five questions at any moment: Where is this lead? Who owns it? What has happened? What needs to happen next? What inventory is relevant? When these answers are available in one connected system, the sales organization spends less time reconstructing context and more time acting on it.
Moving from lead to booking is not a single transaction. It is a chain of decisions, activities and handoffs. A connected workflow makes that chain visible, accountable and easier to manage. That is the foundation on which PREOS positions its sales operating system.
See how PREOS can work for your project. Request a demo and explore a connected operating system for real estate sales and operations. Request a demo →
Publishing note: verify any customer/project names, numerical claims, regulatory statements, awards or performance statistics before publishing.
Request a demo and explore a connected operating system for real estate sales and operations.
The most useful AI for real estate sales may not be the AI that makes decisions. It may be the AI that helps salespeople make better decisions faster.
AI is often discussed in terms of automation, but real estate sales involve decisions that require context. A buyer may be interested but uncertain. A site visit may have happened without a follow-up. A lead may have become silent after several conversations.
The practical opportunity is to use AI to organize this information and surface useful recommendations while keeping commercial authority with the team.
Sales conversations contain information that is difficult to capture consistently. Buyers discuss budget, configuration, location preferences, objections, timelines and next steps.
Call analysis can help convert conversation into structured signals. Instead of relying entirely on a salesperson's memory, the organization can use analyzed interactions to improve lead understanding and follow-up.
Not every lead deserves the same immediate attention. AI can help rank leads based on available signals, such as conversation outcomes, engagement, stage progression and other configured factors.
The score should be treated as an aid, not an absolute truth. A sales manager should be able to review the context behind a recommendation.
One of the most useful AI applications is suggesting what should happen next. A lead that completed a site visit two days ago without a follow-up may warrant a callback. A buyer who has requested pricing may need a structured response. A silent lead may require a different approach.
Reos is positioned around this idea: AI suggests the next move, while the team decides.
Salespeople spend time writing repetitive messages. AI can help draft a follow-up based on the available context, allowing the salesperson to review and approve it before sending. This preserves human judgment while reducing administrative effort.
AI can also help identify exceptions that might otherwise remain buried in activity. Examples include silent leads, expiring holds or unusual changes in engagement. The value comes from surfacing the exception at the right time, not from generating more notifications.
Real estate involves financially significant decisions. AI should not independently confirm bookings, change prices, apply discounts, or hold and release inventory without explicit authorization.
PREOS's stated Reos boundaries reflect this principle: Reos suggests and assists, but it does not independently execute sensitive commercial actions.
AI is only as useful as the context available to it. If lead information is fragmented, inventory status is outdated or activities are not recorded, recommendations become weaker. This is why AI should not be treated as an isolated feature. It works best when it sits on top of a connected operating system.
A useful enterprise model is human-in-the-loop AI. The system detects, summarizes, scores and recommends. The responsible employee reviews, decides and executes. This approach can improve productivity while maintaining accountability and organizational controls.
PREOS positions Reos as an AI assistant within its operating system. It can analyze calls, score leads, suggest next actions, draft follow-up messages and flag risks. At the same time, it is explicitly designed not to independently hold or release a unit, confirm a booking or change a price. The goal is not to replace the sales organization. It is to give the sales organization better context and a faster path to action.
The strongest AI strategy for real estate may not be "AI replaces sales". It is "AI makes every salesperson better informed". When intelligence is connected to real workflows and bounded by human authority, AI becomes an operational capability rather than a novelty.
See how PREOS can work for your project. Request a demo and explore a connected operating system for real estate sales and operations. Request a demo →
Publishing note: verify any customer/project names, numerical claims, regulatory statements, awards or performance statistics before publishing.
Request a demo and explore a connected operating system for real estate sales and operations.
Collections should begin with the booking and continue through every payment milestone, with clear ownership and escalation.
A booking creates a commercial commitment, not the end of the customer lifecycle. Payment schedules, milestones, reminders and collections activities follow.
When these activities are managed separately from sales and booking information, teams may spend time reconciling what was booked, what is due and what has been received.
Manual trackers can work for a limited number of customers, but they become difficult as the customer base grows. Payment dates can change, milestones can vary and multiple people may need visibility.
The operational challenge is not simply recording whether money arrived. It is knowing what is due, when it is due, who owns the follow-up and what happens when payment does not arrive.
A structured collections workflow starts with the booking. The relevant payment schedule can be associated with the customer and unit so that future milestones are visible.
This creates continuity between sales and collections. The collections team does not need to reconstruct the transaction from separate documents.
A proactive process can use defined escalation levels. A reminder may be sent before or around a due date. If the payment remains outstanding, a call task can be created. Continued delay can trigger manager attention.
The exact escalation rules should be configured to the developer's commercial and customer-service policies.
Management should be able to see collections at the level appropriate for their role: upcoming milestones, overdue amounts, ageing, project-level trends and exceptions. A dashboard does not replace collections activity, but it helps management identify where attention is required.
Collections should be firm and organized without becoming disconnected from the customer relationship. A system that provides context can help teams understand previous interactions, commitments and relevant information before contacting the customer. Consistency also reduces the chance that different employees give conflicting information.
Collections information can provide insight into the commercial health of a project. Developers can examine payment performance, overdue patterns and the relationship between bookings and collections. These insights can support operational planning, provided the underlying data is accurate and consistently recorded.
PREOS describes collections as a connected workflow in which every booking carries its payment schedule. When a milestone is due, the platform can support an escalation ladder involving reminders, call tasks and manager alerts. The intention is to make collections proactive rather than dependent on manual checking.
Collections performance is influenced by process discipline as much as by the ability to record payments. A connected workflow gives teams the information and accountability needed to follow up consistently. For developers, the objective is simple: know what is due, know what is overdue, know who is responsible and make the next action visible.
See how PREOS can work for your project. Request a demo and explore a connected operating system for real estate sales and operations. Request a demo →
Publishing note: verify any customer/project names, numerical claims, regulatory statements, awards or performance statistics before publishing.
Request a demo and explore a connected operating system for real estate sales and operations.
Choosing real estate software should start with the developer's operating workflow — not a generic feature checklist.
Many software evaluations begin with a list of CRM features. That is useful, but a developer should first map how the business actually operates.
Ask how a lead enters the organization, who owns it, how site visits are managed, how inventory is selected, who can hold a unit, how bookings are recorded, how collections are followed up and how management receives reports.
A modern system should provide a structured lead pipeline with source, ownership, status, activities, follow-ups and relevant customer information. Duplicate detection and conflict visibility are also important when multiple channels and teams generate enquiries.
Site visits should be connected to the lead journey rather than maintained as an isolated calendar. Teams should know scheduled visits, completed visits, missed visits and the next action after a visit.
Real estate software should provide a reliable view of unit availability and status. Developers should evaluate whether the system can represent project structures and distinguish available, held and booked units. Authority controls are equally important. A system should make it clear who can perform sensitive inventory actions.
The software should support the organization's actual sales stages, not force every developer into a generic process. Teams should be able to see where opportunities are, what activities have happened and what needs to happen next.
Booking should connect customer information, unit information and relevant commercial workflow. The objective is continuity, not duplicate data entry.
A developer should evaluate what happens after booking. Payment schedules, reminders, overdue tracking and post-sales activities should not disappear into a separate manual process.
Executives need a different level of information from sales executives. A strong platform should provide role-appropriate dashboards and management reporting without requiring teams to manually build every report.
Real estate sales happen across channels. A platform should be evaluated on how it captures or connects relevant communication, including calls, portals, walk-ins and other configured channels.
AI should be evaluated based on specific business outcomes rather than generic claims. Useful applications include call analysis, lead scoring, next-action recommendations, message drafting and exception detection. Developers should also ask what AI is allowed to do. Human control over commercial decisions is important.
A powerful system that teams do not adopt has limited value. Ask about onboarding, configuration, role setup, training, deployment time, support and data migration. The implementation model should be realistic about the organization's requirements rather than promising that every deployment is identical.
Evaluate software across eight areas: lead capture, sales workflow, inventory control, booking continuity, collections, reporting, AI assistance and implementation. Score each area based on actual business requirements, not only demonstrations.
PREOS positions itself around the broader operating problem: leads, inventory, sales teams and collections in one platform, with Reos providing AI assistance. The product is designed for Indian real estate developers and is organized around connected workflows rather than lead management alone.
The right question is not "Which CRM has the most features?" It is "Which platform can become the operating layer for the way our project actually runs?" That distinction helps developers evaluate software based on operational value instead of feature count.
See how PREOS can work for your project. Request a demo and explore a connected operating system for real estate sales and operations. Request a demo →
Publishing note: verify any customer/project names, numerical claims, regulatory statements, awards or performance statistics before publishing.
Request a demo and explore a connected operating system for real estate sales and operations.
A modern developer's technology stack should connect the complete project lifecycle instead of creating separate islands of information.
As developers manage larger teams, more projects and more customer interactions, technology becomes part of daily operations rather than a back-office convenience.
The challenge is that organizations often accumulate tools over time. One tool handles leads, another handles communication, another contains inventory, another produces reports, and spreadsheets fill the gaps.
The first layer captures demand from marketing channels, portals, calls, walk-ins, referrals and channel partners. The system should create a consistent record and assign ownership. The key objective is to ensure that demand enters the organization's workflow rather than remaining trapped in individual channels.
Once a lead is captured, the technology should support qualification, follow-up, site visits, negotiations and booking activities. This layer creates process discipline and makes pipeline progression visible.
Inventory is the physical and commercial foundation of the project. Technology should represent units, availability and status accurately and connect them to sales activity. Without this connection, sales data and inventory data can diverge.
Booking is the point where an opportunity becomes a commercial transaction. The technology stack should maintain continuity from the sales record into booking and subsequent customer activities.
Payment schedules, reminders, overdue tracking and escalation form another operational layer. Connecting collections with bookings creates a more complete view of the customer lifecycle.
Executives need consolidated visibility. Dashboards and MIS should bring together relevant operational data so that management can identify trends, exceptions and areas requiring action. The best reporting systems minimize the need for manual reconstruction.
AI can sit across the operating stack and add intelligence to existing workflows. It can analyze calls, summarize interactions, rank leads, recommend next actions and identify exceptions. AI becomes more useful when it has access to structured operational context.
Imagine a lead in one system, a unit in a spreadsheet, a conversation in WhatsApp and a payment schedule in another file. Each item exists, but the relationship between them is weak. A connected architecture allows the organization to move from records to context. The team can understand not only what exists, but how each piece relates to the next step.
A source of truth does not mean every employee sees every piece of information. It means the organization has a reliable underlying record and defined workflows around it. Role-based access, authorities and responsibilities can then determine who sees or changes what.
Technology projects often mirror organizational charts. But customers and transactions move across departments. A lead becomes a site visit, a site visit becomes a negotiation, a negotiation becomes a booking, and a booking creates collections activity. The technology should therefore connect the workflow across departments while still respecting each team's role.
PREOS is positioned as an AI-integrated operating system for Indian real estate developers. Its core concept is to bring leads, inventory, sales and collections into one connected operational environment, with Reos providing AI assistance. The objective is to reduce the number of disconnected operational layers and give developers a clearer source of truth.
The modern real estate technology stack is not defined by how many applications a developer owns. It is defined by how well information and workflows move through the organization. A connected operating system can provide a stronger foundation for growth, visibility and disciplined execution than a collection of isolated tools.
See how PREOS can work for your project. Request a demo and explore a connected operating system for real estate sales and operations. Request a demo →
Publishing note: verify any customer/project names, numerical claims, regulatory statements, awards or performance statistics before publishing.
Request a demo and explore a connected operating system for real estate sales and operations.