Small on purpose. Engineering-first by conviction.
Centralux is an AI-native engineering practice registered in North Carolina and run from Fayetteville. We build production systems for businesses whose operations are physical — crews, trucks, jobs, materials — and whose software has never quite kept up with them.
An engineering practice that happens to use AI, not an AI company looking for a use case.
There are two kinds of firm selling AI to operating businesses right now. One sells strategy: a workshop, a maturity assessment, a deck with a roadmap, and an invoice. The other sells seats in somebody else’s product with a service wrapper around it.
We do neither. Centralux builds and ships operational software, using AI where it earns its place — reading documents, extracting structure from messy input, answering questions of data, drafting outward communication for a human to release — and using ordinary, boring, verifiable engineering everywhere else. Most of the value in these systems comes from the boring part.
Founder-led means the person who scopes the work is the person who builds it. There is no account manager between you and the system, no junior team learning your business on your budget, and no handoff where the context quietly evaporates. When a specialist is needed, they are named and scoped in the proposal.
The reason to stay small is not romance about craft. It is that the failure mode we design against — a system confidently producing a wrong number nobody can trace — is exactly the failure mode that scales fastest when nobody in the room fully understands the build.
Written before built. Verified before trusted.
The survey comes before the software
We follow a real job from the first phone call to the deposited payment and write down every place it changes hands, every place a number is re-typed, and every place the process only works because a specific person remembers something. That document is the design input, and you keep it whether or not you hire us for the build.
Prototypes are reviewed against real jobs
Demo data hides every interesting problem. We prototype against your actual records — the job with the three change orders, the customer who pays in two installments, the week half the crew was out — because those are the cases that decide whether a system survives contact with your operation.
One client’s system never touches another’s
Separate tenants, separate credentials, separate storage. We do not build a shared platform and sell you a compartment of it, and we do not use one client’s data, documents or workflows to improve another client’s system.
Automation earns its autonomy
New automations run proposing, not doing. A human reviews the output on real work until the behaviour is boring, and only then does the gate move. Anything that reaches a customer keeps its gate permanently.
We leave the lights on
Every build ships with a runbook written for your team: how it works, what breaks, what to do when it does, and how to get your data out. A system only you can operate is a system we have failed to finish.
Fayetteville, North Carolina — and on site when it matters.
109 Hay St Suite 202
Fayetteville, NC 28301
Downtown Fayetteville is a working town of contractors, service companies, retailers and military-adjacent businesses — which is to say, exactly the operations this practice is built for. Being local is not a marketing line here; it is how the survey phase gets done properly.
For field-service work in particular, the first phase benefits enormously from being physically present. We would rather see the whiteboard, ride along on a job, and watch a ticket get filled out in a truck than receive a description of all three in a meeting. Everything after the survey — build, review, cutover, support — runs fine remotely, which is why work outside the region is welcome.
There is no phone line published on this site by design. Booking a time gets you a real conversation faster than a switchboard would, and email reaches the person doing the work rather than an inbox someone triages.
The part of this practice that is not up for negotiation.
You are being asked to put your customer list, your pricing, your margins and your payroll-adjacent records into a system built by someone else. That is a serious ask. These are the commitments that make it a reasonable one.
Your tenant is yours alone
Provisioned for your business, with your own database, storage and credentials. No shared tables partitioned by a customer ID, no pooled search index, no cross-client fallbacks in code. Multi-tenant architectures are cheaper to operate and harder to reason about; we take the other trade deliberately.
Your data does not train models
We do not use your records, documents or conversations to train or fine-tune anything — not for us, not for another client, not for a vendor. Where a third-party model provider is used to process a request, it is chosen and configured for non-retention, and named in your documentation.
Every written value has a source
When an automation writes a number, it records where the number came from. When it cannot determine a value, it writes nothing and flags it — because a missing value you can see is recoverable, and a fabricated zero you cannot see is not.
History is append-only
Corrections are new entries with a reason attached. Nothing overwrites its own past. This is what makes a disputed invoice a lookup instead of an argument, months after everyone has forgotten the job.
You can leave
Exports in open formats, on request, without an offboarding negotiation or a fee. Credentials are yours, transferred at handoff. The strongest reason to keep working with us should be that the work is good.
Three phases. Flat fees. Every phase a real stopping point.
You should never be buying the next phase in order to make the last one worth something. Each phase produces a deliverable that stands alone, and each one is priced before it starts.
Understand the operation
We map how the work actually flows, on site where possible, and identify where value is leaking. Fixed fee, agreed in advance.
- Written system survey
- Current-state and target-state diagrams
- Prioritized list of failure points
- A scoped, fixed-price build proposal
- Yours to keep if you stop here
Ship the system
The build runs in your own tenant against your own data, reviewed at agreed checkpoints. Fixed fee for the scope in the proposal; changes are re-priced in writing before they happen.
- Single-tenant provisioning
- Data migration with a reconciliation report
- Checkpoint reviews against real jobs
- Parallel run, then cutover with rollback
- Runbook and team walkthrough
Keep it healthy, or hand it over
Optional monthly retainer, or a clean handoff with documentation and credentials. Cancel with notice; nothing is held hostage either way.
- Monitoring and alerting
- Change requests and small builds
- Quarterly integrity review
- Exports in open formats on request
Flat fee per phase, never hourly billing on a build. No revenue share — it prices our work off your execution risk rather than our own. No seat licences layered on top of a system you already paid to have built. Pricing depends on scope and is quoted after the survey, or after a discovery call for smaller pieces of work.
Who this works for — and who it doesn’t.
You will probably get value here
- An operating business with crews, jobs, customers and materials — not a pre-revenue idea
- The owner or a decision-maker is in the room and can commit
- Real operational pain: quotes that go stale, work that never gets invoiced, a schedule only one person understands
- Willing to let someone watch how the work is actually done, including the ugly parts
- Wants to own the system rather than rent it forever
You will be better served elsewhere
- Looking for the cheapest possible implementation of a tool you have already chosen
- Wanting AI in the business because it should be there, with no specific process in pain
- Needing a deck for a board rather than a system for a crew
- Unable to give access to the real data the system will have to run on
- Expecting an unattended agent to email customers and move money with no human gate
Central + lux.
Lux is Latin for light. Centralux is light at the centre — the point a scattered operation converges on and becomes legible. The mark says the same thing in geometry: an open C holding a single diamond at its centre.
The practical version of that idea is unglamorous. When every number in your business has one home and one traceable source, you can finally see the operation clearly enough to make decisions about it. Everything on the previous six sheets is in service of that.
Start with the survey conversation.
The discovery call is free and useful on its own. If we are not the right people for what you need, you will hear that on the call rather than in a proposal three weeks later.