Kuhn Consulting designs, builds, and hosts custom software: web apps, phone apps, AI tools, and the systems behind them. The first half of this page explains what that means in everyday terms, using products I've built and run. The technical detail your developers will want comes after that.
No jargon here. Each one links to the technical version if you or your team want it.
AI can read a long contract document and pull out every requirement, write a first draft in your company's voice, or answer questions about your own data. I build it to show its work and to wait for a person before it changes anything. In Cairn Federal, nothing the AI proposes takes effect until someone says yes.
Selling software by the month takes more than the software. It needs sign-up, plans, billing, and a guarantee that one customer never sees another customer's data. I build all of it. Cairn Federal went from its first line of code in June to live in July.
Replace the spreadsheet everyone's afraid to touch with an app built around how your team actually works: the screens, the reports, and the data behind them. There's nothing to install. It runs in any browser.
iPhone and Android apps that share their logic with your web app, so a feature built once shows up in both places. They can sign people in with a fingerprint or face, take in-app purchases, send alerts, show maps, and keep working without a signal.
Card payments, monthly subscriptions, and purchases inside a phone app. That includes the unglamorous parts that eat support time if they're done badly: upgrades, pauses, cancellations, refunds, and a record of every transaction.
Your users can sign in with a passkey (the same fingerprint or face they use to open their phone) or with a password plus a code. Sensitive details like tax IDs are stored encrypted, and each customer's data is walled off from everyone else's.
Most businesses run on data that lives somewhere else. Cairn Federal pulls from the government's contract and grant databases. ProvisionSync keeps product details in step with retailers like Kroger and Walmart. I can also open your own systems up to AI assistants, so they look up real answers instead of guessing.
I run the servers too. Updates go out without drama, backups get tested by actually restoring them, and alerts reach me before a problem reaches your customers. If an update goes wrong, it can be rolled back quickly.
Both are live today. I designed them, wrote them, and host them, so they're the clearest picture of what working with me produces.
Cairn Federal helps small businesses find and win government contracts and grants. Before it, the routine was scrolling government websites by hand, tracking opportunities in a spreadsheet, and doing the deadline math in someone's head.
If your business runs on a slow, paperwork-heavy process, this is the pattern I'd bring to it: the AI does the reading and the first draft, and your people make the decisions.
ProvisionSync is one home for a food brand's product information: nutrition facts, ingredients, allergens, photos, and where to buy. When a recipe changes, the brand updates it once and every website that shows it updates too. Stale PDFs and hand-edited nutrition tables go away.
If the same information lives in five places and someone keeps it in sync by hand, that's fixable. You change it once, and everything else follows.
I'll turn your phone app idea into a real app, and it stays your app and your idea. I won't reuse it or build a competing version for anyone else. Here's what the apps I build can do.
A single app for both kinds of phone that shares its business logic with the web version. A feature built once shows up everywhere, and the versions don't drift apart over time.
When an iPhone app should feel completely at home on Apple's platform, I build it natively in Swift. I also maintain a library of ready-made native iPhone screens for sign-in, payments, AI chat, and more, so those parts don't start from scratch.
Passkeys (a fingerprint or face instead of a password), Sign in with Apple, and two-step codes. Sign-in details are kept in the phone's secure storage, so people stay signed in without that information sitting somewhere it shouldn't.
In-app purchases and subscriptions, with every purchase double-checked on the server so it can't be faked. Restoring a purchase on a new phone works too.
Push notifications open the right screen when someone taps them. Maps handle anything location-based, people can talk instead of type, and documents can be attached and shared. Storage on the phone itself keeps the app working without a signal.
Cairn Federal's phone app, which covers nearly every screen of the web version, including the AI assistant answering from live pipeline data. Northway, an AI coaching app you can talk to. TrailForecast, which pairs AI trail-condition forecasts with maps, offline storage, and push alerts.
Most of what a new app needs has already been built, tested, and run in production. That's the Wildwood platform. I built it, and I build on it.
Almost every app needs sign-in, subscriptions and payments, AI chat, notifications, a cookie banner, a feedback button, and document storage. On Wildwood, those parts already exist. Your budget goes to what makes your product different, not to rebuilding the basics.
Cairn Federal and ProvisionSync both run on Wildwood today. When a shared piece gets better for one of them, every product built on it gets the improvement.
The same building blocks exist for websites, iPhone, and Android, and they're checked to behave the same way on each one. A sign-up flow won't quietly work one way on the web and another way on a phone.
Thousands of automated tests run against the platform. Settings are backed up automatically before every change, so a change that doesn't work out can be rolled back.
Big changes go in stages. After each one, an independent AI reviewer checks the work against the plan before the next stage starts, and the whole change gets a final review at the end. Problems get caught while they're small and cheap to fix.
Wildwood can also host the app and its database, with backups and a one-step return to the previous version if an update misbehaves.
Everything above, in the terms your developers or IT team will want: the stacks, the standards, and how it all gets run.
The application side: what gets designed, written, and shipped.
Add AI features that hold up in production, built across the major providers.
Make your existing APIs usable by AI assistants and agents. With Kuhn Consulting's API2MCP platform, your REST APIs become Model Context Protocol (MCP) servers, so tools like Claude can call your services directly. No custom integration code to build or maintain.
Launch a SaaS product that can scale: multi-tenant architecture built for growth, security, and the day-to-day work of running it.
Fast, reliable web applications, built on the proven Microsoft .NET stack.
Native apps for Windows, iOS, macOS, and Android without a separate codebase for each one. I build in whichever stack fits the project: .NET MAUI when the rest of the system is already C#, React Native with TypeScript when the team lives in JavaScript, and Swift with SwiftUI when an iPhone app should be fully native.
Take payments without the headaches: Stripe, PayPal, and in-app purchases, with the full subscription lifecycle handled.
Protect your users and their data with modern authentication: passwordless login, multi-factor security, and enterprise SSO.
Keep users in the loop with reliable, compliant messaging: email, SMS, and real-time notifications across multiple providers.
Build or enhance learning management platforms with 20+ years of e-learning industry expertise and standards compliance.
The local, hands-on side of the practice. On-site and remote technology work for homes and small businesses across Eagle County, Colorado, from Vail down to Glenwood Springs.
Someone still has to run the servers, ship the releases, and keep the whole thing healthy. On most engagements that's me too.
Code that only runs on a laptop isn't finished. I build the hosting underneath an application and then run it in production.
Releases should be boring. Every change builds, tests, and deploys the same way, so shipping stops being an event.
The safest port is the one that was never opened. Access gets designed in, not bolted on after the first incident.
Finding out something broke before your customers do, and being able to put it back.
Most of the time lost on a project goes to integration and onboarding. This is the part that goes after both.
Straight answers about how engagements work.
Not at all: you don't need to know how software works to hire someone to build it, and a good developer should be able to explain every decision in plain English. Tell me what slows your business down, or what you want your customers to be able to do, and I'll handle the technical decisions and walk you through them as we go. Kuhn Consulting can also host and maintain what it builds, so you don't need an IT department to keep it running.
AI integration consulting means connecting your application to large language model (LLM) APIs (OpenAI, Anthropic Claude, Google Gemini, or Azure OpenAI) and building the infrastructure around them: prompt engineering, streaming responses, session and conversation history, cost controls, and per-user usage analytics. Kuhn Consulting builds production-grade implementations, not prototypes.
Model Context Protocol (MCP) is an open standard that lets AI assistants like Claude call external tools and APIs directly. Instead of users copy-pasting data between their tools and an AI, MCP lets the AI query your systems on demand. Kuhn Consulting builds MCP servers that expose your REST APIs as AI-native tools, and also built API2MCP, a platform that automates this for any OpenAPI-documented service.
A minimum viable SaaS backend with authentication, multi-tenancy, subscription billing, and a basic API typically takes 8 to 16 weeks depending on complexity. Kuhn Consulting speeds that up with the Wildwood Platform, a production-tested SaaS backend that already has these pieces built, so new products launch on enterprise-grade infrastructure in a fraction of the time.
Both. Kuhn Consulting builds the application and the infrastructure it runs on: Linux servers, container hosting on Kubernetes, separate staging and production environments, TLS and access control, backups, and monitoring. If you already have a platform team, I work inside what you have. If you don't, I set it up and hand you the runbook that explains it.
It takes the manual steps out of releasing, which is where releases usually go wrong. Every pull request builds and runs the test suite, and a merge only happens if that passes. The change then deploys to staging on its own, and the same verified build gets promoted to production when you're ready. Database migrations run as part of the deploy so environments don't drift, and a bad release rolls back with one command.
Most of it comes down to context, because an AI assistant is only as useful as what it knows about your systems. Kuhn Consulting wires your issue tracker and repository into the development workflow, encodes your API and your conventions as reusable AI skills, and exposes internal services as AI-native tools the assistant can call. The same groundwork that makes an assistant productive makes a new engineer productive, so onboarding tends to get easier as a side effect.
Yes. Kuhn Consulting is based in Eagle, Colorado and works remotely with clients across the United States. Every engagement is handled directly by Mark Kuhn, with no subcontractors or junior developers.
Tell me what you're building, and let's figure out if it's a fit.