WEBSITES, CRM & AI FOR REAL ESTATE

Connect your website, lead follow-up and daily operations.

Improve the website you have, organize your sales pipeline or automate a specific task. We build around your listings, tools and team, with clear handoffs to a person.

Discuss your project Explore the modules

Start with one defined module. Scope, delivery dates and fees are agreed after we review your systems and priorities.

Work with your existing website and tools
Start with the module you need
Human review for sensitive decisions

CHOOSE YOUR STARTING POINT

Fix the part of the operation that needs attention first.

Choose a focused project or combine modules where they depend on each other. We assess your existing setup before recommending a rebuild.

Existing website improvements

Fix inquiry forms, mobile usability, page speed and listing presentation. Keep what works and define the changes needed to support your buyers and sellers.

Search visibility

Review indexing, page structure, local content and property pages. Prioritize the technical and content changes that make your services easier to find and understand.

CRM and lead follow-up

Define pipeline stages, ownership, next steps and follow-up sequences in your current CRM, or assess a suitable tool if you need one.

Client-facing AI

Handle routine inquiries over SMS, email or WhatsApp, where supported. Use approved listing data, capture buyer requirements and transfer negotiations to your team.

Document workflows

Extract fields from contracts and deeds, flag missing information and populate approved templates. Your team reviews the source and output before anything is used or sent.

Availability depends on access, data quality and provider capabilities. Each module has its own deliverables and acceptance criteria.

LEAD FOLLOW-UP DEMO

From the first inquiry to an agent handoff.

This Brazilian example shows a WhatsApp conversation alongside listing search, buyer qualification, viewing scheduling and CRM updates. The video interface is in Portuguese.

This example illustrates the workflow. Your channels, integrations, qualification rules and handoff criteria are defined with your team.

WHERE INQUIRIES LOSE MOMENTUM

An inquiry arrives while your team is out on viewings.

Website, email and portal inquiries arrive outside office hours or while agents are with clients. Follow-up becomes inconsistent, listing details are checked manually and the next step is not always recorded.

After-hours inquiries waiting for a reply
Follow-up without a clear owner or next step
Qualification that changes from agent to agent
Agents spending time on repetitive questions
Listing details checked across separate tools
Promised follow-up that never happens
Notes added to the CRM late or incompletely

A defined workflow gives the team a shared way to respond, record context and decide what happens next.

CLIENT-FACING AI MODULE

Routine inquiries handled with your data and your rules.

The agent checks approved listing data, captures the information your team needs and hands the conversation to a person when it reaches a defined limit.

Task	Common manual workflow	Defined agent workflow
First response	Depends on an available team member	Responds on supported channels within the agreed coverage
Buyer qualification	Questions and notes vary across the team	Captures location, budget in the relevant currency, timing and team-approved criteria
Listing recommendations	Searches separate listing tools manually	Checks connected listing data and flags missing or uncertain information
Viewing scheduling	Several messages to find an available time	Suggests available slots and records confirmed appointments
Follow-up	Depends on reminders and individual habits	Follows agreed sequences, consent rules, frequency limits and opt-outs
Handoff to an agent	Conversation copied without a clear summary	Shares requirements, conversation history and the next step
CRM records	Notes added later when someone has time	Records permitted updates in the connected CRM

Your team stays responsible for negotiation, advice and decisions that require professional judgment.

BUILT AROUND YOUR OPERATION

Your listings, your tools and your commercial process.

We define what to connect, what to change and what needs a person before implementation starts.

Connect the tools you already use

Listing, CRM and calendar connections are assessed against the available APIs, permissions and data quality.

Agree on the boundaries

Your team approves the qualification criteria, permitted actions and situations that require a human handoff.

Expand in separate phases

Additional channels, branches and workflows can be scoped after the first module is evaluated.

Document ownership and dependencies

The proposal identifies the code and configuration delivered to you, along with third-party licenses, fees and access requirements.

The first conversation establishes priorities. The assessment confirms access, dependencies and the smallest useful scope.

DELIVERY

Put one defined workflow into use, then decide what to add.

01
Assess the current setup
Review the website, inquiry channels, listing data, tools and manual steps relevant to the selected module.
02
Agree on scope
Document deliverables, dependencies, fees, dates and acceptance criteria before implementation.
03
Implement and review
Demonstrate working changes and test the workflow with your team before a controlled release.
04
Evaluate the next step
Review usage, response times, handoffs and failures where relevant. Decide whether to adjust, expand or hand over.

Investment

Scope and fees

Quoted by module

Fees depend on the selected module, integrations, data and review requirements. We agree on deliverables and milestones before work starts.

Discuss your project

Monitoring, support and further changes can be quoted separately where needed. Messaging, AI models, hosting and third-party tools are listed separately in the proposal.

CONTROLS AND DATA

Define what the workflow can do and how it is reviewed.

Controls are designed for the selected workflow and systems. We document access, data flows, failure handling and the decisions that need a person.

Supported channels

Connect SMS, email or WhatsApp through supported providers and APIs where access allows.

Checked events and duplicate handling

Verify incoming events where supported and prevent duplicate actions during retries.

Clear workflow stages

Separate classification, routing, response and record updates so the team can inspect each step.

Limited actions

Define which information the agent can read and which actions it can take.

Source-based answers

Check listing details against approved sources and route missing information to the team.

Team-approved qualification

Capture the fields and status labels your team uses, with budget recorded in the relevant currency.

Handoff with context

Share a summary, requirements and conversation history with the person taking over.

Access boundaries

Restrict each integration and user to the data and actions required for their role.

Documented data flows

Identify which systems and providers process data and define retention and deletion responsibilities.

Monitoring

Record workflow status and failures so the team can investigate and respond.

Action history

Keep the context and outcome needed to review permitted actions.

Failure recovery

Limit retries, record unresolved work and alert the responsible team.

Privacy requirements depend on your market, systems, contracts and operating process. Technical controls do not provide automatic legal compliance.

RELEVANT EXPERIENCE

Real estate platforms and systems integration.

Professional experience

Pilar Homes: real estate platform experience

Lucas worked on Pilar Homes as part of his individual professional experience, including real estate product and engineering work. This is not a direct Syntesi client engagement, and no commercial results are attributed to the studio.

View the experience

Engineering

What to ask us to demonstrate

Connect SMS, email or WhatsApp through supported providers and APIs where access allows.
Check listing details against approved sources and route missing information to the team.
Capture the fields and status labels your team uses, with budget recorded in the relevant currency.
Share a summary, requirements and conversation history with the person taking over.
Restrict each integration and user to the data and actions required for their role.

Ask to see how an action is checked, how a conversation reaches a person and how an integration failure is handled.

FAQ

Questions to assess a suitable starting module.

Do we need a new website?

Not necessarily. We can improve the website you already have. A rebuild is considered when its structure or platform prevents the changes you need.

Do we need a CRM?

Website, SEO and document modules can be scoped without one. CRM and follow-up work depends on how your team records inquiries and next steps; we can assess your existing tool or a suitable alternative.

Which channels can an AI agent use?

SMS, email and WhatsApp can be assessed according to your provider, access and customer preferences. We confirm the supported channels and permitted actions before implementation.

Can you automate contracts and deeds?

We can extract fields, compare information and populate templates approved by your team. Outputs need human review. The workflow does not provide legal advice or independently approve a contract or deed.

How are fees and delivery dates set?

We assess the selected module, existing systems, data and dependencies, then agree on a proposal with deliverables, milestones and acceptance criteria. Support and third-party fees are identified separately.

What happens when an AI agent makes a mistake?

We limit its actions, check answers against approved sources and route uncertain cases to your team. Logs help investigate issues and improve the workflow; they do not eliminate every error.

How do you handle privacy?

Data flows, providers, retention, permissions and responsibilities are documented for the project. Applicable requirements depend on your market and operation; technical architecture alone does not establish legal compliance.

Why choose a custom project over an existing platform?

An existing platform may be the right choice when it covers your needs. A custom module is useful when you need specific website improvements, integrations or workflows that your current tools do not cover.

Next step

Which part of your real estate operation needs work?

Tell us what already exists and what is getting in the way: your website, search visibility, follow-up, client inquiries or document handling. We will assess a suitable starting module.