Miles IT and the art of keeping work moving

At Newman & Company, a paperboard manufacturer, important updates traveled in envelopes. Employees printed information and left it around the facility. Behind this paper relay sat an aging application whose developer was retiring. The software had become difficult to maintain. The business still needed to make paperboard, ship orders, and understand what was happening on the floor.

Here was a technology problem with a wonderfully human complication. The manufacturer wanted its replacement software to look and feel like the system people already knew. Progress, in this case, needed a familiar face. Miles IT took on the job.

The envelope is the clue

In its account of the project, Miles describes visiting the manufacturer and interviewing employees to understand the logic behind their tasks. Industry software had been considered and rejected as a poor fit. The assignment was to preserve useful business knowledge while replacing a fragile technical foundation.

The resulting system connected order handling and production information, reduced manual work, and made operating data easier to access. The company describes an ongoing relationship extending beyond eight years. The interesting decision came before the code: treat the existing workflow as evidence. A workaround can contain knowledge that a tidy software specification misses.

“We have real-time information access, which we’ve never had before”

Customer quotation / Newman & Company case study

For another business owner, the exercise is available immediately. Follow one order. Count every re-entry, printout, and handoff. Ask why each exists. That is an editorial lesson from the case, rather than a promise that every envelope conceals a profitable software project.

The builder behind the business

Chris Miles came to technology through construction. In a 2020 interview, he described using computers to run his own construction company, then noticing that business owners wanted someone who understood both technology and the practical demands of running a firm. He started Miles Technologies in his basement in 1997.

His recollection includes an early mistake: wiring a health club incorrectly, producing a connection that worked only intermittently, then returning to fix it. The anecdote is useful because it makes competence a process. Something can appear to work and still fail the people depending on it.

Today, that practical breadth is visible in the service menu. Miles IT maintains networks, develops applications, builds websites, and runs digital marketing programs. Its customers span manufacturers, healthcare organizations, professional services, construction businesses, and other sectors. Legal services are one part of the mix.

A document’s unnecessarily long journey

At Imedview, a claims and litigation services business, the problem was repetitive document handling. Staff spent hours downloading, saving, and assembling packages. After investigating packaged software, the company chose a custom system. Miles IT developed Viewpoint, with document queues, automated task handling, templates, and checks against duplicate data.

Imedview’s own website now presents Viewpoint as its proprietary platform, offering clients access to case information, documents, and updates. Its history dates the client launch to 2020. That distinction matters: the useful output of a development project is something a customer can keep using as part of its business.

The two cases suggest where Miles fits. It can serve organizations whose operating details are too particular for a straightforward software purchase, but whose leaders also need somebody to maintain the result.

The monthly business of fewer interruptions

Custom development is only one entry point. The Miles Assurance Plan bundles managed IT support, proactive maintenance, and cybersecurity on a month-to-month basis. The company advertises around-the-clock helpdesk coverage and remote and onsite assistance. Customers with an internal IT department can instead use co-managed services to add capacity or specialist help.

On the software side, Support & Advance provides maintenance and enhancements, including for applications built elsewhere. Marketing adds another recurring relationship, covering search visibility, advertising, content, and conversion work. The business model mixes ongoing services with scoped projects.

What does it cost? Clutch lists a minimum project size of $10,000 and an hourly reference band of $100 to $149. Those directory figures are buying signals, not a quote for the Assurance Plan or either featured software project. A sensible comparison needs the actual scope, support obligations, and cost of keeping a system useful.

Against separate providers for infrastructure, code, and marketing, Miles offers a broad relationship. The potential advantage is less coordination for the customer. Breadth alone cannot establish quality; the relevant question is who accepts responsibility when a problem crosses those boundaries.

The practical buying test is to make that responsibility explicit. Ask who owns the source code, how another team could take over, what happens during an outage, and which changes count as additional work. A monthly relationship can make improvement easier to organize, but the agreement still has to describe the job.

Continuity needs a business model, too

Miles says it remains owned by its founder and family trusts, with succession planning intended to preserve continuity. Its remote-first approach still includes visits to customer sites. Training through Miles University supports the same proposition: knowledge should survive the absence of a particular person.

There is a practical limit to custom work. If a packaged application already fits, commissioning a bespoke replacement adds maintenance responsibilities without necessarily adding value. A buyer also needs employees willing to explain their work, someone empowered to make decisions, and a budget that extends beyond launch. These are implications of the projects, not reported failures at Miles.

There is also a distinction between repairing today’s bottleneck and preparing for tomorrow’s. A faster document queue solves one problem. A maintained application, documented decisions, and backup expertise address another. The company’s appeal rests on connecting those jobs, giving a customer somewhere to return when the next operational wrinkle appears.

The envelopes are a useful place to end. They carried information the factory needed, using a process people understood. Improving that process required curiosity about why it existed. For businesses considering Miles IT, that is the question worth borrowing: where does useful work stop moving, and who understands enough to get it going again?