Skip to main content

Custom software for Twin Cities shops and offices

The week before a device maker audits your Twin Cities shop, you search a binder, a spreadsheet and one person's memory. We build the job record that makes that week ordinary.

Software for Twin Cities shops and offices

A medical device maker that buys from a Twin Cities machine shop judges the shop on its records as much as its parts. Its auditor wants to see which job a part came from, who inspected it, against which drawing revision, and what changed between the quote and the shipment. The auditor asks for the record itself and expects it to agree with the one beside it.

Behind that customer is a shop of a few dozen people where traceability often lives in a binder, a spreadsheet and one person's memory. What the auditor needs from such a shop is not a factory system. It is a job record that follows the part from quote to shipment, an inspection log that cannot lose a page, or a connection between the quoting spreadsheet and the accounting package. The customer's audit list decides the design: with the quality lead, we write down which records are audited, the rules each must follow and who in the shop may see it, before anything is built. The quality lead decides what counts as a finished record, and anything the tool cannot tie to a job waits for that person. Work starts from a brief that fixes the scope and price of the build, then one release the shop can try, after we check whether a product it already owns can do part of the job. An office near the plants gets the same approach for the two systems someone now bridges by retyping.

Today the shop's parts travel across the metro, to a customer close enough to visit. Its records can be read much farther away. A buyer in Milwaukee or Chicago, or at a device company on either coast, asks for the same proof the current customer does. That buyer can receive it with the quote, drawn straight from the job record, without making the trip. A binder cannot be sent that way. A customer won at that distance adds jobs to the system, and the tool is built so the office's paperwork does not grow at the same rate.

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

Our customer audits us. Can the software produce what the auditor asks for?

That is the first requirement we write down. We collect the records and reports your customer's auditor asks for and build the tool so they come out of the daily work, not out of a scramble the week before.

Our quotes live in a spreadsheet and our invoices in an accounting package, with an older ERP between them. Do we have to replace any of it?

Usually not. We look at what each one can export and accept and build the link around them, so an accepted quote becomes a job and an invoice without retyping. Replacing the ERP is a bigger decision than a first project should force.

Our customers' drawings are confidential. Where would the job records be kept?

On hardware Butler Agency owns. What the software may read is agreed in writing before it reads anything, and the proposal states who has access and how you get everything back if we part ways.

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