The deposit-tier read on a market — scorecards, comps, Go/No-Go and headline underwriting, to decide whether to pursue.
You are where the value is made. A developer is deciding whether to put millions of dollars of capital into the ground, and before they commit they need a firm, holistic understanding of the market — not a single number, but the whole picture: who lives and works here and whether they can afford the rent, how much supply is coming and how fast the market absorbs it, what a unit can actually command, and how all of that translates into the returns the deal has to earn. That understanding is the difference between a confident yes, a disciplined no, and an expensive mistake.
They can’t see that market the way you can. You are the one who gathers it, verifies it, and assembles it into something they can act on — every scorecard, rent range, comp, absorption figure and demographic in this study comes from the record you build. When you get it right, the client understands exactly what they are buying and what it will yield; when it’s thin or wrong, they are underwriting a decision on sand. That is the weight of this step, and it is where you create value: not by filling in fields, but by handing a capital decision-maker the market, whole and true. Your accuracy and clarity are the product the client is paying for.
Own the data and the fundamentals end to end — that is where you create value. The access and billing mechanics are handled around you; your job is to make the numbers true and the story clear.
The value you deliver doesn’t begin when a deposit lands — it begins long before, in the work you do continuously so that the moment a client engagement begins you already understand their market better than baseline. A fast desktop study is only credible if the ground under it is already current. This is a standing responsibility, not something started at kickoff.
As an analyst you are expected to:
Open the News Editor — from Publish News in your account menu, or the 📰 News Editor button in the Admin Console. Pick the stream (Platmetrix News and Industry Best Practices show in every client’s rail; Market & Industry shows in the main column, targeted by audience), write the headline, source, blurb and an optional link/image, and Publish. It appears on the client home immediately.
Market analysts publish. Editing and deleting articles are reserved for the CEO and COO (and administrators). You write the market thinking; the executives curate it.
When a client arrives, they should feel you already know their market — and that head start is only possible if the underlying data and your national perspective are already current. Proactive upkeep is what turns a fast study into a trusted one; it is a visible part of the value the client is buying.
The Desktop Study is the first tier of a Market Intelligence engagement — it unlocks once the client’s deposit is paid. It is the fast, decision-grade read on a market: enough to decide whether a site is worth pursuing before committing to the full study.
Sign in, open your project card, and choose Open Desktop Study. If the card shows Study In Preparation, it hasn't been published yet.
A quick, credible screen — pursue or pass — without the full underwriting depth.
When a client pays the deposit for a desktop study, the alert goes to the Director of Sales — not to you directly. The Director of Sales owns the client relationship and assigns the market to a market analyst. That assignment is your cue to build and publish.
A deposit is a sales signal as much as a production one. Routing the alert to the Director of Sales keeps ownership and the upsell path (Site Intelligence, Full Study) with the person who manages the client, who then assigns the build to you.
So you can see where your kickoff comes from, here is the full chain from quote to assignment:
Sales admin builds and prices the quote → a manager approves it → the client pays the deposit link in their portal → an admin confirms and raises the tier → the Director of Sales is notified and assigns you. Your part starts at that assignment.
When the Director of Sales assigns you a market, this lands in your inbox — your kickoff to start populating the desktop study.
Everything the client sees in the desktop study — the scorecards, the Go/No-Go read, the rent picture — is built from the market record you enter. This is where you create the value: a developer about to commit capital is trusting these figures to decide yes or no. Enter them well and the study earns its fee. Here is exactly where you go, what you enter, and how you publish it.
You populate everything in one screen — Edit Market Data — then Save. The study reads what you saved. This is the whole form, top to bottom:
Getting there: Admin Console → ✎ Edit Market Data (top-right of the console header) → the editor opens in a new tab, live.
Load your market at the top, work down through the sections, and Save at the bottom. Saving publishes to the study — no file to re-upload.
market-editor.html. If Supabase isn’t connected at all, the page drops to a labeled DEMO mode where changes are held locally and never saved.)dayton_oh — and click ↻ Load. An existing market fills in with its saved data; a brand-new market opens blank.26Q2) and As-of date, then Inventory, Under construction, Pipeline, 12-mo absorption, Vacancy, Asking rent, Sale price/unit, and Cap rate.The moment you Save, the client’s desktop study reflects your work. There is no separate publish and no re-upload — Save is publish. That’s the value of the pipeline: you keep a market current by entering good data, and the client always opens the latest.
Representative values for the dayton_oh 26Q2 snapshot, so you can see the shape and units of each field:
| Field | What it is | Dayton 26Q2 (representative) |
|---|---|---|
| Reporting period · As-of | Labels the dated snapshot | 26Q2 · 2026-06-30 |
| Inventory | Total multifamily units | ≈ 78,000 |
| Under construction · Pipeline | Building · planned | ≈ 1,900 · 3,400 |
| 12-mo absorption | Net units absorbed, trailing year | ≈ 1,200 |
| Vacancy · Asking rent | % vacant · $/mo | 6.2% · $1,150 |
| Price/unit · Cap rate | $K · prevailing cap | $118K · 6.6% |
Beyond the KPIs, every desktop study carries these five. Each one answers a question the client will ask:
| Section | The client’s question it answers |
|---|---|
| Suggested market absorption | “How fast will this market lease what gets built?” (e.g. Dayton ≈ 1,200/yr) |
| Projected rent ranges | “What can I charge?” — low–high by unit type |
| Demand calculation | “Where does that demand number come from?” — household growth × renter share × capture |
| Direct rent comps | “Who am I competing with, and at what rent?” |
| Demographics | “Who lives here and can they afford it?” |
Every Save appends a dated snapshot — the trend lines are built from your prior saves, so save once per reporting period when the numbers are final. And the figures above are representative: replace them with your verified sources (CoStar, county records, BLS) before you publish, because the client is making a real decision on them.
The desktop study a client opens is not a static page, and it is not something you rebuild from scratch each time. It is two pieces working together:
| Piece | What it is | Where it lives |
|---|---|---|
| The study tool | A single self-contained HTML file — one per market — holding the layout, charts and logic of the study. | Private Supabase storage (the protected-pages bucket), at the market’s study_path. |
| The market_data record | A JSON record holding the numbers and text: KPIs, demographics, submarkets, employers, and the fundamentals (suggested absorption, projected rent ranges, demand, direct rent comps). | The market_data table, keyed by Market ID. |
v=study.protected-pages.market_data record for that Market ID.Edit them in Edit Market Data and Save. That updates the market_data record, and the study shows the new figures on the next load. You never re-upload anything to change data.
Altering the layout, adding a new kind of section, or changing the charts means the study tool file itself is edited and re-uploaded to protected-pages. That is a platform/admin task and the only time a file is replaced.
One tool, many refreshes. The same tool serves every reporting period on that market, so you keep the study current by saving data — not by rebuilding or re-uploading. It is also why a new field you enter appears automatically once the tool has been set to read it.
If something you entered (say the new fundamentals) doesn’t show on a market’s study, that market’s tool hasn’t been updated to read that field yet. Your data is saved and safe — flag it to the platform admin to update the tool once, and it renders on every load after that.
Your edits are never client-facing the instant you save. Market data now moves through a review gate, so you can build and save your work freely, and only an approved version reaches the client.
market_drafts) — clients never see it, and you can return to it any time.You (analyst) save and submit drafts. The Director of Sales (or an admin) approves and publishes, or returns with a note. Editing rights and approval rights are enforced on the server — a draft cannot go live without a sales-manager sign-off.
The editor shows the current state: Draft → In review → Published · live (or Changes requested). Loading a market always opens your latest draft if one exists, otherwise the live record.
Submitting your draft emails the Director of Sales that it’s awaiting approval. If they return it you get an email with their notes; if they approve, it publishes live and you’re notified.
viewer.html?id=dayton_oh&v=study. Confirm the scorecards, comps, Go/No-Go radar, maps and headline underwriting all render.Ctrl/Cmd-P. Destination: Save as PDF. Paper: Letter, Portrait. Margins: Default. Scale: Fit to width. Background graphics: ON — essential, or the navy panels and green accents drop out.Market_Period_Type → Dayton_OH_26Q2_DesktopStudy.pdf.The PDF is a fixed snapshot; the live study stays interactive in the viewer. When a client wants something to circulate, deliver both.
The desktop study deliberately stops at the market. That boundary is the opportunity: the moment it flags a promising submarket, the client's next questions are site-level and underwriting-level — which is exactly Site Intelligence and the Full Study.
When a submarket scores well, the client asks “is this parcel buildable?” — topography, utilities, environmental, zoning. In your desktop-study narrative, name the open site-level questions explicitly (e.g. “Austin Landing infill — confirm sanitary capacity and floodplain”). Those bullets become the Site Intelligence scope and make the upsell self-evident.
When the client wants to underwrite for real, the Full Study adds the complete development proforma, IRR/DSCR, sources & uses, and sensitivity — everything the desktop's headline underwriting only gestures at.
The same Dayton market moves Desktop Study → Site Intelligence → Full Study without starting over. Your desktop record is the foundation for all three. See also: Site Intelligence and Market Intelligence — Full Study.
When you're ready to underwrite for real, pay in full and the same project unlocks the Full Study — deeper comps, full underwriting, sensitivity and the complete report. Your tier moves from Deposit paid — study to Paid in full; nothing to re-request.