Trade software built for 20 vans, sold to 1: what a one-van business actually needs

Job management platforms built for a business with a dispatcher and a crew carry that shape through the whole product. There is a scheduling board because someone has to decide which tech goes where. There is GPS because the owner cannot see the vans. There are roles and permissions because different people should see different things. A one-van business has none of those problems. The dispatcher, the tech, the estimator and the bookkeeper are the same person, and that person already knows where the van is. One post on r/Plumbing put it plainly: "Looked into Jobber and ServiceTitan but honestly I don't need scheduling, dispatching, GPS tracking, or any of that. I just need to send a clean looking quote with line items and my logo on it without it taking 20 minutes." That is not a feature request. That is someone describing a product that does not exist at their scale. The vendor's answer is usually a cheaper tier of the same product, which is the same crew software with fewer seats rather than a different shape. The result is predictable. The subscription gets paid, a handful of screens get used, and the actual work drifts back to the Notes app, a photo roll and a spreadsheet.

It is about scope. The missing middle is not a shorter feature list. It is that nothing is designed around one person doing every role in sequence. A crew tool assumes handoffs. Someone books the job, someone else attends, someone else invoices. Every screen is a handoff point, and handoffs need structure: statuses, assignments, notifications, approvals. A solo operator has no handoffs. They have one continuous thread per job. Enquiry, quote, attend, photos, invoice, chase. What they need is that thread in one place, not five modules that each represent a different person's shift. Two-tool stacks do not fix it either. Splitting job management and accounting across two products leaves a solo operator with two subscriptions, two logins and a sync to keep an eye on, which is more admin, not less. The same pattern turns up outside trades. A post on r/therapists described the clinician version: "Started with SimplePractice which a lot of therapists seem to use and it's fine, it does a lot, but I felt like I was paying for a ton of features I didn't need (I don't do insurance billing, don't need telehealth through them) and the interface felt cluttered to me." Different industry, identical complaint. The software is built for a practice with admin staff and billing complexity, sold to a person with neither.

Six objects, and honestly not much more. A jobs list, so there is one place to see what is on, what is quoted and what is done. Crew software adds a dispatch board and technician workload views you do not need. Notes per job, covering site access, what the customer said and what you found. Crew software adds threaded internal comments, mentions and approvals. Photos per job, as evidence for variations and disputes. Crew software adds asset libraries, tagging taxonomies and sharing permissions. A quote you can send, with line items and your logo, from the van. Crew software adds multi-tier estimate templates, margin analysis and approval chains. An invoice, so you get paid and your accountant is fed. Crew software adds payroll, timesheets and job costing across crews. A follow-up reminder, the step that gets dropped when there is nobody else to chase. Crew software adds campaign builders, pipeline stages and lead scoring. The follow-up item is the one worth pausing on. For a solo operator, chasing a quote is the step with nobody else to catch it, and it is the feature that gets buried deepest in the platforms built for fleets.

Sometimes, and the honest answer depends on how stable your process is. Build makes sense when your process is genuinely simple, you already know exactly which six screens you need, and the subscription is buying you fifty things you never open. A small owned build means the tool matches the way you already work rather than the other way around, there is no seat pricing, and nothing changes underneath you when a vendor reprices or redesigns. Subscribing makes sense when you are about to hire, when you need compliance features you are not qualified to build such as payment card handling, clinical records or tax lodgement, or when you genuinely do not want to touch the thing again. A real platform has support, backups and someone else's liability. That is worth paying for. The counter-argument to building is real and worth stating: software you own is software you maintain. If nobody in the business can debug it, an owned tool is worse than a subscription, because a broken subscription has a support queue and a broken personal build has you at 9pm. That is exactly why the deciding question is not whether this can be built, but whether anyone here will own it. Ownership is a capability, not a purchase.

They fail for the same reason automations fail: the person who built it moves on, nobody else understands it, and the first time it breaks the business quietly goes back to the spreadsheet. They stick when the owner can diagnose the problem themselves. Not write elegant code, just work out which step failed and why. That skill is process-mapping and debugging, and it is far more transferable than any particular tool. The trap is easy to describe. Tools aimed at this problem tend to be either built for a much larger business or thin enough that someone still has to review every item by hand. The manual-review problem is the tell. A tool that still needs you to check everything has not removed the work, it has moved it. The way out is understanding your own process well enough to know which steps genuinely need a human and which are just habit. For a one-van business, that usually means quoting needs your judgement and follow-up does not. Diagnosis on site needs you, recording the job does not.

Work through it in this order. First, write down every step of one real job, from enquiry to paid. Not the ideal version, the actual one. Second, mark the steps that cost you money when they are skipped. Follow-ups and variations usually top this list. Third, count how many of the six core objects your current setup handles badly. Fourth, check what you are already paying for and how much of it you opened last month. Fifth, decide whether the gap is a tool problem or a habit problem, because software will not fix a habit problem. If the first three steps point at a small, stable process and the fourth shows you are paying for a fleet, a small owned build is a reasonable answer. If your process changes every month, or you are hiring soon, buy the platform and revisit later.

Is Jobber or ServiceTitan overkill for a solo tradie? It depends on whether you are about to hire. Both are built around scheduling and dispatching a crew. If you are the only van, most of that value never applies. The solo plumber quoted above looked at both and wanted none of the scheduling, dispatch or GPS, just a clean quote he could send quickly. What is the minimum software a one-person trade business needs? Six things: a jobs list, notes per job, photos per job, a quote you can send from the van, an invoice, and a follow-up reminder. If a tool covers those six reliably and nothing else, it is enough. Everything beyond that exists to coordinate people you do not employ. Is it cheaper to build my own trade job app than pay for software? Cheaper is the wrong test. The test is whether anyone in the business can maintain it. An owned tool with no owner is more expensive than any subscription, because it fails at the worst moment. If someone can debug it, an owned build often fits a simple process far better. Why do solo operators end up back in the Notes app? Because the software asks for structure their business does not have. Statuses, assignments and approvals are handoff mechanics, and a solo operator has no handoffs. When entering a job takes longer than doing the paperwork by hand, people default to whatever is fastest, which is usually notes and photos. Does this apply to solo clinicians and consultants too? Yes. The complaint pattern is close to identical. Practice management software is built for a clinic with admin staff and billing complexity, then sold to a single practitioner who needs bookings, notes and an invoice. The mismatch is scope, not features. What should I do before buying anything? Map one real job from enquiry to paid and mark the steps that lose you money when skipped. The map will show whether your gap is a few specific moments or a whole platform. That map is also the only useful brief if you later decide to build something small.

Verbatim quotes are reproduced from public Reddit posts and attributed to the subreddit only, never to an individual. Each quote is a single post and is not evidence of how common the view is. r/Plumbing: https://www.reddit.com/r/Plumbing/comments/1sr32k5/solo_guys_how_are_you_sending_quotes_to_customers/ . r/therapists: https://www.reddit.com/r/therapists/comments/1tjf9n5/finally_got_my_documentation_time_under_control/ . No statistics are cited in this article. The pattern described is drawn from public forum discussion and is not claimed to be Australian-specific or measured by survey.