Hiring an app development company in Minnesota: AI apps under the MCDPA

Minnesota has its own broad privacy law, and it covers AI decisions too. If you plan to build an AI app for Minnesota customers, that law shapes what the app must do.

This guide explains the law in plain words, gives AI app ideas that fit Minnesota industries, and lists the state programs that help. It ends with the questions to ask any app company before you hire it.

What does the Minnesota small business base look like?

The SBA Office of Advocacy's latest state profile came out in 2025, using 2022 Census data. It counts 560,428 small businesses in Minnesota. They employ about 1.3 million people, or 45.8 percent of the state's workers.

These are the top industries for small business jobs:

Industry	Small business employees
Health care and social assistance	225,087
Accommodation and food services	144,092
Manufacturing	130,620
Retail trade	109,142
Construction	106,925

What an experienced developer or agency actually charges

Skip the noise from junior freelancers and offshore bidding sites, they are not what you are really comparing when you are hiring for a real project. Here is what the experienced end of the market actually costs in the US.

• An experienced, independent developer typically charges $100 to $150 an hour, and AI, cloud or security specialists often charge $150 to $200 an hour or more.
• A US development agency, billing a blended rate that covers a developer, a designer and a project manager, typically runs $150 to $250 an hour, sometimes higher in major tech hubs.

Both of those are hourly, which means the final bill depends entirely on how long the work takes, and that is exactly the part neither you nor they can know for certain at the start. It is also why I do not price by the hour at all.

What does the Minnesota Consumer Data Privacy Act require?

The Minnesota Consumer Data Privacy Act, or MCDPA, took effect on July 31, 2025. The Attorney General enforces it.

Who has to follow it?

The law covers firms that do business in Minnesota and meet either test below.

• Volume test: They handle the personal data of 100,000 or more Minnesota residents.
• Data sale test: They handle data on 25,000 or more residents and earn over 25 percent of revenue from selling personal data.

A small business, as the SBA defines it, is left out of most of the law. There is one catch. Under section 325M.17, a small business still must not sell a person's sensitive data without that person's prior consent.

What rights do people get?

Minnesotans can see, correct and delete their data. They can get a list of the third parties that received it. They can opt out of data sales, targeted ads and profiling.

The AI part matters most for app builders. People can opt out of profiling used for automated decisions with legal or similar effects. Examples include decisions on housing, insurance, jobs, health care and loans. People can also question such a decision, ask why it was made, and ask for a review if the data was wrong.

What does that mean for your app?

• Explain decisions: If your AI scores or screens people, your app must be able to show the main reasons for a result.
• Keep a data inventory: Section 325M.16 asks covered firms to keep an inventory of the data they manage. Plan the database so this list is easy to produce.
• Handle requests: Build simple screens for staff to export or delete a person's data.
• Secure the data: The law asks for reasonable security practices.

The 30-day grace period to fix problems before enforcement ended on January 31, 2026. After that date, the law no longer requires a warning before action.

Does Minnesota have other AI laws?

In 2026, Minnesota passed a law against AI "nudification" tools. These tools turn photos of real people into fake nude images. The bill was HF 1606, and it became Chapter 72 of the 2026 session laws. Governor Walz signed it on May 7, 2026, and it took effect on August 1, 2026. It bans websites and apps from letting users make these images, and it bans ads for such tools. The Attorney General can seek fines of up to $500,000 for each use.

xAI sued to stop the law. A federal district judge refused to block it in September 2026. Then on October 2, 2026, the 8th Circuit Court of Appeals granted xAI's request and put the law on hold while the case goes on. If you build any app that edits photos of people, block this kind of output anyway.

The federal government is pushing back on state AI rules too. A December 2025 executive order, EO 14365, created a federal team to bring court cases against some state AI laws. The MCDPA is a privacy law, and it still applies in full.

What Minnesota programs help businesses build technology?

• Minnesota SBDC: The state's Small Business Development Centers have nine main regional offices plus satellite centers.
• DEED startup support: The Department of Employment and Economic Development runs a startup program with a Startup Showcase, Friday Forums and a Small Business Digital Toolbox.
• Angel Tax Credit: This credit rewards investors who put money into startups built on new proprietary technology. The credit goes to the investor.

How do you choose an app development company in Minnesota?

Ask questions that test both skill and care with data:

• MCDPA: How will my app handle access, delete and opt-out requests?
• AI decisions: If the app scores people, how will it explain a result?
• Proof: Can I use an app you have shipped that has real users?
• Ownership: Will the code, the hosting and the AI accounts be in my name?
• Support: Who fixes problems after launch?

My guide on how to build an AI app walks through the steps.

Is a local Minnesota team better than a remote one?

A local team in Minneapolis or St. Paul can meet you in person. A remote team can do the same work if it shares progress every week and knows the MCDPA. Judge each team on shipped work, clear contact and how it treats your data.

Which businesses in Minnesota benefit most, by type

Software and AI are not just for large companies. Here is how different kinds of businesses in Minnesota tend to use them, so you can see where you fit, whichever end of that list you are on.

Healthcare and medical technology

Minnesota has one of the deepest medical device and healthcare clusters in the country, with careful, compliant software needs.

Retail

Home to several major retail headquarters, with a wide supplier and service base needing its own internal tools.

Agriculture

A genuinely significant part of Minnesota's economy, with steady demand for tracking and logistics tools.

Manufacturing

A steady source of demand for production and inventory tools across the state.

Founders building and launching a new product

If you are not running an existing business at all, you are building one: this applies just as much to you. A lot of what I do is exactly this, taking a founder from an idea, or a rough first version, to something real people can actually use and pay for. You do not need to be technical, and you do not need a co-founder who writes code. You need someone who takes the idea seriously, asks good questions, and builds the smallest version that proves it works.

Local retail and restaurants

Online ordering, loyalty programs, or a simple AI agent that answers the questions customers ask most, these are small builds with a fast, visible payoff.

Trades and home services

Plumbers, electricians, contractors and similar businesses usually just need scheduling, quoting and job tracking that does not depend on a whiteboard or a notebook in a truck.

Professional services firms

Small accounting, legal and consulting practices need client portals and document tools built around how they actually work, not a bloated enterprise platform.

How a typical agency or freelancer works

It helps to know what you are comparing before you pick anyone, so here is the standard model, honestly.

An agency usually assigns you an account manager, who is not the person writing the code. Your project is scoped, then billed by the day or the hour, and the price tends to grow as the scope becomes clearer, which is often after you have already signed. You might talk to two or three different people across the project, and if one of them leaves, someone new picks up where they left off, at your expense while they get up to speed. For a well-funded company, that structure can work fine. For an owner-run business, you are usually paying for layers you do not need.

A freelancer solves the overhead problem, often at a lower price, but creates a different one: they are one person, usually juggling several other clients at the same time as yours. Replies can be slow exactly when you need them fast, and if they get busy, sick, or simply move on to a bigger contract, your project waits. Ownership of the code and accounts is not always clearly settled either, worth confirming before you sign anything, with anyone.

How I work instead, and why

I think the standard model is built to make projects bigger and slower, not better, because most of the industry is paid by the hour or the day. I am not. Every project I take on is priced once, fixed, in writing, before I touch anything, so finishing fast is in my interest as much as yours, not a cost to me.

That belief shapes everything else. I work directly with you, from the first call to launch and after, there is no account manager and no handoff. I plan the smallest version that actually proves the idea or fixes the problem, build it, and test it on your real examples before anyone relies on it. If a cheaper software subscription would genuinely solve your problem better than a custom build, I tell you that on the first call, even though it costs me the job. And the code, the domain, the hosting and every AI account sit in your name from day one, not mine, so none of this depends on me staying available forever.

In practice, a project runs like this: one call to understand the real problem, a fixed price and a written plan, a small first version built and tested on your real data, weekly updates so you always know what is next, launch together, and the Owner's Manual handed over at the end, a plain-language document explaining how everything works so any developer could pick it up if they ever needed to.

What matters	A typical agency	A typical freelancer	Me
Who you talk to	An account manager	One person, often stretched thin	Me, directly, every time
Price	Day rate, tends to grow	Cheaper, less predictable	Fixed, in writing, upfront
Code and account ownership	Check the contract closely	Usually you, confirm it	You, always, from day one
After launch	A new, separate contract	Depends on availability	A Care plan, or fixed-price fixes whenever you need them

What projects typically start at

As a broad reference: fixes and finishes start at around $1,500, and a new build starts higher, always a fixed price agreed in writing before any work begins, never a day rate. My AI app cost guide covers what actually moves that number.

Mistakes owners in Minnesota make when hiring a developer

I have been brought in to fix enough of these to know they are the usual suspects.

• Starting work without a price in writing. "We will figure out the scope as we go" is how a small job quietly becomes a large one.
• Not confirming who owns the code and the accounts. Ask this before you sign anything, not after you want to leave.
• Choosing the lowest hourly rate. A cheap rate with no fixed scope almost always costs more in total than a fixed price from someone slightly more expensive.
• Skipping a real test before launch. An AI feature that was never tested on your actual customers, documents or questions will embarrass you in front of them instead.
• Forgetting the monthly bill. Hosting and AI usage cost something every month, forever. Ask for a real number before you launch, not after the first invoice surprises you.
• Building the whole thing before anyone outside the company sees it. A smaller first version that real people use beats a bigger one that launches six months late.