On October 1, 2026, Sharad Mehta and Tyler Scott hosted a webinar-style masterclass featuring guest John Figueiredo, a REsimpli user and former software developer who scaled a real estate investing operation from zero to a 15-person team in 14 months.

The call closed with John sharing his contact information and Sharad announcing that the recording would be distributed with chapters and a downloadable transcript.

John explained that most teams assign a lead to one person for the entire lifecycle, but top-performing operations worth $600,000 or more per month use a communal pile where no salesperson owns a lead until rapport is established through a set appointment or a made offer. This lets the entire team use the triple-line dialer to rip through the uncontacted pile each day, ensuring no lead goes untouched.
​

His team moved from 120 to 150 calls per day to over 250, an increase of 60 to 80 percent depending on the person. The offer rate jumped from the 40th percentile to the 70th in two weeks (00:09:03). At a 3 to 5 percent connection rate on outbound cold calls, John argued that volume is now the primary lever, especially with iOS call screening filtering out more inbound rings than ever.

John walked through his dashboard, built in Claude using REsimpli's Open API. It displays September's lead count, contracts signed, closes, and a week-over-week leaderboard showing which team members are converting the most. A ROAS leaderboard tracks marketing spend per employee against revenue generated, with the North Star metric being ROAS per team member.
​

Channel-specific breakdowns show lead-to-contract ratios for PPL, PPC, and SMS separately, with blended performance trending from 1-in-77 early on down to 1-in-15 to 1-in-20 as the team matured. Disposition metrics, active listings per month, days to list, and estimated versus actual closed revenue are all charted over time. John stressed that every operator's dashboard should look different because different businesses prioritize different metrics (00:33:49).

The command center connects to Slack through Claude's connector capability. When a team member does not contact a lead within the defined window, a Slack notification fires automatically. John's target is a five-minute SLA on the disposition side and sub-60-second speed to lead on the acquisition side.
​

Claude uses both the REsimpli API and browser scraping to gather the data it needs. If a data point is not available through the API, Claude opens a browser session, navigates to the REsimpli interface, and scrapes the relevant information from the page HTML (00:55:02). This hybrid approach allowed John to run the system for months before the Open API existed in its current form.

To demonstrate the workflow for non-technical users, John opened a fresh Claude session, pasted the REsimpli API documentation URL, and typed a plain-English prompt asking for speed-to-lead data by team member over the past two weeks. Claude read the documentation, identified the available endpoints, requested the API key, and then pulled the data and generated a visual dashboard in roughly 10 minutes (00:58:57).
​

Sharad emphasized that this approach does not require a developer background. Users who prefer not to build it themselves can hire someone on Upwork for $100 to $200 to get the initial setup done. John recommended the Claude Max plan at $100 to $200 per month rather than paying for API credits, which get expensive quickly (00:54:19).

A user asked whether Claude can edit information directly inside REsimpli. Sharad confirmed that the current API is read-only but that write endpoints are actively in development. Once live, the API will support changing lead status, adding leads to automations, creating tasks and appointments, updating custom fields, adding tags, and editing contact information. John noted that this will unlock use cases like automatically splitting a departing team member's leads across remaining staff in minutes instead of hours (00:57:31).

A separate question surfaced an appointment KPI issue: the business dashboard counts appointments by scheduled date rather than booked date, so a September-booked appointment scheduled for October appears under October. Sharad pointed to the existing appointments API endpoint as a workaround for pulling data by creation date instead.

Sharad announced that the team would email the recording to all users and begin adding chapter markers and transcripts to office hours and webinar recordings going forward, addressing feedback that long calls are difficult to navigate after the fact.
​
John dropped his email and phone number for anyone who wants to replicate his setup, and Sharad noted that John would return in about a month to show how his command center has evolved once the write-capable API endpoints go live.
​
The next office hours call was confirmed for Friday, October 2, at 1:00 PM Pacific on the standard Zoom link.