In short
Company Intelligence means a real estate business connects its existing systems (CRM, website, portals, accounting, property management), its knowledge (properties, processes, responsibilities) and its team through one central layer, the Company OS, supported by AI. Nothing gets rebuilt. What works stays and gets connected. The build-up runs in three phases (Learn, Improve, Create), and the entry point is a single workflow, for example enquiries that land cleanly in the CRM with a prepared follow-up. Which of the 16 building blocks come when is decided by the business case: where time is lost, where information is missing, what customers and team notice immediately.
Over the past months I have built a Company OS for several clients, block by block. Along the way the term Company Intelligence took shape for me. Not as a product, but as a principle: the company knows what it knows, and everyone on the team gets what they need for the next step. The diagram in this article is the best practice from those projects, using a real estate business as the example.
What a Company OS is and what it is not
A Company OS is not a new piece of software that replaces everything. It is the connection between what is already there: the CRM holding contacts and properties, the website with its forms, the portals, the accounting, the file store with exposés and contracts, the calendar, the phone. Plus the knowledge that today sits in heads, emails and folders. And the people who work with all of it.
AI sits inside that connection as an assistant: it reads, assigns, prepares, answers questions from the released knowledge. It does not decide, and it replaces no system that runs well. That is exactly the difference from what many people mean by digitalisation: I do not have to rebuild the existing business to make it better.
The 16 building blocks in four fields
The diagram is the map, not a mandatory programme. No company needs all 16 blocks, and certainly not all at once. For orientation, the four fields:
Acquisition and marketing
More owners, more suitable properties, more reach.
- Owners and acquisition: valuation funnels, referrers, search engines and AI search, campaigns, lead qualification.
- CRM and data: contacts and properties, search profiles, duplicates and data quality, integrations.
- Website and portals: property pages, listing portals, forms and appointment booking, tracking with consent.
- Marketing and brand: exposés and property copy, photos and floor plans, social media, SEO, GEO and ads, brand rules.
Sales and transactions
The right buyers, secure processes, successful closings.
- Sales and matching: matching property and prospect, lead routing, viewings and feedback, offers, pipeline and follow-ups.
- Transaction and compliance: documents and data rooms, identification and anti-money-laundering checks, creditworthiness, contracts and e-signature, notary appointments.
- Lettings: rental prospects, self-disclosure, viewing appointments, tenancy agreements, deadlines.
- Partners and network: banks, notaries, photographers, tradespeople, referrals with status.
Operations and service
Efficient workflows, satisfied customers, long-term relationships.
- Communication: email and calendar, call notes, chat, tasks, reply drafts and translation.
- Customer service and portals: owner portal, marketing reports, prospect portal, status updates, reviews.
- Property management and portfolio: tenants and owners, damage and service tickets, maintenance, statements, deadlines.
- Knowledge and team: processes and checklists, onboarding, market knowledge, internal search, responsibilities and cover.
Business and development
Transparency, better decisions, new opportunities.
- Finance and steering: commissions and invoices, payment status, budgets, revenue forecasts, cost per lead and mandate.
- Reporting and leadership: marketing and sales figures, lead sources through to closing, time to sell, team and office reports.
- Security and operations: roles and access rights, approvals, retention and deletion, backups, monitoring.
- New products: phone assistant, valuation assistant, matching service, market reports, customer and partner portals.
Three phases: Learn, Improve, Create
I always build in the same order, whatever the size of the company.
- Learn. Bring released knowledge together and understand how the company actually works. Not as the org chart says, but how an enquiry really travels from the form to the appointment today, who files what and where it gets stuck.
- Improve. Connect existing systems better, remove duplicate work, improve workflows. This is where most of the value comes from, with tools that are already paid for.
- Create. On that basis, develop new functions and products when they are needed: an owner portal, a phone assistant, a valuation assistant. Then, not before.
Three entry points that pay off within weeks
You start with a single workflow. These three have proven themselves as first building blocks in the projects:
- Enquiries that arrive cleanly. Every enquiry from website, portal or phone lands in the CRM, is assigned to the right property and agent, gets a priority and a prepared follow-up. The team decides, the preparation is already there.
- Internal search. The team finds information on properties, processes and responsibilities in seconds instead of minutes. Questions like "Which documents do we need for the financing confirmation?" or "Who covers the north office during holidays?" are answered by the Company OS from the released knowledge.
- Marketing report for owners. Instead of collecting figures from portal, CRM and statistics at month end, the report is generated from existing data and the agent adds the assessment.
Which blocks come next, and in which order, is decided by the business case. Three questions are enough: Where is time lost today? Where is information missing? What gives customers and team a benefit they notice immediately?
Prerequisites nobody likes to talk about
A Company OS is only as good as its foundation. Three things therefore belong in from the start:
- Clear responsibilities. Who maintains which data, who releases content, who decides when two systems conflict.
- Clean data. Duplicates, outdated contacts and properties without a status make any automation unreliable. The clean-up is part of Learn, not a project afterwards.
- Control over access. Who may access which knowledge, which data goes to an AI model and which does not, what gets deleted and when. That is not a footnote, it is the condition for the team trusting the system.
Real estate is the example case
The diagram shows a real estate business because that is where I have built the most. The principle is the same for a property manager, a developer, a law firm or a retailer: connect systems instead of replacing them, release knowledge instead of searching for it, start with one workflow instead of everything. How extensive the implementation becomes depends on the existing tools, the integrations, the data quality and the priorities. We define the stages together.
Frequently asked questions
Do we have to change our CRM?
No. The Company OS builds on the CRM you have, as long as it offers an API or an export. A change only becomes a topic when the existing system is the problem itself.
How long does the first building block take?
A single workflow such as enquiry handling is usually live within four to eight weeks, including the Learn phase. The duration depends mainly on data quality and integrations.
Which data goes to the AI?
Only released data. In the Learn phase we define which content the model may see and which it may not, for example salaries, contracts or personal data without consent. Confidential areas stay out or are masked.
What does a Company OS cost?
That depends on the scope. The first building block is a manageable project, further expansion follows the business case. There is no licence for everything, only building blocks that each have to pay for themselves.
Do we need our own IT for this?
Not for operations. What you need is one person in-house who owns responsibilities and data maintenance. The technology runs on existing systems and standard services.