About

A practice, not an agency roster.

Centralux AI LLC is a founder-led AI engineering practice in Fayetteville, North Carolina. We build and hand over production systems for operators — and we are deliberately small, because the work we do badly at scale is exactly the work clients hire us for.

What Centralux is

Engineering-first, founder-led

  • A North Carolina limited liability company
  • The person who scopes the work is the person who builds it
  • Flat fees, full handover, no lock-in
  • A small number of engagements at a time, on purpose

Most firms selling AI to small and mid-sized businesses sell advice: an assessment, a roadmap, a vendor shortlist, and an invoice. The client is left holding a document and the same operational problem they started with.

Centralux sells the system. We scope a real operational problem, build the software that solves it, put it into production, and hand it to you with the code and the credentials. Strategy happens — it just happens as part of building the thing, not instead of it.

Founder-led means the person who scopes your engagement is the person who builds it. There is no account manager between you and the work, no junior team learning your business on your budget, and no handoff to a delivery pod after the sale. It also means we take on a small number of engagements at a time, and we will tell you when the next slot is rather than pretending capacity we don't have.

We have production systems live for field-service, retail and e-commerce operators. We don't publish client names or logos — the sort of operator we work with generally prefers their systems not be advertised, and a case study that has to be anonymized isn't proof of anything anyway. What we will do is walk you through architecture and approach in detail on a call.

How an engagement works

Scoped, priced, built, handed over.

Three phases, each quoted in writing and approved before it starts. You can stop after any of them with something useful in hand.

Phase one

Map

We sit with the people doing the work and trace a job from first call to money in the bank. Where does it wait? Where is it retyped? Where does the number change? You get a written map of the workflow, its failure points, and an estimate of what fixing each is worth. It is yours regardless of what happens next.

Phase two

Build

We build against the map in working increments, so your team is using real slices of the system while the rest is still being built. That is deliberate: it surfaces the places the map was wrong while changing them is still cheap. Isolation, provenance and access rules are part of the build from the first table.

Phase three

Hand over

Code, data, credentials, accounts and written documentation transfer to you. We train the people who will run it day to day. If you want us to keep maintaining it, that is a separate optional agreement — never a condition of the handover, and never a lever we hold.

Flat fees
Every phase is a fixed price agreed before work begins. Scope changes are quoted before they happen. No hourly meter running in the background.
You own it
The code, the data and the accounts are yours on final payment. Everything runs on infrastructure in your name, not ours.
No lock-in
No proprietary runtime you can only rent from us, no exit fee, and no hostage data. Another engineer can pick it up from the documentation.
The stance

Data integrity is the product.

Everything else we build sits on top of it. This is the part of the work a client can't easily inspect, which is exactly why we write it down and invite the inspection.

01

Your data stays isolated

Every engagement gets its own store, its own credentials and its own boundary. We do not run a shared multi-tenant platform where clients sit in the same tables behind a filter, because a filter is one bug away from a breach. Your records are never used to train a model, and never used to improve another client's system.

02

Automation is provenance-gated

When a system acts on your behalf, the record shows what acted, on what input, at what time, under whose authority. Actions that reach the outside world — money, customers, third-party systems — are gated behind an explicit approval until you decide otherwise. Silent automation is how trust gets spent without anyone noticing.

03

Answers carry their sources

Anything a system tells you should be traceable to the records it came from. We build interfaces that show their work by default, because a confident wrong answer and a confident right one are indistinguishable until you can check.

04

Credentials stay yours

Accounts are created in your name on your infrastructure wherever the platform allows it. We work with access you grant and can revoke in an afternoon. When an engagement ends, ending our access is a setting you change — not a favour you ask us for.

If you can't revoke us in an afternoon, we built it wrong.

Where we operate

Fayetteville, North Carolina

Office The Hub
109 Hay St Suite 202
Fayetteville, NC 28301
United States

Centralux AI LLC is a North Carolina limited liability company, based at The Hub, 109 Hay St Suite 202, Fayetteville, NC 28301. Being physically here matters for the work we do: the operations we build for are field businesses, and the useful version of discovery involves standing in the shop, riding along on a job, or sitting with the person who actually cuts the invoice.

We work on-site across the Sandhills and the wider Fayetteville–Raleigh corridor, and remotely with operators anywhere in the United States. Remote engagements start with a working session and stay on a regular call rhythm — we don't run silent multi-week stretches where the only signal is an invoice.

Our niche gravity is trades and field-service operations, and specifically the quote-to-cash path through them. That is not a hard boundary — the same problems appear in retail and e-commerce operations, and we build there too — but it is where the pattern library is deepest and where we can be most useful fastest.

What we don't do

Stated plainly, so nobody wastes a call

  • Marketing chatbots and website widgets with nothing operational behind them
  • Strategy decks, readiness assessments and vendor shortlists as a standalone deliverable
  • Content generation at volume, or anything whose value depends on nobody checking it
  • Reselling someone else's SaaS with a markup and calling it an implementation
  • Engagements where we hold the credentials and you rent access to your own system
What we do insist on

The conditions that make this work

  • Access to the people doing the work, not just the person buying the project
  • One decision-maker who can approve scope and grant system access
  • A real operational problem with a cost attached, defined before we build
  • Permission to say the honest thing when the answer is "don't build this"
Next step

The fastest way to judge us is to make us scope something.

Bring an operational problem you already know the cost of. Forty-five minutes, no cost, and a straight answer about whether it is worth building.

No cost, no obligation. If it isn't a fit, we'll say so on the call.