A small builder can send AI-written weekly updates for as little as $20 a month: a paid chat assistant (ChatGPT Plus or Claude Pro) plus your phone's camera and email. Adding a photo app such as CompanyCam Core brings it to about $83, and a full portal like JobTread starts at $199. Your review time is the larger cost.
The assistant writes only from what you give it. Photos and site notes go in, a plain-English update comes out, and you read it before it is sent. Watch the cost per update rather than the subscription: with six homes and weekly updates, $83 a month is about $3 an update, and the 15 minutes you spend checking each one is worth more than that.
What each piece costs, and what it asks of your time
These are list prices from the vendors' own pages in October 2026, in dollars. Business plans for ChatGPT and Claude carry a two-seat minimum, so a one-person firm pays for two seats or uses an individual plan.
| Item | What it does for an update | Price | Your time |
|---|---|---|---|
| Chat assistant, free tier | Drafts from typed notes. Photo uploads are tightly capped | $0 | Typing the notes yourself |
| ChatGPT Plus or Claude Pro | Reads photos and keeps a Project holding your house style and each plot's history | $20 a month each; Claude Pro is $17 a month if billed annually ($200 a year) | About two hours once to set up the template |
| Google AI Pro | The same job inside Gemini | $19.99 a month list price | The same set-up |
| ChatGPT Business or Claude Team | Shared workspace for you and a site manager, no model training on your content by default | $20 a seat billed annually or $25 monthly, two seats minimum | Adding the second user |
| Phone camera and a shared album | Collects photos by plot | $0 if you already have storage | 10 minutes a home to choose photos |
| CompanyCam Core | A photo timeline per project and live job updates for clients | $63 a month billed annually, one user (two at most), extra users $29 | Getting the crew to use it |
| CompanyCam Crew | Adds custom client access and auto-generated reports | $129 a month billed annually, three users | As above |
| JobTread | Customer portal, daily logs and an AI summary of several daily logs for buyers | $199 a month with one internal user, then $20 for each extra; portal users are free; about 20 per cent off on annual billing | Onboarding time; no free trial, but a 30-day money-back guarantee on monthly plans |
| Voice-note transcription (optional) | Turns spoken site notes into text for the prompt | Otter Pro $8.33 a user a month annually, $16.99 monthly | Dictating after each visit |
Two of these entries have wrinkles worth knowing. CompanyCam's pricing page shows AI credits of 10 on Core, 100 on Crew and unlimited on Scale, while the FAQ on the same page says AI features are included in Crew, Scale and Enterprise. So if you buy Core for the AI, ask what you actually get. And JobTread's pricing page says every feature is included and you pay only by internal user, while its AI page names no price or usage limit, so confirm that the daily-log summaries are covered at your volume. The same pricing page says field crew who only upload photos, log daily notes or view schedules and tasks can be added free, which matters if your site manager's job in the system is exactly that. I could not read Buildertrend's pricing page, so I have not priced it.
Four set-ups priced for six homes and for twelve
Six homes under construction means about 26 weekly updates a month (six homes times 4.3 weeks); twelve homes means 52. The set-ups below add tools in the order that most builders find they need them.
| Set-up | Monthly cost | Per update at 26 a month | Per update at 52 a month |
|---|---|---|---|
| Assistant only ($20 plan), phone photos, your own email | $20 | $0.77 | $0.38 |
| Assistant plus CompanyCam Core | $83 | $3.19 | $1.60 |
| Assistant plus CompanyCam Crew | $149 | $5.73 | $2.87 |
| JobTread with three internal users | $239 | $9.19 | $4.60 |
The first row is the starting point. It works because the assistant does the writing and you already own the camera and the mailbox. The jump to $83 buys organisation: a photo timeline per plot, so the week's photos are already sorted when you sit down. The jump to the platform buys replacement: scheduling, daily logs, selections and a portal in one place, and it only makes sense if it retires other subscriptions. The JobTread pricing tutorial for a five-person builder costs that platform in more detail.
The photo app has a simple break-even. At $45 an hour of your own time, CompanyCam Core's $63 equals 84 minutes a month. Spread over 26 updates, the app must save about three minutes on each one (finding the week's photos, sorting them by plot, sending a link instead of attaching files) to pay for itself, and about a minute and a half at 52 updates. If your photos already arrive in a tidy shared album, it will not.
A free assistant is not a real option for photo updates. When checked, OpenAI's file-uploads FAQ gave free ChatGPT accounts three uploads a day, and its pricing page lists only 'limited messages with uploads' on Free. You can write text-only updates from typed notes for $0, which is a fair way to start, but photos are what buyers want to see.
The weekly routine: photos and notes in, a plain update out
This routine takes about 15 minutes a home once it is running, and the same five steps work whichever tools you buy.
- Friday morning, on site. The site manager takes 10 to 15 photos of progress and dictates a two-minute voice note: what was done, what was delayed, what is next, anything the buyer must decide.
- Choose 8 to 10 photos. Pick the ones that show progress, not every angle. Write the plot number and what each shows in the notes (photo 1: trusses craned, photo 2: roof frame complete).
- Upload to the plot's chat or Project. Keep one Project per plot and save each update you send into its files, so you can tell the assistant not to repeat last week's wording.
- Run the same prompt every week. The prompt holds your house style and your rules.
- Check, edit and send from your own email. Read it against the notes, delete anything you cannot support, and attach the chosen photos.
You write weekly build-progress updates to a home buyer for a small builder.
Write in plain English, warm and clear, no jargon, under 200 words.
Use ONLY the site notes and the photo list below. If something is not in them,
leave it out. Never give a completion date or promise a date unless it is in
the notes. After each sentence add the note line or photo number that supports
it in square brackets. End with any question the buyer must answer, and the
date we need it by. Do not mention other plots or other buyers.
Plot: 7. Week: 14.
Site notes: [paste notes]
Photos: [list: 1 trusses craned, 2 roof frame complete, ...]The input and draft below are illustrative. The numbered notes say: (1) trusses delivered Monday and craned Tuesday, roof frame complete by Wednesday lunchtime; (2) felt and battens started Thursday and the west side is done; (3) rain stopped work on Friday afternoon; (4) bricklayers finished the garage wall; (5) scaffold alteration booked for Monday; (6) windows delivered Tuesday next week; (7) the buyer must choose the kitchen island position by the 20th.
Hi [first name], here is your update for plot 7, week 14. The roof trusses arrived on Monday and were craned into place on Tuesday, and the roof frame was complete by Wednesday lunchtime [note 1, photos 1 and 2]. On Thursday the team started the felt and battens, and the west side is done [note 2, photo 3]. Rain stopped work on Friday afternoon [note 3], so the east side will be next week. The bricklayers finished the garage wall [note 4, photo 4]. Next week the scaffold is altered on Monday [note 5] and the windows are delivered on Tuesday [note 6], which keeps the roof on track to finish in two weeks. One question for you: where would you like the kitchen island? We need your answer by the 20th [note 7].
What you would fix: two clauses carry no source tag. 'So the east side will be next week' follows a tag for note 3, which says only that rain stopped work, so it assumes a plan nobody wrote down. 'Which keeps the roof on track to finish in two weeks' has no tag at all, and is a completion date the notes never gave. Delete both. The tags make the check take seconds, because an untagged claim is the one to question. Strip the tags before sending.
Before and after: the weekly message used to be 'Roof's on, windows next week, pics attached.' It is quick, and it leaves the buyer guessing what 'roof's on' means and why Friday was quiet. The drafted update names what was done and when, states the rain stop in one sentence, lists the two events next week and asks one question. The extra detail costs minutes only because the assistant drafts it, and the buyer reads it differently because it answers questions before they are asked.
A Friday shot list that gives the assistant something to write about
- One wide shot of the front of the plot, taken from the same spot every week, so the buyer sees the change.
- One wide shot of the rear.
- Each trade's finished work, close enough to show what it is: the roof frame, the brickwork, the first-floor deck, the plasterboard.
- A photo of anything delayed or at risk, such as standing water or an empty space where a delivery should be, so the delay has evidence.
- A photo of anything the buyer must decide, such as the kitchen island position marked out on the floor.
- Materials delivered and stacked, such as windows and doors, to support the 'arriving next week' line.
A delay week
Plain wording matters most when the news is bad. Take plot 9, week 11, where the notes read: no work from Tuesday to Thursday because the concrete supplier did not deliver; concrete arrived Friday and the slab was poured; nothing needed from the buyer. A typical first draft says 'we hit a small hiccup with a supplier but the team bounced back and the slab is poured'. What you would fix: 'small hiccup' and 'bounced back' soften three lost days into something vague. Rewrite it as 'Work stopped from Tuesday to Thursday because the concrete delivery did not arrive. It came on Friday and the slab was poured that day.' Then add a line to the prompt: 'State delays plainly, say how many working days were lost and why, and do not speculate about knock-on dates.' A plain sentence is easier for a buyer to trust than a vague one.
On a platform: daily logs rolled into the weekly update
A builder platform changes where the words come from. JobTread's AI page describes AI Daily Log Summaries, which turn several daily logs into one shareable summary of job progress for your team, customers and vendors. Used for buyer updates, the routine moves earlier in the week: the site manager writes a short daily log each evening (what was done, what stopped work, what arrived) with photos attached, and on Friday you generate the summary for that plot and edit it before it goes out through the customer portal or by email.
The same checks apply, plus one more. A summary of five daily logs inherits every vague log: 'cracking on with first fix' on Tuesday becomes 'first fix progressed well' in the summary, which tells the buyer nothing. So the daily log needs the same discipline as the Friday notes, with plain facts and counts ('first-fix electrics done in four of six rooms'). Trial it on one plot for two weeks: generate the summary, write the update the old way as well, and compare. If you rewrite more than half of the summary, the logs are too thin, and the fix is in the logs rather than the AI.
For a wider set of prompts, including snag lists, the tutorial on client updates and snag lists for builders goes further, and the field photos and punch lists tutorial covers turning photos into lists.
Where AI-written updates go wrong, and the check that catches it
The assistant writes smoothly whether or not it has the facts, so the errors that matter are fluent ones. These are the five to expect.
- A stage declared complete. 'First fix is finished' from a photo of one room. The check: every stage claim needs a source tag pointing to a note you wrote.
- An invented or implied date. The draft above shows it. The check: search the update for any day, week or 'on track' phrase and match it to a note.
- Mixed-up plots. Two plots uploaded into one chat, or last week's photos reused. The check: one Project per plot and the plot number in every prompt.
- The wrong tone about a delay. Relentlessly cheerful copy about a week lost to rain reads as evasion. The check: tell the assistant to state delays plainly in one sentence and say what is being done.
- Things in the photo you did not mean to share. A neighbour's garden, a worker's face, an open hazard. The check: look at every photo before attaching it.
Dates deserve extra caution because buyers act on them: they book removal vans, give notice on rentals and arrange mortgage timing. Check what your sales contract says about estimated completion before you send anything that reads like a commitment, and ask your legal adviser if the wording is unclear. The assistant should never be the one to say when a home will be ready.
Photo and upload limits that decide which tier you need
Limits change often, so treat these as figures to check. As of October 2026, from the vendors' help pages as read in September and October: free ChatGPT accounts allow three file uploads a day, and paid plans allow up to 80 files every three hours; ChatGPT accepts PNG, JPEG and non-animated GIF images up to 20 MB each. Claude accepts up to 20 files per chat, and 10 MB per image on claude.ai. Gemini apps take 10 files per prompt.
Three consequences follow. A weekly round of 60 photos across six homes is fine on a paid plan, as long as you upload each plot separately; ten photos a plot is inside every cap above. Ordinary phone photos are usually well under those caps, but panoramas and some high-resolution modes can exceed 10 MB, so resize those first. If your phone saves photos as HEIC, test an upload before relying on it, because the formats OpenAI lists are PNG, JPEG and GIF. And because OpenAI's page says file names and metadata are not read, the plot number, date and what each photo shows should be in your notes, not trusted to the file.
Hidden costs: review time, storage and buyer replies
The subscription is the visible cost. The ones that bite are less obvious.
Review time. Assume a manual update takes 40 minutes (gather photos, write, check) and an AI-assisted one takes 15 (5 to choose photos, 2 to upload and prompt, 6 to read and edit, 2 to send). Those are assumptions for the sum, so time your own next five. On those figures, 26 updates a month take 17.3 hours by hand and 6.5 hours with the assistant, which saves 10.8 hours. At $45 an hour of your own time that is about $490 against an $83 stack. The saving is real only if you spend the time you save on something that earns, and only if you keep the reading step. Skip the reading to save 6 more minutes and you have saved nothing the first time a wrong date reaches a buyer.
Buyer replies. Weekly updates produce questions. A buyer who gets a clear update on Friday will reply on Saturday with three queries. Decide who answers and by when, because an update that raises questions you ignore is worse than none. If a buyer replies asking for a change to the specification, take it through your normal variation process and keep the update thread for progress only.
Storage. A home's photos over a build run to thousands. A phone or free cloud allowance fills. A photo app stores them for you, which is part of what its fee buys; otherwise budget for a larger cloud storage plan and a simple folder-per-plot rule.
Set-up and change. Plan two to three hours once to write the prompt, test it on three past weeks and agree the photo rules with your site manager. For a platform with a customer portal, add its implementation time, because JobTread offers no free trial, only a 30-day money-back guarantee on monthly plans, so the first month is your test.
Cutting the bill without cutting the checking
- Start with one plot. Run the routine on a single home for three weeks before paying for anything beyond the assistant.
- Use voice notes. Your phone's built-in dictation is free. Pay for Otter only if site managers will not type and the phone's version fails on site noise.
- Pick the cheaper billing only when sure. Claude Pro is $40 a year cheaper billed annually, and CompanyCam's prices are quoted on annual billing. Start monthly where a monthly option exists, switch after two months.
- Share through email first. Sending updates from your own mailbox with six photos attached costs nothing. Move to a portal when buyers ask for one, not before.
- Do not buy the AI tier for the AI. The assistant plan is where the writing quality is. A photo app's credits are a bonus.
A one-sheet review after four weeks of updates
After four weeks, put four numbers on one sheet and compare them with what you assumed.
- Updates sent on the day. If any slipped, find the blocker. It is usually photos arriving late, not the assistant.
- Minutes per update. Compare with the 15 assumed above. If you are at 25, your photo selection or your review is the slow step, and a photo app may be worth its fee.
- Sentences you delete per draft. If you remove more than two on average for four weeks, tighten the prompt, for example by banning the phrases you keep deleting ('on track', 'hiccup').
- Buyer questions per update. A falling number means the updates are answering what buyers want to know. A rising one means they are vague. A buyer who asks for a phone call instead is telling you about the format for that person, not marking your updates as a failure.
Which set-up for which size of builder
| Homes under construction | Sensible set-up | Why |
|---|---|---|
| 1 to 3 | Assistant only, $20 | Organising photos is not yet a problem, and $63 more is about $4.85 an update at three homes |
| 4 to 10 | Assistant plus a photo app if photos are scattered across phones, otherwise assistant only | The app earns its fee by saving search time and by giving buyers a live view |
| 10 or more, or buyers who expect a portal and selections | A builder platform that replaces other tools | The fee is spread across more homes and replaces scheduling and daily-log tools you would otherwise pay for |
The pattern holds whatever you choose: begin with the cheapest set-up that gets buyers a good update each Friday, measure the minutes it takes you, and add a tool only when you can name the minutes it will save. The tutorial on photo documentation apps and their plans helps if the photo app is where you are heading.
Questions builders ask about AI progress updates
Is it safe to put buyers' details into a chat assistant?
Keep it to what the update needs: a plot number or first name, site notes and photos. Leave out contracts, bank details and full addresses. Consumer ChatGPT and Claude plans offer a model-training switch in privacy settings, and the business plans do not train on your content by default. Check the setting on whichever plan you use before the first upload.
Can the assistant read dates and locations from my photos?
Do not count on it. OpenAI's image FAQ, when checked, said file names and metadata are not read and that images are resized before analysis. Put the plot number, the week and what each photo shows in your notes, so the update does not depend on information the assistant cannot see.
Should the update be sent automatically?
No. An automatic send removes the one check that catches a wrong date or an overclaimed stage. The saving comes from drafting, and drafting is where the assistant helps. Read each update, remove anything you cannot back with a note or photo, and press send yourself. Automations are fine for collecting photos into a folder.
How many photos should go into each update?
Eight to ten chosen photos is a good working range for one home. It keeps you inside upload limits (Claude accepts up to 20 files per chat, Gemini 10 per prompt) and keeps the buyer's attention. Name each photo or list what it shows in your notes so every sentence in the update can be traced to a photo.
Do I need a builder platform just to send updates?
Not for updates alone. An assistant plus photos you organise yourself covers the writing at $20 a month. A platform such as JobTread earns its price when it also replaces your scheduling, daily logs, selections and customer portal, and when you have enough homes under construction to spread $199 or more a month across them.
Further reads
- AI Software for Custom Home Builders: Selections, Budgets, Client Portal — Selections, budgets and portals for custom builders.
- AI Tools for Home Builders: Build Schedules, Delays and Sub Chasing — Schedules, delays and chasing subcontractors with AI.
- JobTread vs Buildertrend for a Small Builder: Price, AI and Fit — Price, AI and fit for two builder platforms.
- AI for Building Contractors: Chasing Subcontractors and Progress Updates — Chasing subcontractors and progress updates.
- AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.
Sources: Claude and ChatGPT pricing pages; CompanyCam pricing page; JobTread pricing and AI feature pages; Otter pricing page; Buildertrend's pricing page would not load, so it is not priced. Upload limits are from vendor help pages as checked in September and October 2026. Google AI Pro uses the $19.99 list price. All other prices read in October 2026.