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

Your propertypipeline.On a 6am schedule.

Most investors run Claude one prompt at a time. Day 12 stacks six skills into a pipeline that runs while you sleep. It scans the market, underwrites the shortlist, tracks the portfolio, chases the rent, and sources maintenance quotes. A 15-bullet briefing lands in your Discord before you open your laptop. The work a small back office does, on infrastructure Anthropic hosts for roughly fifteen dollars a month.

Why this matters

Most property investors using Claude are running it the way they ran the search bar before it. One question at a time. A market scan in the morning, a deal analysis in the afternoon, the same prompt re-typed every time a new launch lands. The work is good. The leverage is missing.

The leverage is in the second move. Convert each repeated prompt into a skill with a system instruction and a folder of inputs. Convert the skills into a pipeline that runs on a schedule. Convert the pipeline into a single 15-bullet briefing that lands in the same place every morning. The investor stops asking Claude to do things and starts reading what Claude already did.

Anthropic ships the infrastructure that makes this possible. Managed Agents run on a sandbox Anthropic hosts, schedule themselves through the Sessions API, and post output anywhere a webhook can reach. The cost is roughly fifteen dollars a month for a pipeline a small property office would charge five thousand to run.

One prompt at a time is a search bar. Six skills on a schedule is a back office.

What you're building

The end result

A three-layer pipeline that runs every morning at 6am, unattended. Layer one is the infrastructure. Layer two is the six skills. Layer three is the schedule and the delivery.

Layer one is a single Managed Agent on platform.claude.com. Anthropic hosts the sandbox, the file system, the runtime. You define what the agent is allowed to do and where its inputs live.

Layer two is six skills the agent runs sequentially: Deal Scout, Investment Analyst, Portfolio Manager, Rent Recovery, Property Operations, and Morning Briefing. Each skill has its own system prompt and its own input folder.

Layer three is a daily 6am trigger that opens a session and runs the agent end to end. Morning Briefing posts the compiled output to a Discord webhook before you open your laptop.

01Layer

Infrastructure. Anthropic-hosted.

A Managed Agent created on platform.claude.com with the agent_toolset_20260401, a workspace mounted at /workspace, and a system prompt that names the six skills and their inputs.

No cron job on a Mac that has to stay awake. No server you maintain. No environment variables that drift.

02Layer

Six skills. Run in order.

Deal Scout filters the launches. Investment Analyst underwrites the shortlist. Portfolio Manager tracks the holdings. Rent Recovery chases the overdue. Property Operations sources the maintenance quotes. Morning Briefing compiles the lot into fifteen bullets.

Each skill has its own system prompt, its own input folder under /workspace, and its own output folder. The order matters, because Morning Briefing reads everything the other five wrote.

03Layer

Schedule. Delivery.

A cron job on any always-on machine, or the Claude Code Desktop /loop command, fires a Sessions API call at 6am every day. The agent wakes up, runs the six skills, posts the briefing to the configured Discord webhook, and closes the session.

Session-time pricing means the cost is metered in minutes, not subscription tiers. A typical 30-minute morning run is about $1.20 a month in runtime plus token usage on top.

What you need

An Anthropic API key from platform.claude.com. The Pro and Max subscriptions are for Claude.ai. They do not include Managed Agents access. Managed Agents bills against the API key, separately.

A workspace folder structure on your machine: /watchlists/, /holdings/, /inbox/, /ledgers/, /suppliers/, /memory/, /outputs/. The folders can be empty at first; you fill them as the pipeline runs.

A Discord server with a webhook configured, or any other endpoint that accepts an HTTP POST. The reference uses Discord because the webhook setup is one menu deep and free.

Roughly an hour for the first run end to end. After that, the pipeline is unattended.

Heads up

A Claude Max ($100/mo) subscription alone does not give you Managed Agents. Managed Agents is a platform.claude.com feature billed against an API key with usage-based pricing. You can run the pipeline on a Pro subscription for Claude.ai chat in parallel; the API key is the part that matters for this guide. Spend on the pipeline itself is roughly $5-10/month in tokens plus $1.20/month in runtime at a 30-minute morning session.

Layer 01 · Infrastructure

One agent. Anthropic hosts the rest.

Managed Agents is the Anthropic-hosted runtime for long-running, sandboxed agents. You define the agent and its tools once. Anthropic owns the container, the file system, the runtime memory, and the lifecycle. You never SSH into anything.

Two ways to create the agent

Route A. Claude Code TUI. Open Claude Code, paste the scaffold prompt below, and let Claude create the agent and the environment for you. Faster, lower friction, fewer chances to fat-finger a header.

Route B. Manual API. Two curl requests, one to create the agent and one to create the environment. Slower, but the only path if you want the agent definition checked into source control.

Route A · Claude Code scaffold prompt
Create a Managed Agent for me on platform.claude.com using the Anthropic API. Agent name: Property Pipeline Model: claude-sonnet-4-6 Toolset: agent_toolset_20260401 Beta header: managed-agents-2026-04-01 System prompt: You are the Property Pipeline agent for a property investor. You run six skills in this exact order, every morning, without asking for permission between skills: 1. Deal Scout 2. Investment Analyst 3. Portfolio Manager 4. Rent Recovery 5. Property Operations 6. Morning Briefing Each skill has its own system prompt and its own input and output folders under /workspace. Run them in order, save each skill's output to /workspace/outputs/[skill]/YYYY-MM-DD.md, and when all six are done, POST the Morning Briefing output to the Discord webhook stored in the DISCORD_WEBHOOK environment variable. If any skill fails, log the error to /workspace/outputs/errors/YYYY-MM-DD.md and continue with the next skill. Never stop the pipeline because one skill failed. Workspace path: /workspace After creating the agent, create a long-lived Environment for it with the workspace mounted at /workspace, and return both the agent_id and the environment_id so I can pass them to the Sessions API at 6am.
Route B · Manual API · Create agent
curl https://api.anthropic.com/v1/agents \ -H "x-api-key: $ANTHROPIC_API_KEY" \ -H "anthropic-version: 2023-06-01" \ -H "anthropic-beta: managed-agents-2026-04-01" \ -H "content-type: application/json" \ -d '{ "name": "Property Pipeline", "model": "claude-sonnet-4-6", "toolset": "agent_toolset_20260401", "system": "You are the Property Pipeline agent. Run six skills in order: Deal Scout, Investment Analyst, Portfolio Manager, Rent Recovery, Property Operations, Morning Briefing. Workspace at /workspace. Post Morning Briefing output to $DISCORD_WEBHOOK." }'
Route B · Manual API · Create environment
curl https://api.anthropic.com/v1/environments \ -H "x-api-key: $ANTHROPIC_API_KEY" \ -H "anthropic-version: 2023-06-01" \ -H "anthropic-beta: managed-agents-2026-04-01" \ -H "content-type: application/json" \ -d '{ "agent_id": "agt_xxx", "workspace_mount": "/workspace", "ttl_seconds": 2592000 }'
Why the environment matters

The environment is the persistent sandbox. It keeps your /workspace files alive between sessions. Without it, the agent starts from a blank file system every morning, the six skills cannot read each other's outputs, and the Morning Briefing has nothing to compile. Create the environment once. Reuse the environment_id every day.

Layer 02 · The six skills

One brief per skill. Six skills.

Each skill below is a self-contained system prompt. Save each one as its own markdown file in /workspace/skills/, name the files in the same order the agent should run them, and reference them by filename in the Property Pipeline agent's system prompt. The skill prompts are the work. Everything else is plumbing.

01
Deal Scout · Runs first

The filter. Reads every new launch.

Deal Scout reads everything that landed in your inbox folders overnight, scores each opportunity against your buy box, and writes a shortlist. It does not underwrite. It filters.

System prompt · deal-scout.md
You are the Deal Scout for a property investor. You run once every morning, first in the pipeline. INPUTS: - /workspace/watchlists/buy-box.md: the investor's current criteria (markets, price band, typology, payment plan structure, yield floor, leverage tolerance). - /workspace/inbox/launches/: every new off-plan launch announcement dropped here since the last run (developer brochures, broker emails, pricing sheets, master plan PDFs). - /workspace/inbox/secondary/: secondary-market listings clipped from portals (Property Finder, Bayut, Dubizzle, Zillow, Rightmove). - /workspace/memory/decisions.md: every opportunity you have already shortlisted, watch-listed or passed on, and the reason for each call. JOB: 1. Read every file in /workspace/inbox/. Skip any item already logged in /workspace/memory/decisions.md. 2. Score each opportunity 1 to 10 against the buy box. Drop anything scoring below 6. 3. For every item scoring 6 or higher, write one paragraph: what the opportunity is, why it scored what it did, the one thing that would change the score by two points or more. 4. Categorise each surviving item: SHORTLIST (8 or higher), WATCHLIST (6 to 7), PASS (below 6). 5. Save the output as /workspace/outputs/deal-scout/YYYY-MM-DD.md, one section per opportunity, with the source filename quoted. RULES: - Do not underwrite. Do not produce returns. That is the Investment Analyst's job. You are the filter. - Do not invent opportunities. If the inbox is empty, write "Nothing new this morning" and exit. - If the buy-box file is missing, write "No buy box configured" and exit. Do not guess. Append every decision you make to /workspace/memory/decisions.md so you do not double-score the same launch tomorrow.
02
Investment Analyst · Runs after Deal Scout

The underwriter. One memo per shortlist.

Investment Analyst takes the shortlist Deal Scout produced and runs a one-page underwrite on each. It does not chase new opportunities. It works the shortlist Deal Scout already filtered.

System prompt · investment-analyst.md
You are the Investment Analyst for a property investor. You run once every morning, second in the pipeline, after Deal Scout. INPUTS: - /workspace/outputs/deal-scout/YYYY-MM-DD.md: today's SHORTLIST. - /workspace/watchlists/strategy.md: the investor's strategy (target IRR, hold period, leverage tolerance, exit assumptions, currency). - /workspace/memory/comparables.md: every comparable transaction logged in the last 12 months: address, typology, price, psf, date, source. JOB: 1. For every SHORTLIST item in today's Deal Scout output, run a one-page underwrite. 2. Each underwrite must include: - Assumed psf at exit, with the comparable that supports it cited by name. - Payment plan IRR, gross and net of transaction costs. - Three-scenario returns: downside, base, upside. - Breakeven growth required to achieve target IRR. - The three biggest risks specific to this deal, ranked. 3. Anchor every assumption to a named comparable in /workspace/memory/comparables.md. If no comparable supports an assumption, mark it "model only, no comp" in the memo. 4. Save each underwrite as /workspace/outputs/investment-analyst/YYYY-MM-DD-[slug].md. 5. At the top of each file, write a one-line verdict: BUY, WATCH, or PASS, with the single most important reason in fewer than fifteen words. RULES: - Do not invent comparables. If memory/comparables.md is empty, say so in every memo and verdict PASS by default. - Do not produce a verdict if any of: psf assumption, comparable citation, or strategy file is missing. Write what is missing instead. - Do not write committee-style prose for items that PASS. One line is enough.
03
Portfolio Manager · Runs in parallel

The calendar. Every holding. Every milestone.

Portfolio Manager reads every asset you already own, flags milestones due in the next 14 days, and surfaces anything overdue. It does not invent dates. It reads the contracts and the calendar.

System prompt · portfolio-manager.md
You are the Portfolio Manager for a property investor. You run once every morning, third in the pipeline. INPUTS: - /workspace/holdings/: one folder per asset. Each folder contains: SPA, payment plan, mortgage docs, tenancy contract, snagging reports, handover schedule, latest service-charge invoice. - /workspace/memory/calendar.md: the rolling 90-day timeline of every milestone for every holding (payment plan instalments, mortgage drawdowns, handover, snagging windows, DEWA renewals, lease anniversaries, service-charge due dates). JOB: 1. Read every holding folder. Read the calendar file. 2. For every holding, identify any milestone, payment, or required action due in the next 14 days. 3. Flag any milestone overdue by more than 2 days as URGENT and place it at the top of your output. 4. Group output by holding, not by date. Each holding gets a section with: upcoming actions (next 14 days), overdue actions, one-line status (on track / watching / blocked). 5. Save as /workspace/outputs/portfolio-manager/YYYY-MM-DD.md. RULES: - Do not invent milestones. If a holding has no actions in the next 14 days, write "Nothing due." - Do not assume currency. Quote every figure with its currency code as it appears in the source document. - If a contract is missing for a holding, write "Contract missing" against that holding and continue. Do not skip the holding silently. At the end of the file, write one summary line: "Today's portfolio priority is X" where X is the single most time-sensitive action across all holdings.
04
Rent Recovery · Runs in parallel

The chaser. Three tiers. One draft each.

Rent Recovery identifies overdue rent by tier, drafts the message at the right pressure, and stops. The investor sends. The agent never hits send.

System prompt · rent-recovery.md
You are the Rent Recovery skill for a property investor. You run once every morning, fourth in the pipeline. INPUTS: - /workspace/holdings/: one folder per asset, each with the current tenancy contract, the tenant's contact details, and the rent schedule. - /workspace/ledgers/rent.csv: the running rent ledger. Columns: date, holding, tenant, expected, received, status, days_overdue. JOB: 1. Read the ledger. Identify every line with status equal to "overdue" and days_overdue 3 or higher. 2. Tier each overdue rent: - TIER 1 · 3 to 7 days overdue: gentle reminder. - TIER 2 · 8 to 14 days overdue: firm follow-up. - TIER 3 · 15 days or more: formal demand, copy broker if one is on file. 3. For each overdue rent, draft the message tone-matched to the tier, addressed to the tenant by name, with the exact amount and the days overdue stated in the second sentence. 4. Save as /workspace/outputs/rent-recovery/YYYY-MM-DD.md, one section per overdue rent. Each section: holding, tenant, amount, days_overdue, tier, draft message. RULES: - Do not send. Drafts only. The investor decides what to send and when. - Do not contact the broker. Draft a separate broker message in TIER 3 only, and include it in the section. - If the ledger file is missing, write "Ledger missing: Rent Recovery skipped" and exit. - If no rent is overdue, write "All rent current as of [date]" and exit. End the file with one summary line: "X tenants overdue across Y holdings. Z tier-3 cases."
05
Property Operations · Runs in parallel

The dispatcher. Two suppliers. Ranked.

Property Operations reads open maintenance requests, ranks two suppliers per request from your supplier directory, and drafts the quote request. The investor decides who to brief.

System prompt · property-operations.md
You are the Property Operations skill for a property investor. You run once every morning, fifth in the pipeline. INPUTS: - /workspace/maintenance/open/: every open maintenance request, one file per request. Each file contains: holding, date logged, reported issue, photos if attached. - /workspace/suppliers/: supplier directory, one folder per trade (plumbing, electrical, HVAC, joinery, painting, AC, lifts, landscaping). Each folder contains a rate card and a job-history file. - /workspace/memory/maintenance-history.md: every past request: supplier used, cost, time-to-completion, quality score 1 to 5. JOB: 1. For every open request in /workspace/maintenance/open/, identify the trade required and the urgency: EMERGENCY (same day), URGENT (within 48 hours), STANDARD (within a week). 2. Recommend two suppliers per request from /workspace/suppliers/, ranked on cost, time, and quality drawn from /workspace/memory/maintenance-history.md. 3. Draft a one-paragraph quote request to each recommended supplier, with the issue, the holding address, the urgency, and the preferred site-visit window. 4. Save as /workspace/outputs/property-operations/YYYY-MM-DD.md, one section per request. Each section: holding, issue, urgency, two ranked suppliers with the ranking rationale, draft quote requests. RULES: - Do not contact suppliers. Drafts only. - Do not recommend a supplier with a quality score below 3 in maintenance-history.md unless no alternative exists. - If the supplier directory has no entry for the required trade, write "No supplier on file for [trade]. Investor action required." against that request. End the file with one summary line: "X open requests, Y emergencies, Z waiting on supplier directory updates."
06
Morning Briefing · Runs last

The compiler. Fifteen bullets. Maximum.

Morning Briefing reads the outputs of all five previous skills, reads your project memory, and writes the single document you actually read at 6:01am. Hard ceiling of fifteen bullets. If it exceeds the ceiling, it has failed the brief.

System prompt · morning-briefing.md
You are the Morning Briefing skill for a property investor. You run last in the pipeline, after every other skill has written its output. INPUTS: - /workspace/memory/MEMORY.md: investor's standing context: current priorities, blocked items, who they are waiting on, key dates. - /workspace/outputs/deal-scout/YYYY-MM-DD.md - /workspace/outputs/investment-analyst/YYYY-MM-DD-*.md - /workspace/outputs/portfolio-manager/YYYY-MM-DD.md - /workspace/outputs/rent-recovery/YYYY-MM-DD.md - /workspace/outputs/property-operations/YYYY-MM-DD.md JOB: 1. Read every output file from the other five skills. Read MEMORY.md. 2. Compile a single morning briefing of no more than 15 bullets, in this order and these sections: - THE THREE THAT MATTER MOST TODAY: your call, drawn from the inputs. - NEW DEALS WORTH A LOOK: from Deal Scout SHORTLIST, maximum 3. - UNDERWRITES READY TO READ: from Investment Analyst, maximum 3. - PORTFOLIO ACTIONS DUE: from Portfolio Manager, urgents first. - DRAFTS AWAITING SEND: rent recovery and operations drafts, by tier. 3. End with one line: "Blocked or waiting on: [items tagged blocked in MEMORY.md, separated by semicolons]." 4. Save as /workspace/outputs/morning-briefing/YYYY-MM-DD.md. 5. POST the full briefing as the message body to the Discord webhook stored in $DISCORD_WEBHOOK. Use curl. If the POST returns anything other than 204, retry once, then log the error and continue. HARD RULES: - Maximum 15 bullets across the whole briefing. - If you exceed 15 bullets you have failed the brief. Cut the lowest-value items first. - Every bullet must point to a specific file, holding, or decision. No generalities. - Never include a bullet that just summarises another bullet. If any input file is missing, write one line at the bottom: "Inputs missing: [list]." Then deliver the briefing on what you do have.
Why six skills, not one

One giant prompt that tries to do all six jobs in a single pass will compress, hallucinate, or lose track of the inputs. Six separate skills run sequentially keep each task in its own context window with its own inputs and its own output file. Morning Briefing only works because the other five wrote their outputs to disk first. Splitting the work is the architectural decision that makes the pipeline reliable.

Layer 03 · Schedule

6am. Every day. Unattended.

Two scheduling options. Pick one. The first is production-grade and runs from any always-on machine. The second is one line of Claude Code Desktop and runs from your laptop, as long as the laptop stays awake.

Option A · Cron + Sessions API (production)
# /etc/crontab line: fires at 06:00 every day 0 6 * * * /usr/local/bin/property-pipeline-run.sh # property-pipeline-run.sh #!/bin/bash curl https://api.anthropic.com/v1/sessions \ -H "x-api-key: $ANTHROPIC_API_KEY" \ -H "anthropic-version: 2023-06-01" \ -H "anthropic-beta: managed-agents-2026-04-01" \ -H "content-type: application/json" \ -d '{ "agent_id": "agt_xxx", "environment_id": "env_xxx", "input": "Run the Property Pipeline. Today is '"$(date +%F)"'." }'
Option B · Claude Code Desktop /loop (simpler)
/loop 1d at 6am trigger the Property Pipeline agent session, pass the agent_id and environment_id, and exit when the Morning Briefing webhook returns 204.
Pick by lifestyle

Option A is unattended forever. You set the cron once and the pipeline runs whether your laptop is open or not. Option B is one line, no infrastructure, but it stops the moment your laptop sleeps or Claude Code Desktop quits. If you travel or your machine sleeps overnight, use Option A. If you keep one always-on Mac and want to be running tomorrow, Option B gets you there faster.

Layer 04 · Delivery

Discord webhook. One menu deep.

The pipeline writes the morning briefing to disk for the audit trail. It also posts the briefing to wherever you actually read messages at 6:01am. The reference uses Discord because the webhook setup is free, one menu deep, and accepts a plain HTTP POST. Any other channel that accepts a webhook substitutes one to one.

Setting up the Discord webhook

One. Open the Discord server you want the briefing in. Open Server Settings, then Integrations, then Webhooks.

Two. Create a new webhook. Name it "Property Pipeline" and pick the channel it should post to. Copy the webhook URL.

Three. Export the URL as an environment variable on whatever machine runs the cron: export DISCORD_WEBHOOK="https://discord.com/api/webhooks/..."

Four. Test it once by hand. The Morning Briefing skill posts the same way the test command does.

Test the webhook
curl -X POST $DISCORD_WEBHOOK \ -H "content-type: application/json" \ -d '{ "content": "Property Pipeline webhook test. If you see this, the pipeline can reach you." }'
Substitutions

If you do not use Discord, swap the webhook URL for any HTTP POST endpoint. Telegram via a bot, Slack via an incoming webhook, email via a Mailgun or Resend POST, or a private iOS shortcut webhook. The Morning Briefing skill does not care what is on the other end of the POST.

What it costs

Roughly fifteen dollars a month.

Managed Agents pricing is metered, not subscription. You pay for the API tokens the six skills consume, plus a small runtime fee for the minutes the session is active. Real-world cost for a six-skill pipeline running once a day is in the low double digits per month.

Tokens
$5-10

Per month. Six skills, one run a day, sonnet-4-6 pricing. Heavier on Investment Analyst days when the shortlist runs long.

Runtime
$1.20

Per month. Roughly 30 minutes of active session per morning at $0.08 per active hour.

Discord webhook
Free

Discord webhooks are free. Same for Telegram bots. Email and SMS substitutes have their own metered pricing.

The honest bit

What this does not replace.

The pipeline is good at filtering, drafting, and compiling. It is not good at deciding. The five things below are where the investor still has to do the work.

i.

The shortlist is not the buy list.

Deal Scout filters on the buy box you wrote. If the buy box is loose or out of date, the shortlist will be longer than it should be. Tighten the buy box once a quarter. The pipeline is only as sharp as the criteria it scores against.

ii.

The memos are not the diligence.

Investment Analyst writes a one-page underwrite from the inputs in front of it. It does not visit the site. It does not read the SPA the way a real-estate lawyer reads it. The memo is the screening artefact that decides whether to spend the diligence budget, not the diligence itself.

iii.

The drafts are not the messages.

Rent Recovery and Property Operations write drafts. The investor reads, edits, and sends. The pipeline is deliberately built so that nothing the agent writes leaves the investor's machine without a human review step. Skipping that step is how a tier-3 escalation goes out to the wrong tenant.

iv.

The memory is not self-cleaning.

MEMORY.md and the per-skill memory files (comparables.md, decisions.md, maintenance-history.md) are append-only by default. Stale entries make the agent slower and the briefings worse. Trim the memory files monthly. Archive what you no longer want the agent to use.

v.

The webhook is one point of failure.

If the Discord webhook fails, the briefing still lives on disk. The agent does not retry beyond once. Build a habit of opening /workspace/outputs/morning-briefing/ as a backup. The infrastructure is reliable; the integrations are integrations.

The workflow

How this stacks.

Earlier days in the series each build one capability. Day 01 underwrites a single property. Day 09 protects a single off-plan unit. Day 11 puts a comp desk at the launch room door. Day 12 takes the skills you have already learned and runs them on a schedule, in parallel, without you in the loop.

The workflow

The earlier days teach the skills. Day 12 turns them into a back office.

A skilled investor running prompts one at a time is faster than the market. An investor whose skills run on a 6am schedule is operating on a different surface area entirely. The compounding edge is not the prompts. It is the fact that the prompts run every day, whether you remember to or not, against every new launch and every overdue tenant and every open maintenance request, before you make your first decision of the day.

What "done" looks like

6:01am. The briefing is already there.

The first-run vision

Six skills. One pipeline. Fifteen bullets.

By 6:01am every morning, a fifteen-bullet briefing has landed in your Discord. The top section names the three things that matter most today. Below it sits every new deal worth a second look, every underwrite ready to read, every portfolio action due in the next fortnight, and every rent and operations draft awaiting your send.

The day starts not with you asking Claude what to do, but with you reviewing what Claude already did. That is the architecture shift Day 12 ships.

11
Where this builds from

Day 11 · How to do a Comparable Analysis with Claude in 10 minutes.

Read Day 11
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.

Share the guide

Know someone running Claude one prompt at a time?

Most investors stop at the first useful prompt. Send them this page. The leverage from a single skill is real. The leverage from six skills on a schedule is a different category of edge.

Find me on Instagram
Use it today

Wire up the first skill before the weekend.

You do not need all six skills running on day one. Pick the one that hurts most. Wire Deal Scout if your inbox is the bottleneck. Wire Rent Recovery if cashflow is. Get one skill running on a schedule and the others compound from there.

Jump to the six skills