Blog · Industry

Home Services

Writing from Sawhorse Engineering on home services.

Articles: 15
Category: Industry

26 September 2026Service request forms that give dispatch useful informationAsk for enough context to route a home-service request without turning the first contact into a diagnostic questionnaire or a false booking confirmation.
26 September 2026Offline job notes without losing office changesDesign a technician workflow that preserves field observations during a connection loss while keeping assignment and approval decisions authoritative.
26 September 2026Arrival windows that do not promise an impossible dayOffer home-service appointment windows from real capacity, then keep confirmation, estimates and changes distinct in the customer experience.
26 September 2026Van stock and return visits need one parts workflowConnect part requests, reservations, van transfers and job consumption so a return visit is scheduled against more than an expected delivery date.
26 September 2026Equipment history that survives a technician changeConnect sites, installed equipment and service visits without turning every note into an unsearchable customer timeline.
26 September 2026A dispatch board that understands the job, not just the calendarModel skills, travel, parts and job state before letting a dispatch board assign technicians. A free rectangle is not proof that a visit is feasible.
23 September 2026How to tell whether a task is an AI problemFour questions that separate work worth evaluating with a model from work that belongs in ordinary code.
20 September 2026What owning your software actually meansOwnership is four separate things, and a supplier can give you some of them while keeping the ones that matter. Here is the checklist.
15 September 2026Idempotency: the idea that prevents duplicate everythingA lost response can turn a reasonable retry into a duplicate order, email or charge. Idempotency helps, but its boundary must include the actual effect.
13 September 2026Automations that stop when the customer repliesThe most damaging automation failure is not a missed send. It is a sequence that keeps chasing someone who already answered.
11 September 2026Why your spreadsheet is the most valuable document in the businessThe file one person maintains usually contains rules nobody has written down. Extracting them is the highest value part of a modernization project.
6 September 2026Fixed scope is a feature, not a constraintAgreeing exactly what gets built before building it protects the client more than the supplier. What a written scope actually contains.
2 September 2026Performance budgets, and why averages lieA page that is fast on a development machine with fifty records tells you nothing. Set the budget first and measure against real conditions.
25 August 2026Where AI should hand over to a personThe handover is a design decision with commercial consequences. Getting it wrong in either direction is expensive.
19 August 2026Taking deposits and charging a balance laterA deposit now and a balance in six weeks touches holds, saved payment methods, authentication rules and cancellation policy. Here is the whole flow.

Other industry categories

Let’s talk about the system you need.

Tell us where the current process breaks down. We can map the workflow, examine the integration requirements and define a practical scope for the build.

Discuss Your Project support@sawhorsesoftware.tech

A mutual NDA is signed before project details are shared.
Scope is fixed in writing before any build starts.
You own the source code, the IP and the documentation at delivery.
Support plans are available and tailored on a discovery or technical call.