The Firm
What Centralux is, where it operates, how an engagement is structured from first call to hand-off, and the stance on data that governs every decision inside it.
What the company is
Centralux is an AI-native services firm. It builds the software small and mid-sized operations run on — the system of record, the path from quote to cash, the interface for asking questions of it — and it builds that software with data integrity as the first constraint rather than the last one.
It is founder-led and engineering-first. There is no separate strategy layer that hands a deck to a delivery team, because the person who scopes the work is the person who builds it. That is a real limit on how many engagements run at once, and it is stated here rather than hidden: the firm takes on what it can finish.
Production systems built by the firm’s founder are live today for field-service, retail and e-commerce operators — running daily, handling real money and real customer records. Those engagements are not named here, because naming a client is the client’s decision, not a marketing asset to be taken.
The name is central plus lux, the Latin for light: light at the center. Not a metaphor about intelligence — a description of what the work does. Operational truth that was scattered across four systems and three people’s memory gets put in one place where it can be seen.
Where it operates
The firm works out of The Hub at 109 Hay St in downtown Fayetteville, North Carolina, and serves operators across the state and remotely beyond it. Being in Fayetteville is not incidental. The businesses this work is built for — contractors, field-service companies, independent retailers, small e-commerce operations — are the businesses that exist here, and the fastest way to understand how work moves through one is to sit in the office while it happens.
Engagements that need it start on site. Everything after that is remote and asynchronous by preference: written findings, milestone reviews, and a working system you can open yourself, rather than a standing weekly call that exists to prove work is happening.
Distance is not the constraint on whether an engagement fits. Access to the people doing the work is. A build scoped entirely from an executive’s description of the process will be a build for a process that does not exist.
How an engagement is structured
Three phases, each one priced and agreed before it starts. You can stop at the end of any of them and keep everything produced so far.
Phase 01 — Survey
A paid, fixed-fee engagement that maps how work actually moves through your business. Time with the people doing the job, three real cases traced end to end, and a read of your own numbers where they exist. It ends in a written finding: what the constraint is, what it is costing measured from your data, what to build, what not to build, and what it would cost to build it.
The finding is yours unconditionally. If you take it to another firm, or to your own developer, or decide to do nothing, that is a legitimate outcome and the Survey has done its job. A Survey that concludes you should not build anything is cheaper than the alternative, and it happens.
Phase 02 — Build
A scoped system delivered against the finding, quoted as a flat fee and broken into milestones you review and sign off individually. No hourly meter, so there is no incentive to take longer. Scope changes are re-quoted in writing rather than absorbed quietly and then discovered at the end.
Every milestone ships something you can open and use, not a status update. Cut-over is rehearsed on a copy of your data before it happens for real, and the old path stays running alongside the new one until the two agree.
Phase 03 — Custody
Optional monthly care once the system is live: monitoring, small changes, and a person who answers when something breaks. Month to month, cancellable, with no minimum term and no annual commitment. If it stops being worth it, you stop paying for it and the system keeps running — it lives in your accounts, not ours.
What we need from you
Access to the people who do the work, not only to the people who describe it. A named decision-maker who can approve a milestone without convening a committee. Read access to the systems in scope during the Survey, and least-privilege credentials during the Build — issued by you, held in your accounts, revocable by you at any moment.
When it is a bad fit
When the deliverable wanted is a document rather than a working system. When the real requirement is a headcount rather than software. When the timeline requires skipping the Survey and building from an assumption. When the data cannot be isolated to your tenancy. And when the goal is to say the word “AI” in a press release — that is achievable far more cheaply elsewhere.
The position on your data
Four commitments that are architectural, not contractual — meaning they are enforced by how the system is built, not only by a clause you would have to sue to enforce.
Why this is the differentiator. The AI services market is full of firms that will demo something impressive on a sample of your data and never explain where the data went. If you have been burned once, the second conversation is not about capability — it is about custody. This entry exists so that conversation can start from a written position instead of a reassurance.
How the work is actually done
- Trace real cases, not described processes. Three live jobs followed end to end will contradict the org chart, and the contradiction is where the money is.
- Measure the constraint from your own records before quoting a build. Industry benchmarks are for pitch decks; your data is for decisions.
- Ship in milestones you can open. A milestone that cannot be used is a status report wearing a milestone’s clothes.
- Rehearse the failure. Restores get run, cut-overs get practiced on a copy, and the rollback exists before the change does.
- Gate the irreversible. Anything that sends, charges, or writes into a system you don’t control asks first, and says which system it is writing to.
- Write it down for your team. Documentation aimed at the person who will run this after we’re gone, because that person is the point.