We replace broken systems, modernize aging software, and build practical tools your team can actually use. Custom apps, integrations, and AI automation to name a few, all built around making businesses easier to run.
From the beginning, they built software by sitting down with business owners, learning what was breaking inside the company, and creating practical tools to fix it. Nearly four decades later, that same approach still guides our work: replacing fragile processes, modernizing aging systems, and building software that teams can actually depend on for the years to come.
John and Sam Mikkalson have spent most of their careers inside the family business. Over the years, they learned the business by doing the work: writing code, supporting clients, answering the phone, and solving the kinds of operational problems that slow companies down.
Operations, Architecture, and Systems
John and Sam have spent decades inside Norsoft’s work, not just managing it from a distance. John keeps projects moving from first conversation to launch, while Sam leads the technical architecture behind the systems we build and modernize. Together, they bring continuity, history, and hands-on experience to every client relationship.
Strategy and Growth
Tim helps clients make sense of the problem before anyone starts writing code. He works with business owners to clarify what is broken, what needs to change, and how the software should support the company’s larger goals.
How we are structured
Norsoft is now led by partners who are close to the work and each other. That means decisions are made by the people responsible for the outcome, not passed through layers of salespeople, account managers, or outside investors.
Real numbers from real projects. Not demos. Not proofs of concept.
Built the scoring engine for USAD. Still running after 10+ years.
Read the story →Replaced a failing ERP for a $40M plastics manufacturer. Clean data helped them sell.
Read the story →A vet supply company faced fines. We built and deployed a compliance tool in one day.
Read the story →Most software projects do not fall apart because nobody can write code. They fall apart because expectations get fuzzy, decisions go unexplained, and business owners are left wondering what is happening. That is why we keep communication close to the work. You talk with people who understand the project, know the decisions being made, and can clearly explain the path forward.
Before we recommend a solution, we learn what is actually slowing the company down. The goal is not to sell the biggest project. The goal is to build the right one.
You are not passed through layers of people who cannot answer your questions. When something needs to be discussed, you talk with someone close enough to the project to give you a real answer.
Good software keeps evolving after it goes live. We stay close enough to support the system, answer questions, and help the work keep serving the business.
You'll talk directly with Tim, John, or Sam.
