The company
We build the path. We do not replace the people who run it.
WhatTheJob is AI field operations software. A customer’s first message or call becomes a job a crew can finish, and the customer hears that it is done.
A customer writes on WhatsApp, SMS, or email, or they call. Someone still retypes the address. A crew member still guesses the site. Most tools start after that mess, once a job form exists. We start when the customer writes or calls.
WhatTheJob reads the conversation and drafts a request: service, customer, place, time, problem. Software checks it against your catalog. A person still approves. You assign. The crew finishes on a phone. The customer hears it is done.
How we build
Four things we will not trade away.
Start at the conversation
The request is already in WhatsApp, SMS, email, or a call. The job is not. Most tools start once a job form exists. We start when the customer writes or calls.
A person still approves
WhatTheJob drafts. Software validates. A person lets the work through. Software that invents jobs will not last a week in a real crew.
You stay in control
We amplify owners. They keep the business. The product gives a small crew the path they used to need a bigger office for.
The catalog is theirs
We do not ship a packaged edition per trade. Your services and checklists stay with your company. Architecture stays generic.
Who it is for
Owners, the office, and the crew.
Same product. You see the request before it becomes a job. The thread is already a draft you can approve. The crew gets today’s jobs, the address, and the checklist.
If you run a crew that goes to the customer, contact sales and tell us what a typical request looks like.
Conversational on purpose. The .ai domain matches the product: unstructured communication to structured work. The name can look a little playful. The sentences around it should not wink.
Tell us how a request becomes a job today.
Tell us how a request becomes a job today. We walk the inbox-to-job path if it fits.