# Software development in Charlotte, NC > Charlotte is the second-largest banking centre in the United States by assets, with energy and a growing fintech layer around it, and the buying culture is conservative, audit-first and unimpressed by a demo. If that describes your company, it describes how we build. Canonical: https://www.techfabric.com/custom-software-development-charlotte Serving: Charlotte, Concord, Gastonia, Rock Hill, Winston-Salem, Greensboro Headquarters: 1530 E Williams Field Rd, Ste 201, Gilbert, AZ 85295. No office in Charlotte. --- ## Why Charlotte work is our work Your lending or servicing system has outlived three teams, and the change the business wants is stuck until you hire engineers who understand it. Our senior engineers join your team, work in your codebase and put policy checks in front of every change instead of piecing them together from logs afterwards. The bank towers along Tryon Street hold software to that standard, and so does a distributor's ordering platform along I-85. ## Dynamics 365 consultants in Charlotte Charlotte's manufacturers and energy contractors, the motorsports engineering shops around Concord and Mooresville, and the firms serving the banks in Uptown run Dynamics 365 Business Central and CRM under the same audit expectations as the lenders they work with. We implement both with approval workflows in Power Automate and reporting in Power BI that reconcile to the ledger without a spreadsheet in between. [Dynamics 365 consulting in Phoenix](https://www.techfabric.com/dynamics-365-consulting-phoenix) ยท [Power BI consulting in Phoenix](https://www.techfabric.com/power-bi-consulting-phoenix) ## Work a buyer here would recognise The iLending work automated lead and loan officer assignment, rate sheet processing and stipulation document management, and improved CRM integration and API performance. Manual errors dropped and agent onboarding got faster, which is what a bank's lending operations team wants from automation sitting on the path of a credit decision. ## The regulator asks about the model Bank of America and Truist both keep their headquarters in Charlotte, and banks of that size answer to SR 26-2, the model risk guidance the Federal Reserve, the OCC and the FDIC issued in April 2026 to replace SR 11-7. It takes a risk-based approach tailored to each bank's model risk profile, and at a bank this size the automated credit and fraud decisions are the ones model risk looks at first. ## Questions ### How do you handle model risk management? An automated decision records what it was given, what it decided and under whose authority, because a bank's model risk team will ask for exactly that, whatever the regulators' guidance says is in scope. Explainability is designed in, since a system that did not record its reasoning cannot have it added later. ### Do you have an office in Charlotte? The office is in Gilbert, Arizona, with teams in Amsterdam, Dnipro and Hyderabad. Delivery is remote or hybrid, and we travel for discovery, workshops and the opening weeks of a build. ## What software development covers ### Web applications Applications built to be changed safely years after the original team has moved on. That means tests that mean something, seams where the business logic can move, and a deployment nobody is afraid of. ### Mobile applications iOS and Android, built as products rather than as ports. The maintenance story is decided at the start, while it is still cheap. ### APIs and integration The seams between systems, done once and properly. Most of the expensive failures we are called into are integration failures wearing another name. ### Data platforms The layer underneath the application, on Databricks, Azure, AWS or Google Cloud. If the reporting and the application disagree, the platform is the reason. ### Modernisation of what exists Often the work arrives as something already built that has become hard to change. We would rather read it and tell you honestly whether it is worth keeping than sell a rewrite you may not need. ### Durable, auditable workflows Processes that take days, call several systems and must never half-complete. Getting that right is a different discipline from getting a request handler right, and it is where we spend most of our time. ## Working with us from Arizona Arizona does not observe daylight saving, so we are two hours behind you from November to March and three hours behind from March to November. That leaves most of your afternoon overlapping our morning, which is usually enough. Most delivery is remote or hybrid. We travel for discovery, workshops and the opening weeks of a build.