Work/RV TechMate 2.0
RV TechMate 2.0, field software for the truck.
A mobile, dark platform for Camp Technologies: jobs, customers, RV units, invoices, and the rest of a shop’s day. The screen below is demo data. It is not a customer account, and the private app is not linked.

Fictional values. Not a customer, not a charge, and not a link to the live app.
What the platform is for
True North Web Design builds the public website and the software behind the shop. CampTech is the site that tells a stranded owner the truck is coming. RV TechMate 2.0 is the other half of that business: a field-service platform for Camp Technologies, used by mobile RV techs and the shops that dispatch them. It is not a brochure with a login taped on. It is the screen a tech opens when the job, the coach, and the invoice have to live in one place.
The product is mobile-first and dark. A lot at noon and a bay after sunset are both normal working light, and a pale dashboard washes out in both. Dark mode is the default, not a theme buried in settings. The same build can serve more than one company. Each company turns features on or off. A one-truck operation does not have to stare at a module it will never use, and a larger shop does not have to wait for a second product when it needs dispatch, claims, or a time clock. The toggle is the difference between a platform and a pile of screens nobody asked for.
A day starts with jobs, a calendar, and dispatch. The job is the unit of work: what is wrong, which tech is going, and when the truck rolls. The calendar is that list in time. Dispatch is the decision of who takes the next stop, so the office is not texting three people and hoping one of them is free. None of that is useful if the customer and the RV are a note in the margin. The customer record and the unit stay attached to the job. A return visit starts from the coach, not from a blank form and a memory of last summer.
Money sits on the same record. An estimate is the number the customer is shown. That estimate becomes the invoice, so the office is not retyping a quote into a second tool. Square takes the payment. We did not invent a processor for this product. The shop already knows how to take a card, and the invoice should be able to use that path without a screenshot and a separate terminal. The figures on this page are not a real charge. Every dollar on the demo is zero on purpose.
Warranty and insurance claims are where a lot of shops lose the afternoon. The claim has to name the unit, the failure, and the company that is supposed to pay. RV TechMate keeps a directory of more than 150 claims companies so the tech is not hunting a PDF of adjuster names in the truck. The claim tool sits next to the job. It is not a second login and it is not a spreadsheet named “claims final FINAL.” A sample claim on this page is labeled as a sample. It is not a customer’s policy.
The repair assistant is an AI tied to a manual library, not a chat box that invents a torque spec. When a tech asks what a code means, the useful answer is the page in the manual, not a confident paragraph with no source. TechMate is the shop system. The manuals are the source. We do not pretend a language model replaces the book. We point the question at the book.
Parts and inventory are the unglamorous half of a repair. The sealant on the truck and the sealant on the shelf have to be the same part, or the tech drives back. The platform tracks what is on hand and what the job used. A demo row on this page says “Sample sealant kit” and a quantity of zero. That is fiction, so nobody can mistake it for a bin count in a real warehouse.
Labor is part of the same day. A time clock records the hours. PTO is requested in the product instead of a text the owner has to remember on Friday. At the end of the day the owner should see profit and loss and the sales tax that belongs to that day, without exporting five files and adding them in a notebook. The daily P&L on the demo is a zeroed sample. It is there to show the shape of the screen, not a company’s books.
The agreement should exist before the truck rolls. Service agreements are attached at booking, so the terms are not a paper form in the glove box that nobody can find when there is a dispute. Customer texting is the update the person at the campsite actually reads: the tech is on the way, the part is in, the invoice is ready. After the job, a Google review request is a step, not a hope that someone will search the shop’s name and feel generous. A marketing tracker records which channel produced the job, so “we should post more” is not the only report.
Hiring is part of operations software too. HR onboarding includes fillable I-9 and W-4 forms so a new hire’s paperwork is a form in the product, not an email attachment that expires in someone’s downloads folder. The demo does not show a real employee, a real Social Security number, or a completed government form. Those fields, if you imagine them, are blank samples. We will not put a person’s identity on a marketing page to prove a form can render.
Some of the platform is still in progress, and this page will not call it finished. Online booking, a customer portal, service plans, and a QuickBooks export are the next pieces. They are named here so a reader does not think they are already in the truck. When they ship, the case study can say so. Until then they are a list, not a screenshot.
Nothing on this page is a customer. The shop name, the tech, the phone number, the unit, the invoice, and the claim are demo values written for the case study. There is no embed of the live app, no screenshot of a real account, and no link to sign in. Field software is private by nature. The public proof is this explanation, plus the websites a person can open. If you need the same kind of tool, the conversation starts with the job your spreadsheet is doing, not with a tour of someone else’s data.
A website still has a job. It gets the call. Software starts when the call is no longer the bottleneck: when the office is retyping the same job into a calendar, an invoice, a claim form, and a group text. True North builds both, and we do not fold a login and a database into a $750 site price. Launch websites build from $750. A platform like this is quoted after we know who signs in, which features each company should see, and what has to work on a phone in a parking lot. Call (865) 235-1305 or start with the discovery questionnaire. Read the CampTech site and Camper Guard if you want the other shapes this studio ships.