A useful monthly builder lead report connects verified sources to inquiry types, project fit, pipeline movement and next-action gaps. It separates raw contacts from buyer conversations and signed work, labels missing attribution and ends with operating decisions. You should be able to trace every summary line back to records in systems you own.
What should the monthly report help you decide?
Where the lead system needs attention. It can show that a plan page produces serious modification questions, that a job-site number has missed calls, that Parade records have no owners, or that a campaign attracts projects outside the working area. Those findings drive changes in content, routing, qualification, staffing and follow-up.
A dashboard of traffic and contact totals with no buyer condition underneath is not an operating report. You need to see which inquiries reached a lot discussion, a plan review, a preconstruction decision, a pause, a referral elsewhere or a documented nonfit outcome. The leads and CRM library explains the intake and pipeline records that make this review possible.
Which questions belong at the top of the report?
Plain ones. Which sources started plausible project conversations? Which active records have no next action? Where are source details missing? Which inquiries keep failing service-area, lot, plan or project-type fit? What changed in the operating environment: a Parade weekend, a new lot release, a finished project video, a paused community?
Answer those before any decorative chart. A principal should not need to decode a marketing vocabulary to see what needs a decision.
Which sections belong in the report?
Use a stable structure so changes show from one review to the next. Keep the definitions beside the measures. If the team changes what counts as a fit review or a meaningful conversation, note the change instead of quietly revising the past.
| Section | What it contains | Decision it supports |
|---|---|---|
| Source health | Known sources, missing source detail, broken tags, routing exceptions | Repair measurement paths |
| Inquiry mix | Buyer, agent, lot owner, warranty, vendor, employment and unrelated contacts | Separate demand from operational noise |
| Fit conditions | Service area, lot status, plan status, project type and stated timing | Improve qualification and content |
| Pipeline movement | Observable stage entries, pauses, handoffs and closed reasons | Find stalled work and unclear stages |
| Follow-up health | Records without owners, next actions or reviewed responses | Correct accountability gaps |
| Content signals | Repeated questions about plans, allowances, lots, selections and warranty | Prioritize useful pages and videos |
| Decisions | Named action, owner, evidence and review point | Turn reporting into operating work |
Do not merge unlike records. A vendor solicitation, a warranty call, a buyer-agent inquiry and a household holding a lot are not interchangeable leads. Use the controlled field design in builder CRM fields to keep the categories readable. Audit call-path exceptions with the phone lead tracking workflow.
How should the report be assembled and checked?
Build it from traceable records, then review exceptions before you interpret channel performance. If a source integration failed for part of the period, say so. If staff did not close outcomes, mark the gap instead of assuming those records were lost or unqualified.
- Freeze the review window. Use one date basis for inquiry creation, stage movement and outcomes, so the same record is not counted under shifting rules.
- Separate contact types. Pull warranty, vendor, employment, spam and unrelated records out of buyer inquiry views while keeping them for routing analysis.
- Audit source completeness. Inspect unknown, direct, phone, website, referral and event labels that lack usable detail, including broken UTM parameters.
- Review duplicate households. Merge or connect repeat forms, calls and event visits without erasing first source or later touches.
- Validate stage evidence. Confirm that movement reflects an observable condition, such as a scheduled fit review or requested plan-and-lot information.
- Read nonfit reasons. Look for service, site, project and timing patterns the website or the intake process could clarify.
- Write the decision page. Name each change, its owner, the affected system and the evidence to check next time.
Where can AI agents assist?
The Claude and Codex agents we run reconcile labels, flag missing fields, group repeated questions, draft record summaries and check whether report statements trace to source data. A person defines the measures, inspects the exceptions and approves every conclusion. No agent fills in unknown sources, infers buyer intent or turns correlation into a claim that one channel caused a contract.
How do you compare sources without false certainty?
Compare them against the same observable conditions and keep the context. A Parade visit, a past-buyer introduction, a plan-page form and a tracked call do not represent identical buyer behavior. Show the path you can verify and say where it ends.
Keep original discovery, later meaningful touches and the contact that triggered action separate when you know them. A buyer reads a cost guide, visits a finished house, gets a referral, then calls from a community page. The report can show those facts without handing all the credit to the final call. The Lead attribution stage sets these source rules in systems you own.
Avoid rankings built on small or incomplete sets. Describe the records instead: this source produced plan questions but few known lot owners; that event produced several fit reviews and incomplete follow-up; another page attracts warranty traffic and needs clearer routing. Attach representative record identifiers to each comparison so the team can open the underlying conversations.
What should happen in the monthly review meeting?
Keep it close to operations. Include the people who own intake, sales follow-up, website changes and the relevant project handoffs. Review exceptions first, then source patterns, then decisions. Give each broken form or routing exception an owner, a repair task and a check condition.
Read selected records, not only summaries. Open the note from a lot owner, the page tied to a plan question, the missed-call route and the stage history for a paused buyer. That catches category errors totals hide. It also surfaces content opportunities grounded in real questions about allowances, site work, selections, draws, punch lists and warranty.
For the full measurement framework across calls, forms, events and offline inquiries, use the builder lead tracking guide. Every finding ends as a repair, a test, a content assignment, a follow-up task or an explicit decision to leave the system alone.
Which records belong in the monthly report?
Should the report show website traffic?
Website traffic can give context in a monthly lead report. Keep visits separate from inquiries, qualified conversations, pipeline movement and signed work so demand is not overstated.
What should happen to records with an unknown source?
Keep unknown lead sources visible in the monthly report. Investigate recoverable context, record how it was verified and leave the source unknown when evidence is unavailable.
Should paused buyers count as lost?
A paused buyer stays distinct from a lost opportunity in lead reporting. Record the pause reason and the review trigger instead of treating a delayed lot search as nonfit.
Who should own the monthly report?
Assign one person to assemble and validate the monthly lead report. Intake, sales and system owners review the evidence and take responsibility for the resulting actions.