A lot of field software is sold as a vertical pack. HVAC edition. Cleaning edition. Property edition. The screens change. The job is the same: a message lands, someone retypes it, a person goes.
WhatTheJob is one product. Queries, a draft, a human gate, assign, the Crew App, done. Architecture stays generic on purpose. A second codebase per trade is a tax you pay forever.
The first conversations are not generic. You tell us who answers the phone. Where the job is written down. How a crew member finds out. How the customer hears it is done. Sales can be trade-shaped. The software does not have to be.
Architecture stays generic. The first conversations do not.
Why packs look busy and cost you later
A homepage with six editions looks like care. It often means six slightly different ways to do isolation, six slightly different gates, and six places a bug can hide. The van on the screenshot changes. The hop from chat to sheet does not.
Trades are real. An HVAC morning is not a cleaning morning. A property desk emails. A homeowner writes WhatsApp. Those differences belong in your catalog, your checklists, and the first sales talk. They do not belong in a fork of the inbox.
We are not a packaged edition per trade. About says the same thing in fewer words. Use cases are examples of the first message, not editions. If a use-case page helps you see your week, good. It is still this product.
A pack also trains the wrong expectation. Buyers start comparing tiles instead of walking the path. The path is the product: first message to job done.
It also slows the thing you actually need. Isolation, the gate, and the Crew App have to be right. Every edition fork is a chance to get one of those wrong in one tile and right in another. Customers do not buy “mostly isolated.” They buy a week that does not leak.
One path, on purpose
The path does not change because the van does.
Conversation in. WhatsApp, SMS, email, and voice. One operational inbox. The request is already in the thread. Field service requests start in chat, not in a job form is that note.
A draft you can trust. Service, site, window, problem, each with a score. Software checks the catalog. A person still converts. The model does not assign, price, or create the job.
Assign. You pick the crew member and the window. The field opens a job record, not a forwarded chat. Close, then the customer is told.
Isolation has to be right once. Retrieval stays inside your company. Empty context beats another company’s thread. Roles stay the same: owners and admins can look back, dispatchers run the day, crew see assigned work, customers do not get a login.
If we split that path into editions, we would split the things that must not be split. A leak in the “HVAC pack” is still a leak. A gate that disappeared in the “cleaning pack” is still a missing gate.
The catalog is yours
Services, checklists, hours, and FAQs live in your company. That is how a generic architecture still feels like your week.
You decide what you sell. Software refuses a service that is not there. You decide what the crew must complete. The Crew App shows that checklist. You decide what the bot may answer. Knowledge answers never create a job.
We do not invent a trade pack so the demo looks closer to your van. A demo that only works because we hard-coded your nouns will lie in week two, when the nouns change.
Use-case copy on the site can say tenant when it means a building occupant. That is property language, not our word for your workspace. In-product and public we say company for your business and workspace for this login. The architecture underneath still isolates each company. You should not have to talk like a SaaS brochure to run a day.
The first conversation is still specific
Contact sales is how a workspace starts. You write how a request becomes a job today. If the path fits, we walk Queries, the human gate, assign, and the Crew App. Then we set up the workspace and invite the owner or admin. Crew members are added by the company.
That walk is not a generic tour. It is your inbox, your hop, your driveway. HVAC, cleaning, property, or a trade we have not put on a use-case page yet: the questions stay the same.
- Who answers the first message or call.
- Where the job is written down today.
- How a crew member finds out.
- How the customer hears it is done.
- What you do when the bot should stop.
Platform billing is handled after a sales conversation. That is separate from invoices you send your own customers. Pilots are explicit. A page on this site is not a price quote or a license.
Contact sales is the page for that walk. This note is why we will not greet you with an edition picker.
An edition picker would also lie about time. It suggests you can skip the walk if you pick the right tile. You cannot. The hop is yours. The catalog is yours. The first conversation is how we find out whether the path fits. The tile would only pick a screenshot.
What we are not selling
We are not generic field-service management that starts after a job form exists. We are not AI theatre: a sticker on a tool that still makes someone retype the address. We are not a story about replacing dispatchers, techs, or owners. We are not a customer portal for the end customer.
We build the path. We do not replace the people who run it. Owners stay in control. The product is supposed to give a small crew the path they used to need a bigger office for. We do not say “leverage” at you.
Public channels stay four: WhatsApp, SMS, email, and voice. If a pack page lists two of them, it is already simplifying the week.
What a trade-shaped walk actually looks like
You do not owe us a category tile. You owe us a morning.
An HVAC owner talks about the personal WhatsApp, the sheet, and the tech who guesses the closet. A cleaning company talks about a mailbox nobody shares and a crew that gets a pin. A property desk talks about email, a unit number, and a tenant in the building sense: the person who lives there.
We walk the same product. Queries. Draft. Gate. Assign. Crew App. Done. Your catalog supplies the nouns. Your checklists supply the visit. Your FAQs supply what the bot may say.
If the path does not fit, we say so. A page on this site is not a license. A use-case page is not a promise that we built a special edition for you.
The walk is also how we refuse the wrong sale. If you want a bot that never escalates, this is not it. If you want a store of trade packs, this is not it. If you want the first message to become a job a person still approves, keep talking.
Bring the hop you already have. Screenshot to sheet. Pin in a group. Voicemail that never became a record. We will walk that, then Queries, then the gate. If your week does not fit, we will say so before anyone pretends a workspace exists.
Why we still show use cases
Use cases exist so a reader can see their first message on a page. They are typed examples: HVAC, cleaning, property, and the rest we publish. They are not forks.
That distinction keeps the journal honest. This company note would be a lie if the product behind the examples were six codebases. It is one. Isolation, the gate, and the Crew App are built once. The example changes. The person we are talking to does not. You, your crew, your customer. Same voice. Different nouns in the catalog. That is the whole reason we will not greet you with six editions that all hide the same hop.
How this sits next to the other notes
The company stance is the reason the other notes can stay short in spirit even when they run long.
Chat intake can be one inbox. The human gate can be one stack. Handoff can be one queue named Needs you. The Crew App can be one field surface. Isolation can be one boundary.
If you want the operational story, start with the chat note. If you want the AI story, start with the draft and the leak. If you want to see the path against a trade-shaped example, use the use cases, then come back here so you do not buy an edition we do not sell.
Tell us how a request becomes a job today. Architecture stays generic. The first conversations do not.
If you arrived from a use-case page, treat that page as a mirror, not a menu. The HVAC example is how a first message sounds. It is not a pack you add to a cart. The same is true of cleaning and property. One product. Your catalog. Your week. The hop you have today is the brief. Screenshot, sheet, group pin, voicemail: that is what we walk, then Queries, then the gate, then assign, then the Crew App. Contact sales when you want to walk it with your morning, not a generic tour.
Questions
No. Architecture stays generic. Queries, a draft, a human gate, assign, the Crew App, done. Sales can be trade-shaped. The software does not have to be.
Yes. You tell us who answers the first message, where the job is written down, how a crew member finds out, and how the customer hears it is done. That talk is specific. The codebase is not.
Your catalog, hours, and FAQs stay yours. We do not invent a trade pack so the demo looks closer to your van. Use cases on the site are examples, not editions.
Contact sales. We walk the inbox-to-job path if it fits, then set up a workspace.