We build the software businesses actually run on.
Larsen Code Labs is a software engineering company in Phoenix, Arizona. We design and build custom software, websites, web and mobile applications, and AI automation for small and mid-sized businesses — all of it in-house.
Lead Engineer & CTO
A software company, not an agency with developers attached.
Larsen Code Labs, Inc. is a Phoenix-based, fully remote software engineering and development company. We design and build custom software, websites, web applications, mobile applications, and AI-powered automation for small and mid-sized businesses. We were incorporated in Arizona in April 2026 and are led by Michael David Larsen, Lead Engineer & CTO.
The distinction matters more than it sounds. Plenty of companies will sell you a website, then subcontract anything harder than a contact form. Others will advise you on AI and hand you a slide deck. We're the other kind: the engineering is the company, and the person who scopes your project is on the same side of the wall as the person who builds it.
So when a website turns out to need a real application behind it — which happens more often than anyone plans for — nothing gets handed off, re-quoted, or explained to a new team from scratch.
Three disciplines, one team, no handoffs.
Mobile isn't a footnote here and AI isn't a bolt-on. All three are engineering work, and all three are done in-house.
Web design & development
Business websites, online stores, and redesigns — built to convert and, just as importantly, built so you can still edit them next year.
- Custom sites & redesigns
- WooCommerce & Shopify stores
- Core Web Vitals performance
- Accessibility built in, not retrofitted
Web & mobile applications
Custom software for the moment spreadsheets, disconnected SaaS, and manual re-entry stop scaling — and start costing real money.
- Internal tools & customer portals
- Dashboards & workflow systems
- iOS and Android applications
- Integrations with what you already run
AI automation & integration
AI put to work inside real workflows — reading, sorting, routing, and drafting — wired into the systems your business already depends on.
- Document processing & classification
- AI agents & workflow automation
- LLM integration into existing tools
- Human-in-the-loop where it matters
Most projects don't stay in one column. A website grows a customer portal; the portal turns into the system the business actually runs on; somewhere in there a manual process gets automated. Because it's the same team across all three, that progression doesn't cost you a new vendor, a new quote, or three months of explaining your business to someone new.
Client engineering is the business. We also run our own software.
We build products under our own name, and we keep operating them. That means we carry the maintenance, the dependency updates, the support load, and the cost of anything we architected badly — which is exactly why we won't recommend something we'd never have to live with.
Zip2APK
A web and Android application that turns raw Android ZIP and Tar.gz files into installable APKs.
Tonalyzer
An AI tone coach for workplace writing. Reads a draft in Slack or the browser and flags what will land badly before you send it.
BizBooks
Zero-bloat double-entry bookkeeping for independent operators and consulting practices, without the corporate ledger noise.
GovScan
Offline-first verification of government-issued digital credentials, for high-security settings where connectivity is sparse.
Michael David Larsen
Michael started writing code at about twelve, in Lua, building addons for World of Warcraft — because the game didn't do something he wanted it to do.
At roughly eighteen he noticed his hometown had no real computer repair company, so he incorporated one. MadGnome Computer Repair, LLC handled consumer repairs, mobile devices, business technology support, and managed IT — and he ran all of it himself. It's where he learned the thing most developers never have to learn: what it feels like to be the person a business calls when their technology stops working.
From there came four-plus years of corporate IT administration — infrastructure, users, security, and the unglamorous reality of systems that have to keep running long after whoever built them has moved on — followed by six years building software professionally, with an Associate's Degree in Computer Science underneath it.
He incorporated Larsen Code Labs in April 2026 to put those three things in one place: engineering, operations, and having actually run a business. It's why our estimates account for what software costs to own, not just what it costs to build.
- ~18 years writing software, 6 of them professional
- 4+ years corporate IT administration
- Associate's Degree in Computer Science
- Founded & operated MadGnome Computer Repair, LLC
You talk to the engineers building it.
No account managers in the middle, no offshore handoffs, and no discovering halfway through that your project was quietly passed to someone else.
Scope, in writing
We agree what's being built and what it costs before work starts. Fixed scope, signed, so "done" means the same thing to both of us.
Architecture first
How the pieces fit, what it costs to run, and what breaks if you grow. Decided deliberately, not discovered in month three.
Built in-house
Frontend, backend, APIs, integrations, deployment, monitoring. Same team start to finish, in Arizona.
Supported after launch
Software isn't finished when it ships. Somebody stays responsible for it when a dependency moves or the business changes.
Solve the business problem first. Choose the technology second.
That sounds obvious and it gets ignored constantly. Good engineering isn't reaching for the newest thing available — it's picking something appropriate and implementing it well. Sometimes that means a smaller build than the one you asked for. Occasionally it means no software at all, and we'll say so.
The question isn't “where can we add AI?” It's “where can AI reliably improve a process enough to justify the complexity?”
AI earns its place on language, unstructured information, classification, and interpretation. For most other work, conventional automation is cheaper, more predictable, and easier to maintain — and we'll tell you which one you're actually looking at, including when the answer costs us the bigger project.
Everything above is verifiable somewhere else.
Larsen Code Labs, Inc. is a registered Arizona corporation, incorporated April 2026, headquartered in Phoenix.
The things people actually ask.
What kind of company is Larsen Code Labs?
Larsen Code Labs, Inc. is a software engineering and development company. We design and build custom software, websites, web applications, mobile applications, and AI-powered automation and integrations for small and mid-sized businesses. We are not a marketing agency, a design-only shop, an IT support provider, or an AI research lab. Software engineering is the core discipline; web design and AI automation are services inside it.
Who leads engineering at Larsen Code Labs?
Michael David Larsen is the Lead Engineer and CTO of Larsen Code Labs, Inc. He has approximately 18 years of software development experience, six of them professional, plus more than four years of corporate IT administration and an Associate's Degree in Computer Science. He previously founded and independently operated MadGnome Computer Repair, LLC.
Is Larsen Code Labs remote or local?
Both. We are headquartered in Phoenix, Arizona and we work fully remotely. Remote is how we operate, not a limit on who we serve. We work with businesses across the Phoenix Valley and well beyond it.
Who will actually work on my project?
You work directly with the engineering side of the company, not a salesperson and not an account manager relaying messages. Every engagement covers requirements and scope, architecture and system design, frontend, backend and APIs, integrations, deployment and monitoring, and ongoing support. All development is done in-house, with no offshore handoffs.
Does Larsen Code Labs build its own software, or only client projects?
Both, and they are connected on purpose. Client engineering is the business. We also design, build, and operate our own software products: Zip2APK, Tonalyzer, BizBooks, and GovScan. Running our own software means we carry our own maintenance and support, so we are not recommending anything we would never have to live with ourselves.
How will we communicate during a project?
Directly and often, through virtual meetings, email, and messaging, with progress visible as the work moves rather than a status report at the end. Scope is agreed in writing before any work starts, so there is a shared definition of done from day one.
What happens after a project launches?
Software is not finished when it ships. We offer ongoing support and maintenance after launch, so the system has someone responsible for it when something breaks, a dependency changes, or the business needs it to do something new.
How do I choose a software development company?
Ask four questions. Who is actually writing the code, and will you talk to them? What is the fixed scope, in writing, before work begins? What does the price include, and is it published? And what happens after launch? A company that answers all four plainly is easier to work with than one that answers none of them until you have signed.
Tell us what your business is trying to do.
We'll tell you straight whether we're the right company to build it, roughly what it would cost, and what we'd do first.
Contact Larsen Code LabsFree, no obligation — you'll get a real answer either way.