Questions people ask.
Luxin, an AI consulting firm, answers the questions people actually ask. The six from the homepage are here in full, plus the ones that come up next.
Getting started
Luxin publishes both, and keeps them short. Every entry on the case-studies page is stamped Live, Delivered, In progress, Proposed or First-party, and Proposed is never a result. The method is eight steps, from a first conversation to a handover, and takes five minutes to read.
The first step with Luxin is a 30-minute conversation about how the work actually happens today. There is no deck and no charge. If there is nothing worth building, we say so.
A Luxin pilot takes about one to two weeks. A larger build runs one to three months. Engagements are not open-ended.
Paper is a normal place for a Luxin build to start. One business we scoped writes hundreds of invoices by hand every year. The first thing we looked at was a photo of one of them.
Luxin works with businesses of roughly five to a hundred and fifty people, and the first build is usually one task. Start with one thing. A two-person office is a normal size for a pilot.
A Luxin system runs on a schedule, knows how your business works, and puts finished work in front of you without being asked. The AI is the engine. This is the car built around it.
Control and approval
A Luxin system never sends anything on its own. Every draft, invoice, and calendar entry waits for a person to read it and approve it. Nothing goes out without you.
Luxin systems get more accurate as you correct them. You see the work before it goes anywhere, so you correct it first. It is about 90% right at handover, and the corrections are the training.
A Luxin system drafts in your own voice, and a person still sends it. Your client reads a message you approved. Nothing goes out without you.
Luxin builds are scoped so the person doing that work keeps the judgement and loses the typing. They review instead of retype. They get the week back for the work only a person can do.
Your data
Luxin builds inside your own email, drive, and software, under your own logins. Your information stays in the accounts you already use. It runs on your accounts, not ours. Nothing moves to a Luxin server.
Luxin scopes access to the one job, so the system sees only what that task needs. A system that drafts invoices cannot read anything else.
Luxin already works inside a law firm that handles confidential client matters. Access is scoped to the task, the files stay in the firm’s own systems, every action is logged, and a person approves every output.
Luxin builds on commercial AI terms, under which your data is never used to train anyone’s models. It stays in your accounts, and the AI provider does not keep it to learn from.
Cost
A Luxin pilot is $500 to $1,500, fixed. That is one payment for one task, built and handed over in about one to two weeks. It pays for itself before it costs you. There is nothing to cancel afterwards.
No subscription is required to work with Luxin. The default is a one-time fixed fee. The monthly budget exists for businesses that want it all built by a date, and it cancels with 14 days’ notice.
A Luxin system costs about $100 to $300 a month to run, paid to the software vendors directly from your own accounts, at cost. A rule of thumb is $50 a month for every $1,000 of system. We do not mark it up.
A Luxin pilot is a few hundred to a few thousand dollars once, and the system runs at about $100 to $300 a month. A hire costs a salary every year. Hiring is a fine answer when the work needs judgement, and this is for the work that does not.
After the build
You own everything Luxin builds for you. The accounts are yours, the code is yours, and the written instructions are yours. We show you how to change them.
Luxin hands over a plain-English runbook and teaches you how to edit it. The systems keep running, because they live in your accounts and not ours. The goal is that you do not need us for small changes.
At Luxin the person who scopes your build is the person who builds it, and everything runs on your own accounts with a written runbook. Engineers come in per project, so the work is staffed to fit rather than sold to fill a payroll.
Tell me what’s eating the most time.
Thirty minutes, no deck. You describe how the work actually happens, and I tell you plainly whether there is something worth building.