A feature list says nothing about the work of the people using it. This is a normal Tuesday at Imofolio, from the first coffee to closing time — each hour with the module doing the work and the screen where it happens.
Nobody starts the morning choosing what to pick up. The dashboard brings each property's signals into one line and writes the reason: overdue, today, expires, tomorrow, stalled. The button that resolves it is on the line itself.
Outlook is read live inside the CRM and linked to the right contact every five minutes. The owner's message leaves one person's inbox and becomes part of the property's history.
Good morning, here is the updated property book. The energy certificate will only be ready next week.
The portal CSV uploads, columns are recognised, and repeated references update instead of duplicating. Missing data does not block the import: it goes to a queue with an owner, severity and a button to resolve it there.
Saving what the client wants runs through every ready and published listing. Each receives a score from 0 to 100, with reasons beside it — and below 50 points it is not suggested at all.
The listing is the public face of the record: title, advertised price, objective and status. The sales team and agency website read the same record, so the price is never right in one place and wrong in another.
Title and price to be written
Choose the listing and the person. The viewing appears in the team calendar and the consultant's personal calendar — Google or Outlook, connected per person — and its follow-up task is born with it.
Follow-up task created for the next day.
Terms in each version are immutable. The seller's reply is version 02 of the same chain, with its value, deposit, closing date, validity and conditions. Anyone joining halfway reads the entire negotiation in order.
Terms are immutable: every reply is a new version of the same chain.
Converting an accepted proposal creates the deal already linked to the property and the chain it came from. From there, what matters is the stage, value and target closing date.
Tasks stay organised by deadline, priority and owner — yours and the ones nobody claimed. Anything not done today appears tomorrow morning on the dashboard, with the delay written out.
Not everything the product does has a screen. These four things run underneath the whole day.
Change the price of a T3 and requirements that now fit are scored again — while the consultant's status for each opportunity survives the recalculation.
Every five minutes, new messages find the contact they belong to — and through them, the property they mention.
Booking creates the next day's task, with an owner. A completed viewing remains pending until someone writes what happened there.
Five days before a proposal expires, twenty-one days after a property stops moving, the minute a task passes its deadline: the dashboard raises each one, with its reason written out.
The left column is not a caricature: it is how these same hours run today in most agencies, with spreadsheets and a contact-first CRM.
| Without Imofolio | With Imofolio | |
|---|---|---|
| The portfolio | One spreadsheet per consultant, with the good version attached to an email | One record per property, with units, parties, documents and history |
| Who knows what | Ask the group who has the property book | The document on the record, with expiry date and alert |
| Finding the right property | The consultant's memory and an afternoon of triage | The portfolio scored from 0 to 100, with reasons written out |
| The negotiation | Values rewritten in one file until nobody knows the order | Immutable versions in a chain, with validity running |
| When someone leaves | The portfolio leaves with them | Viewings, proposals, emails and notes stay on the property |
| Monday's report | Copy numbers from three places | Statuses and totals in the list, always up to date |
Fourteen days on the Agency plan, no card. Import the portal CSV and the day above becomes your agency's day.
