Software Development · Minneapolis, MN
Software and AI for Minneapolis Teams That Have to Explain Their Decisions
Minneapolis businesses make medical devices, sell food and goods to the whole country, and serve customers in health care and finance. When a business covered by Minnesota's privacy law profiles a customer to make a significant decision, the customer can ask why. We build custom applications and AI features with that question in the design.
Schedule a call for your Minneapolis project →What does Minnesota's privacy law mean for AI and automated decisions?
Since 31 July 2025, a Minnesota consumer profiled by a covered business in a decision with legal or similarly significant effects can question the result, be told why, review the data used and have errors corrected and the decision re-evaluated. Software that makes such decisions should record its inputs and reasons, and be able to run again.
Designing for the right to question a decision
The Minnesota Consumer Data Privacy Act covers businesses that control or process the personal data of 100,000 or more Minnesota consumers a year, or of 25,000 or more while earning over 25 percent of gross revenue from selling personal data. Its exclusions include chartered banks and credit unions, insurance companies, protected health information under HIPAA and, for most of its duties, small businesses. For a covered business, the consumer's rights after a profiling decision are specific: question the result, learn the reason, find out where feasible what they could have done to get a different outcome, review the personal data used, and, if that data was wrong, have it corrected and the decision reconsidered.
Each of those maps to features we can scope per engagement with your counsel:
- →Keep a decision record. What data went in, which rules or model produced the result, and the reason given, stored with the decision.
- →Produce a plain reason. Reason codes a staff member can read out, rather than a score with no explanation. We have built underwriting that returns reason codes.
- →Let a person review it. A queue where a challenged decision lands with its record attached, for a human to look at.
- →Re-run on corrected data. The same decision logic, applied again once the data is fixed, with both outcomes kept.
Whether a given feature counts as profiling with significant effects is a question for your counsel. We scope it with them in the design phase, because adding a decision record after launch is much harder than building one in.
Health, life sciences and medical devices
Greater MSP lists health and life sciences among the region's key industries and points to its large medical device workforce and to a major health insurer among its largest companies. The health software we build is the business side: prior authorization, patient intake, scheduling and patient communication. If a project handles protected health information, we sign a business associate agreement for it and build the system to HIPAA's safeguards. More on the healthcare page.
Food, retail and the companies headquartered here
The same partnership lists food and water, and headquarters and business services, among the region's key industries. For consumer brands and distributors, that tends to mean order, inventory and storefront work, including Shopify stores and Stripe payments (see e-commerce). For large corporate teams, it can mean added engineering capacity next to an in-house group; see staff augmentation.
Financial services and insurance
Greater MSP also names financial services and insurance. The Minnesota act excludes insurance companies, chartered banks and credit unions, and data handled under the federal Gramm-Leach-Bliley Act, so section 1 may not reach many of those firms; your counsel decides. Our fintech page covers the fraud, onboarding and underwriting work we have built.
Services we offer in Minneapolis
AI Implementation
Custom AI systems built around your existing workflows. Average 30–60% reduction in manual process costs.
Learn more →AI Workflow Automation
Automation pipelines built around the systems you already run, eliminating manual data entry and cross-system copying.
Learn more →Legacy Modernization
Replace outdated software with modern, maintainable code.
Learn more →Custom Software Development
Full-stack web apps, APIs, and integrations built to your spec, from MVP to enterprise-grade production systems.
Learn more →How an engagement works
01
Workflow Audit
We map your existing processes against current AI capabilities in the 90-minute AI workflow audit, identifying exactly where automation creates measurable ROI. The audit is complimentary when it is bundled with a larger build and available as a paid one-off on its own.
02
Build Sprint
A scoped build against a written scope. Prototype, staging, and deployment milestones are agreed in the written scope. Most large builds are fixed-price, with a monthly retainer after launch.
03
Launch + Support
Deployment and handover. Post-launch support and maintenance are scoped per engagement.
Common questions from Minneapolis businesses
Does the Minnesota Consumer Data Privacy Act affect an AI feature we are planning?
It may, if your business is covered by the act and the feature profiles consumers in decisions with legal or similarly significant effects. Then a consumer can question the result, be told the reason, review the data used, and have errors corrected and the decision re-evaluated. Your counsel decides whether it applies; we scope the records and review steps it would need during design.
Can you build AI that explains its decisions?
Yes. Depending on the engagement, the scope can include stored inputs and reasons for results, reason codes a person can read, and a queue for challenged decisions to reach a human reviewer. We agree which records and review steps are needed with your team during design.
Do you build for health insurers and medical device companies?
We build business software for health organizations, such as prior authorization, patient intake and scheduling. Any part of that work touching protected health information runs under a signed BAA and follows HIPAA's safeguards.
How long does an AI feature take to build?
A quick AI implementation takes 2 to 4 weeks, and longer, up to months, depending on complexity. Decision records and a review queue are scoped per engagement.
Minneapolis is on Central time. How does that work with a South Carolina company?
Mt Pleasant, SC, where we are based, is one hour ahead of Minneapolis: 9am in Minneapolis is 10am in Mt Pleasant.
Ready to start your Minneapolis project?
Book the 90-minute AI workflow audit. The audit is complimentary when it is bundled with a larger build and available as a paid one-off on its own.
Schedule a call for your Minneapolis project →