About
Parka Software is a boutique .NET consultancy in Minneapolis. Twenty years of work across enterprise integrations, legacy migrations and custom applications, concentrated in two industries: healthcare and law. The technical problems vary. The underlying patterns repeat across both: disconnected systems, data quality gaps, outdated platforms that still run something critical.
Healthcare engagements have included data visualization platforms for federally mandated registries, interactive clinical reporting tools and patient-facing outcome interfaces, built for the Scientific Registry of Transplant Recipients, HRSA, and the United States Renal Data System at NIH/NIDDK. These applications present complex statistical data to non-clinical audiences and require careful handling of confidence intervals, cohort sizes and display logic. The same underlying data needs different treatment depending on whether the end user is a clinician reviewing center performance or a patient evaluating treatment options.
Legal engagements have included AmLaw 200 firms, document management integrations and full-text search platforms built for legal research workflows. The constraints in that domain are consistent: strict confidentiality requirements, complex entity relationships between clients, matters and documents, and users operating under time pressure who need tools that work without friction.
Public-sector and enterprise work runs alongside both, including the migration of the Minnesota Secretary of State's official website from Umbraco 7 to 14 and .NET Framework to .NET Core, and event and membership systems for AGC of Minnesota.
Working across multiple organizations in the same industry builds a kind of pattern recognition that's hard to get any other way. The same integration problem that shows up at one law firm has usually shown up at a few others in a slightly different form. That means less time relitigating decisions that have clear answers and more time on the problems that are actually specific to your situation.
Why it's structured this way
The standard consulting model separates the person who sells the work from the people who do it. That separation is what makes an agency scalable, and it is also what produces the experience most people have had: a sharp first meeting, a contract, and then a team you didn't meet building from a specification that lost the reasoning somewhere in the handoff.
Parka Software is built to not do that. Engagements are limited in number so that the engineer who scopes the work is the engineer who executes it. When a project needs more capacity than one person, it comes from engineers who have been worked with directly, and you know who they are and what they own before they start.
The tradeoff is real and worth stating: this firm cannot staff twelve people against a deadline. If that's the requirement, a larger shop is the right answer and you'll hear that in the first conversation.
Where AI fits
AI tooling is used heavily in this work, and it should be. It has genuinely compressed timelines. Work that used to take weeks often takes days, and that changes what a fixed scope can include and what an engagement costs.
What it has not changed is the judgment layer, and that distinction is worth being precise about rather than defensive about. A model can write a data access layer. It cannot tell you that the outcomes for a center with eleven cases must be suppressed rather than charted next to a center with four hundred. It cannot tell you which three billing integrations will break when the document management platform is upgraded, because that fact exists only in your environment. It cannot tell you that the binding constraint on your project is a security review board rather than a sprint. That knowledge comes from having been inside these systems before.
The net effect has been to make a firm this size more competitive, not less. The overhead that used to be necessary to deliver at this scope isn't necessary anymore, and clients get the benefit of that directly.
It has also produced a new category of work worth naming: systems written quickly with AI assistance, shipped to production, and now unchangeable because no one on staff can say what depends on what. That work is project rescue with a different origin story, and there is going to be a great deal of it.
Minneapolis
Based in Minneapolis, engaged nationally. Most work is remote. If you're local and want to talk through a project before committing to anything formal, happy to meet in person.
Working on something?
Describe the project and the problem. We can figure out together whether it's a good fit.
Get in touch