From lead to paid on one home inspection board

“Lead to paid” sounds like a simple funnel until an inspection company tries to trace a job. A buyer calls from an agent referral. Someone writes the address in a notebook, checks a calendar, emails an agreement, creates a payment link, sends a text, and assigns an inspector. After the visit, photos live on a phone, findings live in a field app, the report is assembled in another place, and the invoice is tracked in a spreadsheet. Every handoff creates a chance for a stale address, a missed agreement, a duplicate job, or a report that is ready but not delivered.

Inspecta Home 360 home inspection software gives that work one inspection-focused board. Inspecta Home is software, not an inspection company. It does not speak for the inspector, certify a condition, or decide that a payment cleared. It gives the team a canonical job record and visible states so the right person can act at the right moment. The board is valuable because it connects the lifecycle, not because it adds another colored column.

The card begins with a real relationship

Create the lead with source, contact details, requested service, property address, preferred timing, and the person who made the introduction. Convert it into a client, property, and inspection without retyping the facts. If an agent referred the client, preserve that relationship. If the property already has an earlier inspection, surface the history without merging two jobs by accident. The office should be able to see what is new, what is waiting for a reply, and what has a scheduled appointment.

A useful card answers five questions immediately: who is the client, which property is involved, what service was sold, when is the visit, and what must happen next? Everything else can open from there. A connected pipeline should show the appointment without a search.

The projects and pipeline guide explains the board states and handoffs. Keep the states limited and meaningful: new, contacted, proposal or agreement pending, scheduled, in progress, report review, delivered, payment pending, paid, and follow-up. Do not create a new status for every exception. Record the exception in the job timeline and keep the main state readable.

Scheduling should protect the promise

When the client accepts, the board should carry service duration, travel details, inspector availability, property time zone, and organization hours into scheduling. A four-point appointment and a full home inspection do not consume the same field time. A reinspection may need the prior report and a narrow scope. A schedule that ignores those differences will make the pipeline look full while making the team late.

Send the appointment details and agreement from the record. Keep the selected template and service price attached. If the client moves the appointment, record who made the change and notify the people who need to know. A retry should update the existing inspection rather than create a second card.

Payment and agreement gates should be visible. The office can decide whether an agreement must be signed before the inspection, whether an invoice is due before delivery, and whether a report hold is appropriate. Those rules belong in the workflow and permissions, not in a hidden personal spreadsheet.

The field step must stay fast

A business board is only useful if the inspector can complete the work without fighting it. The field writer should open the correct inspection and template, show a clear next component, support large touch targets, attach photos to findings, and expose save or sync state. Voice input reduces typing. Offline queues protect work when the property has poor service. A blocked attic or inaccessible electrical panel should be recorded as a limitation, not silently skipped.

Findings remain first-class records. Store the inspection, section, system, component, location, condition, severity, narrative, recommendation, media, author, and timestamps. That structure lets the report summarize serious findings, lets the office see whether a review is needed, and lets the client receive a coherent explanation. A single paragraph in a general notes field cannot carry that operational load.

InterNACHI's Standards of Practice can help an inspection company discuss scope and coverage with its team. ASHI's resources provide another professional reference for practice and ethics. Neither reference is a substitute for your agreement, local requirements, training, or judgment. Use standards to shape the pack, then record what was actually observable at this property on this visit.

Review turns captured work into a deliverable

When the inspector finishes, move the job to report review rather than treating “field complete” as “client ready.” Run required-capture checks. Verify property details, inspector information, agreement status, finding severity, recommendations, selected photos, disclaimers, and addenda. The web report and PDF should come from the same structured report model. Preview on a phone and a desktop. Freeze the published version so a later template edit does not change history.

The report state should be explicit: draft, generating, review, published, held, delivered, or expired. If a render fails, show the failure and let the office retry. Do not leave the board saying delivered because an email request was accepted by a browser. Delivery and payment events should have their own audit trail with the operation, time, user, and relevant job identifier.

Messages should use the context

Clients ask predictable questions: What time will you arrive? Did you receive the agreement? When will the report be ready? How do I pay? The client messages guide shows how to answer from the job record. Templates can save typing, but a message should still name the correct property, service, appointment, and next action. Avoid copying a generic email and accidentally sending another client's address.

Keep the human in the loop for exceptions. If a client asks for a structural opinion that is outside the inspection scope, route it to the inspector. If a payment fails, show the invoice state and send a safe retry path without exposing card data. If the report is held, explain the condition without implying that the inspection itself is incomplete. Good communication protects trust when the workflow is waiting.

Payment closes the job without closing the record

An invoice should belong to the inspection and organization. Payment state should come from an authoritative processor webhook or an authorized office action. Record the event id so retries do not create duplicate receipts or double-count revenue. Never trust a client-provided “paid” field, store raw card numbers, or log payment credentials. Once paid, the card can move to follow-up while the report, agreement, invoice, and audit history remain accessible.

Inspecta Home 360 does not charge a percentage of the inspection fee. Solo is $119, Team is $169, and Scale is $229. Inspecta Copilot is included, extra seats are $25, and the trial lasts 7 days. There is no per-job fee and no payment cut. The firm keeps its pricing and payment relationship with the client. Predictable seat pricing makes the board easier to budget as lead volume becomes completed work.

Training works best with a full rehearsal. Take a sample referral from intake through schedule, agreement, inspection, report preview, invoice, payment event, and follow-up. Ask each role to complete the step they own. Look for duplicate data entry, unclear states, missing permissions, and places where the inspector would have to type too much with tools in hand. Fix the handoff, not just the label.

Copilot is an assistant, not a closer

Inspecta Copilot can draft a reply, summarize a confirmed set of findings, improve a narrative, or suggest a next-action reminder. It should label suggestions and preserve the person who accepted or changed them. It cannot approve a discount, promise a delivery time the team did not set, mark a payment settled, or transform an image guess into a confirmed finding. Review AI output before it reaches a client or a report.

The best automation is observable and recoverable. When the inspection reaches completed, a job may queue report generation, check agreement and payment conditions, publish, notify, and schedule follow-up. Each step should show success or failure and be safe to retry. A one-board workflow is not a silent chain. It is a shared record of work that people can understand.

Use the board to earn the next job

Follow-up belongs to the same lifecycle. Ask whether the client received the report, whether an agent needs controlled access, whether an invoice remains open, and when a review or referral request is appropriate. Measure the source of the lead, the value of the service, delivery speed, and repeat referral. Keep the relationship attached to the inspection so growth analysis is based on real business data rather than memory.

From lead to paid on one board means fewer copies, clearer ownership, and a more reliable inspection record. It does not mean software replaces the inspector or the office. It means the team can book, inspect, document, generate, deliver, get paid, and grow without leaving the platform to remember what happened.

Continue with home inspection business management for the broader operating model and growing referrals without a second app for the relationship loop after payment.