Next WrldFeatured case · Next Wrld product
INMOCRM / PROPTECHInmoCRM — The operating system for agencies with 2 to 20 agents.
A platform for managing properties, leads, follow-up, visits and commercial activity across daily sales and rental work.
Strategy · Product · UX/UI · Engineering · Cloud + AI
01 · Operational fragmentation
A sale moves forward over weeks. The information changes location every day.
An inquiry arrives on WhatsApp. The property lives in a spreadsheet, the contact in an agent phone and the visit in a group chat. When the lead asks again, the team rebuilds the story from scratch.
Each tool covers its part. The cost shows up in the follow-up that never happened and the visit nobody recorded.
02 · Product opportunity
Treat the operation as one continuous journey.
InmoCRM organizes work around the property as a commercial asset. Four principles guided the product from domain model to interface.
Record, statuses, media, owner and agent in charge in one place.
Every lead has an owner, a status and a next contact date.
AI drafts commercial copy. The team approves before saving.
Data, users and permissions isolated per agency.
Properties, leads, visits and notes spread across tools and individual memory.
One journey where each property keeps its record, its pipeline, its visits and its history.
INMOCRM · CONNECTED OPERATIONS03 · Understand and model
We defined how each commercial decision relates to the next.
The complete journey goes from loading a property to sharing its public page. In between, contacts become leads, leads move through the pipeline, visits produce outcomes and activity preserves the history.
Owners are contacts with owner type, not a separate entity. Each task, note and visit lives next to the case it belongs to, and activity records the complete timeline.
04 · Product walkthrough
The day starts with clear priorities.
The dashboard shows what needs attention today, which leads lack follow-up, which properties are incomplete, which visits are coming and which opportunities are active or stalled.
AttendLeads without follow-up and stalled negotiations in view.
CompleteIncomplete properties before publishing.
ScheduleUpcoming visits next to the daily schedule.
05 · The record as an asset
Each property keeps its commercial history.
Statuses from draft to published, operation and property types, linked owner, agent in charge, media with cover and ordering, flexible attributes and features, and a quality score showing whether the record is ready.
The web never calls AI directly. Python suggests through an internal endpoint. Go validates, decides, audits and persists only after explicit approval.
06 · Pipeline and visits
From first contact to visit outcome.
Leads move through statuses with movement history and per-agent views. No-follow-up detection keeps opportunities from going cold. Each visit links property, contact and agent, and keeps its outcome in notes.
Status changes with history. Each move keeps who made it and when.
Leads without a next date appear flagged for re-engagement.
Scheduled, confirmed, completed, cancelled, no-show or rescheduled, with recorded outcome.
The timeline brings events together for auditability and operational visibility.
07 · Public front door
The same record, ready to share.
Each property generates its public page with images, details, description, agency information and WhatsApp contact, plus a view counter. Internal CRM data is never exposed.
Load onceThe internal record feeds the public page without duplicating data.
Publish with judgmentThe quality score and AI approval support the decision.
Measure interestThe view counter shows which properties attract inquiries.
08 · Multi-organization product
One shared foundation with isolated operation per agency.
InmoCRM runs as a multi-tenant SaaS. Each organization keeps its profile, timezone and currency, with owner, admin, agent and assistant roles. Every operational query is scoped by organization.
- Properties
- Leads
- Users
- Permissions
Isolated data, users and operations
- Properties
- Leads
- Users
- Permissions
Isolated data, users and operations
- Properties
- Leads
- Users
- Permissions
Isolated data, users and operations
Shared database with shared schema. Isolation resolves through organization_id on operational tables, with RLS possible in the future.
09 · System thinking
The interface is the visible layer of connected decisions.
We designed experience, workflows, rules and data as parts of the same product, so a recorded visit retains its meaning through the dashboard and the public page.
ExperienceDashboard · records · pipeline · visits · public page
Product workflowsProperties · leads · tasks · notes · appointments
Business logicStatuses · roles · tenancy · AI approvals
Data & infrastructurePostgreSQL · media storage · deployment
Technology by responsibility
Each technical decision supports a concrete product responsibility.
Private CRM interface and public page, with session state and API client.
Modular monolith that validates, decides, audits and persists. Organization-scoped queries, UUID keys, timestamptz in UTC.
Suggests descriptions, titles, messages and missing-data detection through a token-protected internal endpoint. Never persists business state.
The database keeps image metadata and keys. Redis and queues remain reserved for future work.
Built to evolve
MVP scope stays closed. The future path stays visible.
- Properties and media
- Leads and pipeline
- Visits and tasks
- Notes and activity
- Bounded AI with approval
- Public pages
- Portal publishing
- Billing and contracts
- Automations
- Lead scoring
- Mobile app
10 · End-to-end involvement
Next Wrld stays with the product from the operational question through its evolution.
In InmoCRM, we work across strategy, product definition, experience, architecture, frontend, backend, data and infrastructure. The decisions stay connected throughout one process.
- 01Discover
Understand the operation and its decisions.
- 02Shape
Define product, scope and model.
- 03Build
Design and implement the workflows.
- 04Launch
Bring the system into operation.
- 05Evolve
Learn from use and decide what follows.
Concrete result
A commercial operation with shared context.
Teams can load properties with media and quality scoring, register contacts and owners, create leads with budget and follow-up, move opportunities through the pipeline, schedule visits with outcomes, generate approved AI content and share public pages from the same record.
The dashboard organizes the current state through attention today, leads without follow-up, incomplete properties, upcoming visits and active or stalled opportunities.
InmoCRM connects how agencies sell and rent with how the product is built. That continuity defines Next Wrld’s work: strategy, product, experience, engineering and cloud under one shared responsibility.
Operational diagnostic
Turn a critical part of your operation into a system.
Let’s review one concrete process and decide where it makes sense to simplify, connect or build.
← Back to case studies