The names of your tools
What you currently use for estimating, scheduling, field work, invoicing and accounting — even if the honest answer for some of them is a spreadsheet or a group chat.
Start with the problem, not the pitch.
Two ways in: book a discovery call directly on the calendar, or send an email and describe what's breaking. Both reach the person who would do the work.
Business details
Centralux AI LLC
- contact@centralux.ai
- Booking
- book.centralux.ai
- Office
- 109 Hay St Suite 202
Fayetteville, NC 28301
United States - Elsewhere
-
LinkedIn — /company/centraluxai
X — @centraluxai
Email is the fastest route and is answered within one business day. Correspondence and any documents you send are handled under the confidentiality posture described in our terms; what the site itself collects is set out in the privacy policy.
The discovery call
What actually happens in those forty-five minutes
It is a working conversation. We spend the time on how your operation really runs, and you leave with an opinion you can act on whether or not you hire us.
- First ten minutes — the problem in your words: what breaks, how often, and what it costs when it does
- Next twenty — the path a job takes through your business right now, tool by tool and handoff by handoff
- Next ten — a candid read: whether software fixes this, and what a first phase would need to cover
- Last five — the practical part: rough shape of scope, and what a written proposal would include
- Afterwards — a short written summary of what we heard and what we'd propose. No pressure sequence, no follow-up campaign
Before you book
Bring one concrete thing.
The calls that produce something useful are the ones with a specific problem in them. You do not need documentation, a budget or a plan — you need one process you can describe.
A number, roughly
Jobs per month, average ticket, how many people touch a job. Approximate is fine. It changes what is worth building far more than any feature preference does.
The one that annoys you most
The recurring task everybody complains about. It is usually where the leak is, and it is a better starting point than a list of capabilities you have read about.
Come with the mess. Polishing it first just hides the useful part.
Common questions
Asked before most first calls.
Is the call a sales pitch?
No. It is scoping. If the honest answer is that your problem doesn't need custom software — or needs a bookkeeper before it needs an engineer — that is what you'll hear, and there is no cost either way.
Do you work with businesses outside North Carolina?
Yes. On-site work concentrates around Fayetteville and the Sandhills; remote engagements run anywhere in the United States on a regular call rhythm.
Do we have to replace our current software?
Usually not all of it. Part of the mapping phase is deciding which tools stay, which get integrated, and which are genuinely costing more than they return.
Who owns what gets built?
You do — code, data and accounts, on final payment for the phase. Ongoing support exists and is optional. Details are in the terms, and every engagement is governed by its own written agreement.
What happens to our data during the work?
It stays in a store isolated to your engagement, under credentials you can revoke. It is never pooled with another client's records and never used to train a model. The full stance is on the about page.
How soon can something start?
We run a small number of engagements at a time, so availability moves. The call is the fastest way to get a real answer on timing rather than an optimistic one.
Pick a time, or just write and describe the mess.
Both land in the same place. The calendar is live — the times on it are real availability, not a queue.
No cost, no obligation. If it isn't a fit, we'll say so on the call.