Built in Charlotte, Used Everywhere
We've been building apps from Charlotte since 2012. Over 100 products shipped, more than 10 million users served, and a front-row seat to the city's evolution from banking hub to genuine tech ecosystem. Charlotte doesn't always get the recognition it deserves as a tech city — but the work coming out of here speaks for itself.
Here are five projects that represent what we do best: solving real problems for real businesses with software that actually ships.
A Healthcare Scheduling Platform That Replaced 3 Systems
A regional healthcare network in the Carolinas was running patient scheduling across three disconnected systems — one for primary care, one for specialists, and a third for telehealth. Front desk staff spent 30+ minutes per day just resolving scheduling conflicts between platforms.
We built a unified scheduling platform that consolidated all three workflows into a single React Native mobile app for patients and a web dashboard for clinic staff.
The hard part: HIPAA compliance isn't just a checkbox. It shaped every architectural decision — encrypted data at rest and in transit, role-based access controls, audit logging for every patient record interaction, and BAA agreements with every cloud vendor in the stack.
The result: Scheduling conflicts dropped by 87%. Patient no-show rates decreased 23% thanks to automated reminders and easier rescheduling. The clinic staff who used to spend their mornings untangling the calendar now spend that time on patient care.
Timeline: 14 weeks from discovery to launch. Built on React Native with a Node.js backend on AWS.
A Fintech Dashboard for Commercial Real Estate
A Charlotte-based commercial real estate firm needed a way to give their investors real-time visibility into portfolio performance. The existing process involved a monthly PDF report assembled manually from spreadsheets — it took their analyst team two full days each month to produce.
We designed and built an investor portal with live dashboards showing property performance, cash flow projections, distribution history, and document access.
The hard part: Financial data accuracy is non-negotiable. We built a reconciliation engine that cross-references the dashboard numbers against the source accounting system every six hours and flags any discrepancies automatically. We also implemented SOC 2-aligned security controls since investor financial data demands the same seriousness as healthcare records.
The result: Monthly reporting went from two days of manual work to fully automated. Investors check their dashboards on average 3-4 times per month (up from once, when the PDF arrived). The firm closed their next fund 30% faster, citing the portal as a key differentiator in investor conversations.
Timeline: 12 weeks. Web application built with React and a PostgreSQL backend.
A Field Service App for an Industrial Equipment Company
A manufacturer with service technicians across the Southeast needed to replace their paper-based work order system. Technicians were driving to the office to pick up printed work orders, handwriting service reports, and then someone back at HQ was manually entering everything into the ERP system. In 2024.
We built a mobile-first field service app that puts work orders on technicians' phones, captures service data (including photos and signatures) on-site, and syncs directly to the company's existing ERP.
The hard part: Technicians work in warehouses, basements, and rural areas with spotty cell coverage. The app needed rock-solid offline capability — full functionality without a connection, with intelligent sync when connectivity returns. We built a local-first architecture using SQLite on-device with conflict resolution logic for when two technicians touch the same work order.
The result: Data entry time dropped from 45 minutes per technician per day to under 5 minutes. The company eliminated one full-time data entry position (reassigned, not laid off). Service report turnaround went from 3-5 business days to same-day. The technicians — who were skeptical about "another app" — became the biggest advocates after the first week.
Timeline: 10 weeks. React Native with offline-first sync layer.
An AI-Powered Customer Intake System for a Law Firm
A mid-size Charlotte law firm was drowning in intake calls. Potential clients would call, describe their situation to a receptionist, and then wait 24-48 hours for an attorney to review the notes and call back. By then, many had already hired another firm.
We built an AI-powered intake system that conducts an initial conversation via web chat, gathers case details through a structured but natural dialogue, performs preliminary conflict checks, and routes qualified leads directly to the right attorney's calendar with a complete case summary.
The hard part: Legal intake requires nuance. The AI needed to ask the right follow-up questions based on practice area (a personal injury case needs different information than a business dispute), recognize when a potential client is describing something outside the firm's practice areas, and handle sensitive disclosures appropriately. We used a RAG architecture with the firm's own practice area guides and intake checklists as the knowledge base.
The result: Response time to potential clients went from 24-48 hours to under 5 minutes. The firm's client conversion rate increased 34%. The receptionist, instead of spending 6 hours a day on intake calls, now handles only the cases that genuinely need a human touch — about 15% of total volume.
Timeline: 8 weeks including the AI discovery phase and PoC. Built on Next.js with Claude API integration.
A Community Events Platform for a Charlotte Nonprofit
A local nonprofit that organizes community events across Mecklenburg County was managing everything through Facebook groups, email chains, and Google Sheets. Volunteers couldn't find events, event organizers couldn't track attendance, and the leadership team had no visibility into what was working.
We built a community platform — mobile app and web — that handles event creation, volunteer sign-up, attendance tracking, and impact reporting.
The hard part: Budget. Nonprofits don't have $100,000 development budgets, and we didn't want to deliver a stripped-down product that would frustrate more than help. We scoped aggressively, focusing on the three workflows that would have the most impact, and built the platform in a way that could expand over time without requiring a rewrite.
The result: Volunteer participation increased 40% in the first quarter after launch. Event organizers save roughly 5 hours per event on coordination. The leadership team now has a dashboard showing volunteer hours, event attendance trends, and community reach — data they'd never had before.
Timeline: 8 weeks at a reduced rate. React Native app with a lightweight Node.js backend.
What These Projects Have in Common
Looking across these five projects, the pattern is consistent:
- Discovery came first — every project started with a focused discovery phase that defined the real problem, not just the requested features
- We chose boring technology —
React Native,Node.js,PostgreSQL, AWS. These aren't trendy, but they're proven, well-supported, and our team knows them deeply - Post-launch support was built in — every client has a maintenance plan because software isn't finished at launch
- The measure of success was business impact — not features shipped, not lines of code, but real numbers that moved
Charlotte is a great city to build software. The business community here understands execution, values relationships, and doesn't get distracted by hype. That's the kind of environment where good work happens.