Skip to main content

Custom software for Portland businesses

A service agreement signed with a plant in Hillsboro turns into visits on a schedule, parts off a van and a report after each call. One tool can carry it from signing to renewal.

Software for firms that service other people's equipment

A customer with a plant in Hillsboro may have others in Washington and Idaho, and would rather have one service partner and one record for all three. Sooner or later that customer asks its Portland-area service firm to look after the Tacoma site too, or the one in Boise. What keeps a firm with ten technicians from saying yes is seldom the technicians. That customer wants a report after every visit and the year's history on request, and a firm assembling those by hand cannot add sites in another state.

The work behind those reports sits in a calendar, a spreadsheet and email. Each customer's agreement sets its own visit schedule, and somebody rereads it to learn what is owed. The plant in Hillsboro, the port and the hospital each expect their report when the visit ends, so technicians write them in the evening. Parts leave the van without leaving the stock sheet. At year's end a customer asks for every visit and every part, and the office digs them out of sent mail. A technician crosses the river twice in a day because nobody saw the two calls together.

We would build the agreements, the schedule, the van stock and the reports into one program, and the customer notices the change first. Their agreement lists the visits owed. Their report is built from what the technician entered on site and reaches them once the technician has signed it. Their history sits on a private page they can open themselves. Parts used come off the van's stock and onto the reorder list. An agreement nearing its end appears on a list with the visits made and the parts used, and the renewal price is yours to set. Field-service products exist, and we look at what you already pay for first. Scope and price are fixed in a brief before building starts. When the customer's Tacoma or Boise plant is added, its visits land in the schedule your dispatcher already opens each morning, and a technician based near that plant files reports as the ten around Portland do.

What you receive

  • Internal tools that replace spreadsheets and manual steps.
  • Customer portals where your clients see their own information and act on it.
  • Connections between systems that do not talk to each other.
  • A first product, from an idea to a release real users can try.

How it runs

  • We map the work: who uses it, what they need to get done, the records and rules involved.
  • We define the smallest useful release and check whether an existing product can do part of the job.
  • We build in pieces you can review, testing real tasks, permissions and what happens when something fails.
  • We release and hand over, with operating notes and a plan for what comes next.
Everything that is included

Scope and investment

Start with the brief: $2,500. We write down what the software has to do, list the screens and give you a fixed price and a timeline. The $2,500 is credited in full when you complete the build with us.

Work you can inspect

The Tucker CPA website home page, built by Butler Agency

Tucker CPA

We built the brand, the website and a national content system for a new CPA firm, and we handle its SEO.

Read the case study
The Beyond the Bedside Foundation website home page, built by Butler Agency

Beyond the Bedside Foundation

A website for a new children’s foundation, built for families, student volunteers and supporters.

Read the case study

Questions before we start

A customer asks for the whole year's visit records at the end of every year. Can they get them without us?

Yes. Each customer gets a private page with their sites, the visits made and each report. It answers the end-of-year request without anyone in your office assembling it.

Our technicians work inside secure plants in Hillsboro. Can they use a phone to log a visit?

Where phones are allowed, yes. Where they are not, the technician enters the visit on leaving the site, and the tool is designed for that. We ask about each site before building.

We have customers in Hillsboro and in Vancouver. Can the schedule keep a technician from crossing the river twice in a day?

Grouping by site is there for that. Visits owed are laid out by location, so two calls on the Washington side show up together and one technician can take both. Your dispatcher still decides who goes.

What would you like your business to do next?

Tell us where the work gets stuck or where you want to grow. We will help you choose a practical first step.

Discuss your project