Use cases / General Contracting / Dispatch & scheduling
Weekly client project updates
Clients call and text constantly about progress.
The business case
This one is mainly a time-saved case, so we don't claim revenue. Assumptions (illustrative): 10 active projects (owner time per weekly update), about 20 min saved each, staff time valued at $75/h, running cost $150/mo, setup $1,800.
| Case | Hours saved / mo | Value of time − running cost |
|---|---|---|
| Conservative | 7.2 h | $391 |
| Expected | 14.4 h | $932 |
| Optimistic | 21.6 h | $1,474 |
Time saved only matters if it gets used on billable work. Track the before and after.
Requirements & gating
- JobTread: has an Open API and webhooks. verified
- CompanyCam: webhooks API with signed payloads. verified
Check what the app already does first:
- No direct native equivalent known. Still ask the owner what they already pay for.
Build steps
- Pull the week's daily logs from JobTread (API) and photos from CompanyCam (webhooks).
- Filter out internal notes and sub pricing before anything reaches the LLM.
- The LLM drafts the update: done, next, decisions needed. The owner approves it Friday and it goes out by email.
Test cases before go-live
- An internal note marked private never appears in the update.
- A week with no photos: the update is text only.
Tool names are examples, not endorsements. Check current features, plan tiers, and pricing before quoting a client.
Sample prompt
From this week's daily logs and photo captions, write a short client update covering what got done, what's next, and any decisions needed from the client. Use plain English.
Pitch it to the owner
"Clients get a Friday update with photos, and you get fewer 'how's it going' calls."
Lead with the outcome, not with "AI," and show the business case using their own numbers.
What can go wrong
- Leaking internal information. Filter the inputs first.
- Texting consent: Under the TCPA, automated texts generally need prior express consent, and marketing texts need prior express written consent. Honor STOP right away and keep consent records.
- Twilio/10DLC (2026): new A2P 10DLC campaigns must include public privacy policy and terms URLs (required since June 30, 2026), a verifiable opt-in, and opt-out language. Third-party lead generation and affiliate marketing are forbidden use cases. verified
- Reactivation defaults to email. Texting past customers is marketing. Use SMS only where written consent is documented.
- Call-recording consent: some states, including California, require all parties to consent (this list is not exhaustive). The safe default is to disclose recording and the automated assistant at the start of every call.
- AI voices: the FCC's February 2024 declaratory ruling (FCC-24-17) treats AI-generated voices as 'artificial voice' under the TCPA, so outbound AI calls generally need prior express consent. Further AI disclosure rules were only proposed in 2024. Keep builds inbound unless counsel approves. verified
- Failure modes: hallucinated details, missed escalations, and integrations that break silently. Add a human fallback, daily error alerts, and a weekly transcript review.
Not legal advice. Texting, calling, and recording rules vary by country and state and change over time. Have the client confirm compliance with qualified counsel before launch.
Suggested price
$1,200–$3,000 setup + $100–$250/mo
Starting estimate only, not verified against market rates. Adjust for scope and support.