Business Management System Development Example for a Plumbing and Water-Services Provider

This case began when a locally focused plumbing and water-services provider reviewed how information was shared from initial reception through on-site work. Office staff who also handled reception received repair requests by telephone and recorded the customer name, address, telephone number, preferred visit time, and fault description on paper dispatch slips. The owner or dispatcher wrote staff names and daily destinations on an office whiteboard, then notified available technicians by telephone or message. Customer information was retained in an Excel ledger, but it was not linked to daily schedules, work photos, or completion reports.

After on-site work was completed, field staff wrote the work performed, parts used, and estimated charges by hand on dispatch slips. Before-and-after photos were stored on their individual smartphones. During busy periods, when seven to ten visits could overlap in a day, the office had to call staff to determine whether they had arrived, whether parts needed to be ordered, or whether the next visit could be rescheduled. When the same customer contacted the company again, the team had to search the Excel ledger, past slips, and individual photo folders separately, making it difficult to confirm repair history while speaking with the customer.

Rather than replacing quotation creation, invoice issuance, and accounting integration all at once, the project was scoped around digitizing the flow from initial reception through site visits and completed-work reports. The system was designed for an operational volume that a small company could manage on a daily basis. For field staff, the core actions were limited to checking the destination, updating arrival or completion status, and registering photos. The initial release established a foundation for information sharing, while invoicing and a customer portal were reserved for a possible second phase based on actual usage.

To make a six-week delivery feasible, the client was asked to provide the paper dispatch slips, reception checklist, staff list and roles, sample jobs and work photos, and acceptance criteria at the start. The initial scope was limited to three roles—Administrator, Customer Service and Dispatch, and Field Staff—along with fixed job-status transitions, standard photo registration, and job and customer-history search. Invoice issuance, inventory management, payment processing, accounting-software integration, a customer portal, and large-scale migration from existing Excel files were excluded.

At the office, staff registered a telephone request as a job, assigned a field technician, and set the planned visit time. Field staff used smartphones to check jobs for the current and following day, then updated the job status to “En Route” and “In Progress.” Once work was complete, they entered before-and-after photos, the work performed, parts used, and any follow-up requirement, then reported the job as “Complete” to the office. By finalizing the input fields and representative screens in the first week and completing reviews in short cycles, we defined a scope that could be delivered for $8,400 in approximately six weeks.

Technical Configuration

An Option for AI-Assisted Handling of Sensitive Operational Data

The standard configuration in this example does not include AI analysis of job notes or work photos. If a business later wants to support internal search, completed-work summaries, or next-action drafts without sending job notes containing personal information, photo descriptions, or repair history to external AI services, we can separately consider a private AI configuration using a locally run LLM on PCs or servers managed by the client. Learn more about our Private AI & Local LLMs service.

This option requires an assessment of source data, authorization design, response speed, available CPU, GPU, memory, and network controls. Because photo handling, possible hardware upgrades, network configuration, and additional validation may be required, it is not included in the standard $8,400 / six-week scope and is quoted separately according to the requirements.

The initial release was limited to the functions required to take a repair request through to a completed-work report for the office. Finalizing service charges, issuing invoices, inventory management, and customer email distribution were outside the initial scope; the client continued to use its existing accounting software and business processes for those functions.

The deliverables consist of the complete web application, an administrator operations manual, a database design document, and a test-results list.

Workflow and Screen Overview

Main Data Managed by the System

This project was completed in approximately six weeks on the assumption that paper dispatch slips, the reception checklist, staff list, and representative job and photo samples were supplied at the start. By completing business-process alignment and major-screen confirmation in Week 1, we reduced late-stage rework and shortened the path from implementation through acceptance testing to production launch.

Payment Terms

As a general rule, we do not require an upfront payment. There was no payment at the time of contract; the full amount was invoiced only after all development work and the client’s acceptance were complete.

The following amount covers implementation of the reception, dispatch, field-completion-report, and history-search functions defined in the initial phase, along with testing and production-release support. Invoice issuance, inventory management, payment processing, accounting-software integration, a customer portal, large-scale existing-data migration, and a private AI / local LLM environment are outside the initial scope.

Currency and Invoicing

All amounts on this page are approximate U.S. dollar (USD) figures, converted from the original Japanese yen (JPY) estimate at an assumed exchange rate of around JPY 150 per USD and rounded for readability. Quotations and invoices can be issued in USD, JPY, or other currencies upon request; the applicable exchange rate, conversion basis, and any bank or payment-provider fees will be confirmed in advance for each project. For clients outside Japan, payments are generally handled as transactions exempt from Japanese consumption tax.

Supplement: Estimated Third-Party Service and Maintenance Costs After Launch

The following figures assume an initial operation with approximately 12 employees, around a dozen regular users, several hundred jobs per month, and attached work photos. These expenses are separate from the initial development cost. Cloud services required to operate the web application in production, as well as any monitoring or notification services selected, incur third-party service charges paid directly to the respective providers.

Third-party cloud-service costs are model estimates informed by published pricing structures for managed database, authentication and file-storage services, web hosting, and object storage.

For small businesses like this plumbing and water-services provider, where telephone reception, site visits, and photo-based completion reports occur daily, it is effective to begin by focusing on sharing each job’s status between the office and the field. Rather than abruptly replacing existing accounting software or invoicing procedures, the initial release moves only the dispatch-schedule and completion-report functions that had been distributed across paper dispatch slips, a whiteboard, and an Excel ledger into a web application. This helps the new workflow take hold without overburdening the field team.

The six-week delivery was possible because the existing slips, fields, and roles were shared at the start and the screens and status transitions required for the initial release were fixed early. This allowed the initial cost to remain at $8,400 while consolidating the status checks that had depended on telephone calls and the repair-history information that had been scattered by customer.

If the client later wants AI to support next-action drafts or internal search based on past work history and job notes, Private AI & Local LLMs is also an option alongside cloud-AI integration. It can be designed to keep operational data within client-managed infrastructure, although it requires a separate design based on data type, photo handling, available hardware, and network requirements.

Typical Scope for Common Add-Ons

After the initial release has become established, a customer portal may be added so customers can log in and view planned visit times, work history, photos, and quotations. Because the existing customer and job data can be reused, a typical estimate is an additional $4,000–$6,000 and approximately 4–6 weeks.

An online-payment integration may also be added to issue a payment link after an on-site repair. This approach uses an external payment service and does not store credit-card information in the company’s own system. A typical estimate is $3,300–$4,700 and approximately 3–5 weeks.

Adding both the customer portal and online payment as a second phase is estimated at an additional $6,700–$10,700 and approximately 7–9 weeks. Combined with the initial release, the total would be approximately $15,100–$19,100. Separate design and estimation would likely be required if the project also needed split billing, batch management of multiple properties, parts-inventory integration, manufacturer-warranty inquiries, or two-way integration with accounting or core business systems.

By first digitizing daily dispatch slips and completion reports reliably, then expanding in stages based on the functions actually needed in operation, the business can avoid unnecessary investment and grow the product into a better fit for its own workflow.