Software for work that happens in the field
An operator with a well in West Texas calls a Houston oilfield service company and asks for a crew. The operator's representative meets that crew on location, watches the work and signs a paper ticket for the hours and the equipment. Then the customer waits. The ticket rides back to Houston in a truck, someone in the office types it up, and a question about one line goes out by text message. The invoice the customer finally receives may not match what their own representative signed, so their accounting office sends it back. The job was finished in the field long ago, and nobody has been paid for it.
With the tool we would build, that customer signs on the crew's phone, on a ticket laid out the way their company requires. The record reaches Houston when the phone is back in range, and the invoice is drafted from the lines the customer already signed, so their accounting office receives its own format without anyone retyping it. Inside the service company the owner still decides who may see a ticket, which rates apply and whether an invoice goes out. Before anything is built, we agree with you what goes on a ticket and what rules it follows. We start with a brief that fixes the scope and price of the build, and deliver one small release your people can try on real jobs.
Other Houston customers want the same thing in a different form. A shipper with a container at the port wants to see the status the forwarder's dispatcher sees. A building owner in Katy wants the mechanical contractor's visit report without phoning for it. Customers further out can have it too. A plant in Lake Charles that hires the crew signs, questions and receives its paperwork exactly as a plant in Pasadena does, and an operator in Louisiana who has never visited the Houston office can follow the job from its first ticket to its invoice. Setting up that customer is a matter of adding their ticket layout.



