A new idea you want to get moving, a build that has slipped two quarters, an AI review that has gone quiet, a model nobody will sign off on, a CV. Six short fields, one business day, and a reply from the person who would actually do the work.
They all reach the same people. The difference is how much you have to write before anybody reads it.
You know roughly what you need and want it on the record. Six short fields, and nothing you have to look up first.
Fill it in →No brief yet. We listen, share where we have done the same thing before, and name the first step. No commitment, no deck.
Open the calendar →A single question, a document to send, an NDA to review, or a photo you would rather we took down. Straight to the inbox.
connect@focaloid.com →Six short fields, all required. Your location helps us reply inside your working hours.
Enquiries are read by the team that would deliver the work - not scored, not routed by a model.
The first response names the person and their role. If it is not the right team, we say so and hand you over rather than keeping you warm.
Your goals, where we have done something comparable, and the honest next step. If that step is not us, we will tell you that too.
Scope, assumptions and what it would take - in writing, so somebody who was not on the call can read it.
One business day is the promise. Where we are going to miss it, you get a holding note with a date - not silence.
What we will not do
Add you to a mailing list, pass your details to a partner, or send a five-email nurture sequence. There is no scoring model behind this form.
Visit, or ring the one whose clock is awake.
Also serving the United Kingdom, Europe and Singapore from these three offices. ISO/IEC 27001:2022 certified - verify on Certipedia →
Including two where the answer is a flat no.
No - it is the most useful one. A fair share of discovery calls end with a recommendation that has no model in it, because the problem turned out to be a data pipeline, a process, or a piece of software that already exists.
Often, yes - it is a large share of what we are asked to do. We will want to read the code and the delivery history before we commit to anything, and we will tell you plainly if the honest recommendation is to rebuild rather than continue.
It reaches our own systems and is handled under our privacy policy and the ISO/IEC 27001:2022 controls covering the rest of the business. No scoring model runs behind it, and nothing you send is added to a mailing list.
Whichever one your team is in. Delivery runs from Kochi and Bengaluru with leadership in New York, and engagements in the US, UK, Europe and Singapore each have a working overlap agreed before the first sprint - not left to chance.
In your cloud and your accounts, under your regional constraints, unless you ask us to host it. Data residency, model hosting and what may leave your environment are settled in writing during discovery, before anything is built.
No. For your own systems the evidence pack, register entry and gate history are deliverables you own and can show to anyone you like. For another client's systems, no - which is the same answer you would want us giving about yours.