Built by operators, not account managers.
A deliberately small senior team applying enterprise-grade engineering to businesses that were never big enough to buy it.
Enterprise practice, small-business economics
Lucentia was founded by practitioners with enterprise technology backgrounds, including experience at IBM, combined with formal finance training at MBA level and international business qualifications. That mix matters more than it sounds: most AI projects fail on the business case rather than the technology, and we are equipped to argue both.
We have seen how large organisations specify, buy and deploy systems. What we build for a twelve-person business uses the same discipline, without the committee and the twelve-month timeline that made it unaffordable in the first place.
Four countries, one team
We operate across the USA, the UAE, India and Canada. In practice that means work continues across time zones, delivery costs stay sensible, and cross-border arrangements — a company registered in one country, operating from a second, serving clients in a third — are ordinary rather than an obstacle.
For clients it also means someone is usually awake when something breaks.
Small on purpose
We keep a small senior core and bring in vetted specialists per project rather than carrying a bench. You talk to the people making the decisions, every time. There is no account manager translating your problem into a brief for someone you never meet, and nothing gets quietly handed to a junior because the senior person moved to a bigger client.
It is also why we turn work down. If a project needs a team of fifteen, we are not the right firm and we will say so.
Four convictions
AI is not the point
The point is the booking you did not lose and the hour you got back. If a spreadsheet and a better phone greeting solve it, that is the honest recommendation.
An agent must know when to stop
Handing over cleanly to a human matters more than answering everything. A confident wrong answer costs you the customer and the trust behind them.
Shipped beats specified
Something working in two weeks teaches you more than a document describing something perfect in six months. We build in short cycles for that reason.
You should be able to leave
We document what we build and you own your domain, your data and your accounts. Retainers should continue because they are worth it, not because leaving is painful.
Plain language, always
If we cannot explain what a system does without jargon, we do not understand it well enough to charge you for it.
Say the uncomfortable thing early
Bad news travels badly when it travels late. If a date is slipping or an idea is wrong, you hear it that week.
Talk to the people who will build it
Twenty minutes with whoever would actually run your project. That is the whole point of a firm this size.