This quarter
Q3 2026 to date. One figure at a time — each opens the page it came from.
Outreach attemptsConfirmed conversations · This quarter · 0–100%
A confirmed conversation is a tour, a logged call, a two-way email exchange, a deal discussion, or a BOV/custom deliverable you sent. Outreach attempts that did not reach anyone are not counted here — they are tracked separately below.
This week
What is on the calendar this week, yours and the team’s. Open an entry to move it or mark it done; add to any day.
Team pipeline
Live work only. Colour marks the stage group. Open any deal to change its stage, next step and owner.
Relationships
Clients tagged as high-value targets, the outreach and meetings on this week’s calendar, and who the call list puts first.
LeClaw suggests
Built from who has gone quiet, what they own, and what is actually happening in the market this month.
Cadence gaps from your own outreach log, ownership within a radius using the coordinates already in the database, and what owners have told you in their own words. LeClaw proposes; nothing is booked, invited or sent without you doing it.
From the team
The intel poll comes back here. Reply in the thread or write straight into the Intel Bank.
Logging an attempt records the try. It becomes a confirmed conversation only when someone actually responds — and a reply that arrives next week stays credited to the week you made the attempt.
Unified schedule
Everything with a date on it — outreach, deliverables, meetings and deadlines. Scheduling something here does not send, publish or complete it.
The schedule underneath still tracks outreach sequences, client workflows, analyst actions, knowledge questions, document requests and the rest separately. On screen they are grouped into the five types above, because that is the distinction that changes what you do next.
Market intelligence
Only what you approved in News Review appears here. Save any story as a PDF to send a client.
FOCUS holds different rights on different sources. Where the licence allows it you get the full story. Where it does not, you get a FOCUS briefing built from your own written take plus the headline, publisher and a link — which is usually the more useful thing to send anyway. Nothing is sent for you; the PDF downloads to your machine.
Q3 2026
Every owner holding property in a market we cover, and whether we have actually had a conversation with them this quarter.
Under 5 is below minimum, 5–9 minimum, 10–19 target, 20+ a great week. Attempts count when made; a reply next week stays credited to this one.
Everything due from your cadences, grouped by what kind of touch it is. Work down a column; each one advances the client when you log it.
What happened
Coverage by market
A market is covered when an owner there has had a two-way conversation this quarter. Attempts do not count. Click a market to work it, or the arrow to see its submarkets.
Counting…
Market
Real coordinates, no basemap. Open a market to draw its own properties. A basemap still needs a tile-provider decision.
Ranked by importance
Ranked on relationship strength, units owned and transaction status together. Open any client for their contacts, properties and full history.
| Pick | Client | Relationship | Units & properties | Brokers | Status | Primary contact | Last conversation | Follow-up |
|---|
Game plan
Pick who to reach and how. FOCUS drafts the plan and schedules it; you approve every send.
The gap right now
You asked for a property to tag itself warm when an active owner reaches roughly two years before loan maturity. loans.maturity_date already exists per property, so the rule is buildable. What it must not do is overwrite a temperature you set by hand — if you have marked something cold after talking to the owner, a date should not silently argue with you. Proposed: the rule suggests the change and flags it for confirmation, and only applies itself where no one has set a value.
Repeatable plans
A cadence is a sequence of touches on a schedule. Put clients on one and the work turns up in Today’s outreach on the right days, by itself.
Running now
Every client currently enrolled, which step they are on and when their next touch is due.
Cadence
Two steps on the same day are a multi-touch: the second is due immediately after the first. A reply at any step takes the client off the cadence and flags them for you.
The one place it all lands
Every attempt, reply and conversation, wherever it was logged from — a task here, the button in the top bar, a deal page, a PDF you sent, the inbox scan. Coverage percentages are computed from this and nothing else.
Shared across the team
Every live deal in one grid. Edit a cell the way you would in Smartsheet; open a deal for the work behind it.
Client
Being built, sent and reviewed
Offering memorandums, BOVs, marketing materials, eblasts, scheduled reports and custom work — one list, same grid as the pipeline.
Client
Step
Everything FOCUS holds, in one place
Find any dataset, filter it, see it on a map, and open any row to see where its numbers came from.
Reading…
Data Library · intake
Add a report, a subscription email or notes from a call. FOCUS proposes the facts in it; you accept, edit or dismiss each one. Accepted facts join the Data Library with their source.
A recap you dictated after a call, a Zoom or Teams transcript, or an email thread. The full text stays private to you; only the facts you accept are shared, and they reach clients unattributed unless the person agreed to be named.
Reading…
Pick a document to review its facts.
Each source keeps its own rules. CoStar and Nick’s Airtable records are approved for any use (DEC-552); other outside sources go to clients cited, in our own words and tables (DEC-549).
Reading…
Collectors that read public feeds on a schedule. Each moves into FOCUS on its own: first its Claude version delivers here, then FOCUS runs it alongside and the two are compared, then the Claude version is switched off. FOCUS reads feeds and official meeting APIs only (Legistar, CivicClerk), follows each site’s robots.txt, never logs in or pays, and keeps a link and a short snippet, not the full text. With Read for facts on, each new item is read for facts into the review queue above. It runs only while this computer is on.
Reading…
Data Library · the foundations
What each dataset holds today, how sure we are of it, who may see it and where it came from. Every figure is counted from the records.
Counting…
Counting the records…
Contacts work for clients. Clients own properties. Search once and follow the links.
Data health
Counted from the database when the page opens. A card opens the records behind it.
Counting…
Review queue
Scored, explained, and never merged for you. Work top-down — the confident ones go fast.
Matching finds candidates; it does not know your business. “Atlantic Properties”, “Atlantic Realty Development Corp.” and “Atlantic Management” look identical to an algorithm and are probably three different companies. Current practice is confidence-scored triage with the reasoning shown, high-confidence pairs cleared in bulk, and genuine edge cases left to a person. Merging is reversible here and the losing record is retained, never deleted.
Client
What everyone else is doing
Most of this is hearsay, so every line says where it came from and how old it is.
Who is winning what
Counted from what we hold. It is an incomplete picture by definition — we only know what somebody told us.
Every property we hold, on a map and in a table, with what we know that a data subscription does not: who owns it, where the relationship stands, when its debt matures and what we have already done on it. Opening a property opens the same record the Database opens.
Admin · learned from your corrections
FOCUS keeps the corrections you make to what it writes and lays out, turns them into rules in plain words, and follows the ones you approve. Nothing is learned without you seeing it.
Reading…
Write the way you already write. FOCUS reads it and offers what it touches and what it implies.
Type [[ to link a client, property, contact or another page.
Start a line with todo, follow up, call, email,
eblast or intel and FOCUS offers to make it real. Nothing is created
until you say so.
Three things go out under your name. Each has its own workspace.
Built from today’s records · reply-all to the team
Five sections in a fixed order. Each one links through to the page it came from.
Sends from the Multifamily FOCUS account as a reply-all thread, so the team sees each other’s intel coming back. Sending is yours alone and the mail connection is not built yet — this composes the brief, it does not send it.
This week · ships Thursday
Write through the week. Thursday it becomes the newsletter.
This month’s issue
Pick what goes in. Everything here already exists somewhere else in FOCUS.
Where a suggestion becomes a plan, and stays on the partners’ radar until it is actually in the calendar.
This quarter
What is left, what is already committed, and whether the things you are proposing fit inside it.
The team’s ideas
Every networking idea the team has added. Each one reminds the partners on it until it is scheduled.
A suggestion with nobody on it and no date is just a nice thought. Anything sitting in Suggested or Planning raises a reminder to the partners you pick, on the cadence you set, until its status reaches Scheduled — at which point the reminders stop on their own.
Idea
Everything your sources pulled in overnight. Skim it, publish what is relevant to the business, hide the rest.
Overnight
Published items appear in the team News Feed. Nothing here goes to a client — that happens when you send one as a PDF.
ATLAS ran a three-rung ladder — Candidate, Verified, Source of Truth. In practice you used the first and last. This is to look at and published, plus hide for the noise. If the middle rung earned its keep, say so and it comes back.
A new skill
Talk it through with LeClaw, decide what it may touch, then write the files.
An example. This step is shown filled in for one skill, a loan maturity scan, so you can see what it produces. Saving and publishing a skill from this page is not built yet; skills are published through the skill registry.
An example. This step is shown filled in for one skill, a loan maturity scan, so you can see what it produces. Saving and publishing a skill from this page is not built yet; skills are published through the skill registry.
skills/loan-maturity-scan/SKILL.md
name and description only. The description is what decides whether this skill gets picked, so it names the job, the scope and what comes back.An example. This step is shown filled in for one skill, a loan maturity scan, so you can see what it produces. Saving and publishing a skill from this page is not built yet; skills are published through the skill registry.
It resolved the scope, found the owners, filtered correctly and reported the gap honestly instead of returning an empty list. That is the right behaviour. It will produce a real call list the moment loan maturity dates are populated.
A draft runs only for you. Publishing to the brokerage makes it available in the Skill Bank inside deliverables, where its output can be added to a client document.