The work that has to happen, and the systems that hold it.
These are the operational systems Lucent builds, laid out in the order the work actually happens. It is a map of the work, not a menu, a price list, or a shelf of finished product. Which of them your business needs is settled in a conversation, not guessed from a page.
Nothing here is bought off a shelf.
Every system on this page is designed around how one business already works, and a build starts from your constraint rather than from this list. The names are stable because the operational responsibilities are stable. What they do inside your operation is not.
This is the work Lucent builds, not a diagnosis.
Naming the system your business should build first is diagnostic work. When the starting point is unclear, or you want the broader operational roadmap, that is the job of the Operational Systems Audit: paid work with a deliverable you keep. This page will not guess at it, and there is no quiz here that pretends to.
Not everything should be automated.
Every system below names the limits it is built with, and the judgment it hands back to a person. Those lines are on the page because they are the part that matters, not the part to skip.
Where most operations begin.
A first build takes one bounded problem and closes it. These are the systems businesses most often start with, because each one is contained, and each one earns the next.
Inbound Inquiry Desk
Every inquiry becomes a record with a first reply and a clear next step, on whatever channel it arrived on, at whatever hour it arrived, including the calls nobody picked up.
See the systemAppointment Booking and Confirmation
The calendar stops being a phone job: open times are offered, the yes is captured, reminders arrive before the date, and a change of plans is rebooked while the time can still be filled.
See the systemNew Client Intake
The forms, files, and details you require before a job can begin are requested at the start, checked off as they arrive, and chased while the client is still responsive, and the team receives one complete record to start from.
See the systemWork Assignment and Dispatch
Open work is matched to the right person or crew by your rules, sent with the address, the history, and the documents already attached, and a reschedule cascades to everyone it touches instead of to nobody.
See the systemOpen Opportunity Follow-Through
Quotes, proposals, and estimates that went quiet are followed to an answer: a fixed number of contacts, spaced the way you signed off, ending the instant a reply arrives.
See the systemFind the part of the week that is breaking.
Grouped by where the work sits, from the moment someone reaches out to knowing what is actually happening. Filter it down, or search for the problem in your own words.
Showing all 26 systems.
Arrival and First Response
Someone reaches out. What happens in the next few minutes, on whatever channel they used, at whatever hour they used it.
Inbound Inquiry Desk
Every inquiry becomes a record with a first reply and a clear next step, on whatever channel it arrived on, at whatever hour it arrived, including the calls nobody picked up.
See the systemCommon Question Handling
The questions with a settled answer get that answer, drawn from wording and documents you approved, and everything else is handed to a person with the context attached.
See the system
Sorting and Routing
What arrives gets read for what it actually is, given an owner, and put in front of the right person with the answers already attached.
Inquiry Qualification and Triage
New requests stop depending on who catches them: each one is taken through your screening questions, labeled by what it is and how soon it needs an answer, and handed to the owner it belongs to, answers included.
See the systemShared Inbox Triage
The mailbox everybody watches and nobody owns becomes tracked work with owners: read for what each item is, routed to a person, and answered only where the answer is already settled.
See the system
Booking and the Calendar
Getting the time agreed, confirmed, prepared, and put back to work when it falls through.
Appointment Booking and Confirmation
The calendar stops being a phone job: open times are offered, the yes is captured, reminders arrive before the date, and a change of plans is rebooked while the time can still be filled.
See the systemVisit Coordination and Preparation
The consultation, site visit, estimate, or appointment is booked with the right person, in the right window, and whoever attends arrives with the history, the access notes, and the paperwork already in hand.
See the systemCancellation and Waitlist Recovery
A cancellation stops being a hole in the day: the freed time is offered to the people already waiting for it, in the order you decide, while filling it is still possible.
See the system
Intake and Start
Turning a yes into a started job: what you always ask for, collected and checked, then handed to the people who do the work.
New Client Intake
The forms, files, and details you require before a job can begin are requested at the start, checked off as they arrive, and chased while the client is still responsive, and the team receives one complete record to start from.
See the systemKickoff and Handoff to Delivery
Won work becomes started work: the record is built, the brief is assembled from what was already collected, the first tasks are set, and the people doing the job are told it is now theirs.
See the system
Delivery and Coordination
Who is doing what, where it stands, what has stopped moving, and what goes wrong on the way.
Work Assignment and Dispatch
Open work is matched to the right person or crew by your rules, sent with the address, the history, and the documents already attached, and a reschedule cascades to everyone it touches instead of to nobody.
See the systemJob Status Communication
When the work moves, the people waiting on it are told and the next step is set, because the status changed, not because someone remembered.
See the systemCheckpoint and Closeout Control
Work cannot advance past a stage, or be closed, until the things that stage requires are actually attached to the record - and closing it fires the invoice, the filing, and the next obligation.
See the systemStalled Work and Exception Watch
Anything that has stopped moving, missed its trigger, or fallen outside the normal path is surfaced to the person who can act on it, with the reason it stopped and who it is waiting on.
See the systemEscalation and Service Recovery
A complaint, a missed commitment, or a job going wrong is recognized as one on arrival, put on the record, and put in front of a named person on a clock, with everything about the job attached.
See the system
Open Work and Return
Work you already earned that has gone quiet, and work the record says is due to come round again.
Open Opportunity Follow-Through
Quotes, proposals, and estimates that went quiet are followed to an answer: a fixed number of contacts, spaced the way you signed off, ending the instant a reply arrives.
See the systemRecurring Work and Renewal Coordination
Work the record says is due again - a service interval, a recheck, a renewal date - surfaces before it lapses, gets contacted on wording you approved, and gets itself back on the calendar.
See the systemReferral and Review Requests
After a completion your team confirms, the ask goes out once in your own words, and whatever comes back - an introduction or an unhappy sentence - is recorded, attributed, and put in front of the right person.
See the system
Money and the Back Office
The admin tail behind the work: the invoice, the quote, the paperwork, and the records that have to agree with each other.
Invoice and Payment Follow-Through
Completed work triggers the invoice, and the ones nobody has answered get a schedule of reminders you approved, stopping the moment they are settled or questioned.
See the systemQuote and Estimate Preparation Support
Everything the person writing a quote has to go and find - the notes, the measurements, the prior jobs, the supplier lines, the standard wording - is assembled and put in front of them before they start.
See the systemDocument Intake and Filing
Documents that arrive by any route are recognized for what they are, named, filed against the right record, and the ones you are still waiting on are surfaced.
See the systemRecord Upkeep and Reconciliation
The record is updated as the work happens rather than at the end of the week, and where two tools disagree the mismatch is surfaced instead of quietly persisting.
See the system
The Team
Hiring, starting, and the requests your own people make of the office.
Candidate Intake and Interview Coordination
Applications become records with the same questions asked of everyone, every applicant gets an answer, and interviews get booked against the real calendars of the people who have to be in them.
See the systemNew Hire Onboarding
A start date triggers the paperwork, the account requests, the equipment, the induction schedule, and the follow-through on whatever is still outstanding in week one.
See the systemInternal Service Desk
The requests your own team makes of the office - approvals, spend, access, time off, and the question that is already answered in the handbook - are logged, answered from approved material, routed to whoever decides, and tracked until closed.
See the system
Oversight
Knowing what is actually happening without asking three people and adding it up yourself.
Operating Brief
The state of the operation, assembled on the cadence you set: what is open, what is booked, what is stuck, what closed, and what is still owed by whom - without anyone being asked for an update.
See the systemCross-System Operations View
One view over every running system - the open work, the schedule, the pipeline, and the exceptions - on one record, under one governance model.
See the system
The catalog is a starting point, not a boundary.
These are the systems businesses most commonly need, which is not the same as everything Lucent can design. Adjacent and custom work is normal.
Built per engagement, not from a shelf
These are built per engagement, not deployed from a shelf. What Lucent runs internally is its own operating system, not a copy of yours.
What makes something buildable
Whether a piece of work can be systematised comes down to a few honest things: whether the process is clear enough to describe, whether the data and the systems can actually be reached, what happens when it gets something wrong, and who is accountable when it does. Those are assessment questions, not sales questions.
Some work should stay with people
Judgment about a person, a diagnosis, a price, a piece of professional advice, a decision that carries real consequence: these stay human, and Lucent will say so rather than sell around it. Every system on this page names where it stops.
The next step is a conversation, not a demo
A conversation establishes fit and diagnostic sufficiency. A bounded problem this page already covers can be quoted directly. When the problem is clear but the right system is not, structured questioning settles it, and Lucent's recommendation is the diagnosis. Work that cannot be priced confidently starts with paid Scoping Discovery, and the Operational Systems Audit remains the standalone diagnostic for the broader operational roadmap. A demo is not the entry point, because these systems are built into an operation, not toured.
Bring the work that is not on this pageKnowing which one you need is the hard part.
Browsing a catalog tells you what is possible. It does not tell you what is costing you the most right now. That starts with a conversation, and when you want the full roadmap, the audit produces the plan the first system gets built from.