What Should Go on Your Roadmap First in Real Estate & Property? Start With Jobs to Be Done
Direct answer: Put first on the roadmap whatever helps your customer make measurable progress on the job they're actually hiring your product or building for — not the feature your loudest stakeholder wants. In real estate and property, that means mapping the specific "jobs" a tenant, buyer, broker, or asset owner is trying to get done (find, transact, occupy, maintain, or dispose of space), scoring which underserved job matters most, and sequencing the roadmap so your next release removes the biggest source of friction in that job. Jobs to Be Done (JTBD) is the framework that forces this prioritization by focusing on outcomes, not personas or feature lists.
Why Jobs to Be Done fits real estate roadmapping
Real estate teams — whether you run a proptech platform, a brokerage, a property-management operation, or a REIT with a digital tenant experience — tend to build roadmaps around whoever asks loudest: a large tenant, a board member, or a competitor's shiny feature. JTBD reframes the question. People don't want a listings portal or a maintenance app; they hire those tools to make progress on a job.
A leasing tenant's job might be: "When my current lease is ending, help me secure suitable space quickly enough that my operations never pause, without overcommitting on term." A property manager's job might be: "When a unit turns over, help me re-lease it at market rent with minimal vacancy days." An asset owner's job: "When capital-allocation season comes, help me decide which assets to hold, improve, or sell with confidence."
Notice these are stable over time. Technology changes; the underlying job of "occupy space that fits my business without pausing operations" has existed for a century. That stability is exactly why JTBD produces a durable roadmap rather than a feature backlog that chases trends.
A concrete JTBD walkthrough for property teams
Here's how to run it. It doesn't require software to start — a whiteboard and honest customer conversations get you most of the way.
1. Name the core functional job. Write it as "When [situation], help me [desired progress], so I can [outcome]." Do this for each customer type you serve — tenant, broker, owner, maintenance vendor. Resist writing features here.
2. Break the job into steps. Every job has a process: define → locate → decide → transact → set up → monitor → conclude. For a leasing job that's roughly: decide requirements → search options → tour/evaluate → negotiate → sign → move in → occupy → renew or exit. Map every step, because friction hides in the transitions.
3. Capture the outcomes customers use to measure success. These are the metrics they care about: days to signed lease, dollars per square foot vs. budget, vacancy days, hours spent on paperwork, certainty the space fits. Phrase each as "minimize / maximize the [metric] of [step]."
4. Score each outcome on importance and satisfaction. Interview real customers. Which outcomes are highly important but poorly served today? That gap — high importance, low satisfaction — is your underserved job. That is what goes first on the roadmap. An outcome that's important but already well-served is table stakes; don't over-invest there.
5. Sequence releases against the biggest gap. If tenants rate "certainty the space fits my operations before I commit" as critical but poorly served, your first roadmap item might be better spatial data, virtual walkthroughs, or fit-scoring — not a slicker payment flow that solves an already-satisfied step.
What "good" looks like: a roadmap where every top item traces directly to a named, underserved outcome for a specific job, with a before/after metric you can defend to a board. If you can't name the job an initiative serves, it doesn't earn a top slot.
Where Percision helps — and where a spreadsheet or consultant is enough
The interviewing and job-mapping work is human work. No tool replaces sitting with tenants and brokers to hear the job in their words. Do that first.
Where it gets hard is turning a wall of outcome scores into a prioritized, board-ready roadmap with the financial case attached — because in real estate every roadmap decision competes with capital that could go to acquisitions, capex, or dividends. That's where a structured analysis platform earns its place.
Percision (disclosure: this article is published by Percision) is an AI-powered strategic intelligence platform that runs your business context through structured reasoning steps across multiple frameworks — Jobs to Be Done among them — and produces board-ready recommendations, scenario analyses, and Excel-exportable financial models in minutes rather than weeks. For a property team, that means feeding in your job map and outcome scores and getting back a sequenced roadmap tied to a financial impact estimate and a presentation deck you can take to an investment committee. It's positioned as a co-pilot, not an autopilot: your leadership team stays in control of the calls.
When you don't need it: if you have one clear underserved job and a small roadmap, a spreadsheet with importance/satisfaction scores is genuinely enough. If your challenge is qualitative discovery — you don't yet know the jobs — you need customer interviews, and possibly a research consultant, more than any analysis engine. Broadly consistent with what BCG and Harvard Business School researchers have reported about generative AI raising knowledge-worker output on well-structured tasks, tools like this help most when the thinking is already scoped and you need speed and rigor on the synthesis — not when the fundamental discovery hasn't happened yet.
Use JTBD to find the job. Use judgment to validate it. Use a platform when you need to convert it into a defensible, financed roadmap fast.
What this looks like when the analysis is actually run
The job to be done here is set by a date: $180M of office debt matures in eighteen months and the lenders will not extend on the same terms.
The subject is Brentmoor Property Group, a sample company profile we use for testing rather than a customer: an owner-operator of 4.1M sq ft of suburban office and light industrial, $137M revenue.
Excerpt from a real Percision run · Pricing Strategy (T2) · sample company profile
First, because it has a clock. Refinance the 24 light-industrial buildings at 55% LTV and 6.8%, generating $381M against the existing $341M allocated industrial debt slice — nine months from term sheet to closing: 60-day lender underwriting, 90-day documentation, 30-day closing.
Why this order. No industrial assets are sold; the pension-fund LP consent gate is not triggered because the transaction is a refinancing, not a sale. The 210-person platform remains intact.
Second, the disposal. A self-mandated sale of the seven-asset $180M office pool at a 9.4% exit cap for $202–210M gross, yielding $118–126M net after the $78M refinancing gap and $4–6M of transaction costs — over a nine-month execution window.
Third, the platform. Platform G&A from 8.0% to 5.5% of revenue within 18 months — $3.4M a year, capitalised at 12× for $40.8M — via a 44-FTE office leasing team reduced by 70%.
The gates. No life-company term sheet at 6.8% and 55% LTV by Month 4; industrial occupancy below 93% for two consecutive quarters; or no indication of interest at a 9.0% cap or better by Month 6.
| Phase | Gate metric | Target | Deadline |
|---|---|---|---|
| Foundation (0-3 months) | Term sheets received | At least two term sheets at ≤6.8% rate and 55% LTV | Month 3 |
| Traction (3-6 months) | Commitment letter | Binding commitment letter at agreed terms | Month 6 |
| Scale (6-9 months) | Closing achieved | Funds wired and $19M cash in treasury | Month 9 |
Both plans are timed against the same eighteen-month maturity and both take nine months to close, which leaves almost no slack. That is the real jobs-to-be-done finding: the sequencing is dictated by lender timetables, not by which option is most attractive.
The Month 4 term-sheet gate is the one that matters. If no life company will lend at 6.8% and 55% LTV, the refinancing route is closed and the disposal becomes the only path — with five months left to run a process that needs nine. Knowing that at Month 4 rather than Month 10 is the entire value of writing the gate down.
Read a complete Percision report — every page, no email required.
FAQ
Q: How is JTBD different from just building a customer-persona roadmap? Personas describe who; jobs describe what progress they're trying to make. A roadmap built on jobs survives changing demographics because the underlying job is stable — people will always need to occupy, transact, and manage property.
Q: What's the single first item JTBD tells us to build? The initiative that improves an outcome customers rate as highly important but poorly served today. That importance-minus-satisfaction gap is the prioritization signal — everything else waits.
Q: Do we need software to run Jobs to Be Done? No. Interviews, a job map, and an outcome-scoring spreadsheet run the whole method. Software helps when you need to synthesize results into a sequenced, financially-backed roadmap quickly — see how Percision structures that analysis.