CompuNet and LINKnet
LINKnet
At nineteen I started LINKnet in Lake Havasu City, a town of 30,000. Getting the service running meant finding a location, arranging carrier contracts and financing, and configuring the hardware and software. Commercial rack-mount modems cost too much, so I built custom racks for 48 external modems.
The people helping me covered support, the website, and the desk, with everyone taking on whatever needed doing. We opened in May 1995, and I ran the business until selling it in summer 1997.
A small business makes the relationship between the machinery and the people very visible. Custom modem racks helped make the service affordable, but support, billing, and the work at the desk still had to fit around what we built. I was learning how much of a technical decision is carried by someone who was not in the room when it was made, and how much useful knowledge sits with the person who has to explain a problem to a customer.
The custom modem racks made LINKnet affordable to start. When I assess that kind of decision now, I weigh the purchase price against the work of diagnosing faults, helping customers, and keeping the service running when its builder is unavailable. A low purchase price does not tell you how much attention a system will need. The useful question is whether the people operating it have the information and support to carry that responsibility.
The people covering support and daily operations need a part in those decisions because they will discover consequences that are difficult to see from the equipment rack. Their experience can change the design before those consequences become normal working conditions.
I judge a technical shortcut partly by who inherits the inconvenience. If I save money on hardware but leave the person at the desk unable to answer a customer's question without finding me, some of that saving has been paid for by their time and confidence. There are circumstances in which that is the only affordable starting point, but I should recognize the dependency and make a plan to reduce it.
I build companies so they stop depending on their founding engineer. Early on a business may need that person intensely; as it grows, other people's ability to run and improve the service is part of what the founder has to build.
CompuNet Credit Services
At CompuNet I moved the whole operation into a web application in 2000, a decade before that became the norm in freight. The company sold credit information that carriers used when deciding who to haul for, and its ability to grow depended on how efficiently it could collect that information and make it available to customers. Bringing data collection, report ordering, and delivery into the same platform made it easier to turn that information into products for both sides of the market.
The existing dBASE application was crashing daily. I first built an interim application in Access, then developed the central web application using ASP, SQL Server, and IIS. Updates happened on the server, and workstations no longer needed a desktop database license. This moved the business through several generations of technology while giving staff a common application for their work.
Collecting and requesting the data
For the call center, I built keyboard-driven data entry with validation as staff typed, so they could collect information without continually switching to a mouse. Brokers could follow a link to update their own profiles, reducing the amount of data collection that had to pass through the call center. The web interface covered report requests as well as data entry, making it easier to get information into the business and to the people who needed it.
Automated fax reporting was integrated into that platform. Customers could still order by telephone and receive a fax, while a shared queue managed requests, generated PDF reports, and retried failed deliveries. Staff could follow up when a report could not be delivered, and email later became another delivery option.
A marketplace for carriers and brokers
The original reports let carriers assess how brokers paid. We added Carrier Profile so brokers could assess carriers' service and professionalism, creating a two-sided information marketplace. CompuNet could sell information to both groups to help them decide who to work with, extending the business beyond credit reports for carriers.
The company grew to around 300 people and reported $5,292,770 in revenue for the year ended 30 June 2004. I had left in May; First Advantage acquired CompuNet that November for $18 million.
I returned for a separate follow-on consulting engagement in 2005.
The significance of moving CompuNet to the web was that collecting information and asking for a report could become parts of the same operation. Staff, brokers, and customers could participate directly in different parts of that process, and the information could support products for both sides of the market. The interface mattered because it changed who could do the work and what the business could sell, well beyond changing how an existing report arrived.
At CompuNet I would distinguish the initial need to stabilize an unreliable application from the opportunity to change the information business. A replacement can be justified by reducing operating risk; a broader investment needs a case for the work and products it makes possible. I would assess those purposes separately so that fixing the immediate problem does not become the limit of the plan.
At CompuNet, the web platform brought collection, requests, and delivery together, while the products expanded to serve carriers and brokers. In a market where timing matters, that change in the operating model is a more useful measure of the work than how new the technology was.
Before I back a modernization, I ask what the business will be able to do afterwards. Replacing an unsupported platform or cutting risk can be reason enough, and I say so plainly. A new interface on the same constraints is a different proposition from changing how information enters the business, how customers request it, and which products can be sold.
The CompuNet work matters to me because those changes were connected. The opportunity came from treating the application as part of the information business and understanding how the people on both sides could participate. The commercial timing was part of the technical judgment, particularly in an industry where being years earlier changes what is possible.
Who did what
I handled LINKnet's business setup and technical systems with help from the people covering customer support and day-to-day operations. At CompuNet I built the initial applications and infrastructure as my role developed into chief engineer and CTO. Later I hired programmers and worked with a full-time database administrator, handing over the running systems so I could develop new products.



