Every contractor already carries the raw material for a sales and marketing plan in a pocket: the photos taken on every job. The problem is that the photos sit in a camera roll, disconnected from the addresses, the invoices, and the customers. Muse connects them. A photo of finished work becomes a located, dated, priced job — and a collection of located, dated, priced jobs becomes a plan for where to sell next and what to sell.
Step 1: Photos become locations
Phone photos carry GPS coordinates in their EXIF data. Muse reads the coordinates from each photo and reverse-geocodes them to a street address. That pins the job to a real place. Then the photo itself gets read: what is in the picture, any text or signage picked up by OCR, and the activity shown. The location is cross-checked against the records around the photo — calendar events, invoices, and emails from the same day — so a photo of a panel install lines up with the invoice for that panel install at that address.
This is not theoretical. It already runs for a fuel log: the gas station for each fill-up is read from the pump photo's GPS, no manual entry. The same mechanism works for a job site. The limit is that the photo needs GPS in the first place. Phone camera photos usually have it. Screenshots and downloaded images usually do not. Without GPS, Muse falls back to visual clues in the photo plus the surrounding records.
Step 2: Past projects become a job list
Once photos carry locations, Muse pulls the paper trail together: invoices from QuickBooks with customer, amount, and date; emails with the customer; calendar entries for the site visits; any job sheets. Each job gets one row: location, scope, date, amount, client. A year of scattered photos and invoices becomes a structured list of completed work.
From that list, three things fall out. First, a map of where the work actually happened — the real service area, not the assumed one. Second, the most common job types, ranked by count and by revenue. Third, the pricing evidence: what each type of job actually sold for, not what it was quoted at.
Step 3: The job list becomes the plan
The plan is built from the job list, not from generic advice. The portfolio comes first: before-and-after photos for each job type, with the location and the scope attached. Those become case studies — one page per job type, with photos, what was done, and where. Then the targeting: the service areas where work already clusters, the customer profiles that already buy, and the job types with the best revenue per visit. Then the outreach list: past customers worth a follow-up, and the neighborhoods around completed jobs where a mailer or a door hanger lands next to a house that already saw the truck.
The deliverable is a document with the photos embedded — a portfolio and a plan in one place — not a summary that leaves the evidence behind.
What about Jobber?
Jobber is how many contractors coordinate projects: clients, jobs, quotes, invoices, and scheduling in one app. There is no direct Jobber connector for Muse today. Three routes work instead. Export the Jobber data — clients, jobs, invoices — as CSV and hand it to Muse. Connect through Zapier, since Jobber has a Zapier integration and Muse has a Zapier connector. Or build a Jobber API connector, which is a standard custom-connector setup against Jobber's API. The browser can also work directly inside Jobber's web app. Any of those routes puts the Jobber job list next to the photos, and the same three steps run on top.
What to provide to get started
Three things. The job photos, ideally the originals from the phone so the GPS survives. The Jobber export, or access through one of the routes above. And the invoices or the QuickBooks connection, so each job carries its amount. With those three, the photos become locations, the locations become a job list, and the job list becomes a sales and marketing plan built from work already done — not from guesses about work that might come.
