A free guide by FourthspaceOS INSTAGRAM WAITLIST
Day 29 · 30 Prompts in 30 Days

You are thebottleneckin your propertybusiness.

The reason your property holdings eat all your time is not the amount of work. It is that you are still the system every task has to pass through. Better prompts do not fix that. Designing the workflow once does.

The work is not the problem. You being the system is.

Think about how a normal week goes. You pull the comparables for the deal you are looking at. You rebuild the same cash flow model from scratch. You chase the agent for the floor plan and the service charge.

None of that is hard. It just all waits for you. That is exactly why you can only ever look at a handful of deals at once.

01Every deal

Pulling the comparables

You open the portals, gather recent sales and launches, and line them up by hand. Nothing moves until you sit down to do it.

02From scratch

Rebuilding the cash flow model

The same rent, service charge and payment-plan maths, typed out again for every new property, in a fresh spreadsheet each time.

03Every time

Chasing the documents

The floor plan, the service charge, the payment schedule. You send the messages, you wait for the replies, you file what comes back.

The real bottleneck

Every one of those jobs routes through the same single point: you. The task itself is fine. The problem is that you are the one thing all of it has to pass through before it moves.

So your capacity is not set by how good the deals are. It is set by how many things you personally have time to touch.

Your holdings do not eat your time because property is hard. They eat it because every task is waiting for you.

Who this is for

Anyone running property who still does every task themselves. The examples are Dubai deals, because that is what I run, but the shift transfers to any market and any portfolio size.

The myth · A better prompt is the answer

Better prompts keep you doing the work.

Most people try to fix the time problem by getting better at prompting. It feels like progress, because each answer comes back sharper than the last.

But a better prompt still leaves you doing every task by hand, one at a time. You have made yourself a faster manual operator. You are still the operator.

A useful piece of history

When factories first switched from steam to electricity, most just swapped the power source and kept the exact same floor plan. The productivity jump did not come for years.

It arrived only when they redesigned the whole factory around the new power. Bolting AI onto a workflow where you are still the hub is the same mistake. Same floor plan, new engine.

A sharper prompt still runs through you. You have not removed the bottleneck. You have just made it type faster.

The shift · Design it once

Stop running each task. Design the workflow once.

The move is to stop being the person who runs each task, and become the person who sets it up once. You define how the research, the underwriting and the document chasing should run, and then they run without you.

You step back in at one point only: the decision. Everything up to that point is a system you designed, not a task you performed.

How to describe a workflow, once

This is the part that matters, and it is not a prompt to memorise. You are not writing a clever instruction. You are describing the finished result you want, clearly enough that Claude can run it every time without you.

  1. The output you want. Name the finished thing, not the task. A filled comparables sheet. An underwriting verdict with the numbers behind it. A one-page portfolio summary.
  2. The inputs it uses. Say where the information comes from each time: the portals you trust, the files in the Project, and the few questions it should ask you when something is missing.
  3. When it runs. On a schedule, every morning, or the moment you drop a new listing in. Decide what starts it, so you do not have to.
  4. Your decision point. Name the one moment you want to step in: approve the shortlist, sign off the model, send the chase. The system does the rest.
The hard part

The hard part is not the tool. It is working out the formula yourself first, then describing it clearly enough that the AI can repeat it. Get the four parts above right and the workflow runs on its own. Skip them and you are back to prompting by hand.

The method · Choose what to design first

You cannot design everything. So choose well.

Before you set anything up, run two quick passes over the jobs that fill your week. The first pass sorts them. The second ranks what is left.

This is how you avoid the classic mistake: automating the wrong thing first, or handing a machine a decision that should stay yours.

Automate
Runs without you

Repeats often, has a clear output, and needs little judgement. Document chasing lives here. The work is defined, so a system can own it end to end.

Assist
You still decide

The AI does the gathering and the first draft, but the call is yours. Underwriting lives here. The model builds the case, you sign it off.

Manual
Keep it yourself

Rare, or high enough stakes that the time saved is not worth the risk. A one-off structuring decision lives here. Do not hand this over yet.

How I rank what is left

Once a job is in the Automate pile, score it on four questions. The higher it scores, the sooner it is worth designing.

  1. How often does it repeat? A job you do every day is worth more than one you do once a quarter. Frequency is where the hours hide.
  2. How many hours does it eat? Half a day of your week beats ten minutes. Weigh the real time it costs you, not how annoying it feels.
  3. Is the output well defined? One clear deliverable you can describe in a sentence beats a fuzzy "look into this". If you cannot name the finished thing, it is not ready.
  4. Can you check the result fast? A job where you can glance and approve beats one where you have to re-audit everything by hand. Quick to verify means safe to hand off.

Score each job, add it up, and the highest totals are what you design first. That is exactly how the three below got picked.

Where not to start

Do not automate the high-judgement or high-stakes calls first, however tempting. Those belong in the Assist and Manual piles. The fastest wins are the jobs that repeat, have a clean output, and are quick to check, not the ones that decide where your money goes.

Start here · Three jobs to hand off first

You do not design all of it at once.

Run those two passes over your own week and the same three jobs surface every time. They repeat the most, eat the most hours, and are the quickest to check. These are the three I would design first, in this order.

01Research

The comparables workflow

Designed once, it pulls recent sales and launches, lines them up, and hands you a ranked shortlist. You review the shortlist instead of building it.

02Underwriting

The cash flow model

One defined model that takes a property and returns the rent, the service charge, the payment plan and the verdict. You sign it off, you do not rebuild it.

03Admin

Document chasing

The floor plan, the service charge, the payment schedule, tracked and requested for you. You approve what to send, the system does the chasing and the filing.

Where the how lives

The mechanics of setting these up are already in this series. Day 12 shows how to stack managed agents so each job has its own skill. Day 21 shows how to put them on a schedule so they run before you sit down.

This page is the why. Those two are the how. Design the workflow once here, then wire it up there.

What this adds up to

You stop being the system every task passes through, and become the person who designed it. You step in to decide, not to do.

That is the whole point of this series. Every prompt I share is one more job you take off your own plate for good, until your capacity is set by your judgement, not by how many tasks you personally have time to touch.

Talk it through

Not sure which job to hand off first?

Message me directly if you want to talk through which workflow to design first and how to describe it so it runs without you. If property is part of your plan, I can also walk you through the opportunities I am tracking right now.

Message me on WhatsApp
26
Where this builds from

Day 26 · Turn Claude into your property analyst in Excel.

Read Day 26
FourthspaceOS

An operating system for property investors.

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.

Join the waitlist

Founding pricing locks in for waitlist members.

One email a day for 30 days. No spam. Unsubscribe whenever.

Instagram

One new prompt every weekday.

The reframe you just read is Day 29 of 30. The full series, daily builds, and live property workflows are on Instagram. Follow for the rest of the run.

If you found this page through the reel, the feed is where the next one lands. One prompt, one workflow, one job off your plate at a time, all built for property investors.

Follow the build

@fourthspaceOS · new prompt every weekday

Follow on Instagram ↗

Free. Daily. Unfollow whenever.