A useful AI assistant for contractors should turn current job information into a short list of decisions and reviewable actions. Start with four questions: what needs billing, what needs a follow-up, what's coming up on the schedule, and what changed on site?
This workflow is for an owner-operator or small crew managing quoted projects. It works as a checklist even without AI. With an assistant, the goal is less time collecting information and more clarity about what needs your attention.
Dave's team wrote this guide using product documentation checked November 1, 2026. The prompts are suggested tasks, and the business below is fictional. They aren't screenshots of tested outputs or a promise that every assistant supports every action.
Start with the records, then choose the assistant
| Where the information lives | Practical starting point | What must be in place |
|---|---|---|
| Projects, invoices, and schedules already in Dave | Ask Dave | Current records and permission to view or change them |
| A few spreadsheets and documents | ChatGPT Work | The right files, a clear reporting date, and defined calculations |
| Several apps you want an agent to work across | Grok Bot | Access to the relevant accounts and a demonstrated workflow |
| An ongoing responsibility that needs follow-up between conversations | ChatGPT Dots | Connected sources, a clear responsibility, and boundaries for actions |
| A mix of personal and business coordination | Meta Muse | The required services connected with appropriate permissions |
These are starting points, not an assertion that each product can only do that task. For a broader comparison and official product links, see AI for contractors.
If you already keep reliable records in another contractor app, try an assistant that can work with that setup before moving your business. If the same information is scattered across texts and spreadsheets, organizing it may deliver more value than adding another chat window.
A worked weekly review for a small outdoor contractor
Imagine you're reviewing three jobs on November 1, 2026. These simplified USD records exclude taxes. The “remaining” amounts below are balances, not profit.
| Job | Current record | What the owner needs to know |
|---|---|---|
| Maple patio | $7,400 estimate sent; not accepted | Follow up on the decision. It isn't booked work or money owed. |
| Cedar fence | $3,400 invoice; $1,000 paid; due October 30 | $2,400 remains due, two calendar days overdue at the review date. |
| Oak pergola | $5,200 invoice; $1,500 paid deposit applied; due November 10 | $3,700 remains due, but it isn't overdue on November 1. |
There's also a $450 unapproved change request for the pergola. It isn't included in the invoice, and the customer hasn't agreed to it.
The correct review should distinguish:
- $6,100 in remaining invoice balances: $2,400 plus $3,700.
- $2,400 overdue at the review date: only the fence balance.
- $7,400 awaiting estimate approval: potential work, not receivables.
- $450 awaiting change approval: a decision to resolve, not an amount to collect yet.
An assistant that adds all four numbers into “revenue to collect” has mixed different business states. It needs correcting before it helps you contact customers or plan spending.
1. Review unpaid invoices
In Ask Dave, start with a supported business question such as which invoices remain unpaid. Then inspect the invoice records before acting.
For a general assistant working from an export, provide the reporting date and specify the fields. A useful request is:
Using these invoice and payment records, prepare an unpaid-invoice review as of November 1, 2026. Show invoice reference, project, due date, remaining balance, and whether it is overdue. Separate invoices from unaccepted estimates and unapproved changes. If a payment or deposit application is unclear, flag it instead of guessing. Don't send messages or change records.
For the example, the fence belongs on the overdue list. The pergola belongs on the upcoming-balance list. Check that an applied deposit hasn't also been deducted as a second payment.
Choose a follow-up after checking correspondence and payment history. If an automatic reminder already covers the invoice, you may not need another message today. Our AI invoicing guide works through the draft and deposit checks in more detail.
2. Follow up on estimates without assuming approval
Open estimates can mean different things: waiting for the customer, waiting for your revised scope, or waiting for a supplier price. Ask for the next step rather than a vague “sales summary.”
Review these open estimate records and attached customer messages. For each project, show the latest estimate version, last known response, unresolved question, and a proposed next step. Mark any missing correspondence. Draft follow-up wording for my review without implying the customer has approved the job.
For the Maple patio, a useful draft might ask whether the customer wants to discuss the drainage allowance or material option. It shouldn't say that materials have been ordered or that an installation date is reserved unless the records support that.
Give an external assistant only the source material needed for the task. If it cannot see recent messages, its silence about them isn't evidence that no customer replied.
3. Check the next week's schedule
List upcoming work, then review crew assignments, supplier confirmations, and unresolved customer decisions. Keep a tentative date separate from a confirmed visit.
| Schedule question | Record to check | Useful action |
|---|---|---|
| Is the right crew assigned? | Saved project event | Correct the assignment if needed |
| Are materials confirmed? | Supplier confirmation | Follow up on an unconfirmed delivery |
| Did the customer agree to access? | Latest customer communication | Resolve access before promising the visit |
| Will reminders reach the right people? | Event notification settings | Check recipients and delivery options |
Dave can help prepare schedules through Ask Dave. Its scheduling guide also documents the regular event workflow, including project connection, team assignment, and notification settings. Open the saved event to confirm the time and recipients. A suggested appointment in chat isn't yet a saved calendar event.
Help prepare a two-hour site visit for the Maple patio next Tuesday morning. Confirm the calendar date and time zone, identify the exact project, and show me the proposed time and recipients before I accept the change.
The request still needs your real availability and the customer's agreement. It doesn't authorize the assistant to treat an unaccepted estimate as a booked construction project.
4. Turn field notes into specific next steps
Instead of “pergola update,” record: “Customer asked about a privacy screen on the west side. Price it separately. No approval yet. Existing delivery remains scheduled for Thursday.” The second note separates a request from an agreed change.
Dave's AI Note Taker turns spoken updates into project notes. AI Walkthrough combines narration and photos in the logbook; it captures photos and audio rather than a video. Availability depends on supported app versions and business access. Ask permission before recording other people.
Review names, dimensions, decisions, and tasks in the finished note. If something is uncertain, keep it uncertain. A transcription shouldn't turn “possibly add a screen” into “install screen.”
When an ongoing agent is the better addition
If your main problem is work across email, files, and several apps, a general agent may be a better fit than changing contractor software. Grok Bot documents persistent context and repeatable routines. Dots can take on continuing responsibilities and follow up between conversations. Muse can continue tasks in the background across permitted services.
A clear ongoing assignment might be: “Review the connected delivery folder every Friday. Flag changed dates affecting next week's jobs. Prepare a summary with links to the original confirmations. Ask before contacting suppliers or changing the schedule.”
That is a proposed workflow to test against the selected product's available connections. It isn't a verified integration with Dave. And this guide doesn't claim Ask Dave independently runs that cross-app monitoring routine; its documented role here is responding to business questions and helping with tasks inside Dave.
Keep the review short enough to use
Finish with three lists: ready for your approval, waiting on someone else, and needs missing information. Attach a project or document reference to every item. “Follow up on payment” is vague; “review invoice F-17's $2,400 balance and last reminder before contacting the fence customer” is actionable.
Judge the assistant by the full review. Did it preserve the distinction between quoted, approved, invoiced, and paid? Did you spend less time gathering records after correcting its output? Can you find the saved changes afterward?
If the assistant struggles, narrow the task to one project or one invoice report. You can build a useful habit without delegating the whole office at once.
Common questions
Can Dave answer questions about unpaid invoices?
Yes. That is a documented example in the Ask Dave guide. Review the underlying invoice and payment history before contacting the customer, especially when partial payments or deposits are involved.
Does an AI assistant replace bookkeeping software?
An admin summary isn't a general ledger, tax return, or bank reconciliation. Keep those responsibilities in your accounting workflow. See our bookkeeping guide for small construction businesses for how job admin and bookkeeping fit together.
Should I use more than one assistant?
Only if each has a clear job. You might use Dave for project records and an external agent for supplier research. Avoid giving two tools overlapping instructions to send reminders or edit the same schedule, then having to reconcile their actions.