Skip to content

Stack & Data

Inside a Bohaus Sprint: A Pump Station Company

Every installed station should become a service customer. How a pump station company builds one station record from first design request to every service call.

April 27, 2026 · 4 min read

By Christopher Vandaele, Principal

Client engagement. Business name and identifying details withheld at the client's request.

The situation

The client is an owner-led company that designs, builds and services wastewater and stormwater pump stations. An engineering team draws stations for consulting engineers, a shop fabricates them, crews install and start them up, and service technicians keep them running under maintenance contracts. Customers include the engineers who specify a station and the owners, such as municipalities, utilities and developers, who live with it for decades.

The company offers free design help to consulting engineers. It is a strong way to get specified early, and it means every design request is a sales lead. In practice, requests arrive by email and web form, land in an inbox and get tracked in a spreadsheet, if at all. Bids go quiet without anyone noticing. Once a project is awarded, status lives in a few people's heads, so engineers and owners call to ask.

After installation, the station's drawings, serial numbers and startup data sit in a project folder. When the warranty runs out, nobody is prompted to offer a maintenance contract. When a tech goes out on a call, the history is a paper file or a memory.

What the sprint finds

In Discover, we follow one station from first request to service call. We read design requests, walk the shop and ride along with a service tech.

The company is good at every stage, but each stage keeps its own records. The design team knows the engineer. The shop knows the components. The service team knows the station. No one record carries the customer and the station from first contact to the tenth service visit.

In Diagnose, we rank the options. Fleet routing and a full inventory system are useful, but not the bottleneck. The biggest gap is the installed base: stations finished, commissioned and handed over with no maintenance contract and no follow-up. Every one of those is service revenue and a long-term customer the company already earned.

So the one live system is a single station record and map, built inside the company's existing CRM and service tools, that starts at the first design request and never closes.

What it builds

In Build, we connect the lifecycle around that record.

First contact. Every free design request automatically creates a CRM record for the engineer and the project. AI reads the submitted specs, such as flows, elevations and pipe sizes, and drafts a first layout outline and a quote checklist for the engineering lead to review. Automated follow-ups go out at set intervals, so no bid goes quiet by accident.

Project stages. Each project moves through defined stages: design, bid, awarded, fabrication, installed. Every stage change sends the engineer and the owner an automatic update.

Commissioning. Startup is where the station record becomes permanent. Drawings, components, serial numbers, startup readings and warranty dates are attached at handover.

The station map. A dashboard plots every station, color-coded by status: in build, under contract, or installed with no contract. The system flags stations coming off warranty and stations without a contract, and AI drafts a maintenance offer for each one, matched to the station's equipment and age, for a person to review and send. Contracts in force get automatic renewal reminders well ahead of their end dates.

Every service call. The tech opens the station file before leaving the shop. It shows the visit history, recurring issues, the equipment installed and the parts most likely needed, with a live stock check. After the visit, AI turns the tech's notes and photos into a clean visit report for the owner, filed on the station record.

Pricing, engineering judgment and every customer offer stay with people. The system drafts and reminds; the team decides.

Hand over

In Hand over, the engineering lead, the service manager and the office lead each learn their part of the system in depth. Techs get a short session on opening the station file and logging a visit from the field. A playbook covers how requests are logged, what each stage means, how offers are reviewed and who owns the system.

The owner gets a dashboard of open design requests and bids by stage, projects in build, stations by contract status, offers out and renewals due, plus a 30/60/90-day roadmap. Next on the list: route planning for service crews and pattern analysis across the station network to spot equipment trending toward failure.

What changes

Design requests stop disappearing into an inbox. Engineers and owners know where their project stands without calling. Every new station leaves commissioning with a complete record and a contract offer already queued. Techs arrive knowing the station. Owners get a report after every visit, the best reminder of why the contract is worth renewing.

The installed base stops being a list of past jobs and becomes a customer base.

What this means for your business

If you build something that needs care for years, the moment you finish it is the moment it should become a service customer.

For a pump station company, that is the station record and map. For an HVAC contractor, the system after installation. For an elevator or fire-protection firm, the inspection cycle.

That is a Bohaus Sprint: six weeks, fixed scope, four phases (Discover, Diagnose, Build, Hand over), and one live system inside the tools you already use, with a trained team, a playbook, a dashboard and a 30/60/90-day roadmap.

Key takeaways

  • For a company that builds and services pump stations, the installed base is the biggest untapped source of recurring revenue.
  • One station record that starts at the first design request and never closes connects sales, fabrication, commissioning and service.
  • AI drafts layouts, maintenance offers and visit reports; engineers, managers and techs review and decide.

The service behind this sprint: AI Tool Selection

FAQ