The harsh truth is most property investors have no idea what their portfolio is actually worth today. They know what they paid and what their broker wants to list it for. Here's how I fixed that for one of my clients: a live dashboard inside Claude that pulls DXB Interact on the first of every month and logs how the portfolio is actually performing. Three prompts. One Chrome extension. No code.
Most retail investors track their portfolio in three spreadsheets and a forwarded broker email. Capital values from last year's launch sheet. Rents from a tenancy contract signed two summers ago. Comparables from whatever WhatsApp thread the broker dropped you in.
The numbers are real. They are never current. The gap between what they paid and what their broker wants to list it for is the gap where the bad decisions live.
A live artefact closes that gap. You give Claude the portfolio once. The Chrome extension lets Claude open DXB Interact in your own browser. Same session as yours. Same DLD-sourced data you would pull yourself.
The artefact lives inside your Claude chat. On the first of every month, Claude reopens DXB Interact, scrapes the latest data, and rebuilds the dashboard in place. Every refresh appends to a month-over-month log.
This is what Power BI and Tableau used to do. The shift is that the dashboard is built in three prompts instead of three weeks. The data layer is whatever the browser can see.
Three prompts. One extension. A dashboard that rebuilds itself every month and logs the history.
One live artefact in Claude, scoped to a real portfolio. It opens itself on the first of every month, pulls the latest DXB Interact data, rebuilds the charts in place, and logs how the portfolio has moved since last month.
Foundation: the Claude desktop app in Cowork mode, with the Claude Chrome extension installed and turned on. Cowork is the agent surface where Claude can open browser tabs, write files, and host an interactive artefact in the same conversation.
Inputs: the portfolio, given to Claude once at the start. Addresses, purchase prices, current rents, and the year of purchase, in a single message. Plus DXB Interact as the data layer Claude reopens on every refresh.
Output: a live artefact dashboard. Metric cards show current value, yield, and equity. Bar charts plot capital appreciation by unit and yield against the market median. A comparable-transactions feed and a month-over-month log build up over time.
The Claude desktop app, switched into Cowork. The Claude Chrome extension installed, signed in, and given site-level access to DXB Interact. This is the only configuration step in the whole build.
No API key. No server. No cron. The schedule lives inside Claude.
One message with the portfolio, the single source to scrape (DXB Interact), and the metrics to assess on every refresh. Claude returns three artefacts: a portfolio strategy document, a data sheet, and a 12-month action plan.
This is the conversation Claude resumes every month. The portfolio context is the spine.
One more prompt converts the numbers into a live Claude artefact: metric cards, bar charts, a yield-against-market panel, and a transaction feed by building. The artefact lives inside the chat. You can bookmark and share the conversation URL.
Every refresh writes back to the same artefact rather than spawning a new one.
One final prompt sets a scheduled task to rerun the scrape and rebuild the artefact on the first of every month. Claude reopens DXB Interact in the same Chrome session, pulls the latest data, and updates the dashboard in place. Each refresh appends to a month-over-month log.
The schedule lives in Claude's task runner, not on your machine. The task fires whether your laptop is open or closed at the trigger time.
Claude Pro, Max, Team, or Enterprise. Cowork plus the Chrome extension is available on these tiers as of December 2025. The free tier does not include Cowork agent mode.
Google Chrome with the Claude extension installed. Available from the Chrome Web Store, signed in with the same Anthropic account as the desktop app.
DXB Interact, no login required. The public search at dxbinteract.com covers transactions, rentals, and building-level analytics for the whole Dubai market.
Fifteen minutes for the first build end to end. After that, the artefact is unattended.
Claude for Chrome blocks three site categories regardless of your prompt: financial services, adult, and pirated content. DXB Interact is not in any blocklist. Site-level permissions still apply, so Claude asks you to approve dxbinteract.com the first time it visits. Approve once and every monthly refresh after that reuses the permission.
Open the Claude desktop app and switch to Cowork. Install the Claude Chrome extension and turn it on in Chrome. These are the only two configuration steps in the whole build. After this, every step is a prompt in the same conversation.
One. Open Cowork. Open the Claude desktop app and switch to Cowork. Cowork is the agent surface where Claude can open browser tabs, write files, and host an interactive artefact in the same conversation. If the toggle is greyed out, your tier does not include it. Pro, Max, Team, or Enterprise is required.
Two. Install the Chrome extension. Open Chrome, go to the Chrome Web Store, search "Claude for Chrome", and install. Sign in with the same Anthropic account as the desktop app and toggle the extension on. Without it, Claude cannot open your browser or pull live data from pages.
The first time Claude visits dxbinteract.com, the extension asks you to approve access to that domain. Approve once. The monthly schedule reuses the same approval. You can revoke the domain at any time from the extension settings, and Claude will ask again the next time it needs the site.
Claude for Chrome ships with a confirmation step before high-risk actions: publishing, purchasing, or sharing personal data. Scraping public DXB Interact pages does not trigger a confirmation. If the prompt tells Claude to log in, submit a form, or click a buy button, the confirmation step is what stops it. Leave it on. Autonomous mode is for repeat tasks you have already vetted.
One message with the portfolio, DXB Interact as the data source, and the metrics to assess on every refresh. Claude opens DXB Interact and pulls the data. Three artefacts come back into the chat: a portfolio strategy document, a data sheet, and a 12-month action plan. This is the conversation Claude resumes every month.
A property dashboard with only price and yield is a screenshot. The other four metrics tell you whether the price is real, the yield is sustainable, and the unit is liquid in its building. Cutting metrics for "simplicity" makes the artefact prettier and the decisions worse.
DXB Interact aggregates DLD transaction records, rental indices, and building-level analytics into one searchable interface. Bayut and Property Finder show asking prices, which run ahead of transaction prices in rising markets and behind in falling ones. Anchor every value to the DLD-sourced number on DXB Interact. One source, one truth, one site permission for Claude to remember.
Once Claude has the data, convert the numbers into a live Claude artefact. The artefact is the visual layer: metric cards, charts, and a transaction feed. It lives inside the chat, shares by URL, and rebuilds in place on every refresh.
The instruction "update it in place" matters. Without it, every refresh spawns a new artefact and the dashboard URL changes. One artefact, updated in place, means the monthly refresh writes back to the same URL you bookmarked, and the log keeps accreting on the same artefact.
The final prompt sets a scheduled task. On the first of every month, Claude reruns the scrape, pulls the latest numbers from DXB Interact, and updates the artefact in place. Each refresh appends to a month-over-month log so the time series builds up over the year.
DLD transaction records register with a lag of days to weeks. A daily refresh against DXB Interact catches mostly noise. Monthly matches the cadence at which property values, yields, and comparables actually move, and lets the log compound into a real time-series after six months.
Claude's scheduled tasks live inside the conversation that registered them. If you delete the conversation, the schedule goes with it. Pin the conversation in the Claude sidebar. If a monthly run skips, open the conversation and type "what happened with the 1st-of-month refresh." Claude reports whether the trigger fired, the scrape ran, or the artefact update failed.
The Chrome extension is free. Cowork and live artefacts are included on Pro, Max, Team, and Enterprise. The morning refresh consumes session minutes from the same allowance you already pay for. No API key, no metered runtime, no third-party bill.
Pro at twenty dollars a month covers the build and the monthly refresh comfortably, even for a thirty-plus unit portfolio. One scheduled run per month barely registers against the allowance.
Claude for Chrome is free from the Chrome Web Store. It is the data layer for the whole pipeline.
The monthly refresh runs inside your existing tier. No metered runtime. Step up to Max only if you want to run the audit on demand mid-month for multiple clients in parallel.
The artefact is good at displaying. It is not good at deciding. The five things below are where the investor still has to do the work.
DXB Interact aggregates DLD records cleanly, but a single source means a single bias. If you ever doubt a number, cross-check against Bayut or Property Finder for a sanity read on broker sentiment, even if you don't anchor value to it.
A unit dropping into the UNDERPERFORMING tier is the trigger for a conversation, not a sell signal. The artefact surfaces the question. You still have to walk the unit, read the SPA, and price the friction of exit before the next move.
If DXB Interact changes its DOM, the monthly scrape can fail silently and the artefact will look fine with stale data. Check the "last refreshed" timestamp on the second of every month. Re-run the audit prompt by hand if the date does not say this month.
The month-over-month log is the actual product. It only gets useful after three or four months of data. Resist the urge to wipe the artefact and start over when the numbers move against you. The history is what tells you whether a soft month is a trend or noise.
The schedule lives inside the chat conversation. If you accidentally delete the conversation, the schedule and the log go with it. Pin the conversation in your Claude sidebar. Treat it like a production system, not a draft.
Day 12 ran a six-skill pipeline on a 6am API schedule, looking out at the market. Day 13 runs a smaller cousin of the same idea on the consumer side, looking in at what you already own. One scans for tomorrow's acquisition. One watches today's holdings.
A retail investor running Day 13 alone has a portfolio that monitors itself. Add Day 12 on top and you have a back office. One pipeline scans every new launch for tomorrow's acquisition. One artefact tracks every existing unit for today's decision. Two surfaces, one schedule, one operator.
By the morning of the 1st, the same artefact URL you bookmarked last month has the new numbers. Capital values pulled from DXB Interact. Yields against this month's comparable rents. New transactions in each building added to the feed. The WHAT CHANGED panel at the top names anything that moved more than 2 percent since last month. The month-over-month log gets a new row.
The month starts not with you asking Claude where the portfolio stands, but with you and the client reading what Claude already pulled. That is the architecture shift Day 13 ships.
Every prompt in this 30-day series is one capability. FourthspaceOS bundles all of them into a single product: underwriting, comps, market research, deal sourcing, portfolio tracking, and investor reporting. The product runs natively on the same Anthropic agents and plugins you are learning to use this month.
Waitlist members get founding pricing, early access, and one new prompt delivered each day for the next 30 days.
Founding pricing locks in for waitlist members.
One email a day for 30 days. No spam. Unsubscribe whenever.
Send them this page. The work it takes to keep a property dashboard alive in Excel is the work the live artefact removes. The leverage is not the chart. It is the fact that the chart is already current when the client opens the laptop on the 1st of the month.
Find me on Instagram ↗You do not need every metric on day one. Wire the setup, paste a single-unit portfolio, and get the first artefact rendering. Add the rest of the holdings the next day. The artefact compounds as you feed it more, and the log starts building from refresh one.
Jump to setup ↑